<html><body bgcolor="#ffffff">Hello, <br>
<br>
My name is Terrence Grannum from the World Wide Workshop Foundation.
We have spoken with Lauren Klein and SJ about integrating closer with
OLPC and harnessing the strength of the growing community, and we
decided it would be a great first step to link into your git/trac
system.<br>
<br>
One issue, however, is that although we will be launching our "Activity
Center" through ONE icon on the Sugar "menu bar," it is really a
gateway to launch other .xo files (10+ by year end). Right now, for
instance, we have 5 more activities besides the "MMM Activity Center"
gateway:<br>
<br><ul><li>
Teacher Center</li><li>
Slider Puzzle</li><li>
Story Builder</li><li>
Cartoon Builder</li><li>
Poll Builder</li></ul>
<br>
Should I fill out one of these forms for each one? Or do we keep them
"together" in some way to convey the sense of a true "bundle." Please
advise.<br>
<br>
Thank you,<br>
Terrence Grannum<br>
<a href="mailto:terrence@worldwideworkshop.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">terrence@worldwideworkshop.org</a><br><br><br><br>1. Project name : MaMaMedia Activity Center<br>2. Existing website, if any : <a href="http://www.worldwideworkshop.org/olpcwiki" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://www.worldwideworkshop<wbr>.org/olpcwiki</a><br>3. One-line description : Colorful menu page for suite of MaMaMedia .XO activities<br><br>4.
Longer description : MAMAMEDIA ACTIVITY CENTER is a colorful
Menu Page, an activity launcher, for introducing all the World Wide
Workshop Foundation OLPC developments. At the center of it we feature
our playful Logo of the Idea Child and it is surrounded by Idea Bubbles
which are buttons for the learning activities, filled with creative
ideas for using the XO laptops for learning and teaching, and lesson
plans for students, educators and families in the OLPC communities.
<br><br>One of the bubbles is the Teachers' Center which includes an
overview of our educational philosophy and design principles, a
glossary, a summary of activities and lesson plans, as well as links to
our Educators Wiki. <script><!--
D(["mb","\u003cbr\> :\u003cbr\> :\u003cbr\> :\u003cbr\>\u003cbr\>\u003cbr\>5. URLs of similar projects : \u003ca href\u003d\"http://www.worldwideworkshop.org/olpcwiki/index.php?title\u003dMaMaMedia_Activity_Center\" target\u003d\"_blank\" onclick\u003d\"return top.js.OpenExtLink(window,event,this)\"\>\nhttp://www.worldwideworkshop\u003cWBR\>.org/olpcwiki/index.php?title\u003cWBR\>\u003dMaMaMedia_Activity_Center\u003c/a\> \u003cbr\>\u003cbr\>6. Committer list \u003cbr\> Please list the maintainer (lead developer) as the first entry. Only list \u003cbr\> developers who need to be given accounts so that they can commit to your\n\u003cbr\>\u003cbr\> project's code repository, or push their own. There is no need to list\u003cbr\> non-committer developers.\u003cbr\>\u003cbr\> Username Full name SSH2 key URL E-mail\u003cbr\> -------- --------- ------------ ------\n\u003cbr\>\u003cbr\> #1 Cn Carlos Neves \u003ca href\u003d\"mailto:cn@sueste.net\" target\u003d\"_blank\" onclick\u003d\"return top.js.OpenExtLink(window,event,this)\"\>cn@sueste.net\u003c/a\>\u003cbr\> #2\u003cbr\> #3\u003cbr\> ...\u003cbr\>\u003cbr\> If any developers don't have their SSH2 keys on the web, please attach them \n\u003cbr\> to the application e-mail.\u003cbr\>\u003cbr\>7. Preferred development model\u003cbr\>\u003cbr\> [X] Central tree. Every developer can push his changes directly to the \u003cbr\>\u003cbr\> project's git tree. This is the standard model that will be familiar to \n\u003cbr\> CVS and Subversion users, and that tends to work well for most projects.\u003cbr\>\u003cbr\> [ ] Maintainer-owned tree. Every developer creates his own git tree, or\u003cbr\>\u003cbr\> multiple git trees. He periodically asks the maintainer to look at one\n\u003cbr\> or more of these trees, and merge changes into the maintainer-owned,\u003cbr\> "main" tree. This is the model used by the Linux kernel, and is \u003cbr\>\u003cbr\> well-suited to projects wishing to maintain a tighter control on code\n\u003cbr\> entering the main tree.\u003cbr\>\u003cbr\> If you choose the maintainer-owned tree model, but wish to set up some\u003cbr\> shared trees where all of your project's committers can commit directly, ",1]
);
//--></script><br> :<br> :<br> :<br><br><br>5. URLs of similar projects : <a href="http://www.worldwideworkshop.org/olpcwiki/index.php?title=MaMaMedia_Activity_Center" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://www.worldwideworkshop<wbr>.org/olpcwiki/index.php?title<wbr>=MaMaMedia_Activity_Center</a> <br><br>6. Committer list <br> Please list the maintainer (lead developer) as the first entry. Only list <br> developers who need to be given accounts so that they can commit to your
<br><br> project's code repository, or push their own. There is no need to list<br> non-committer developers.<br><br> Username Full name SSH2 key URL E-mail<br> -------- --------- ------------ ------
<br><br> #1 Cn Carlos Neves <a href="mailto:cn@sueste.net" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">cn@sueste.net</a><br> #2<br> #3<br> ...<br><br> If any developers don't have their SSH2 keys on the web, please attach them
<br> to the application e-mail.<br><br>7. Preferred development model<br><br> [X] Central tree. Every developer can push his changes directly to the <br><br> project's git tree. This is the standard model that will be familiar to
<br> CVS and Subversion users, and that tends to work well for most projects.<br><br> [ ] Maintainer-owned tree. Every developer creates his own git tree, or<br><br> multiple git trees. He periodically asks the maintainer to look at one
<br> or more of these trees, and merge changes into the maintainer-owned,<br> "main" tree. This is the model used by the Linux kernel, and is <br><br> well-suited to projects wishing to maintain a tighter control on code
<br> entering the main tree.<br><br> If you choose the maintainer-owned tree model, but wish to set up some<br> shared trees where all of your project's committers can commit directly, <script><!--
D(["mb","\u003cbr\>\u003cbr\> as might be the case with a "discussion" tree, or a tree for an individual \n\u003cbr\> feature, you may send us such a request by e-mail, and we will set up the \u003cbr\> tree for you.\u003cbr\>\u003cbr\>8. Set up a project mailing list:\u003cbr\>\u003cbr\>\u003cbr\> [ ] Yes, named after our project name\u003cbr\> [ ] Yes, named ______________________\n\u003cbr\> [X] No\u003cbr\>\u003cbr\> When your project is just getting off the ground, we suggest you eschew\u003cbr\> a separate mailing list and instead keep discussion about your project\u003cbr\>\u003cbr\> on the main OLPC development list. This will give you more input and \n\u003cbr\> potentially attract more developers to your project; when the volume of \u003cbr\> messages related to your project reaches some critical mass, we can \u003cbr\>\u003cbr\> trivially create a separate mailing list for you.\u003cbr\>\u003cbr\>\n If you need multiple lists, let us know. We discourage having many \u003cbr\> mailing lists for smaller projects, as this tends to\u003cbr\> stunt the growth of your project community. You can always add more lists\u003cbr\>\u003cbr\> later.\n\u003cbr\>\u003cbr\>9. Commit notifications\u003cbr\>\u003cbr\> [ ] Notification of commits to the main tree should be e-mailed to the list\u003cbr\> we chose to create above\u003cbr\> [ ] A separate mailing list, <projectname>-git, should be created for commit\n\u003cbr\>\u003cbr\> notifications\u003cbr\> [X] No commit notifications, please\u003cbr\>\u003cbr\>10. Shell accounts\u003cbr\>\u003cbr\> As a general rule, we don't provide shell accounts to developers unless \u003cbr\> there's a demonstrated need. If you have one, please explain here, and\n\u003cbr\>\u003cbr\> list the usernames of the committers above needing shell access.\u003cbr\>\u003cbr\>11. Notes/comments:\n",0]
);
//--></script><br><br> as might be the case with a "discussion" tree, or a tree for an individual
<br> feature, you may send us such a request by e-mail, and we will set up the <br> tree for you.<br><br>8. Set up a project mailing list:<br><br><br> [ ] Yes, named after our project name<br> [ ] Yes, named ______________________
<br> [X] No<br><br> When your project is just getting off the ground, we suggest you eschew<br> a separate mailing list and instead keep discussion about your project<br><br> on the main OLPC development list. This will give you more input and
<br> potentially attract more developers to your project; when the volume of <br> messages related to your project reaches some critical mass, we can <br><br> trivially create a separate mailing list for you.<br><br>
If you need multiple lists, let us know. We discourage having many <br> mailing lists for smaller projects, as this tends to<br> stunt the growth of your project community. You can always add more lists<br><br> later.
<br><br>9. Commit notifications<br><br> [ ] Notification of commits to the main tree should be e-mailed to the list<br> we chose to create above<br> [ ] A separate mailing list, <projectname>-git, should be created for commit
<br><br> notifications<br> [X] No commit notifications, please<br><br>10. Shell accounts<br><br> As a general rule, we don't provide shell accounts to developers unless <br> there's a demonstrated need. If you have one, please explain here, and
<br><br> list the usernames of the committers above needing shell access.<br><br>11. Notes/comments:<div><font face="Verdana" size="2"></font></div>
</body></html>