Re: [openstack-dev] Migrating existing projects in the stackforge namespace - question about Fuel Plugins
Excerpts from Irina Povolotskaya's message of 2015-08-24 15:09:23 +0300: > Hi to everyone, > > I've seen a message from Jim on migrating in the stackforge namespace. > > I have a question about Fuel Plugins: > >- Fuel is not the part of upstream; neither are Fuel Plugins (and each >of them has a separate project under Stackforge). >- Nevertheless, the number of Fuel Plugins grows and developers will >keep on requesting stackforge project creation. > > > Question: > I would like to know how you plan to work with these issues in this very > case. > Do you plan to mark those somehow just to show that they are actually > maintainted and not the part of upstream yet? > Do you need any extra confirmation from development teams that their > plugins are being constantly updated and worked on? Who is "you" in this case? The Fuel team, the TC, or the community in general? In case you mean the TC: Jim's proposal is to rename the gerrit repositories under stackforge/ so they are under openstack/. That does not change their official status, just the name of the repository. Projects must explicitly ask to become official by submitting a patch to add themselves to reference/projects.yaml in the openstack/governance repository. Doug __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] Migrating existing projects in the stackforge namespace - question about Fuel Plugins
Hi to everyone, I've seen a message from Jim on migrating in the stackforge namespace. I have a question about Fuel Plugins: - Fuel is not the part of upstream; neither are Fuel Plugins (and each of them has a separate project under Stackforge). - Nevertheless, the number of Fuel Plugins grows and developers will keep on requesting stackforge project creation. Question: I would like to know how you plan to work with these issues in this very case. Do you plan to mark those somehow just to show that they are actually maintainted and not the part of upstream yet? Do you need any extra confirmation from development teams that their plugins are being constantly updated and worked on? Thanks. -- Best regards, Irina *Business Analyst* __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Migrating existing projects in the stackforge namespace
On 14 August 2015 at 22:01, James E. Blair wrote: > > Please reply with any feedback or suggested improvements to this plan. > If we can achieve consensus on the approach, we will make further > announcements as to specifics soon. > This looks like a well considered an appropriate plan to me. +1 Jesse IRC: odyssey4me __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] Migrating existing projects in the stackforge namespace
Hi, As mentioned previously[1], we are retiring the stackforge/ namespace for git repositories and creating new projects in openstack/. This is largely a cosmetic change and does not change the governance model for new projects. As part of this we want to move all of the projects that are currently in the stackforge/ namespace into openstack/ to make it easier for them to become official OpenStack projects in the future while reducing the impact to the community that the current practice of sporadic renaming causes. To that end, I propose the following process: 1) We choose a date upon which to perform a mass migration of all stackforge/ projects into openstack/. I suggest either October 17 or November 7 (both Saturdays), as least likely to interfere with the release or summit. 2) We create a wiki page for all such projects to either sign up for that migration or indicate that they are no longer maintained. 3) Any stackforge projects that do not sign up for the migration within a certain time are placed on the list of projects that are no longer maintained. 4) We attempt to contact, by way of posts to the openstack-dev mailing list, announcements at the cross project meeting, and direct emails to the individuals who initially requested repository creation, people who might be responsible for projects which have not responded and ensure that they have a chance to respond. We will freeze the list of projects and portions of the project-config repository several days before the migration, to facilitate creating and reviewing the necessary change. 5) On the migration date, the Infrastructure team will move all of the projects at once. We will generate the changes needed to do so automatically, individual projects will not need to do anything except approve .gitreview changes and possibly help fix any CI jobs that break as a result of the moves. 6) For the projects that are no longer maintained, we will merge changes to them that indicate that and make them read-only. We will schedule a move in early September for the projects that have already requested moves as part of becoming official OpenStack projects. Please don't propose any more changes to move projects before the mass migration. While most new projects are being created directly in the openstack/ namespace, we will continue to create additional git repositories associated with existing projects in the stackforge/ namespace so that the constituent repositories associated with those projects are not split across namespaces. We will happily move those projects along with the rest as part of the mass migration. Please reply with any feedback or suggested improvements to this plan. If we can achieve consensus on the approach, we will make further announcements as to specifics soon. Thanks, Jim [1] http://lists.openstack.org/pipermail/openstack-dev/2015-August/071816.html __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
