RE: Help for the Log4cxx podling

2016-01-08 Thread ulrik.pedersen
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. Howeve

AW: Help for the Log4cxx podling

2016-01-08 Thread Wiebesiek, Torsten
Hello log4cxx community, here's another one against the Attic. :-) log4cxx is used and needed even though the community is not very large. Actually, the community has never has been very large, and this hasn't been a problem before, when only Curt Arnold maintained the project. Including log4c

Re: Help for the Log4cxx podling

2016-01-08 Thread Thorsten Schöning
Guten Tag Wiebesiek, Torsten, am Freitag, 8. Januar 2016 um 11:16 schrieben Sie: > I am not familiar with the Apache requirements for a project. From > what I understand, there have to be reports filed every three month. > What else? How can we proceed with the limited resources, we have? The rep

Re: Help for the Log4cxx podling

2016-01-08 Thread Wiebesiek, Torsten
Hi, > I am not familiar with the Apache requirements for a project. From > what I understand, there have to be reports filed every three month. > What else? How can we proceed with the limited resources, we have? > The reports every 3 months shouldn't be a big problem, but you need > to do e.g.

Build tools discussion

2016-01-08 Thread Thorsten Schöning
Guten Tag Wiebesiek, Torsten, am Freitag, 8. Januar 2016 um 13:28 schrieben Sie: > log4cxx need one well documented cross platform build process. From my experience such a thing doesn't exist. I can't remember ANY of my used OSS projects using ANY build tool promising cross platform support witho

Re: Help for the Log4cxx podling

2016-01-08 Thread William A Rowe Jr
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 > stand-alone library - and I guess many

Re: Help for the Log4cxx podling

2016-01-08 Thread Thorsten Schöning
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 wi

Re: Help for the Log4cxx podling

2016-01-08 Thread William A Rowe Jr
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 once in a while because

Re: Help for the Log4cxx podling

2016-01-08 Thread Thorsten Schöning
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 simp

Re: Help for the Log4cxx podling

2016-01-08 Thread Greg Stein
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" wrote: > Gute

Re: Help for the Log4cxx podling

2016-01-08 Thread William A Rowe Jr
On Fri, Jan 8, 2016 at 1:10 PM, Thorsten Schöning wrote: > 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 >