Development process overview

From Growstuff Wiki
Jump to: navigation, search

The Growstuff project uses a methodology called Extreme Programming to develop our software. This page is a brief overview of how that works for us.

QUICK GUIDE: how to get involved as a developer

  1. Join our Discussion forums
  2. Optionally, hang out on IRC
  3. Find an issue you're interested in working on, and leave a note saying you're working on it.
  4. Find someone to pair with
  5. Fork the Growstuff/growstuff code repository
  6. Work on your story -- see Development/Coding session for details
  7. If you need help or feedback or want to discuss your work, ask on any of our Discussion forums
  8. Submit a pull request to the "dev" branch
  9. Your work will be reviewed (usually within a few days) and should be integrated into the dev branch, then deployed to the staging server for testing
  10. Eventually (usually within a matter of weeks) it will be included in a release deployed to production.

Coding practices

We like working in pairs, to help cross-train and to make our software higher quality. We also use test-driven development as a discipline to help us code better and make sure we don't break things. This is a definite help when Refactoring, or improving older code, because the tests can demonstrate that our changes haven't broken functionality.

When pairing, we usually work together using voice chat (Skype or similar) and a screen-sharing tool. Sometimes, when they live near each other or are at an in-person event, they work side by side in front of one computer.


We want our software development process to be sustainable. This means that we don't push people til they burn out. We encourage people to work at a comfortable pace, and to pass on work that's proving to be too difficult, too time-consuming, or too frustrating.

See also: Technology stack, Category:Development tools

Personal tools