<HTML>
<HEAD>
<TITLE>Re: [Openstack] best practices for merging common into specific projects</TITLE>
</HEAD>
<BODY>
<FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>Ya, let me know, I’ll jump in and see what I can do also...<BR>
<BR>
On 7/4/12 3:18 PM, "Gabriel Hurley" <<a href="Gabriel.Hurley@nebula.com">Gabriel.Hurley@nebula.com</a>> wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>Having a team/leader in that arena would definitely help. I'd contribute to common more if I knew what needed contributing, who to talk to about it, etc... Same goes for helping in terms of packaging, etc. to make it a proper common library.<BR>
<BR>
- Gabriel<BR>
<BR>
> -----Original Message-----<BR>
> From: <a href="openstack-bounces+gabriel.hurley=nebula.com@lists.launchpad.net">openstack-bounces+gabriel.hurley=nebula.com@lists.launchpad.net</a><BR>
> [<a href="mailto:openstack-">mailto:openstack-</a><BR>
> <a href="bounces+gabriel.hurley=nebula.com@lists.launchpad.net">bounces+gabriel.hurley=nebula.com@lists.launchpad.net</a>] On Behalf Of<BR>
> Thierry Carrez<BR>
> Sent: Wednesday, July 04, 2012 2:57 AM<BR>
> To: <a href="openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><BR>
> Subject: Re: [Openstack] best practices for merging common into specific<BR>
> projects<BR>
><BR>
> Monty Taylor wrote:<BR>
> > However, with a versioned library model, the projects can consume<BR>
> > things pinned to specific versions, and then they can submit a change<BR>
> > that updates the version depend and the code which needs to be updated<BR>
> > to support the version change, and that change can be atomic.<BR>
> ><BR>
> > So honestly, I'd say the real key is getting us closer to the point<BR>
> > where openstack-common is a proper library, because all of the rest of<BR>
> > the complexity is stuff we're inventing to make life harder on<BR>
> > ourselves, when the standard library with api-contract and a version<BR>
> > model of the world works pretty fine without needing coordinated<BR>
> > changes across multiple repositories.<BR>
><BR>
> Yes, that's the end goal. And IMHO we are not very far away. I think the main<BR>
> reason we are not there yet is that while a lot of people enjoy giving their<BR>
> opinions about how openstack-common should be done and consumed by<BR>
> projects, not so many people follow up and actually do the work.<BR>
><BR>
> Making our multiple projects converge onto consolidated and well-accepted<BR>
> APIs is a bit painful work, but it is a prerequisite to turning openstack-<BR>
> common into a proper library (or set of libraries).<BR>
><BR>
> I'd say the whole thing suffers from not having a proper<BR>
> team/leader/coordinator dedicated to it: relying on existing, overstretched<BR>
> PTLs to lead that effort might not be the fastest path.<BR>
><BR>
> Regards,<BR>
><BR>
> --<BR>
> Thierry Carrez (ttx)<BR>
> Release Manager, OpenStack<BR>
><BR>
><BR>
> _______________________________________________<BR>
> Mailing list: <a href="https://launchpad.net/~openstack">https://launchpad.net/~openstack</a><BR>
> Post to : <a href="openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><BR>
> Unsubscribe : <a href="https://launchpad.net/~openstack">https://launchpad.net/~openstack</a><BR>
> More help : <a href="https://help.launchpad.net/ListHelp">https://help.launchpad.net/ListHelp</a><BR>
<BR>
<BR>
<BR>
_______________________________________________<BR>
Mailing list: <a href="https://launchpad.net/~openstack">https://launchpad.net/~openstack</a><BR>
Post to : <a href="openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><BR>
Unsubscribe : <a href="https://launchpad.net/~openstack">https://launchpad.net/~openstack</a><BR>
More help : <a href="https://help.launchpad.net/ListHelp">https://help.launchpad.net/ListHelp</a><BR>
<BR>
</SPAN></FONT></BLOCKQUOTE>
</BODY>
</HTML>