Read ETexts Activity

Henry Hardy hhardy01 at
Thu Feb 28 15:45:09 EST 2008

Mr. Simmons,

I regret I have not seen your hosting request until now because the
subject line under which you submitted it did not indicate that it was
such a request. The usual way of requesting a hosting via the devel
list would be to submit it with a subject line such as, "Activity
hosting application: Read".

Now that I have seen your request, I am still as yet unable to process
it as you omitted your ssh public key from your application, listing
"?" instead.

Your application as I have seen it follows:

1. Project name             : Read ETexts Activity
2. Existing website, if any : None
3. One-line description     : A simple Python Activity for reading
Gutenberg etexts

4. Longer description       : This will be a fairly trivial activity that allows
                            : paging through Gutenberg etexts.  It will support
                            : reading text files (loaded from a USB device) or
                            : Zip files containing a single text file (which is
                            : the easiest format to download to the
Journal using
                            : the Browse activity).  It will have a
user interface
                            : quite similar to the Read activity, and
will support
                            : most of the functions of that activity except it
                            : will support plain text files instead of PDFs.

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 jdsimmons  James Simmons         ?
ja.simmons 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 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

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

12. Notes/comments:  Since the toolbar will be adapted from the Read
toolbar I should
   be able to use the same translations.  Also, since the activity
will be simple
   and entirely in Python it might be good sample code for new
Activity developers
   to look at.  The memory requirements of the Activity will be very
low, because
   I'm building a list of pointers to where each page begins rather than storing
   the document in memory.

Henry Edward Hardy
henry at

More information about the Devel mailing list