On 27/05/2011 08:25, ant elder wrote:
On Fri, May 27, 2011 at 8:01 AM, Jochen Wiedmann
<[email protected]>  wrote:
On Fri, May 27, 2011 at 8:48 AM, ant elder<[email protected]>  wrote:

...

  - provide access to non-existing ASF people. Perhaps something like
as long as there is an ASF committer initially creating the lab then
they can get non-asf people access to participate.

Difficult. Violates a standard ASF policy.  My guess is that the'd
need at least to sign the standard CLA, which is basically the same
hurdle than accepting them as committers.


I don't see any policy violations, as you say the new person submits a
CLA and then the Labs PMC votes them as a committer. Where's the
issue? The point is to make it known that its an available and easy
option. The last lab created was monsoon and that has now moved out to
google code for exactly this reason that a non-existing ASF committer
couldn't participate here.

The whole point of labs, when it was created, was that it was not another hosting environment for all comers. It was the provision of infrastructure for committers to play around with stuff.

Changing this would mean changing the whole purpose of labs, it would no longer be labs.

...

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


So as this option isn't available yet instead they're doing it out of
the ASF at places like github. How is that better?

It isn't and this is not encourage (but it does happen in a small number of cases).

Ross


--
[email protected]
@rgardler

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

Reply via email to