Re: Proposal to deploy GitLab on gnome.org

On Fri, May 19, 2017 at 9:55 PM Shaun McCance wrote: > I don't disagree with anything you're saying. As long as there's an > easy way to get a list of issues with a specific label across all > projects (and projects in different groups?), then we'll figure it out. > And if

Re: Proposal to deploy GitLab on gnome.org

On Thu, 2017-05-18 at 18:08 +0200, Andre Klapper wrote: > On Tue, 2017-05-16 at 10:51 -0400, Shaun McCance wrote: > > > > That said, here's a potential pain point: in Bugzilla, you can have > > different components auto-assign to different accounts, and we made > > these @gnome.bugs fake accounts

Re: Proposal to deploy GitLab on gnome.org

On Thu, May 18, 2017 at 11:36 AM, Andre Klapper wrote: The Traceparser is another (basically) unmaintained custom extension we have in our Bugzilla, with some confusing bugs (e.g. bug 744491). I think we should remove this extension immediately. It provides limited value,

Re: Proposal to deploy GitLab on gnome.org

Hi, One thing we missed from the translators requirements is the workflow for tracking issues. At the moment, there's a "l10n" product [1] at Bugzilla where users report bugs choosing a language from "Components" list. My question here is, how things are going to work with Gitlab now that all

Re: Relicensing Nautilus to GPLv3+

Hey A. Walton, Relicensing from gpl2+ (supposed current nautilus) to lgpl2+ (current gtk+) requires agreement of all copyright holders, and the software license is free software one. Relicensing from gpl3+ requires ecxactly the same process, and both are still free software licenses. Do you