Open Stack

On 26 Jul 2015 at 20:25:43, Sheena Gregson (sgregson at mirantis.com) wrote:

Patrick –

 

Are you suggesting one project for all Fuel plugins, or individual projects for each plugin?  I believe it is the former, which I prefer – but I wanted to check.

Sheen,

I meant, one individual project for each plugin or one individual project for several plugins when it makes sense to regroupe them under one umbrella like LMA toolchain as stated earlier.


 

Sheena

 

From: Patrick Petit [mailto:ppetit at mirantis.com]
Sent: Saturday, July 25, 2015 12:25 PM
To: Igor Kalnitsky; OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Fuel][Plugins] Plugins on separate launchpad projects

 

Igor, thanks for your comments. Please see below.

Patrick

On 25 Jul 2015 at 13:08:24, Igor Kalnitsky (ikalnitsky at mirantis.com) wrote:

Hello Patrick,

Thank you for raising this topic. I think that it'd be nice to create
a separate projects for Fuel plugins if it wasn't done yet.

Yes there is a launchpad project for fuel plugins although it’s currently not possible to create blueprints in that project.

But that’s not what I meant. I meant dedicated projets for each fuel plugins or for a group of fuel plugins if desired.

For example a project for LMA series of fuel plugins.

Fuel
plugins have different release cycles and do not share core group. So
it makes pretty much sense to me to create separate projects.

Correct. We are on the same page.




Otherwise, I have no idea how to work with LP's milestones since again
- plugins have different release cycles.

Thanks,
Igor

On Fri, Jul 24, 2015 at 8:27 PM, Patrick Petit <ppetit at mirantis.com> wrote:
> Hi There,
>
> I have been thinking that it would make a lot of sense to have separate
> launchpad projects for Fuel plugins.
>
> The main benefits I foresee….
>
> - Fuel project will be less of a bottleneck for bug triage and it should be
> more effective to have team members do the bug triage. After all, they are
> best placed to make the required judgement call.
> - A feature can be spread across multiple plugins, like it’s the case with
> LMA toolchain, and so it would be better to have a separate project to
> regroup them.
> - It is counter intuitive and awkward to create blueprints for plugins in
> Fuel project itself in addition to making it cluttered with stuffs that
> unrelated to Fuel.
>
> Can you please tell me what’s your thinking about this?
> Thanks
> Patrick
>
> --
> Patrick Petit
> Mirantis France
>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>

__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__________________________________________________________________________ 
OpenStack Development Mailing List (not for usage questions) 
Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe 
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150727/ad31d0d8/attachment.html>