Page tree
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

The Coding to Learn and Create project is worked on by a distributed team. We have several methods of doing our work collaboratively and openly. Please join us!

Talk to Each Other

Weekly Team Meeting

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 work road blocks.

Daily Check-in Meeting

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.

Casual Chats

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.

Share Documents, Links, Ideas and Prototypes

Working Documents

The project team uses Google drive to share working documents.

Sharing Links and Ideas

The project team uses a mailing list for asynchronous conversations about the project. You can join the mailing list or view the archives.

How to Use the Mailing List

  1. Subscribe to it:

    1. Put your email address and name here and click the Subscribe button: https://lists.idrc.ocad.ca/mailman/listinfo/code.learn.create/

    2. Check your junk folder in case the confirmation email goes there

  2. Once you’ve confirmed your subscription, send your email to: code.learn.create@lists.inclusivedesign.ca and everyone will get it

Prototypes

The design and development team sometimes makes prototypes of various technologies being created. Currently there is a prototype of a simple web based programming environement that can draw shapes with straight lines.

Plan Our Work

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. 

Bi-weekly Iteration Planning Meeting

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 is organized in this spreadsheet.

Develop Software

The development team uses JIRA to track issues and features being built into the development environment and tools.

The development team uses Github to manage our source code.


  • No labels