Changes

* '''The initial meeting.'''  Everyone on the team should get together on phone, IRC, or in real life, to set goals.  Which objective would you like to tackle?     

* '''The initial meeting.'''  Everyone on the team should get together on phone, IRC, or in real life, to set goals.  Which objective would you like to tackle?     

* '''The weekly meeting.'''  Maybe it's weekly, maybe it's bi-weekly, maybe it's monthly -- but team members should agree on a time when they can all get together to assess one another's progress, hold one another accountable for milestones, and generally support one another.

* '''The weekly meeting.'''  Maybe it's weekly, maybe it's bi-weekly, maybe it's monthly -- but team members should agree on a time when they can all get together to assess one another's progress, hold one another accountable for milestones, and generally support one another.

* '''Teachers: defining features and testing code.''' Teachers, your primary mission is to tell the developers the kind of things you'd like to see. What sort of activities would students enjoy doing? Can the activity be done with minimal supervision, teach a concept, and then test mastery of that concept?  It's your job to direct the developer, and then test the code to make sure it's doing what you think it should be doing.

* '''Teachers: defining features and testing code.''' Teachers, your primary mission is to tell the developers the kind of things you'd like to see and to help them understand pedagogy and how children learn.  Can the activity be done with minimal supervision, teach a concept, and then test mastery of that concept?  It's your job to direct the developer, and then test the code to make sure it's doing what you think it should be doing.

* '''Developers: designing activities and writing code.'''  Developers, your primary mission is to listen to the teachers' intent, and then write activity code that expresses that intent.  You should commit to writing your code in the open source way.  That means working together, using gitorious or the like to maintain code publicly, keeping at least a bit of a TODO list, and documenting your code well enough that new developers can pick up and join in.  And yes, that last part isn't always "the open source way," but it should be, and for us, it will be.  :)

* '''Developers: designing activities and writing code.'''  Developers, your primary mission is to listen to the teachers' intent, and then write activity code that expresses that intent.  You should commit to writing your code in the open source way.  That means working together, using gitorious or the like to maintain code publicly, keeping at least a bit of a TODO list, and documenting your code well enough that new developers can pick up and join in.  And yes, that last part isn't always "the open source way," but it should be, and for us, it will be.  :)

First complete team gets to pick their own, favorite [[wikipedia:Set_(mathematics) |number set]] as a name.

First complete team gets to pick their own, favorite [[wikipedia:Set_(mathematics) |number set]] as a name.

== Math4 Red Team ==

== Math4 Red Team ==