Ground rules

1. No new features until the rewrite is finished. Minor alterations to existing functionality are permissible if there's a good technical reason, but no new functionality will be accepted until the new project launches.

2. All code should come with tests. If you aren't sure how to test or are having trouble, ask a mentor for help.

3. Don't reinvent the wheel. High-quality 3rd-party libraries are vastly preferable to homegrown code. Reuse whenever possible.

4. Reviewing highly encouraged. Look at your peers' work. Offer constructive criticism leveled at the code, not the person. If you are on the receiving end, accept criticism graciously and use it as a chance to improve your code.

5. New features must mesh with the Plans vision. Does this feature make the community healthier or more vibrant? Or does it make Plans safer/more pleasant to use? How does this feature relate to the core functionality of Plans?