Duncan McGreggor wrote: >> Creating a packaging team that acknowledge their contribution to the >> upstream project will show that the packagers contributions are an >> integral part of the openstack development, it would motivate new >> packagers to contribute their changes upstream instead of keeping them >> in a patch directory within the package. >> >> I think there is an opportunity to leverage the momentum that is >> growing in each distribution by creating an openstack team for them to >> meet. Maybe Stefano Maffulli has an idea about how to go in this >> direction. The IRC channel was a great idea and it could become more. >> >> Good packages make a huge difference when it comes to deploying a >> solution made of numerous components. A packaging team that spans all >> openstack components would reduce the workload as intended while >> keeping the subject on the agenda. >> >> Cheers > > Wow. I'm so +1 on this. Very well said; sums up my feelings on the > matter too. > > Maybe this could be made an agenda item for the next PPB meeting?
(Speaking with my PPB elected member hat): You don't need the permission of the PPB to form and grow a team to work on something. Just do it :) The PPB is there to prevent conflicts, not to stand in the way of work getting done. It should be consulted only if the work adversely affects other groups, or stretches the definition of OpenStack beyond its commonly-accepted limits. In this case, forming a group to share and coordinate packaging work should not adversely affect anyone... Go for it ! -- Thierry Carrez (ttx) Release Manager, OpenStack _______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp