The Coding to Learn and Create project is an open, collaborative project that welcomes new contributors. We have several forums where we share our work and have discussions about the project. Please join us!
The project team meets on Wednesdays at 10 am Eastern using Goto Meeting. We update each other on what has been done in the past week and talk through any issues or questions.
The design and development team meets for quick check-ins on Mondays, Thursdays, Fridays and alternate Tuesdays at 11:45 am Eastern using Vidyo in the fluid_standup room.
The design and development team uses the Fluid Project IRC rooms for casual conversations about the project work. In particular, we can be found in the #fluid-work and #fluid-design rooms that are logged by the Fluid Project: #fluid-work logs and #fluid-design logs.
The project team uses Google drive to share working documents.
The project team uses a mailing list for asynchronous conversations about the project. You can join the mailing list or view the archives.
Subscribe to it:
Put your email address and name here and click the Subscribe button: https://lists.idrc.ocad.ca/mailman/listinfo/code.learn.create/
Check your junk folder in case the confirmation email goes there
Once you’ve confirmed your subscription, send your email to: firstname.lastname@example.org and everyone will get it
The design and development team sometimes makes prototypes of various technologies being created. Currently there is a prototype of a simple web based programming environment that can connect to Dash or Sphero robots and have them follow paths. There is also a prototype of the Educator's Toolkit which contains coding related lesson plans and materials.
The project team uses this wiki to document tasks and features that have been completed, are being worked on and are planned for the future.
The design and development team meets on alternate Tuesdays at 10 am Eastern for an Iteration Planning Meeting. During this meeting, work that has been completed in the last iteration is shared and reviewed, and work is planned and assigned for the iteration that is starting. Tasks for each iteration are organized in this spreadsheet.
The development team uses JIRA to track issues and features being built into the development environment and Github to manage our source code.