Most Dojo meetings are now being commited here with comments showing what pairs produced that commit and what was its intent. Regular dojo sessions are committed as folders containing the number of the session and the name of problem. Example: 53-Haskell-basico There is a parallel session for "UberDojo"(or "Kake") in which folders have a serial number, the name "UberDojo" and the language it was written in. Example: 01-UberDojo-Python There is also a project we built to help us have dojos in C: Dojo Unit - a small library for testing C programs.
dojosp/participant-s-projects
This is a space for projects that maybe did or didn't start at a Dojo session and the participants continued developing.
Ruby