I just posted the answer comments to the reports wiki
(trinidad)
-M
On 3/26/07, Noel J. Bergman <[EMAIL PROTECTED]> wrote:
Justin Erenkrantz wrote:
> Noel J. Bergman wrote:
> > > what's the incentive for a project [to] push for diversity/graduation?
> > That's an appropriate and important ques
Justin Erenkrantz wrote:
> Noel J. Bergman wrote:
> > > what's the incentive for a project [to] push for diversity/graduation?
> > That's an appropriate and important question.
> They can release without the Incubator PMC looking over their
> shoulder? Less bureaucracy is probably appreciated.
W
Niclas Hedhman wrote:
> No community -> no releases ??
Minimal community != none. Lack of diversity != none. Lack of releases may
be viewed as blocking community development.
--- Noel
-
To unsubscribe, e-mail: [EMAI
On 3/18/07, Guillaume Nodet <[EMAIL PROTECTED]> wrote:
So the problem is
when a single company provides resources for a given
project. In such a case, other committers usually come from
the user community and this takes time. I think that
one of the goal of the podling should be to build a user
"Davanum Srinivas" <[EMAIL PROTECTED]> writes:
> Niclas,
>
> Here the scenario is a project with all committers from one employer
> and regular releases.
Then they shouldn't have regular releases. I think Niclas's
suggestions on community requirements for releases are fine,
particularly for podl
And zero incentive to ever graduate. The point is that we've taken
this position because an incubating project ISN'T permitted to operate
or publicize as an ASF Project.
It's accepted, but the podling is accepted provisionally. Abuse of the
Apache name results in ejection of the podling.
We see
On Mar 18, 2007, at 4:08 AM, Niclas Hedhman wrote:
Irregardless of that, the IPMC could stipulate that releases are
"final
stepping stones" towards graduation, and require an active and diverse
community to allow for releases. After all, it is the Incubator
that does the
release (legally)
On Sunday 18 March 2007 21:16, Guillaume Nodet wrote:
> I don't think this would be a good idea to not allow one podling
> to release anything.
See my disclaimer, that I think it is reasonable to allow 'limited' releases.
Point is to deter the 'coziness' and force graduation.
Cheers
Niclas
---
I don't think this would be a good idea to not allow one podling
to release anything.
Let me state my thoughts: the goal of a podling is to build
a lively and heterogeneous community to be able to graduate.
Usually, there is one or more company behind a project. If there
are more than one company,
On Saturday 17 March 2007 21:54, Davanum Srinivas wrote:
> On 3/17/07, Niclas Hedhman <[EMAIL PROTECTED]> wrote:
> > No community -> no releases ??
> Here the scenario is a project with all committers from one employer
> and regular releases.
Sorry, I don't fully follow. I thought you were speaki
Tuscany has issues though. When you look at active committers (at
least one commit in the last 3 months) it is a different picture: 14
from IBM and 3 from elsewhere (83%). Worse, there are modules where
no non-IBM committer has ever been active (e.g. Java/SDO, Java/DAS, C+
+/*).
--
Jeremy
Ant,
No, question is not about tuscancy. It's a general question as the
situation can arise in the future where someone is trying to game the
system.
thanks,
dims
On 3/17/07, ant elder <[EMAIL PROTECTED]> wrote:
<[EMAIL PROTECTED]>
On 3/17/07, Davanum Srinivas <[EMAIL PROTECTED]> wrote:
>
>
<[EMAIL PROTECTED]>
On 3/17/07, Davanum Srinivas <[EMAIL PROTECTED]> wrote:
Niclas,
Here the scenario is a project with all committers from one employer
and regular releases.
Are you talking about Tuscany still? Not all the Tuscany committers are from
the one employer. There's 25 committers
Niclas,
Here the scenario is a project with all committers from one employer
and regular releases.
-- dims
On 3/17/07, Niclas Hedhman <[EMAIL PROTECTED]> wrote:
On Friday 16 March 2007 19:46, Davanum Srinivas wrote:
> What are we going to do
> about projects that will show signs of life but wi
On Friday 16 March 2007 19:46, Davanum Srinivas wrote:
> What are we going to do
> about projects that will show signs of life but will remain in
> incubator for a very long time. when do we kick them out? 3 years? 5
> years?
No community -> no releases ??
Cheers
Niclas
Justin,
From previous experience as mentor, i can safely say that it is very
easy to push out releases by getting a few incubator pmc votes than it
is to attract new committers and more importantly keep them engaged.
Am afraid we are removing that incentive. What are we going to do
about projec
On 3/15/07, Noel J. Bergman <[EMAIL PROTECTED]> wrote:
> what's the incentive for a project [to] push for diversity/graduation?
That's an appropriate and important question.
They can release without the Incubator PMC looking over their
shoulder? Less bureaucracy is probably appreciated. -- j
Dims,
Let's focus this on the general part of your question:
> what's the incentive for a project [to] push for diversity/graduation?
That's an appropriate and important question.
--- Noel
-
To unsubscribe, e-mail: [E
On Mar 15, 2007, at 7:59 PM, Davanum Srinivas wrote:
Frank Question, Would your vote be the same if you thought Tuscany
would graduate very soon?
Yes, my vote has nothing to do with Tuscany. I'm actually pretty
ambivalent about the result and was voting more for consistency
across TLPs tha
Jeremy,
[I pulled this out from the vote thread, so that the vote thread is
not cluttered]
Frank Question, Would your vote be the same if you thought Tuscany
would graduate very soon? In other words, what's the incentive for a
project (full of committers from one employer) to push for
diversity/
20 matches
Mail list logo
