I like these two:

>> - perhaps provide a really low overhead type of lab where you don't
>> need a vote to accept it, create doap files, or update websites etc,
>> more like just an svn sandbox to hold some code

when i outlined my json component, I was not sure how much work I
could put into it. Feeling was, if you create a lab, you have to show
some committment for it. May it be true or not, it was my feeling.

>>  - allow releases. Just need to make sure its all clearly identified
>> as not an official ASF release.
>
> Any suggestions on how to "clearly identify as not"?

everybody can make a release out of asf code if he wishes.  I think
not using the word "apache" in the name would work out well. Having
the term "unofficial" in the release name would be another plus. For
example, if the lab is named Apache Lab Foo:

grobmeier-foo.zip
alab-unofficial-foo.zip

or something like that.

A notice file can hold the words: "Grobmeier Foo is based on Apache
Lab Foo. Apache Lab Foo is experimental code and not considered as
stable".

Announcement should not be spread through official channels, but
announced on the labs mailinglist

Christian

>
>
>>  - encourage the ASF GSoC students to do their projects here. There's
>> some discussion right now on code-awards@ about where students do
>> there work for the ASF projects and it sounds like currently most use
>> github
>
> I think that GSoC students have it difficult enough to work with a new
> environment even without the additional problems of the lab. Apart
> from that, they are better off in the same environment than their
> respective mentors.
>
>
> Jochen
>
>
>
> --
> I Am What I Am And That's All What I Yam (Popeye)
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>



-- 
http://www.grobmeier.de

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to