166
edits
Changes
no edit summary
<noinclude>{{GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}{{TeamHeader|Math4Team}}
<noinclude>{{GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}{{TeamHeader|Math4Team}}
= Math4 Team =
= Math4 Organizers =
The current members of the Math4 Team are:
Organizers are responsible for making sure that development teams have everything they need, and are moving forward. The current organizers of the Math4 Team are:
* Greg DeKoenigsberg ([[User:Gdk]]) <gdk redhat com>
* Greg DeKoenigsberg ([[User:Gdk]]) <gdk redhat com>
* Karlie Robinson ([[User:KRobinson]]) <karlie_robinson webpath net>
* Karlie Robinson ([[User:KRobinson]]) <karlie_robinson webpath net>
= Math4 Teams =
== Introduction ==
Math4 Teams are small teams that concentrate on developing activities that address objectives from the [[Math4Team/Resources/CurriculumChart|Math4 Curriculum Chart]]. These teams should consist of 2-4 developers and 2-3 teachers, working together in close coordination to make awesome stuff.
== Responsibilities ==
Team members should be ready to commit to the following responsibilities:
* '''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.
* '''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.
* '''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. :)
== Math4 Team Signups ==
Volunteers! Please sign up below. When enough volunteers have signed up, an organizer will be in touch to help kick off your team.
=== Math4 Red Team ===
* Teacher One Needed, <email at wherever dot com>
* Teacher Two Needed, <email at wherever dot com>
* Developer One Needed, <email at wherever dot com>
* Developer Two Needed, <email at wherever dot com>
* Developer Three Needed, <email at wherever dot com>
=== Math4 Blue Team ===
* Teacher One Needed, <email at wherever dot com>
* Teacher Two Needed, <email at wherever dot com>
* Developer One Needed, <email at wherever dot com>
* Developer Two Needed, <email at wherever dot com>
* Developer Three Needed, <email at wherever dot com>