<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><meta name="Generator" content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Cambria;
panose-1:2 4 5 3 5 4 6 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
p.airmailon, li.airmailon, div.airmailon
{mso-style-name:airmail_on;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Cambria",serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style></head><body lang="EN-US" link="blue" vlink="purple"><div class="WordSection1"><p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Cambria",serif;color:#1f497d">Patrick –</span></p><p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Cambria",serif;color:#1f497d"> </span></p><p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Cambria",serif;color:#1f497d">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.</span></p><p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Cambria",serif;color:#1f497d"> </span></p><p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Cambria",serif;color:#1f497d">Sheena</span></p><p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Cambria",serif;color:#1f497d"> </span></p><div><div style="border:none;border-top:solid #e1e1e1 1.0pt;padding:3.0pt 0in 0in 0in"><p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Patrick Petit [mailto:<a href="mailto:ppetit@mirantis.com">ppetit@mirantis.com</a>] <br><b>Sent:</b> Saturday, July 25, 2015 12:25 PM<br><b>To:</b> Igor Kalnitsky; OpenStack Development Mailing List (not for usage questions)<br><b>Subject:</b> Re: [openstack-dev] [Fuel][Plugins] Plugins on separate launchpad projects</span></p></div></div><p class="MsoNormal"> </p><div id="bloop_customfont"><p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Helvetica",sans-serif">Igor, thanks for your comments. Please see below.</span></p></div><div id="bloop_customfont"><p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Helvetica",sans-serif">Patrick</span></p></div><p class="airmailon"><span style="font-size:10.0pt;font-family:"Helvetica",sans-serif;color:black">On 25 Jul 2015 at 13:08:24, Igor Kalnitsky (<a href="mailto:ikalnitsky@mirantis.com">ikalnitsky@mirantis.com</a>) wrote:</span></p><div><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt;text-align:start;word-spacing:0px"><div><div><p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Helvetica",sans-serif;color:black">Hello Patrick,<br><br>Thank you for raising this topic. I think that it'd be nice to create<br>a separate projects for Fuel plugins if it wasn't done yet.</span></p></div></div></blockquote></div><p><span style="font-size:10.0pt;font-family:"Helvetica",sans-serif">Yes there is a launchpad project for fuel plugins although it’s currently not possible to create blueprints in that project.</span></p><p><span style="font-size:10.0pt;font-family:"Helvetica",sans-serif">But that’s not what I meant. I meant dedicated projets for each fuel plugins or for a group of fuel plugins if desired.</span></p><p><span style="font-size:10.0pt;font-family:"Helvetica",sans-serif">For example a project for LMA series of fuel plugins.</span></p><div><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt;text-align:start;word-spacing:0px"><div><div><p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:10.0pt;font-family:"Helvetica",sans-serif;color:black">Fuel<br>plugins have different release cycles and do not share core group. So<br>it makes pretty much sense to me to create separate projects.</span></p></div></div></blockquote><p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Helvetica",sans-serif">Correct. We are on the same page.</span></p></div><div><p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Helvetica",sans-serif"><br><br></span></p><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><div><div><p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Helvetica",sans-serif;color:black">Otherwise, I have no idea how to work with LP's milestones since again<br>- plugins have different release cycles.<br><br>Thanks,<br>Igor<br><br>On Fri, Jul 24, 2015 at 8:27 PM, Patrick Petit <<a href="mailto:ppetit@mirantis.com">ppetit@mirantis.com</a>> wrote:<br>> Hi There,<br>><br>> I have been thinking that it would make a lot of sense to have separate<br>> launchpad projects for Fuel plugins.<br>><br>> The main benefits I foresee….<br>><br>> - Fuel project will be less of a bottleneck for bug triage and it should be<br>> more effective to have team members do the bug triage. After all, they are<br>> best placed to make the required judgement call.<br>> - A feature can be spread across multiple plugins, like it’s the case with<br>> LMA toolchain, and so it would be better to have a separate project to<br>> regroup them.<br>> - It is counter intuitive and awkward to create blueprints for plugins in<br>> Fuel project itself in addition to making it cluttered with stuffs that<br>> unrelated to Fuel.<br>><br>> Can you please tell me what’s your thinking about this?<br>> Thanks<br>> Patrick<br>><br>> --<br>> Patrick Petit<br>> Mirantis France<br>><br>><br>> __________________________________________________________________________<br>> OpenStack Development Mailing List (not for usage questions)<br>> Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>><br><br>__________________________________________________________________________<br>OpenStack Development Mailing List (not for usage questions)<br>Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a></span></p></div></div></blockquote></div></div></body></html>