You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4cxx-dev@logging.apache.org by Curt Arnold <ca...@apache.org> on 2005/04/29 19:10:20 UTC
Call for developers (Re: Recent updates)
On Apr 29, 2005, at 10:59 AM, Ceki Gülcü wrote:
>
> Curt,
>
> It is nice to see that you are making progress on log4cxx. One of the
> promises that we made to the ASF when log4cxx graduated from the
> incubator was to increase the committer base of log4cxx. Have you
> taken steps to enlarge the committer base for log4cxx? What are your
> plans regarding this matter?
>
> Please keep me posted so that I can include your input in my report to
> the Board.
>
I was aware it was a concern at graduation, but I was not aware that
any promises have been made. I'm definitely open to contributions and
additional committers. Consider the rest of the message as a step to
enlarge the committer base.
Definitions of ASF Roles:
http://www.apache.org/foundation/how-it-works.html#roles
We seem to have a fairly healthy user base, the users mailing list has
146 subscribers, the dev list 66 (roughly 6 of each are mailing list
archivers).
The following people have submitted patches (if I missed someone speak
up), would be considered a "developer" and therefore could be
considered for promotion to "committer".
Andreas Fester: Port of telnet appender to APR network io
Ingo Lütkebohle: Configuration patch
Daniel Einspanjer: NTEventLog privilege fix
Christopher Smith: logstream proposals
Tommi Mäkitalo: thread id patch
We could definitely use someone to own autoconf builds and release
management and may attempt to recruit someone from another Apache C++
project particularly for the next release.
So if anyone is interested in having a cool @apache.org mail address
and all the fame (little) and money (none) that come with being an ASF
committer, submit patches to new or existing bug reports if you haven't
already done so, read the Contributor License Agreement
(http://www.apache.org/licenses/#clas) and determine if you'd be able
to sign one, and speak up and let us know how you would see yourself
contributing to log4cxx. If your involvement and interest speaks well
for you, then one of the existing Logging PMC members can nominate you
to the full PMC for a vote.
Re: Call for developers (Re: Recent updates)
Posted by Tommi Mäkitalo <to...@epgmbh.de>.
Hi,
I'm still alive;-) And yes - I would like to help. I once signed and faxed
already a CLA (if I remember right I used another e-mail-address
tommi@tntnet.org).
I was busy in other projects, but I can spend more time for log4cxx now. I
would love to see aa active c++-logging library and log4cxx is the best I
have seen.
Tommi
Am Freitag, 29. April 2005 20:42 schrieb Curt Arnold:
> On Apr 29, 2005, at 12:30 PM, Ceki Gülcü wrote:
> > The 3+ active committer should not come as a surprise. Having 3+
> > active committers has always been a requirement for graduation. There
> > are numerous discussions of this rule in the general@incubator mailing
> > list. The Incubator PMC made several remarks regarding log4cxx's
> > committer base when we asked for its graduation. The went along under
> > the assumption that the committer base eventually seek to increase the
> > number of committers.
> >
> > Why don't you start by nominating the current developers, namely
> >
> > Andreas Fester
> > Ingo Lütkebohle
> > Daniel Einspanjer
> > Christopher Smith
> > Tommi Mäkitalo
> >
> > Given the liberal nature of the Contributor License Agreement, it is
> > rarely (if ever) a hurdle.
>
> I definitely could be concerned if I had to take the CLA to my
> employer's legal department. Especially if I felt that I needed to
> have my employer sign off on a Corporate CLA.
>
> I tried to list everyone who has contributed a non-trivial patch since
> JIRA was started. I did not attempt to filter the list by whether the
> developer was currently active on the mailing list or make any judgment
> whether I would support them as a committer. Barring special
> circumstances, the next log4cxx committer would likely come from the
> universe of people who have submitted patches.
>
> If they have no current interest in contributing to log4cxx, it does
> the project no good to promote an inactive developer to an inactive
> committer.
>
> If the individuals don't respond to this thread in the next few days,
> I'll send personal emails to follow up. But unless someone is
> interested and can sign the CLA, there is no reason to call a vote on
> them.
>
> Lets say by next Friday, I will either nominate one or more people or
> given an explanation to the PMC.
Re: Call for developers (Re: Recent updates)
Posted by Ceki Gülcü <ce...@qos.ch>.
The Corporate CLA is intended for very large corporate contributors who
come to Apache with dozens of developers. If a developer can contribute to
the ASF, then the CLA is *never* a problem from the developer's point of
view. To the best of my knowledge, in the years I've been at Apache, no
committer refused to sign it, not one. The real question is whether the
developer's employer allows him/her to contribute.
Usually, one first nominates committers and check whether they are
interested. We worry about the CLA at the end of the process. We don't want
to unnecessarily scare away potential committers for the fun of it, or do we?
You don't need to have 3 active committers by next Friday. However, you
should really have a plan to increase the number of committers in log4cxx
and follow it through.
At 20:42 4/29/2005, you wrote:
>On Apr 29, 2005, at 12:30 PM, Ceki Gülcü wrote:
>
>>
>>The 3+ active committer should not come as a surprise. Having 3+
>>active committers has always been a requirement for graduation. There
>>are numerous discussions of this rule in the general@incubator mailing
>>list. The Incubator PMC made several remarks regarding log4cxx's
>>committer base when we asked for its graduation. The went along under
>>the assumption that the committer base eventually seek to increase the
>>number of committers.
>>
>>Why don't you start by nominating the current developers, namely
>>
>> Andreas Fester
>> Ingo Lütkebohle
>> Daniel Einspanjer
>> Christopher Smith
>> Tommi Mäkitalo
>>
>>Given the liberal nature of the Contributor License Agreement, it is
>>rarely (if ever) a hurdle.
>
>I definitely could be concerned if I had to take the CLA to my employer's
>legal department. Especially if I felt that I needed to have my employer
>sign off on a Corporate CLA.
>
>I tried to list everyone who has contributed a non-trivial patch since
>JIRA was started. I did not attempt to filter the list by whether the
>developer was currently active on the mailing list or make any judgment
>whether I would support them as a committer. Barring special
>circumstances, the next log4cxx committer would likely come from the
>universe of people who have submitted patches.
>
>If they have no current interest in contributing to log4cxx, it does the
>project no good to promote an inactive developer to an inactive committer.
>
>If the individuals don't respond to this thread in the next few days, I'll
>send personal emails to follow up. But unless someone is interested and
>can sign the CLA, there is no reason to call a vote on them.
>
>Lets say by next Friday, I will either nominate one or more people or
>given an explanation to the PMC.
--
Ceki Gülcü
The complete log4j manual: http://www.qos.ch/log4j/
Re: Call for developers (Re: Recent updates)
Posted by Curt Arnold <ca...@apache.org>.
On Apr 29, 2005, at 12:30 PM, Ceki Gülcü wrote:
>
> The 3+ active committer should not come as a surprise. Having 3+
> active committers has always been a requirement for graduation. There
> are numerous discussions of this rule in the general@incubator mailing
> list. The Incubator PMC made several remarks regarding log4cxx's
> committer base when we asked for its graduation. The went along under
> the assumption that the committer base eventually seek to increase the
> number of committers.
>
> Why don't you start by nominating the current developers, namely
>
> Andreas Fester
> Ingo Lütkebohle
> Daniel Einspanjer
> Christopher Smith
> Tommi Mäkitalo
>
> Given the liberal nature of the Contributor License Agreement, it is
> rarely (if ever) a hurdle.
>
I definitely could be concerned if I had to take the CLA to my
employer's legal department. Especially if I felt that I needed to
have my employer sign off on a Corporate CLA.
I tried to list everyone who has contributed a non-trivial patch since
JIRA was started. I did not attempt to filter the list by whether the
developer was currently active on the mailing list or make any judgment
whether I would support them as a committer. Barring special
circumstances, the next log4cxx committer would likely come from the
universe of people who have submitted patches.
If they have no current interest in contributing to log4cxx, it does
the project no good to promote an inactive developer to an inactive
committer.
If the individuals don't respond to this thread in the next few days,
I'll send personal emails to follow up. But unless someone is
interested and can sign the CLA, there is no reason to call a vote on
them.
Lets say by next Friday, I will either nominate one or more people or
given an explanation to the PMC.
Re: Call for developers (Re: Recent updates)
Posted by Ceki Gülcü <ce...@qos.ch>.
The 3+ active committer should not come as a surprise. Having 3+
active committers has always been a requirement for graduation. There
are numerous discussions of this rule in the general@incubator mailing
list. The Incubator PMC made several remarks regarding log4cxx's
committer base when we asked for its graduation. The went along under
the assumption that the committer base eventually seek to increase the
number of committers.
Why don't you start by nominating the current developers, namely
Andreas Fester
Ingo Lütkebohle
Daniel Einspanjer
Christopher Smith
Tommi Mäkitalo
Given the liberal nature of the Contributor License Agreement, it is
rarely (if ever) a hurdle.
At 19:10 4/29/2005, Curt Arnold wrote:
>On Apr 29, 2005, at 10:59 AM, Ceki Gülcü wrote:
>
>>
>>Curt,
>>
>>It is nice to see that you are making progress on log4cxx. One of the
>>promises that we made to the ASF when log4cxx graduated from the
>>incubator was to increase the committer base of log4cxx. Have you
>>taken steps to enlarge the committer base for log4cxx? What are your
>>plans regarding this matter?
>>
>>Please keep me posted so that I can include your input in my report to
>>the Board.
>
>
>
>I was aware it was a concern at graduation, but I was not aware that any
>promises have been made. I'm definitely open to contributions and
>additional committers. Consider the rest of the message as a step to
>enlarge the committer base.
>
>Definitions of ASF Roles:
>http://www.apache.org/foundation/how-it-works.html#roles
>
>We seem to have a fairly healthy user base, the users mailing list has 146
>subscribers, the dev list 66 (roughly 6 of each are mailing list archivers).
>
>The following people have submitted patches (if I missed someone speak
>up), would be considered a "developer" and therefore could be considered
>for promotion to "committer".
>
>Andreas Fester: Port of telnet appender to APR network io
>Ingo Lütkebohle: Configuration patch
>Daniel Einspanjer: NTEventLog privilege fix
>Christopher Smith: logstream proposals
>Tommi Mäkitalo: thread id patch
>
>We could definitely use someone to own autoconf builds and release
>management and may attempt to recruit someone from another Apache C++
>project particularly for the next release.
>
>So if anyone is interested in having a cool @apache.org mail address and
>all the fame (little) and money (none) that come with being an ASF
>committer, submit patches to new or existing bug reports if you haven't
>already done so, read the Contributor License Agreement
>(http://www.apache.org/licenses/#clas) and determine if you'd be able to
>sign one, and speak up and let us know how you would see yourself
>contributing to log4cxx. If your involvement and interest speaks well for
>you, then one of the existing Logging PMC members can nominate you to the
>full PMC for a vote.
--
Ceki Gülcü
The complete log4j manual: http://www.qos.ch/log4j/