On 11/20/2012 01:03 AM, Stefano Zacchiroli wrote: > Disclaimer: I'm not doing any packaging work related to Debian "cloud" > stuff up to now, so I surely welcome living this choice to the people > who are doing that work. > > Still, I wonder which benefit do you see in scattering the packages > across the various, programming language oriented, projects you mention > above. That would mean that people interesting in more than one cloud > related package will have to join several teams. Clearly, we can turn > the argument around saying that people interested in, say, Python > packaging will have to join the cloud Alioth project. But to me the > former case seems significantly more likely than the latter, no? I do agree with the above. Plus there are few projects which are of interest for multiple could stacks: - cloud-init - these AMI images - euca2ools
Probably, there will be more later on. But I guess it depends on which package. In Openstack, we have a big number of python libraries that have a wider purpose than just cloud computing. In such case, probably, it's better to leave them to the Python team, *IF* they have enough time for them. Thomas -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
