Project hosting request: xo-lambda

[Eben Eliason]

Agreed!  I have been secretly wanting to play around with lisp myself,
so I look forward to playing with this a lot.

As a small nitpick, I'd recommend dropping 'XO' from the name.  While
I just discovered that I omitted this detail while discussing naming
in the HIG, it doesn't really provide any useful information in the
activity name itself.  Moreover, since Sugar is quickly becoming
available on various distributions, it's incorrect to tie Sugar
activities to the XO itself, which is the name of the OLPC specific
hardware.

It would still be fine, of course, to refer to activities (especially
those that are brethren of applications already found on other OSes)
as, perhaps, "Sugar Lambda" to differentiate them in the public image,
but even then it doesn't seem necessary to include it in the activity
name itself. =)

- Eben

PS.  I'm somewhat unfamiliar with the project hosting process, but
would there be a good place to introduce this type of information, so
we can make things as simple as possible?  Should we just mention this
guideline/requirement on the wiki page
(http://wiki.laptop.org/go/Project_hosting) or the application? I
think the name is the only item on the application which needs to
adhere to a guideline.  However, we might link to the full HIG from
that page anyway, and/or include a link to it in the project hosting
response, to get budding developers pointed in the right direction.


On Wed, Sep 24, 2008 at 9:04 PM, Bobby Powers <bobbypowers at gmail.com> wrote:
> very cool!
>
> On Wed, Sep 24, 2008 at 7:26 PM, Antoine van Gelder
> <hummingbird at hivemind.net> wrote:
>> 1. Project name             : XO-Lambda
>> 2. Existing website, if any : http://wiki.laptop.org/go/XO-Lambda
>> 3. One-line description     : XO-Lambda is a simple Lisp interpreter
>> for the OLPC XO-1
>> 4. Longer description       : XO-Lambda is a simple Lisp interpreter
>> for the OLPC XO-1
>>                             : which aims to be both fun for the
>> beginning programmer as
>>                             : well as simple enough to yield it's
>> secrets to the curious
>>                             : student.
>>
>> 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 antoine  Antoine van Gelder      http://dev.laptop.org/~antoine/id_rsa.pub
>>        hummingbird at hivemind.net
>>    #2
>>    #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:
>>
>>    [ ] 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:
>> _______________________________________________
>> Devel mailing list
>> Devel at lists.laptop.org
>> http://lists.laptop.org/listinfo/devel
>>
> _______________________________________________
> Devel mailing list
> Devel at lists.laptop.org
> http://lists.laptop.org/listinfo/devel
>