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 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

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

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

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

Re: Help for the Log4cxx podling

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.

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