Project Hosting Application: SocialCalc

[Manusheel Gupta]

 1. Project name             : SocialCalc

2. Existing website, if any : http://wiki.laptop.org/go/SocialCalc  and
http://www.socialtext.net/socialcalcxo/index.cgi?sweet_socialcalc

3. One-line description     : The spreadsheet activity.

4. Longer description       : SocialCalc is a JavaScript-based spreadsheet
being developed as a sugar activity using XOCom, a
                                        package build for JS-Python
communication.                           :
                           :
                           :

5. URLs of similar projects :

6. Committer list


    Username         Full name              SSH2 key URL
E-mail
     --------   ---------             ------------                    ------
  #1 manusheel      Manusheel Gupta    manu.pub
(attached)            manu<at>laptop<dot>org

  #2                       Dan Bricklin            dan.pub
(attached)               danb<at>bricklin<dot>com
  #3                       Luke Closs             luke.pub (attached)
            luke<dot>closs<at>socialtext<dot>com

  #4                       K.S. Preeti             preeti.pub
(attached)            kspreeti<dot>13<at>gmail<dot>com

     ...

  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. Translation
  [X] Set up the laptop.org Pootle server to allow translation commits to be
made
  [ ] Translation arrangements have already been made at _______________


12. Notes/Comments

      The first version of the activity is available to download from
http://www.socialtext.net/socialcalcxo/index.cgi?sweet_socialcalc .

     XOCom will help us in our efforts to motivate the JS developers'
community to develop activities for the XO.


Regards,
Manu
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.laptop.org/pipermail/devel/attachments/20080713/91154386/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: manu.pub
Type: application/vnd.ms-publisher
Size: 413 bytes
Desc: not available
URL: <http://lists.laptop.org/pipermail/devel/attachments/20080713/91154386/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: dan.pub
Type: application/vnd.ms-publisher
Size: 410 bytes
Desc: not available
URL: <http://lists.laptop.org/pipermail/devel/attachments/20080713/91154386/attachment-0001.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: luke.pub
Type: application/vnd.ms-publisher
Size: 229 bytes
Desc: not available
URL: <http://lists.laptop.org/pipermail/devel/attachments/20080713/91154386/attachment-0002.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: preeti.pub
Type: application/vnd.ms-publisher
Size: 226 bytes
Desc: not available
URL: <http://lists.laptop.org/pipermail/devel/attachments/20080713/91154386/attachment-0003.bin>