Getting involved

There are many ways of contributing to Insoshi.  Just participating in the Insoshi developer site helps us make Insoshi better.  If you discover bugs or have feature requests, file a ticket at our Lighthouse issue tracker. 

Developers who want to contribute code should of course install Insoshi with Git and get it running.  You should use Option #3, which involves forking the Insoshi GitHub repository.  Once you make your changes, issue a pull request and we'll take it from there.  You should email Insoshi cofounder Long Nguyen (long.nguyen@insoshi.com) with any questions.

Looking over the tickets at Lighthouse is a good place to start if you want to find something to work on.  As we move forward with our community-building efforts, we will be actively soliciting contributors for particular features.

Code guidelines

• Maximum 80 characters across (with rare exceptions
  
• Tests strongly encouraged (Insoshi uses RSpec; see the current tests for examples)
• rake spec should have all passing tests for any submission
  
• Emulated (soft) tabs consisting of two spaces; no tab (\t) characters
• All pages should be valid XHTML 1.0 strict
• All pages should look OK in Firefox 2 & 3, Safari, and IE 6 & 7
  
• Changes should be made against the edge branch (follows our development workflow)
  

Data model

Useful links

• GitHub repository
• Lighthouse issue tracker
• Google Group
• Developer site
• Blog