This seems fine to me if we assume that the powers and responsibility of a core dev is approving code for merge into trunk. I think as the project grows, it might be useful to include more a linux-style hierarchy where there are core maintainers of different sections of the code. This could easily be done on a per-project basis, though. Despite the large amount of time I spend working with the code, it is hard for me to stay completely up to date with the stuff I'm not directly working on (XenApi for example).
I also think Ewan's point is valid. It makes sense to have some kind of core-contributor type group for people that want to receive notifications and participate in blueprints and such but may not actually be reviewing code and approving merge proposals. Vish On Jan 17, 2011, at 7:42 AM, Jonathan Bryce wrote: > We have a proposal to take under consideration on the process for adding > developers to the core group for sub-projects. The full proposal can be read > here on the wiki: > > http://wiki.openstack.org/Governance/Proposed/CoreDevProcess > > This proposal had previously been sent to the OpenStack mailing list on > December 20th for comments > (https://lists.launchpad.net/openstack/msg00140.html). One comment that came > back which is not addressed in the proposal is the process for removing a > developer from the core group. > > Please review the proposal and respond to the list with either approval of > the proposal or concerns and requested changes. > > > _______________________________________________ > Mailing list: https://launchpad.net/~openstack-poc > Post to : openstack-poc@lists.launchpad.net > Unsubscribe : https://launchpad.net/~openstack-poc > More help : https://help.launchpad.net/ListHelp _______________________________________________ Mailing list: https://launchpad.net/~openstack-poc Post to : openstack-poc@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-poc More help : https://help.launchpad.net/ListHelp
