Project hosting request: xo-lambda

Thu Sep 25 07:48:40 EDT 2008

On Wed, Sep 24, 2008 at 9:04 PM, Bobby Powers <bobbypowers at gmail.com>  
wrote:
> very cool!

On 25 Sep 2008, at 04:10, Eben Eliason wrote:
> Agreed!  I have been secretly wanting to play around with lisp myself,
> so I look forward to playing with this a lot.

*grin*

Tx guys!

> 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. =)

Good points, thank you Eben.

Lambda activity it is!

Shall I resubmit a hosting request with the name change ?

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

I would have caught it if it was mentioned on the Project_hosting wiki  
page.

  - a

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.laptop.org/pipermail/devel/attachments/20080925/a36a766e/attachment.html>