Hosting Request - ABCFlower

muriel_godoi at muriel_godoi at
Mon May 21 12:23:47 EDT 2007

1. Project name             :ABCFlower
2. Existing website, if any :
3. One-line description     :A more appropriate version of the hangman game

4. Longer description       :In this game children work  
collaboratively to write
                             : the name of the object presented. It  
uses flowers
                             :to show the results and how the  
collaboration happened.
                             :The main pedagogical purpose is to work  
with spelling.

5. URLs of similar projects :

6. Committer list
    Please list the maintainer (lead developer) as the first entry. Only list
    developers who need to be given accounts so that they can commit to your
    project's code repository, or push their own. There is no need to list
    non-committer developers.

       Username   Full name             SSH2 key URL                    E-mail
       --------   ---------             ------------                    ------
    #1 muriel   Muriel de Souza Godoi  
muriel_godoi at
    #2 junia    Junia Coutinho Anacleto  junia at

    If any developers don't have their SSH2 keys on the web, please attach them
    to the application e-mail.

7. Preferred development model

    [X] Central tree. Every developer can push his changes directly to the
        project's git tree. This is the standard model that will be familiar to
        CVS and Subversion users, and that tends to work well for most  

    [ ] Maintainer-owned tree. Every developer creates his own git tree, or
        multiple git trees. He periodically asks the maintainer to look at one
        or more of these trees, and merge changes into the maintainer-owned,
        "main" tree. This is the model used by the Linux kernel, and is
        well-suited to projects wishing to maintain a tighter control on code
        entering the main tree.

    If you choose the maintainer-owned tree model, but wish to set up some
    shared trees where all of your project's committers can commit directly,
    as might be the case with a "discussion" tree, or a tree for an individual
    feature, you may send us such a request by e-mail, and we will set up the
    tree for you.

8. Set up a project mailing list:

    [ ] Yes, named after our project name
    [ ] Yes, named ______________________
    [X] No

    When your project is just getting off the ground, we suggest you eschew
    a separate mailing list and instead keep discussion about your project
    on the main OLPC development list. This will give you more input and
    potentially attract more developers to your project; when the volume of
    messages related to your project reaches some critical mass, we can
    trivially create a separate mailing list for you.

    If you need multiple lists, let us know. We discourage having many
    mailing lists for smaller projects, as this tends to
    stunt the growth of your project community. You can always add more lists

9. Commit notifications

    [ ] Notification of commits to the main tree should be e-mailed to the list
        we chose to create above
    [ ] A separate mailing list, <projectname>-git, should be created  
for commit
    [X] No commit notifications, please

10. Vhost setup

    [ ] Yes, set up a vhost for the domain _______________ pointing to our
        project website.

    [X] No, we don't have a project domain, or don't want to use one. We'll
        use the website address.

11. Shell accounts

    As a general rule, we don't provide shell accounts to developers unless
    there's a demonstrated need. If you have one, please explain here, and
    list the usernames of the committers above needing shell access.

12. Notes/comments:
This activity was originally developed for Portuguese speakers.
The current code can be found at
It is functional, but without the mesh sharing functionality yet.

This message was sent using IMP, the Internet Messaging Program.

More information about the Devel mailing list