Project Hosting Application

Deepank Gupta deepankgupta at gmail.com
Mon Mar 24 13:14:48 EDT 2008


1. Project name               :    Educational Toolkit
2. Existing website, if any :
http://wiki.laptop.org/go/Educational_toolkit
3. One-line description     :    The educational toolkit aims at
facilitating discussion of problems among students and class and allow for
an automated way of conducting tests.

4. Longer description       :   The educational toolkit is a software to
facilitate discussion in classroom with the help of technology. It aims at
providing teachers and students with a tool to pose problems, compare and
discuss solutions by revolving the discussion around it in something known
as Demo Mode. It can provide flash cards and other objective and subjective
tests that can be used as a formal testing tool for class tests and quizzes
to provide a better gauge of a student's progress to the teacher.

5. URLs of similar projects :
                (HyperCard) http://en.wikipedia.org/wiki/HyperCard
                (Many custom Windows Based Free Software)
http://www.sheppardsoftware.com/teachers.htm

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 deepank    Deepank Gupta
http://www.nsitonline.in/it/students/2005/deepank/deepank.pub
deepankgupta at gmail.com
   #2 david         David Goulet          Attached along with
mail
david.goulet2 at usherbrooke.ca
   #3 ross          Ross Light
http://rlight2.googlepages.com/id_rsa.pub
                              rlight2 at gmail.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:

   [ ] 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
   later.

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
       notifications
   [X] 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:
Find more information at : http://wiki.laptop.org/go/Educational_toolkit and
at http://www.nsitonline.in/it/students/2005/deepank/projects.html
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.laptop.org/pipermail/devel/attachments/20080324/738954b4/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: david.pub
Type: application/octet-stream
Size: 601 bytes
Desc: not available
URL: <http://lists.laptop.org/pipermail/devel/attachments/20080324/738954b4/attachment.obj>


More information about the Devel mailing list