If you're not already signed up, the very first step for getting involved with Dojo is to sign up for the Dojo Interest mailing list.

Dojo is an Open Source project, and while we don't believe in some of the oft-repeated Open Source mantras, the project depends on contributions from a wide variety of people with broad expertise.

To protect ourselves against possible legal trouble, we require that all contributors sign a short document, the Contributor License Agreement, that makes the ownership of their contributions clear. Please print a copy of that document, sign it, and mail it to the Dojo Foundation (the address is in the document.)

Here is a short collection of some of the ways that you can get involved with Dojo (if you're not already).

• Documentation
  
  • Write articles in the wiki describing some part of the system. See ContributingToTheWiki for information about signing up for a wiki account. Here are some topics that need better coverage:
    
    • dojo system configuration
    • how to use the package system (i.e., what gets loaded when)
    • how to write unit tests
    • how to use the drag-and-drop APIs
    • using "upgrade" widgets like the resizeable textarea to subtly improve user experience
    • how to use the animation APIs
    • how the event system makes writing JavaScript easier
    • how to write a Transport class for the Dojo I/O layer (exposed via dojo.io.bind)
    • how to use Dojo in command-line or Java environments
  • volunteer to help with the website (it needs a redesign badly, and everyone knows it)
  • help develop and write about patterns for using Dojo in degradeable ways
• Tools
  • the project needs better tools for generating documentation for JavaScript sources
  • improve the scope of the command line unit testing tools to allow them to attempt to create widgets without the need of a browser
  • improve the unit testing tools to allow in-browser tests to be generated and run
  • help debug and fix the linker
  • improve the linker by letting it take an HTML page and not just a JavaScript file as an input
• Widgets
  • help write or contribute to widgets already on the Dojo roadmap
  • contribute widgets from your own applications
  • work on alternate themes for widgets
  • report to the group on how the usability of existing widgets can be improved
• Core
  • help US figure out the right way to do keystroke handling and dispatch
  • contribute ways to reduce the amount of boilerplate code in widgets
  • help fill in any of the empty namespaces using code already available in the contributed code bases (nWidgets, burst, f(m))

If you'd like to work on any of the projects mentioned, send mail to Alex Russell (alex@dojotoolkit.org) to see if there are already others working on the problem that you can collaborate with.