SnipForge

Subversion

Check out with

svn co http://snipforge.org/svn/modulname

• Core http://snipforge.org/svn/snipsnap/core/
• Search http://snipforge.org/svn/search-ng
• Graph macro http://snipforge.org/svn/snipsnap/snipsnap-graph-macro/
• JDBC Storage http://snipforge.org/svn/jdbcstorage
• RssServlet http://snipforge.org/svn/rss-ng
• XMLRPC http://snipforge.org/svn/xmlrpc-ng

SnipForge Guidelines for Projects

• Source: part of an email of Stephan Schmidt (aka funzel) to the SnipSnap developer list

File Structure

(classic SVN structure)

tags/
branches/
trunk/
   src/
     java/
     test/
   libs/
   jar/
   doc/
   licenses/
   README.txt

• tags contains tagged releases
• branches contains temporary branches
• src/java contains all java sources
• src/test contains all testing sources, unit test should have the same package name as the classes they test (no test in the package name)
• licenses should contain a license text file which reflects the package name and the license style, e.g. GROOVY_LICENSE_BSD
• libs contains all libs
• jar contains the build jars
• doc contains the documentation
• README.txt contains general notes about the plugin

Guide lines

1. Minimize lib dependencies
2. Code should be testable and have unit tests
3. Good documentation
4. Installation should be easy

License

• Open Source (OSI)
• As open as possible, we suggest Apache licenses for all projects

Resources

• SnipSnap Mailing list archive http://snipforge.org/lurker/