document development process

[GoogleCodeExporter]

- how to become a project member
- how to submit a code review
- commit policy

Original issue reported on code.google.com by [email protected] on 24 Jun 2009 at 7:37

[GoogleCodeExporter]

To help out new developers, also add info on what's in each directory and how 
the
code is laid out.

Original comment by [email protected] on 24 Jun 2009 at 8:16

[GoogleCodeExporter]

We also need to add a roadmap explaining the milestones and goals we hope to 
achieve
by said milestones.

Original comment by [email protected] on 24 Jun 2009 at 8:24

[GoogleCodeExporter]

Note to self (excerpts from email to Clint)

Before you commit anything, please have me review it. You can use
http://codereview.appspot.com/ to upload patches for review. Sample review here:
http://codereview.appspot.com/68042/show

... patches without reviews may get reverted!

Big patches:

They are hard to review. Please break it down into a few incremental changes 
and that
will be much easier to review piece by piece. This also has the effect of 
making it
look like you're working really hard because you'll be making more commits. ;-)

Original comment by [email protected] on 24 Jun 2009 at 9:01

• Added labels: Type-Enhancement
• Removed labels: Type-Task

[GoogleCodeExporter]

Original comment by [email protected] on 28 Jun 2009 at 4:49

• Added labels: Type-Task
• Removed labels: Type-Enhancement