Project hosting :: ColingoXO

[Benjamin Lowenstein]

Hi, we applied for Project Hosting on 23 Oct and heard no response, SJ
suggested that we reapply...

1. Project name             : ColingoXO
2. Existing website, if any : http://wiki.laptop.org/go/colingoXO
3. One-line description     : ColingoXO creates a platform for
constructivist language-learning by letting children splice video clips to
create and share video narratives.

4. Longer description       :

Children will be able to use all video clips from the copyleft Colingo video
library or alternatively record new clips with the XO camera and microphone.
Beyond its role as a simple video editor, ColingoXO will focus on taking
advantage of the XO's mesh capabilities. Videos will not be housed on
individual XO's, but rather be housed and streamed from the School server.
Video narratives, which are essentially XSPF playlists, will be kept locally
in the Journal and be easily passed through the mesh due to their
lightweight, text-based format. Please see our wiki page for more info and a
screenshot of the UI, designed by Eben...

5. URLs of similar projects : http://wiki.laptop.org/go/Shtooka_Project

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 awjrichards    Arthur Richards
http://dev.colingo.org/mediawiki/index.php/User:Arthur
    arthur at colingo.org
   #2 lionstone    Ben Lowenstein
http://dev.colingo.org/mediawiki/index.php/User:Ben
       ben at colingo.org
   #3
      ...

   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
projects.

   [ ] 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:

   [X] Yes, named after our project name
   [ ] Yes, named ______________________
   [ ] 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
   later.

9. Commit notifications

   [X] 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
       notifications
   [ ] No commit notifications, please

10. 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.

11. Notes/comments:

To get the latest code:
http://dev.colingo.org/mediawiki/index.php/HOWTO_Checkout_ColingoXO
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.laptop.org/pipermail/devel/attachments/20071101/8bd49ac0/attachment.html>