Hi all, Gitlab migration with it's proper support for CI/CD and merge requests can not come fast enough, I'm very excited that the move is planned. I've been using home-hosted gitlab instance for a while now and it's useful even for a single developer operation, it will be a lot more beneficial for a big project like KiCad.
In terms of issues migration I think moving open issues via script and locking down launchpad tracker is the best option. Even if migrated issues and comments on them will be owned by some service account/bot. It should be doable to include enough information there so that it's clear who originally posted it and the context is not lost. Regards, Andrew On Wed, Oct 9, 2019 at 4:36 PM Wayne Stambaugh <stambau...@gmail.com> wrote: > On 10/9/19 3:32 PM, Mark Roszko wrote: > >> I've applied for an open source GitLab license. Assuming we get > > accepted, > > > > Technically not required for now. The license just unlocks extra > > features but the base free feature set is more than adequate for now. > > I prefer some of the extra permission features that the license gives us > over the free version. I suspect we will be approved long before 5.1.5 > is released. > > > > > > >>Would it be possible to migrate open bug reports to GitLab? I suspect > >>we could come up with a script like we did when we migrated from > >>SourceForge. > > > > Basically, yes and no. You can copy the content of issues over no > > problem. You cannot copy over the authors of comments and posts. It'll > > have to done under some fake/throwaway user account for migration as > > it'll become owner of them all. > > If it's too problematic, I'm fine with leaving existing bug reports in > Launchpad. Not sure what to do with the open reports other than let > them expire. > > > > > > >>What to do about the mailing list? GitLab doesn't support mailing lists > >>yet so I'm thinking we leave the mailing list on Launchpad for the short > >>term. We can always migrate the mailing list at a later date or use > >>some other communication tool such as discourse. > > > > Someone was adding mailing list functionality to GitLab a few months ago > > but the PRs been sitting for a few months. > > Yes, either a forum or google groups would be an alternative. > > > > A forum can be inviting to the most inexperienced users. But because I > > that I would say an absolute minimum is there must some level of > > segregation to prevent developers being flooded with tech support. > > That is one of the shortcomings of using a forum. However, with > adequate moderation (i.e. no support for non-development issues), it > does provide a richer communication environment than a mailing list. I > don't have a strong preference one way or the other. I was just > throwing it out there as an alternative. > > > > > > > On Wed, Oct 9, 2019 at 12:36 PM Wayne Stambaugh <stambau...@gmail.com > > <mailto:stambau...@gmail.com>> wrote: > > > > The lead development team has been discussing migrating the KiCad > > project to GitLab[1]. Given the issues with Launchpad, I think this > is > > a good move. I've applied for an open source GitLab license. > Assuming > > we get accepted, I would like to start this process after the 5.1.5 > > release. Here is a short list of action items that need to be done > for > > the source repo transition: > > > > * Freeze the Launchpad source repo. > > * Push the frozen repo to GitLab. > > * Disable the Launcpad bug tracker. > > * Add a note and link to the Launcpad project page that the project > is > > now hosted on GitLab. > > * Create blog announcement once the transition is complete. > > > > There are a few unknowns: > > > > Would it be possible to migrate open bug reports to GitLab? I > suspect > > we could come up with a script like we did when we migrated from > > SourceForge. > > > > What to do about the mailing list? GitLab doesn't support mailing > lists > > yet so I'm thinking we leave the mailing list on Launchpad for the > short > > term. We can always migrate the mailing list at a later date or use > > some other communication tool such as discourse. > > > > Further down the road, I would like to see all of the KiCad source > repos > > including the library, documentation, website, and translation repos > > migrated to GitLab as well. It would make my life a lot easier from > a > > project management perspective if they were all in the same place. I > > expect there to be some resistance to using a source code version > tool > > but I'm hoping folks will see this as a beneficial move. I'm not > > terribly familiar with GitLab but I suspect it's not that much > different > > than GitHub as a hosting platform so I don't expect there to be a > very > > steep learning curve. If you have any concerns, now is the time to > > speak up or forever hold your peace. > > > > Cheers, > > > > Wayne > > > > [1]: https://gitlab.com/ > > > > _______________________________________________ > > Mailing list: https://launchpad.net/~kicad-developers > > Post to : kicad-developers@lists.launchpad.net > > <mailto:kicad-developers@lists.launchpad.net> > > Unsubscribe : https://launchpad.net/~kicad-developers > > More help : https://help.launchpad.net/ListHelp > > > > > > > > -- > > Mark > > _______________________________________________ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp >
_______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
