Cliff Schmidt wrote:
> I definitely don't think the PPMC should lower the standard
> for commit access
But the flip side of that, particularly with active management by the
(P)PMC, is what standards should be applied by the Community? And how best
do we leverage source control?
That is a quite
Rodent of Unusual Size wrote:
> Participation is growing nicely, but the Derby
> PPMC is being careful not to hand out commit
> access like candy.
And the current PPMC discussions about learning how best to deal with Commit
karma is one of the things to learn, and learn to practice, in the
Incuba
On 4/22/05, Roy T. Fielding <[EMAIL PROTECTED]> wrote:
> The three independent committers rule is an absolute minimum
> based on the legal fact that US employees are required to be
> loyal to their full-time employer *even* when we know the people
> involved are beyond question, independently minde
On 4/22/05, Geir Magnusson Jr. <[EMAIL PROTECTED]> wrote:
> Maybe we should look for an additional metric for community health and
> diversity for next time. It could be in addition to the "rule of 3",
> but I think this example shows where we can improve things to help
> ensure healthy communiti
On Apr 22, 2005, at 9:33 PM, Roy T. Fielding wrote:
I have no doubt that Derby can and will reach that level soon
while staying inside the incubator. Meanwhile, continued moves
to give Derby special treatment are NOT APPROPRIATE.
I don't think that there is a move to give "special treatment", at
Brian Behlendorf wrote:
> If there really is still just one outside committer, then in my opinion
> the community has not yet passed that test; and rather than coding,
> those who care about that project should be advocating its existance to
> others, giving presentations at conferences,
Pity my
On Apr 22, 2005, at 11:55 AM, Brian Behlendorf wrote:
On Fri, 22 Apr 2005, Geir Magnusson Jr. wrote:
Well... the three committer rule is (although there are exceptions
for corner cases...), but we have a bit of dissonance between how we
are defining "independent committer" here
(http://incubato
On Fri, 22 Apr 2005, Geir Magnusson Jr. wrote:
Well... the three committer rule is (although there are exceptions for
corner cases...), but we have a bit of dissonance between how we are defining
"independent committer" here (http://incubator.apache.org/incubation/
Incubation_Policy.html#Minimu
Brian Behlendorf wrote:
It's not so much "dissonance" as an exception. In an incubating
project, the developers are usually new to the ASF, and skipped the
meritocracy step by virtue of association with the project before it
entered Apache ("here's the list of committers"). Therefore it's
reas
Roy T. Fielding wrote:
[snip]
> We have the same problems as Derby within the Jackrabbit project,
> though not only did we *start* with a far more diverse set of
> committers, we actively encouraged new folks to take responsibility
> for their own contributions. Nevertheless, it is quite clear to
On Apr 22, 2005, at 8:55 AM, Brian Behlendorf wrote:
It's not so much "dissonance" as an exception. In an incubating
project, the developers are usually new to the ASF, and skipped the
meritocracy step by virtue of association with the project before it
entered Apache ("here's the list of commi
On Fri, 22 Apr 2005, Brian Behlendorf wrote:
It's not so much "dissonance" as an exception. In an incubating
project, the developers are usually new to the ASF, and skipped the
meritocracy step by virtue of association with the project before it
entered Apache ("here's the list of committers"
On Apr 22, 2005, at 3:37 PM, Roy T. Fielding wrote:
Here's an idea -- how about encouraging a couple Derby developers
to participate in Jackrabbit (it is a database API after
all) and then convince some of the Jackrabbit developers to
participate on performance tuning Derby when used within a CMS.
On Apr 22, 2005, at 2:22 PM, Daniel John Debrunner wrote:
I personally don't see this problem with Derby, all Derby design
decisions seem to be happening on the list. So I'm not sure if
Jackrabbit and Derby have the same problems.
How can you know? I know the amount of progress that we are
making
On Apr 22, 2005, at 2:16 PM, Daniel John Debrunner wrote:
Pity my Derby internals proposal was rejected by Apachecon Europe :-)
Would you consider doing it as a BOF if you will be there? I would like
to attend it!
-Brian
-
To uns
On Apr 22, 2005, at 8:40 AM, Leo Simons wrote:
On 22-04-2005 13:47, "Geir Magnusson Jr." <[EMAIL PROTECTED]> wrote:
On Apr 18, 2005, at 12:59 PM, Cliff Schmidt wrote:
...
I'd love to see what some people think about the community - go look
at
the lists. That is what I looked at first, and it gav
-BEGIN PGP SIGNED MESSAGE-
Geir Magnusson Jr. wrote:
>
> I think it has a diverse community. However, I don't think we have any
> good way of measuring that, or if things like the following are
> quantitatively meaningful. We can look at dev mail list traffic, info
> taken from ey
On 22-04-2005 13:47, "Geir Magnusson Jr." <[EMAIL PROTECTED]> wrote:
> On Apr 18, 2005, at 12:59 PM, Cliff Schmidt wrote:
>> ...
> I'd love to see what some people think about the community - go look at
> the lists. That is what I looked at first, and it gave me confidence.
Derby seems to be doi
On Apr 18, 2005, at 12:59 PM, Cliff Schmidt wrote:
On 4/18/05, Rodent of Unusual Size <[EMAIL PROTECTED]> wrote:
-BEGIN PGP SIGNED MESSAGE-
Brian Behlendorf wrote:
Wouldn't "how can we increase the number of new developers on Derby
while
still in incubation" a better question to ask?
I th
On Mon, 2005-04-18 at 09:59 -0700, Cliff Schmidt wrote:
> On 4/18/05, Rodent of Unusual Size <[EMAIL PROTECTED]> wrote:
> > -BEGIN PGP SIGNED MESSAGE-
> >
> > Brian Behlendorf wrote:
> > >
> > > Wouldn't "how can we increase the number of new developers on Derby while
> > > still in incuba
On 4/18/05, Rodent of Unusual Size <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
>
> Brian Behlendorf wrote:
> >
> > Wouldn't "how can we increase the number of new developers on Derby while
> > still in incubation" a better question to ask?
>
> I think only if the answer to 'do
-BEGIN PGP SIGNED MESSAGE-
Brian Behlendorf wrote:
>
> Wouldn't "how can we increase the number of new developers on Derby while
> still in incubation" a better question to ask?
I think only if the answer to 'does Derby need more committers before
it can graduate' is 'yes.' Participati
On Fri, 15 Apr 2005, Rodent of Unusual Size wrote:
It appears that the committer issue is the only thing that is keeping
everyone from being in favour of Derby graduating. The committer base
has been expanded beyond the original IBM team by one, but progress
is being made to add more.
Does anyone
-BEGIN PGP SIGNED MESSAGE-
It appears that the committer issue is the only thing that is keeping
everyone from being in favour of Derby graduating. The committer base
has been expanded beyond the original IBM team by one, but progress
is being made to add more.
Does anyone think that the
Brian McCallister wrote:
Derby depends on nothing else at Apache (except ant for its build), and
is depended on by nothing else at Apache.
Let's not forget that the Derby codebase extends back to the dim dark
distant days of the 1990's before many of the ASF's Java projects even
existed.
More
To clarify my statement on project dependencies:
I think that Derby has already grown a large and diverse community
around itself, and that is important to consider as well. Projects
dependent upon derby, be they ASF or otherwise, have a significant
second-order effect on the project's truck num
JDO (currently incubating in Apache DB) uses Derby to validate the
implementation of JDO against relational databases.
Craig
On Apr 4, 2005, at 6:56 AM, Geir Magnusson Jr. wrote:
On Apr 3, 2005, at 11:51 AM, Brian McCallister wrote:
Derby depends on nothing else at Apache (except ant for its buil
On Mar 29, 2005, at 4:59 PM, Ted Leung wrote:
-1
I am surprised that people think the committer diversity issues are
not an issue for graduation.
As far as I can tell, the distribution of committers in Derby is worse
than either Xerces-J, or Xalan-J
both of which have been viewed negatively beca
On Apr 3, 2005, at 11:51 AM, Brian McCallister wrote:
Derby depends on nothing else at Apache (except ant for its build),
and is depended on by nothing else at Apache. This is *good* from a
technical point of view, but is a weakness from a community health
point of view.
Geronimo uses it.
--
Gei
On Monday 04 April 2005 08:50, Greg Stein wrote:
> Finally, I usually worry about PMC's oversight of sub-projects. If there
> is more than one developer list under a PMC, then you explicitly have
> partitioned communities. How is an existing PMC's community going to help
> grow another community if
On Sun, Apr 03, 2005 at 11:51:10AM -0400, Brian McCallister wrote:
> On Apr 3, 2005, at 11:02 AM, Rodent of Unusual Size wrote:
>
> >At least one person from the DB PMC has voted in favour of graduation,
> >which I hope means that the project understands the issues of
> >assuming oversight and fee
On Apr 3, 2005, at 11:02 AM, Rodent of Unusual Size wrote:
At least one person from the DB PMC has voted in favour of graduation,
which I hope means that the project understands the issues of
assuming oversight and feels comfortable doing so. Having more
people from the DB PMC/project weigh in on
-BEGIN PGP SIGNED MESSAGE-
Ted Leung wrote:
>
> -1
>
> I am surprised that people think the committer diversity issues are not
> an issue for graduation.
If Derby's destination was to be a TLP, I would agree completely,
and not even have started this. As it is, however, it's headed
to
Jim Jagielski wrote:
I vote -0. Ideally, a more diverse group of contributors
would alleviate concerns, or at least some plan of
action, post-graduation, which would address those
concerns.
There is a plan in place to do this which would continue after graduation.
There are currently several people
Noel J. Bergman wrote:
Actually, I agree with you, and others have expressed the same concern,
although without casting a vote. Adding new Committers is probably the #1
issue facing the Derby project, which has otherwise performed excellently to
date. As even Jeremy pointed out, were IBM to withd
I vote -0. Ideally, a more diverse group of contributors
would alleviate concerns, or at least some plan of
action, post-graduation, which would address those
concerns.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional com
On Mar 29, 2005, at 6:58 PM, Noel J. Bergman wrote:
Ted Leung wrote:
-1
I am surprised that people think the committer diversity
issues are not an issue for graduation.
Actually, I agree with you, and others have expressed the same concern,
although without casting a vote. Adding new Committers i
Ted Leung wrote:
> -1
> I am surprised that people think the committer diversity
> issues are not an issue for graduation.
Actually, I agree with you, and others have expressed the same concern,
although without casting a vote. Adding new Committers is probably the #1
issue facing the Derby pro
-1
I am surprised that people think the committer diversity issues are not
an issue for graduation.
As far as I can tell, the distribution of committers in Derby is worse
than either Xerces-J, or Xalan-J
both of which have been viewed negatively because of the number of
committers from a single
+1 now that Jeremy has addressed Roy's concerns.
On Mar 28, 2005, at 1:51 PM, Rodent of Unusual Size wrote:
-BEGIN PGP SIGNED MESSAGE-
As mentor, I feel comfortable proposing that Derby graduate from the
incubator and take up its place in the DB project. So I'd like
to start a formal vote
-BEGIN PGP SIGNED MESSAGE-
Roy T. Fielding wrote:
> Sorry, I'd like to vote for this, but someone was being cute
> and removed a lot of relevant questions from the template at
>
>http://incubator.apache.org/projects/derby.html
Actually, I don't think the above is the case at all; th
Roy T.Fielding wrote:
The incubator site uses Forrest, not Maven; most people just edit the
content under site-author and let someone else generate the real site.
True to form, I updated the content, added the project specific goals
and am leaving for someone else to generate the real site.
Pleas
Pardon my ignorance but where does this file live and do I have karma
to update it?
Any committer on an incubator project has karma
Information on how to make incubator site changes can be found at
http://incubator.apache.org/howtoparticipate.html
The incubator site uses Forrest, not Maven; most
Pardon my ignorance but where does this file live and do I have karma to
update it?
--
Jeremy
Roy T.Fielding wrote:
Sorry, I'd like to vote for this, but someone was being cute
and removed a lot of relevant questions from the template at
http://incubator.apache.org/projects/derby.html
and thus
Sorry, I'd like to vote for this, but someone was being cute
and removed a lot of relevant questions from the template at
http://incubator.apache.org/projects/derby.html
and thus I don't have the answers that the ASF needs. For
comparison, see the tables in
http://incubator.apache.org/projects
+1
- Alex
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-BEGIN PGP SIGNED MESSAGE-
As mentor, I feel comfortable proposing that Derby graduate from the
incubator and take up its place in the DB project. So I'd like
to start a formal vote on the issue.
- --
#kenP-)}
Ken Coar, Sanagendamgagwedweinini http://Ken.Coar.Org/
Author, developer,
47 matches
Mail list logo
