Re: Help for the Log4cxx podling

I have to point out that all of this is exactly why the project moved to the incubator from the logging project. While all the logging projects are obviously related by what they do, the language and implementation differences make it difficult for committers to cross over from one project to

Re: Help for the Log4cxx podling

On Fri, Jan 8, 2016 at 10:19 AM, Thorsten Schöning wrote: > Guten Tag William A Rowe Jr, > am Freitag, 8. Januar 2016 um 15:33 schrieben Sie: > > > Forty forks means 40 prospective committers. > > Or just people, like some of those currently involved, which change > things

Re: Help for the Log4cxx podling

Have no fear, we can extract all history from the svn repo. I don't know what approach you used, such that your IP was auto-banned, but that can be solved. We've done this before. So: please don't worry about that, within this discussion. On Jan 8, 2016 1:11 PM, "Thorsten Schöning"

Re: Help for the Log4cxx podling

On Fri, Jan 8, 2016 at 6:06 PM Dennis E. Hamilton wrote: > [not cross-posting] > Just curious - but why? The hope is to collaborate between the two groups to get a consensus. > > If there is a read-only GitHub mirror of the in-attic SVN repository > subtree, will that

RE: Help for the Log4cxx podling

[not cross-posting] If there is a read-only GitHub mirror of the in-attic SVN repository subtree, will that provide enough history for you? Or would you actually require a (compressed) dump of the read-only SVN repository subtree (not the entire ASF subversion), assuming Apache Infra could

Re: Help for the Log4cxx podling

Guten Tag William A Rowe Jr, am Freitag, 8. Januar 2016 um 19:18 schrieben Sie: > I'm trying to understand whether we are looking at a cultural refusal to > ever put a post in the stand and say "this is a release, there will be other > releases, but this is our release as of now"? Or is this

RE: Help for the Log4cxx podling

Ament [mailto:johndam...@apache.org] > Sent: Friday, January 8, 2016 17:14 > To: general@incubator.apache.org; dennis.hamil...@acm.org; > tschoen...@am-soft.de > Subject: Re: Help for the Log4cxx podling > > On Fri, Jan 8, 2016 at 6:06 PM Dennis E. Hamilton > <dennis.hamil...@acm.o

RE: Help for the Log4cxx podling

As a user (and small time contributor once) of log4cxx, I would vote for a move to a central hosting on github. I don't mind what happens to the project in terms of the apache organization as I use log4cxx as a stand-alone library - and I guess many others use log4cxx in the same fashion.

Re: Help for the Log4cxx podling

On Fri, Jan 8, 2016 at 3:31 AM, wrote: > As a user (and small time contributor once) of log4cxx, I would vote for a > move to a central hosting on github. I don't mind what happens to the > project in terms of the apache organization as I use log4cxx as a >

Re: Help for the Log4cxx podling

Guten Tag William A Rowe Jr, am Freitag, 8. Januar 2016 um 15:33 schrieben Sie: > Forty forks means 40 prospective committers. Or just people, like some of those currently involved, which change things once in a while because of bugs or such. I'm always just happy if my fixes are simply merged

RE: Help for the Log4cxx podling

y 8, 2016 08:20 > To: general@incubator.apache.org > Cc: log4cxx-...@logging.apache.org > Subject: Re: Help for the Log4cxx podling > [ ... ] > The problem and difference to GitHub I see now with the Attic is, that > you have a huge, centralized SVN repo, which is very hard to clo

Re: Help for the Log4cxx podling

On Thu, Jan 7, 2016 at 6:32 AM Rhys Ulerich wrote: > > It doesn't look like there's other members still around > > I'm still lurking but have not touched the code for awhile. > > It is, and has been, unclear what needs to happen for a 0.11.0 release > candidate [1].

Re: Help for the Log4cxx podling

Guten Tag Greg Stein, am Donnerstag, 7. Januar 2016 um 13:31 schrieben Sie: > ps. as ALv2 source, of course anybody willing can clone it elsewhere, but > may need to change the name. What I meant was to let @infra create one official/original/whatever git repo/mirror containing the current

Re: Help for the Log4cxx podling

On Thu, Jan 7, 2016 at 6:16 AM, John D. Ament wrote: > ... > Your lack of mentors is probably the biggest issue on the incubator side. > Without mentors, you have no one to steer you through graduation. Though > Marvin raises a good point - you're coming from an existing

Re: Help for the Log4cxx podling

Guten Tag Roberta Marton, am Donnerstag, 7. Januar 2016 um 17:14 schrieben Sie: > Just curious. The product I work on, Apache Trafodion, uses log4cxx. If the > incubator goes to the "Attic", what does that mean to products that are > using the code? No development of any kind, I think of it as

Re: Help for the Log4cxx podling

Guten Tag Rhys Ulerich, am Donnerstag, 7. Januar 2016 um 18:22 schrieben Sie: > Any chance apr-util could pick up the torch? That would at least centralize > it as anyone needing log4cxx needs apr-util. And who would get commit access then, would we be able to keep ours? I doubt it. The traffic

Re: Help for the Log4cxx podling

Guten Tag Marvin Humphrey, am Donnerstag, 7. Januar 2016 um 18:57 schrieben Sie: > If you can't make a release, you're dead enough for the Attic. According to the logs, the former maintainer Curt Arnold didn't release for years as well after the project moved to Apache and nevertheless provided

Re: Help for the Log4cxx podling

On Mon, Jan 4, 2016 at 5:37 PM, John D. Ament wrote: > Hi all, > > I happened to stumble upon the log4cxx mailing list where there is concern > over mentor participation. It appears that they may need help, more mentor > participation to help get reports through. > >

Re: Help for the Log4cxx podling

Hi John, thanks for the warning. Just saw the thread between Thorsten and you on the mailing list. Let me try to take a look tomorrow. Maybe we can talk together directly tomorrow, wdyt ? Regards JB On 01/05/2016 02:37 AM, John D. Ament wrote: Hi all, I happened to stumble upon the

Help for the Log4cxx podling

Hi all, I happened to stumble upon the log4cxx mailing list where there is concern over mentor participation. It appears that they may need help, more mentor participation to help get reports through. They're a small podling, so I'm wondering if there's ways to help them out? It seems like