Difference between revisions of "Math4Team/Contacts"

From Sugar Labs
Jump to navigation Jump to search
(New page: = Math4 Team = The leaders of the Math4 Team are: User:Gdk Greg DeKoenigsberg <gdk redhat com> User:KRobinson Karlie Robinson <karlie_robinson webpath net> Don't hesitate to sen...)
 
 
(17 intermediate revisions by 7 users not shown)
Line 1: Line 1:
= Math4 Team =
+
<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|home=Project Home|xbgColor=ffe792}}{{TOCright}}</noinclude>
 +
== Math4 Organizers ==
  
The leaders 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:
  
[[User:Gdk Greg DeKoenigsberg]] <gdk redhat com>
+
* Greg DeKoenigsberg ([[User:Gdk]]) <gdk redhat com>
[[User:KRobinson Karlie Robinson]] <karlie_robinson webpath net>
+
* Karlie Robinson ([[User:KRobinson]]) <karlie_robinson webpath net>
  
Don't hesitate to send a note to say hello.  :)
+
== Math4 Project Teams ==
 +
 
 +
== Introduction ==
 +
 
 +
Math4 Teams are small teams that concentrate on developing activities that address objectives from the [[Math4Team/Resources/Curriculum Chart|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 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.  :)
 +
 
 +
=== 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.
 +
 
 +
First complete team gets to pick their own, favorite [[wikipedia:Set_(mathematics) |number set]] as a name.
 +
 
 +
Teachers - If you have never edited a wiki page before, just email the people on your team and they will help you get started.
 +
 
 +
== Math4 Red Team ==
 +
 
 +
* Teacher One Needed, <email at wherever dot com>
 +
* Teacher Two Needed, <email at wherever dot com>
 +
* [[User: bigdaveyl| David Liana]], <dliana at frontiernet dot net>
 +
* [[User: mcbrighton| Mark Brighton]], <mcbrighton at gmail 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>
 +
 
 +
== [[Math4Team/RIT|Math4 RIT Team]] ==
 +
{{:Math4Team/RIT/WhosWho}}
 +
 
 +
 
 +
== Math4Team UTOS-XO ==
 +
{{:Team:UTOS-XO}}
 +
 
 +
== [[User:Ossfm|Team ossfm]] ==
 +
*05/26/09:<br>We are developing the Hop-A-Round activity. It is targeted at topic 4.N.16-Rounding. I expect we'll post our beginnings on the git server soon. Our goal is project completion by no later than August 2009.
 +
[[Category:Contact]]

Latest revision as of 11:10, 28 May 2009

Project Home   ·   Join   ·   Contacts   ·   Resources   ·   FAQ   ·   Roadmap   ·   To Do   ·   Meetings

Math4 Organizers

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:

Math4 Project Teams

Introduction

Math4 Teams are small teams that concentrate on developing activities that address objectives from the 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 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. :)

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.

First complete team gets to pick their own, favorite number set as a name.

Teachers - If you have never edited a wiki page before, just email the people on your team and they will help you get started.

Math4 Red Team

  • Teacher One Needed, <email at wherever dot com>
  • Teacher Two Needed, <email at wherever dot com>
  • David Liana, <dliana at frontiernet dot net>
  • Mark Brighton, <mcbrighton at gmail 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>

Math4 RIT Team

This team consists of those working on Math4 projects within the RIT Honors Seminar.

They may end up also in a Math4 Prime, Complex, Rational, Real, Fuzzy, Fibonacci, Julia, ... team.

Who's Who in the RIT Math4 project?

See Math4Team/RIT/Students.


Math4Team UTOS-XO

The Utah Open Source Foundation is sponsoring once a month hackfests for the OLPC (XO) 4th Grade Math's Curriculum.

The UTOS-XO team has a mailing list to coordinate local activities and development. We encourage status updates to continue to be on the 4gm mailing list.

So far, we have 11 members of our team.

SL/Davis/Weber Counties

Utah County

  • Richard Holden
  • Jason Corbett

Cache County

  • Andrew Hamblin

We will probably divide this team into two geographically located teams for convenience. Salt Lake and Utah counties tend to be good choices for team borders. If more folks start appearing north of Salt Lake County, it's possible to splinter a little more.

Status

Currently, we're working on four xo activities from the list:

4.N.2

2009-04-22 - Assigned tasks

4.N.7

Created Team for signup purposes

  • Goal: Recognize classes (in particular, odds, evens; factors or multiples of a given number; and squares) to which a number may belong, and identify the numbers in those classes. Use these in the solution of problems.
  • Members
    • Doug Glenn

2009-06-09 - Assigned tasks

4.N.12

2009-04-22 - Assigned tasks

4.N.13

2009-04-22 - Assigned tasks

More details to come.

Team ossfm

  • 05/26/09:
    We are developing the Hop-A-Round activity. It is targeted at topic 4.N.16-Rounding. I expect we'll post our beginnings on the git server soon. Our goal is project completion by no later than August 2009.