Re: [openstack-dev] Migrating existing projects in the stackforge namespace - question about Fuel Plugins

2015-08-24 Thread Doug Hellmann
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 th

[openstack-dev] Migrating existing projects in the stackforge namespace - question about Fuel Plugins

2015-08-24 Thread Irina Povolotskaya
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 Plugin

Re: [openstack-dev] Migrating existing projects in the stackforge namespace

2015-08-17 Thread Jesse Pretorius
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

[openstack-dev] Migrating existing projects in the stackforge namespace

2015-08-14 Thread James E. Blair
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 curren