You want to contribute? Start by checking out the SVN repository. Details are on the Download page.

• patches (against the SVN trunk)
• documentation in any form (HTML and OpenDocument formats are preferred, doc is fine also)
• feedback

The preferred language is English, but please send it anyway! Google translation is our friend :)

Please adhere to our defined code style.

Please check your code against:

• Checkstyle + Sun checks for code style
• Cobertura for test coverage (try to reach 30% for new features)

If you add new features, please contribute also the technical specification and test cases (JUnit + test plan).

A collection of documentation for developers is available in each version-specific documentation section :

• 2.0 : Development Documentation
• 1.2 : Development Documentation

Documentation for new features in versions yet-to-be-released can be published in the special section of this wiki: :documentation:future.

You can find the forge of LSC on http://tools.lsc-project.org/. There you can fill bugs, see the history of commits, etc.

Hudson is available on http://build.lsc-project.org and will complain about any commits breaking the build in the #lsc-project IRC channel on Freenode.

A Sonar is available on http://sonar.lsc-project.org/, here you can see how code the LSC code is :)

LSC is under BSD license. To contribute new features or documentation, you need to send your code with a precise notice about the license under which you want to contribute. If this is not the original project license, your contribution will be integrated in a “third parties contribution” directory (non existent at this time).

Here is what Ohloh thinks about LSC: