Building Sakai (a.k.a. sakai-dev)

The Building Sakai area is oriented towards the needs of designers, programmers, developers, and quality assurance members of the Sakai community. It encompasses a broad range of topics, including documenting, designing, developing, testing, and releasing Sakai.

In addition to this area in Confluence, there is also an email list for discussing topics and asking questions related to building Sakai: sakai-dev@collab.sakaiproject.org (join sakai-dev list.) This is a very active list, with several or more messages a day (sakai-dev list archive).

• Development Infrastructure (and how to get access or report problems )
  
  • Sakai Source Code Repository (Subversion)
  • mSub - Deployment Source Code Repository
  • Issue and bug tracking (Jira)
  • Sakai wiki. You've already found it.
  • Having trouble with any of these? See Sakai Development Infrastructure.

Related Working Groups

There are also a number of smaller Working Groups that deal with specific topics within the broader context of Building Sakai, some of which overlap into Deploying Sakai and Using Sakai:

• Accessibility
• Documentation
• Internationalization and Localization
• Licensing
• QA
• Release Management (Core team)

Developer Documentation

Most of the development docs are in the Programmers Cafe Space and are linked to in the Programmers Manual but helpful docs can and should be added here as well.

Development Tips / Guidelines:

• Best Practices for High Quality Code - offers tips on ensuring you are writing high quality code for Sakai (and Java in general)
• Best Practices for Javascript - offers tips on writing good javascript and widgets in Sakai
• Programming Best Practices - Best practices for writing code in Sakai
• Release Practice Guidelines - How Sakai releases are assembled and maintained
• Sakai Developer Practices - describes trunk/branch/patch management, developer etiquette and the mechanics of technical decision-making

Add your own pages down here:

• your page!