important process reminder

[David Nalley <da...@gnsa.us>]

Hi folks,

Just a couple of quick housekeeping reminders

If you are a committer:
* You may freely commit any of your code to the cloudstack repos.
* You may freely commit any work of anyone else who has submitted the
code you wish to apply to one of the following:
 ** The cloudstack-dev mailing list
 ** reviews.apache.org
 ** the bug tracker
You (generally) may NOT commit code that you have arrived at by any
other manner. (there are processes in place to deal with code that has
not arrived by one of these means, but requires that the PPMC request
IP Clearance from the IPMC for the specific swath of code in question)

If you have questions about this, please ask!

If you are not yet a committer, but wish to have your code included in
CloudStack, you must submit it to one of:
* The cloudstack-dev mailing list
* reviews.apache.org
* the bug tracker
In general a public record MUST be made of code to be included into
CloudStack. (I am sure there are exceptions, but I can't find or think
of any at the present moment.)

Why is this important? Apache CloudStack must be able to establish the
legal provenance of all code that enters the code base, and these
public, archived, methods are the way that is accomplished.  There are
also other problems with subverting this process - such as not
collaborating and developing in the open with the rest of the
CloudStack community, lack of recognition of contributions which is
important for recognition and nomination as a committer.

If this causes you heartburn, or you have questions, please do not
hesitate to ask.

--David