Re: Infrastructure | Gitlab reorganisation (#333)
Allan Day commented on a discussion: https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/333#note_1215823 It's still all to be done, really. I think it's stuck somewhere between the release team, the circle committee, and the board. @felipeborges tried to get things going again not so long ago - https://discourse.gnome.org/t/rfc-defining-a-policy-for-whats-a-gnome-project/5922 -- Reply to this email directly or view it on GitLab: https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/333#note_1215823 You're receiving this email because of your account on gitlab.gnome.org. ___ gnome-infrastructure mailing list gnome-infrastructure@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-infrastructure
Re: Infrastructure | Gitlab reorganisation (#333)
Andrea Veri commented: @aday anything still pending here or this can be closed? -- Reply to this email directly or view it on GitLab: https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/333#note_1215769 You're receiving this email because of your account on gitlab.gnome.org. ___ gnome-infrastructure mailing list gnome-infrastructure@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-infrastructure
Re: Infrastructure | Gitlab reorganisation (#333)
Andrea Veri commented: Me, @aday and @csoriano met. Next steps at https://etherpad.gnome.org/p/circle_admin. -- Reply to this email directly or view it on GitLab: https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/333#note_846442 You're receiving this email because of your account on gitlab.gnome.org. ___ gnome-infrastructure mailing list gnome-infrastructure@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-infrastructure
Re: Infrastructure | Gitlab reorganisation (#333)
Andrea Veri commented: @aday, can we please schedule a meeting and go over this? got any preferred date/time? -- Reply to this email directly or view it on GitLab: https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/333#note_841844 You're receiving this email because of your account on gitlab.gnome.org. ___ gnome-infrastructure mailing list gnome-infrastructure@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-infrastructure
Re: Infrastructure | Gitlab reorganisation (#333)
Neil McGovern commented: Let's ping the sysadmins here explicitly: cc: @averi @barthalion -- Reply to this email directly or view it on GitLab: https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/333#note_841118 You're receiving this email because of your account on gitlab.gnome.org. ___ gnome-infrastructure mailing list gnome-infrastructure@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-infrastructure
Re: Infrastructure | Gitlab reorganisation (#333)
Allan Day commented on a discussion: https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/333#note_841114 We can certainly run any changes past the release team, in order to avoid any back and forth. -- Reply to this email directly or view it on GitLab: https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/333#note_841114 You're receiving this email because of your account on gitlab.gnome.org. ___ gnome-infrastructure mailing list gnome-infrastructure@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-infrastructure
Re: Infrastructure | Gitlab reorganisation (#333)
Michael Catanzaro commented: Sorry, I guess we only need to worry about additions to core. The goal of figuring out core app changes before the reorg would be to avoid moving apps out of GNOME/ and then right back into GNOME/ shortly after. That only affects proposed additions, not proposed removals. -- Reply to this email directly or view it on GitLab: https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/333#note_840167 You're receiving this email because of your account on gitlab.gnome.org. ___ gnome-infrastructure mailing list gnome-infrastructure@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-infrastructure
Re: Infrastructure | Gitlab reorganisation (#333)
Michael Catanzaro commented: Let's make an attempt to resolve at least some of the issues in https://gitlab.gnome.org/GNOME/gnome-build-meta/-/issues/150 before proceeding with this. Currently that's blocked on https://pagure.io/fedora-workstation/issue/125 to make sure upstream changes are also suitable for downstream. -- Reply to this email directly or view it on GitLab: https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/333#note_840164 You're receiving this email because of your account on gitlab.gnome.org. ___ gnome-infrastructure mailing list gnome-infrastructure@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-infrastructure
Infrastructure | Gitlab reorganisation (#333)
Allan Day created an issue: https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/333 The Foundation Board of Directors [is proposing a new policy for how GNOME classifies its software](https://discourse.gnome.org/t/official-proposal-how-we-define-gnome-software/3371/). This proposal has some implications for how projects are organised in our Gitlab instance. With the new plan, [the GNOME group](https://gitlab.gnome.org/GNOME) will just include modules from the core modulesets [1]. Those modules which don't qualify to be included in the GNOME group will be moved elsewhere. The goals with regards to Gitlab are to make it clearer which projects are core, and to ensure that the additional permissions and requirements which are associated with the GNOME group are only applied to those modules that really need them. The current plan is to perform the reorganisation incrementally, as a series of batches. At each stage the sysadmins will be provided with the details on which modules are to be moved where. Before the board votes on the proposal, it would be good to hear whether the sysadmins think that this is practical and/or desirable. [1] - [meta-gnome-core-developer-tools](https://gitlab.gnome.org/GNOME/gnome-build-meta/-/blob/master/elements/core/meta-gnome-core-developer-tools.bst) - [meta-gnome-core-os-services](https://gitlab.gnome.org/GNOME/gnome-build-meta/-/blob/master/elements/core/meta-gnome-core-os-services.bst) - [meta-gnome-core-shell](https://gitlab.gnome.org/GNOME/gnome-build-meta/-/blob/master/elements/core/meta-gnome-core-shell.bst) - [meta-gnome-core-utilities](https://gitlab.gnome.org/GNOME/gnome-build-meta/-/blob/master/elements/core/meta-gnome-core-utilities.bst) -- Reply to this email directly or view it on GitLab: https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/333 You're receiving this email because of your account on gitlab.gnome.org. ___ gnome-infrastructure mailing list gnome-infrastructure@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-infrastructure
