[Openstack] best practices for merging common into specific projects

Christopher B Ferris chrisfer at us.ibm.com
Tue Jul 3 00:42:21 UTC 2012



-----openstack-bounces+chrisfer=us.ibm.com at lists.launchpad.net wrote: -----

>To: "andrewbogott at gmail.com" <andrewbogott at gmail.com>, Andrew Bogott
><abogott at wikimedia.org>, openstack <openstack at lists.launchpad.net>
>From: Joshua Harlow 
>Sent by: openstack-bounces+chrisfer=us.ibm.com at lists.launchpad.net
>Date: 07/02/2012 07:21PM
>Subject: Re: [Openstack] best practices for merging common into
>specific projects
>
>
>
>Re: [Openstack] best practices for merging common into specific
>projects
>
>
>What about using openstack-common as a library instead of a
>preprocessor ‘inclusion’ system/copy code around system....??
>
>
>
>Maybe its time for that to happen? 
>
>
>
>It always seemed sort of silly to me that files are being copied around
>to different projects like this, instead of referring to code in a
>common library package.

+1

Cheers,

Christopher Ferris
IBM Distinguished Engineer, CTO Industry and Cloud Standards
Member, IBM Academy of Technology
IBM Software Group, Standards Strategy
email: chrisfer at us.ibm.com
Twitter: christo4ferris
phone: +1 508 234 2986





More information about the Openstack mailing list