[oe] OE Commit Policy and other procedures

[Richard Purdie]

Hi,

We've been conscious that the OE project has lacked direction and in
some senses management. In an attempt to clear all this up the "core
team" have put together some policies to try and give structure to the
way we do things. These have been put onto the wiki and are linked off
the http://wiki.openembedded.net/index.php/Category:Policy page.

The newly added pages are:

http://wiki.openembedded.net/index.php/Branching_Policy
http://wiki.openembedded.net/index.php/Bug_days
http://wiki.openembedded.net/index.php/Commit_Policy
http://wiki.openembedded.net/index.php/Community_Servers
http://wiki.openembedded.net/index.php/Documentation_Team
http://wiki.openembedded.net/index.php/New_commit_rights
http://wiki.openembedded.net/index.php/OE_core_team
http://wiki.openembedded.net/index.php/User_contributions

Of these, the ones of particular importance are the commit policy and
the core and documentation teams. These formalise
arrangements/agreements that have partially existed for a while.

These policies pretty much reflect the way things have happened up until
now so its hoped they're not too controversial and not too much
discussion should be needed but obviously if anyone has any questions or
issues please do raise them. Its hoped this clarifys the situation for
everyone concerned.

Of key importance is the commit policy which should now give us a clear
run on the changeover to git. I'll follow up this email with another
about that.

Also listed here but slightly out of place is a proposal/RFC: 

http://wiki.openembedded.net/index.php/Structure_of_.dev_branch

I've proposed this in various ways before and I think this is needed,
not least to help with the commit policy and what is defined as a "core"
component needing more careful review. Please consider this as a RFC and
follow up on the list with any questions/issues/counter proposals etc.

Regards,

Richard (on behalf of a unanimous core team decision)