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 "John D. Ament" <jo...@apache.org> on 2017/04/06 03:19:09 UTC
Re: [RESULT][VOTE] Return Log4cxx to the Logging Services project
Ralph,
Have you completed the process? I see log4cxx is still listed as active in
the incubator records.
John
On Thu, Mar 16, 2017 at 10:45 PM Ralph Goers <ra...@dslextreme.com>
wrote:
> This vote has been open for more than 5 days. It received 5 +1 votes and
> no other votes. So we will begin the process of moving the project back to
> Logging Services.
>
> Ralph
>
> > On Mar 11, 2017, at 10:31 AM, Ralph Goers <ra...@dslextreme.com>
> wrote:
> >
> > Log4cxx was originally a sub-project of the Logging Services. In 2013
> several users became frustrated that they were submitting patches but there
> were no committers who could apply them. The Logging Services PMC was not
> comfortable making them committers as that would have given them commit
> rights to all the Logging Services projects, which at that time were all
> hosted in Subversion. As a consequence Log4cxx became an incubator project
> in hopes those who had expressed interest would start actively contributing
> to the project. After 3 1/2 years this has not had the hoped for result,
> although it does have more activity than it did prior to entering the
> incubator.
> >
> > The Logging Services PMC believes there is no longer a point to having
> Log4cxx remain in the incubator. The one active committer on Log4cxx has
> been voted in as a Logging Services committer and the PMC has voted [1] to
> move the project back to Logging Services. This is a vote for the incubator
> to affirm that move.
> >
> > [] +1 Move the project back to Logging Services
> > [] +0 I don’t care where the project resides
> > [] -1 The project should remain in the incubator because …
> >
> >
> > [1]
> https://mail-search.apache.org/pmc/private-arch/logging-private/201703.mbox/browser
> <
> https://mail-search.apache.org/pmc/private-arch/logging-private/201703.mbox/browser
> >
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
Re: [RESULT][VOTE] Return Log4cxx to the Logging Services project
Posted by Ralph Goers <ra...@dslextreme.com>.
I don’t really know the answer to that.
Ralph
> On Apr 10, 2017, at 3:35 AM, Thorsten Schöning <ts...@am-soft.de> wrote:
>
> Guten Tag Ralph Goers,
> am Montag, 10. April 2017 um 01:12 schrieben Sie:
>
>> Yes, please go ahead.
>
> What happens to the former GIT mirror on GitHub? Should it be
> deactivated/deleted?
>
> 2 of the 3 PRs there have already been applied in the past and I asked
> the author of the most current third one to provided another PR
> against the new repo.
>
> https://github.com/apache/log4cxx
>
> Mit freundlichen Grüßen,
>
> Thorsten Schöning
>
> --
> Thorsten Schöning E-Mail: Thorsten.Schoening@AM-SoFT.de
> AM-SoFT IT-Systeme http://www.AM-SoFT.de/
>
> Telefon...........05151- 9468- 55
> Fax...............05151- 9468- 88
> Mobil..............0178-8 9468- 04
>
> AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
> AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
Re: [RESULT][VOTE] Return Log4cxx to the Logging Services project
Posted by Ralph Goers <ra...@dslextreme.com>.
I don’t really know the answer to that.
Ralph
> On Apr 10, 2017, at 3:35 AM, Thorsten Schöning <ts...@am-soft.de> wrote:
>
> Guten Tag Ralph Goers,
> am Montag, 10. April 2017 um 01:12 schrieben Sie:
>
>> Yes, please go ahead.
>
> What happens to the former GIT mirror on GitHub? Should it be
> deactivated/deleted?
>
> 2 of the 3 PRs there have already been applied in the past and I asked
> the author of the most current third one to provided another PR
> against the new repo.
>
> https://github.com/apache/log4cxx
>
> Mit freundlichen Grüßen,
>
> Thorsten Schöning
>
> --
> Thorsten Schöning E-Mail: Thorsten.Schoening@AM-SoFT.de
> AM-SoFT IT-Systeme http://www.AM-SoFT.de/
>
> Telefon...........05151- 9468- 55
> Fax...............05151- 9468- 88
> Mobil..............0178-8 9468- 04
>
> AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
> AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [RESULT][VOTE] Return Log4cxx to the Logging Services project
Posted by Thorsten Schöning <ts...@am-soft.de>.
Guten Tag Ralph Goers,
am Montag, 10. April 2017 um 01:12 schrieben Sie:
> Yes, please go ahead.
What happens to the former GIT mirror on GitHub? Should it be
deactivated/deleted?
2 of the 3 PRs there have already been applied in the past and I asked
the author of the most current third one to provided another PR
against the new repo.
https://github.com/apache/log4cxx
Mit freundlichen Grüßen,
Thorsten Schöning
--
Thorsten Schöning E-Mail: Thorsten.Schoening@AM-SoFT.de
AM-SoFT IT-Systeme http://www.AM-SoFT.de/
Telefon...........05151- 9468- 55
Fax...............05151- 9468- 88
Mobil..............0178-8 9468- 04
AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow
Re: [RESULT][VOTE] Return Log4cxx to the Logging Services project
Posted by Thorsten Schöning <ts...@am-soft.de>.
Guten Tag Ralph Goers,
am Montag, 10. April 2017 um 01:12 schrieben Sie:
> Yes, please go ahead.
What happens to the former GIT mirror on GitHub? Should it be
deactivated/deleted?
2 of the 3 PRs there have already been applied in the past and I asked
the author of the most current third one to provided another PR
against the new repo.
https://github.com/apache/log4cxx
Mit freundlichen Grüßen,
Thorsten Schöning
--
Thorsten Schöning E-Mail: Thorsten.Schoening@AM-SoFT.de
AM-SoFT IT-Systeme http://www.AM-SoFT.de/
Telefon...........05151- 9468- 55
Fax...............05151- 9468- 88
Mobil..............0178-8 9468- 04
AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [RESULT][VOTE] Return Log4cxx to the Logging Services project
Posted by Ralph Goers <ra...@dslextreme.com>.
Yes, please go ahead.
Ralph
> On Apr 9, 2017, at 3:06 PM, John D. Ament <jo...@apache.org> wrote:
>
> Ralph,
>
> It looks like most everything is done. If you don't get to it, I'll update the podlings.xml and content/projects/log4cxx2.xml file to reflect graduation status.
>
> John
>
> On Fri, Apr 7, 2017 at 1:10 AM Ralph Goers <ralph.goers@dslextreme.com <ma...@dslextreme.com>> wrote:
> Thanks for the info Greg!
>
> Ralph
>
> > On Apr 6, 2017, at 9:14 PM, Greg Stein <gstein@gmail.com <ma...@gmail.com>> wrote:
> >
> > On Thu, Apr 6, 2017 at 4:04 AM, Thorsten Schöning <tschoening@am-soft.de <ma...@am-soft.de> <mailto:tschoening@am-soft.de <ma...@am-soft.de>>> wrote:
> > >...
> > > and I am not quite sure what the process is to move
> > > from svn to git without losing history. I guess I will just create
> > > a Jira issue for infra and find out.
> >
> > From my understanding, a logging PMC needs to create the GIT repo:
> >
> > Yeup.
> >
> > >...
> > Additionally, the current SVN repo needs to be imported into a local
> > GIT repo and that import can than be pushed to the newly created at
> > Apache. Not sure where the SVN repo goes afterwards...
> >
> > The svn repo sticks around, and we just switch it to read-only (file an INFRA ticket when ready for that).
> >
> > In some former Mail, Matt thankfully offered to do the repo creation
> > and GIT import, but at least the import is something I could have a
> > look at myself as well. Shouldn't make any difference who pushes the
> > history in the end.
> >
> > Yes. The Logging community can run svn2git and tweak its operation until you have everything you want in the resulting (local) git repository. Once it all looks good, then push all of that history into the newly-created git-wip repository. (you may want to have INFRA disable commit emails during that push)
> >
> > Cheers,
> > Greg Stein
> > Infrastructure Administrator, ASF
> >
>
Re: [RESULT][VOTE] Return Log4cxx to the Logging Services project
Posted by Ralph Goers <ra...@dslextreme.com>.
Yes, please go ahead.
Ralph
> On Apr 9, 2017, at 3:06 PM, John D. Ament <jo...@apache.org> wrote:
>
> Ralph,
>
> It looks like most everything is done. If you don't get to it, I'll update the podlings.xml and content/projects/log4cxx2.xml file to reflect graduation status.
>
> John
>
> On Fri, Apr 7, 2017 at 1:10 AM Ralph Goers <ralph.goers@dslextreme.com <ma...@dslextreme.com>> wrote:
> Thanks for the info Greg!
>
> Ralph
>
> > On Apr 6, 2017, at 9:14 PM, Greg Stein <gstein@gmail.com <ma...@gmail.com>> wrote:
> >
> > On Thu, Apr 6, 2017 at 4:04 AM, Thorsten Schöning <tschoening@am-soft.de <ma...@am-soft.de> <mailto:tschoening@am-soft.de <ma...@am-soft.de>>> wrote:
> > >...
> > > and I am not quite sure what the process is to move
> > > from svn to git without losing history. I guess I will just create
> > > a Jira issue for infra and find out.
> >
> > From my understanding, a logging PMC needs to create the GIT repo:
> >
> > Yeup.
> >
> > >...
> > Additionally, the current SVN repo needs to be imported into a local
> > GIT repo and that import can than be pushed to the newly created at
> > Apache. Not sure where the SVN repo goes afterwards...
> >
> > The svn repo sticks around, and we just switch it to read-only (file an INFRA ticket when ready for that).
> >
> > In some former Mail, Matt thankfully offered to do the repo creation
> > and GIT import, but at least the import is something I could have a
> > look at myself as well. Shouldn't make any difference who pushes the
> > history in the end.
> >
> > Yes. The Logging community can run svn2git and tweak its operation until you have everything you want in the resulting (local) git repository. Once it all looks good, then push all of that history into the newly-created git-wip repository. (you may want to have INFRA disable commit emails during that push)
> >
> > Cheers,
> > Greg Stein
> > Infrastructure Administrator, ASF
> >
>
Re: [RESULT][VOTE] Return Log4cxx to the Logging Services project
Posted by "John D. Ament" <jo...@apache.org>.
Ralph,
It looks like most everything is done. If you don't get to it, I'll update
the podlings.xml and content/projects/log4cxx2.xml file to reflect
graduation status.
John
On Fri, Apr 7, 2017 at 1:10 AM Ralph Goers <ra...@dslextreme.com>
wrote:
> Thanks for the info Greg!
>
> Ralph
>
> > On Apr 6, 2017, at 9:14 PM, Greg Stein <gs...@gmail.com> wrote:
> >
> > On Thu, Apr 6, 2017 at 4:04 AM, Thorsten Schöning <tschoening@am-soft.de
> <ma...@am-soft.de>> wrote:
> > >...
> > > and I am not quite sure what the process is to move
> > > from svn to git without losing history. I guess I will just create
> > > a Jira issue for infra and find out.
> >
> > From my understanding, a logging PMC needs to create the GIT repo:
> >
> > Yeup.
> >
> > >...
> > Additionally, the current SVN repo needs to be imported into a local
> > GIT repo and that import can than be pushed to the newly created at
> > Apache. Not sure where the SVN repo goes afterwards...
> >
> > The svn repo sticks around, and we just switch it to read-only (file an
> INFRA ticket when ready for that).
> >
> > In some former Mail, Matt thankfully offered to do the repo creation
> > and GIT import, but at least the import is something I could have a
> > look at myself as well. Shouldn't make any difference who pushes the
> > history in the end.
> >
> > Yes. The Logging community can run svn2git and tweak its operation until
> you have everything you want in the resulting (local) git repository. Once
> it all looks good, then push all of that history into the newly-created
> git-wip repository. (you may want to have INFRA disable commit emails
> during that push)
> >
> > Cheers,
> > Greg Stein
> > Infrastructure Administrator, ASF
> >
>
>
Re: [RESULT][VOTE] Return Log4cxx to the Logging Services project
Posted by "John D. Ament" <jo...@apache.org>.
Ralph,
It looks like most everything is done. If you don't get to it, I'll update
the podlings.xml and content/projects/log4cxx2.xml file to reflect
graduation status.
John
On Fri, Apr 7, 2017 at 1:10 AM Ralph Goers <ra...@dslextreme.com>
wrote:
> Thanks for the info Greg!
>
> Ralph
>
> > On Apr 6, 2017, at 9:14 PM, Greg Stein <gs...@gmail.com> wrote:
> >
> > On Thu, Apr 6, 2017 at 4:04 AM, Thorsten Schöning <tschoening@am-soft.de
> <ma...@am-soft.de>> wrote:
> > >...
> > > and I am not quite sure what the process is to move
> > > from svn to git without losing history. I guess I will just create
> > > a Jira issue for infra and find out.
> >
> > From my understanding, a logging PMC needs to create the GIT repo:
> >
> > Yeup.
> >
> > >...
> > Additionally, the current SVN repo needs to be imported into a local
> > GIT repo and that import can than be pushed to the newly created at
> > Apache. Not sure where the SVN repo goes afterwards...
> >
> > The svn repo sticks around, and we just switch it to read-only (file an
> INFRA ticket when ready for that).
> >
> > In some former Mail, Matt thankfully offered to do the repo creation
> > and GIT import, but at least the import is something I could have a
> > look at myself as well. Shouldn't make any difference who pushes the
> > history in the end.
> >
> > Yes. The Logging community can run svn2git and tweak its operation until
> you have everything you want in the resulting (local) git repository. Once
> it all looks good, then push all of that history into the newly-created
> git-wip repository. (you may want to have INFRA disable commit emails
> during that push)
> >
> > Cheers,
> > Greg Stein
> > Infrastructure Administrator, ASF
> >
>
>
Re: [RESULT][VOTE] Return Log4cxx to the Logging Services project
Posted by Ralph Goers <ra...@dslextreme.com>.
Thanks for the info Greg!
Ralph
> On Apr 6, 2017, at 9:14 PM, Greg Stein <gs...@gmail.com> wrote:
>
> On Thu, Apr 6, 2017 at 4:04 AM, Thorsten Schöning <tschoening@am-soft.de <ma...@am-soft.de>> wrote:
> >...
> > and I am not quite sure what the process is to move
> > from svn to git without losing history. I guess I will just create
> > a Jira issue for infra and find out.
>
> From my understanding, a logging PMC needs to create the GIT repo:
>
> Yeup.
>
> >...
> Additionally, the current SVN repo needs to be imported into a local
> GIT repo and that import can than be pushed to the newly created at
> Apache. Not sure where the SVN repo goes afterwards...
>
> The svn repo sticks around, and we just switch it to read-only (file an INFRA ticket when ready for that).
>
> In some former Mail, Matt thankfully offered to do the repo creation
> and GIT import, but at least the import is something I could have a
> look at myself as well. Shouldn't make any difference who pushes the
> history in the end.
>
> Yes. The Logging community can run svn2git and tweak its operation until you have everything you want in the resulting (local) git repository. Once it all looks good, then push all of that history into the newly-created git-wip repository. (you may want to have INFRA disable commit emails during that push)
>
> Cheers,
> Greg Stein
> Infrastructure Administrator, ASF
>
Re: [RESULT][VOTE] Return Log4cxx to the Logging Services project
Posted by Ralph Goers <ra...@dslextreme.com>.
Thanks for the info Greg!
Ralph
> On Apr 6, 2017, at 9:14 PM, Greg Stein <gs...@gmail.com> wrote:
>
> On Thu, Apr 6, 2017 at 4:04 AM, Thorsten Schöning <tschoening@am-soft.de <ma...@am-soft.de>> wrote:
> >...
> > and I am not quite sure what the process is to move
> > from svn to git without losing history. I guess I will just create
> > a Jira issue for infra and find out.
>
> From my understanding, a logging PMC needs to create the GIT repo:
>
> Yeup.
>
> >...
> Additionally, the current SVN repo needs to be imported into a local
> GIT repo and that import can than be pushed to the newly created at
> Apache. Not sure where the SVN repo goes afterwards...
>
> The svn repo sticks around, and we just switch it to read-only (file an INFRA ticket when ready for that).
>
> In some former Mail, Matt thankfully offered to do the repo creation
> and GIT import, but at least the import is something I could have a
> look at myself as well. Shouldn't make any difference who pushes the
> history in the end.
>
> Yes. The Logging community can run svn2git and tweak its operation until you have everything you want in the resulting (local) git repository. Once it all looks good, then push all of that history into the newly-created git-wip repository. (you may want to have INFRA disable commit emails during that push)
>
> Cheers,
> Greg Stein
> Infrastructure Administrator, ASF
>
Re: [RESULT][VOTE] Return Log4cxx to the Logging Services project
Posted by Greg Stein <gs...@gmail.com>.
On Thu, Apr 6, 2017 at 4:04 AM, Thorsten Schöning <ts...@am-soft.de>
wrote:
>...
> > and I am not quite sure what the process is to move
> > from svn to git without losing history. I guess I will just create
> > a Jira issue for infra and find out.
>
> From my understanding, a logging PMC needs to create the GIT repo:
>
Yeup.
>...
> Additionally, the current SVN repo needs to be imported into a local
> GIT repo and that import can than be pushed to the newly created at
> Apache. Not sure where the SVN repo goes afterwards...
>
The svn repo sticks around, and we just switch it to read-only (file an
INFRA ticket when ready for that).
> In some former Mail, Matt thankfully offered to do the repo creation
> and GIT import, but at least the import is something I could have a
> look at myself as well. Shouldn't make any difference who pushes the
> history in the end.
>
Yes. The Logging community can run svn2git and tweak its operation until
you have everything you want in the resulting (local) git repository. Once
it all looks good, then push all of that history into the newly-created
git-wip repository. (you may want to have INFRA disable commit emails
during that push)
Cheers,
Greg Stein
Infrastructure Administrator, ASF
Re: [RESULT][VOTE] Return Log4cxx to the Logging Services project
Posted by Matt Sicker <bo...@gmail.com>.
I have to find the instructions again, but I think I posted them on the
commons dev mailing list. It's not too hard to do. After migrating the
repo, you also need to file an infra ticket to switch over the GitHub
mirror settings and other things.
On 6 April 2017 at 08:56, Ralph Goers <ra...@dslextreme.com> wrote:
>
> On Apr 6, 2017, at 2:04 AM, Thorsten Schöning <ts...@am-soft.de>
> wrote:
>
> Guten Tag Ralph Goers,
> am Donnerstag, 6. April 2017 um 07:10 schrieben Sie:
>
> No. To be honest, I’m not 100% sure if the community wants to move
> to git or not
>
>
> "We" want, as nobody objected in the discussion and Matts description
> of how to deal with GitHub PRs sounds very promising.
>
> and I am not quite sure what the process is to move
> from svn to git without losing history. I guess I will just create
> a Jira issue for infra and find out.
>
>
> From my understanding, a logging PMC needs to create the GIT repo:
>
> With the continued growth of git usage, a service was created to
> support creating new repositories for PMCs. It is a fully automated
> tool, eliminating any additional tickets. The tool can be found at
> https://reporeq.apache.org.
>
>
> https://git-wip-us.apache.org
>
>
> I know about the tool. I’ve used it a few times. I don’t know how to
> import from svn without losing history.
>
>
> Additionally, the current SVN repo needs to be imported into a local
> GIT repo and that import can than be pushed to the newly created at
> Apache. Not sure where the SVN repo goes afterwards…
>
>
> The above is the part I don’t know how to do.
>
> In some former Mail, Matt thankfully offered to do the repo creation
> and GIT import, but at least the import is something I could have a
> look at myself as well. Shouldn't make any difference who pushes the
> history in the end.
>
> As I didn't do such an import in the past yet, it might simply take
> some time. But there seem to be some good examples out there:
>
> http://stackoverflow.com/a/3972103/2055163
> https://github.com/nirvdrum/svn2git#readme
>
> I will (try to) look into the import itself at the weekend.
>
> Mit freundlichen Grüßen,
>
> Thorsten Schöning
>
>
>
> Ralph
>
--
Matt Sicker <bo...@gmail.com>
Re: [RESULT][VOTE] Return Log4cxx to the Logging Services project
Posted by Ralph Goers <ra...@dslextreme.com>.
> On Apr 6, 2017, at 2:04 AM, Thorsten Schöning <ts...@am-soft.de> wrote:
>
> Guten Tag Ralph Goers,
> am Donnerstag, 6. April 2017 um 07:10 schrieben Sie:
>
>> No. To be honest, I’m not 100% sure if the community wants to move
>> to git or not
>
> "We" want, as nobody objected in the discussion and Matts description
> of how to deal with GitHub PRs sounds very promising.
>
>> and I am not quite sure what the process is to move
>> from svn to git without losing history. I guess I will just create
>> a Jira issue for infra and find out.
>
> From my understanding, a logging PMC needs to create the GIT repo:
>
>> With the continued growth of git usage, a service was created to
>> support creating new repositories for PMCs. It is a fully automated
>> tool, eliminating any additional tickets. The tool can be found at
>> https://reporeq.apache.org.
>
> https://git-wip-us.apache.org <https://git-wip-us.apache.org/>
I know about the tool. I’ve used it a few times. I don’t know how to import from svn without losing history.
>
> Additionally, the current SVN repo needs to be imported into a local
> GIT repo and that import can than be pushed to the newly created at
> Apache. Not sure where the SVN repo goes afterwards…
>
The above is the part I don’t know how to do.
> In some former Mail, Matt thankfully offered to do the repo creation
> and GIT import, but at least the import is something I could have a
> look at myself as well. Shouldn't make any difference who pushes the
> history in the end.
>
> As I didn't do such an import in the past yet, it might simply take
> some time. But there seem to be some good examples out there:
>
> http://stackoverflow.com/a/3972103/2055163
> https://github.com/nirvdrum/svn2git#readme
>
> I will (try to) look into the import itself at the weekend.
>
> Mit freundlichen Grüßen,
>
> Thorsten Schöning
Ralph
Re: [RESULT][VOTE] Return Log4cxx to the Logging Services project
Posted by Greg Stein <gs...@gmail.com>.
On Thu, Apr 6, 2017 at 4:04 AM, Thorsten Schöning <ts...@am-soft.de>
wrote:
>...
> > and I am not quite sure what the process is to move
> > from svn to git without losing history. I guess I will just create
> > a Jira issue for infra and find out.
>
> From my understanding, a logging PMC needs to create the GIT repo:
>
Yeup.
>...
> Additionally, the current SVN repo needs to be imported into a local
> GIT repo and that import can than be pushed to the newly created at
> Apache. Not sure where the SVN repo goes afterwards...
>
The svn repo sticks around, and we just switch it to read-only (file an
INFRA ticket when ready for that).
> In some former Mail, Matt thankfully offered to do the repo creation
> and GIT import, but at least the import is something I could have a
> look at myself as well. Shouldn't make any difference who pushes the
> history in the end.
>
Yes. The Logging community can run svn2git and tweak its operation until
you have everything you want in the resulting (local) git repository. Once
it all looks good, then push all of that history into the newly-created
git-wip repository. (you may want to have INFRA disable commit emails
during that push)
Cheers,
Greg Stein
Infrastructure Administrator, ASF
Re: [RESULT][VOTE] Return Log4cxx to the Logging Services project
Posted by Thorsten Schöning <ts...@am-soft.de>.
Guten Tag Ralph Goers,
am Donnerstag, 6. April 2017 um 07:10 schrieben Sie:
> No. To be honest, I’m not 100% sure if the community wants to move
> to git or not
"We" want, as nobody objected in the discussion and Matts description
of how to deal with GitHub PRs sounds very promising.
> and I am not quite sure what the process is to move
> from svn to git without losing history. I guess I will just create
> a Jira issue for infra and find out.
From my understanding, a logging PMC needs to create the GIT repo:
> With the continued growth of git usage, a service was created to
> support creating new repositories for PMCs. It is a fully automated
> tool, eliminating any additional tickets. The tool can be found at
> https://reporeq.apache.org.
https://git-wip-us.apache.org
Additionally, the current SVN repo needs to be imported into a local
GIT repo and that import can than be pushed to the newly created at
Apache. Not sure where the SVN repo goes afterwards...
In some former Mail, Matt thankfully offered to do the repo creation
and GIT import, but at least the import is something I could have a
look at myself as well. Shouldn't make any difference who pushes the
history in the end.
As I didn't do such an import in the past yet, it might simply take
some time. But there seem to be some good examples out there:
http://stackoverflow.com/a/3972103/2055163
https://github.com/nirvdrum/svn2git#readme
I will (try to) look into the import itself at the weekend.
Mit freundlichen Grüßen,
Thorsten Schöning
--
Thorsten Schöning E-Mail: Thorsten.Schoening@AM-SoFT.de
AM-SoFT IT-Systeme http://www.AM-SoFT.de/
Telefon...........05151- 9468- 55
Fax...............05151- 9468- 88
Mobil..............0178-8 9468- 04
AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [RESULT][VOTE] Return Log4cxx to the Logging Services project
Posted by Thorsten Schöning <ts...@am-soft.de>.
Guten Tag Ralph Goers,
am Donnerstag, 6. April 2017 um 07:10 schrieben Sie:
> No. To be honest, I’m not 100% sure if the community wants to move
> to git or not
"We" want, as nobody objected in the discussion and Matts description
of how to deal with GitHub PRs sounds very promising.
> and I am not quite sure what the process is to move
> from svn to git without losing history. I guess I will just create
> a Jira issue for infra and find out.
From my understanding, a logging PMC needs to create the GIT repo:
> With the continued growth of git usage, a service was created to
> support creating new repositories for PMCs. It is a fully automated
> tool, eliminating any additional tickets. The tool can be found at
> https://reporeq.apache.org.
https://git-wip-us.apache.org
Additionally, the current SVN repo needs to be imported into a local
GIT repo and that import can than be pushed to the newly created at
Apache. Not sure where the SVN repo goes afterwards...
In some former Mail, Matt thankfully offered to do the repo creation
and GIT import, but at least the import is something I could have a
look at myself as well. Shouldn't make any difference who pushes the
history in the end.
As I didn't do such an import in the past yet, it might simply take
some time. But there seem to be some good examples out there:
http://stackoverflow.com/a/3972103/2055163
https://github.com/nirvdrum/svn2git#readme
I will (try to) look into the import itself at the weekend.
Mit freundlichen Grüßen,
Thorsten Schöning
--
Thorsten Schöning E-Mail: Thorsten.Schoening@AM-SoFT.de
AM-SoFT IT-Systeme http://www.AM-SoFT.de/
Telefon...........05151- 9468- 55
Fax...............05151- 9468- 88
Mobil..............0178-8 9468- 04
AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow
Re: [RESULT][VOTE] Return Log4cxx to the Logging Services project
Posted by Matt Sicker <bo...@gmail.com>.
Oh, so that's where the page is to change it back to infra! I was on the
helpdesk view which doesn't have much there.
On 6 April 2017 at 00:24, Ralph Goers <ra...@dslextreme.com> wrote:
> I created https://issues.apache.org/jira/browse/INFRA-13831 for the move
> from svn to git.
>
> Ralph
>
>
> On Apr 5, 2017, at 10:14 PM, Ralph Goers <ra...@dslextreme.com>
> wrote:
>
> I figured out how to see the issue - https://issues.apache.org/
> jira/browse/INFRA-13651 <https://issues.apache.org/jira/browse/INFRA-13651>.
> It seems it is in a status of waiting for user but the reporter has no way
> to kick it back to infra. It has been sitting there for over a week.
>
> Ralph
>
>
> On Apr 5, 2017, at 10:10 PM, Ralph Goers <ra...@dslextreme.com>
> wrote:
>
> No. To be honest, I’m not 100% sure if the community wants to move to git
> or not and I am not quite sure what the process is to move from svn to git
> without losing history. I guess I will just create a Jira issue for infra
> and find out.
>
> Also we have an outstanding infra request to combine all the logging dev
> lists but I don’t seem to have permission to view the status of it.
>
> Ralph
>
> On Apr 5, 2017, at 8:19 PM, John D. Ament <johndament@apache.org <
> mailto:johndament@apache.org <jo...@apache.org>>> wrote:
>
> Ralph,
>
> Have you completed the process? I see log4cxx is still listed as active
> in the incubator records.
>
> John
>
> On Thu, Mar 16, 2017 at 10:45 PM Ralph Goers <ralph.goers@dslextreme.com <
> mailto:ralph.goers@dslextreme.com <ra...@dslextreme.com>>> wrote:
> This vote has been open for more than 5 days. It received 5 +1 votes and
> no other votes. So we will begin the process of moving the project back to
> Logging Services.
>
> Ralph
>
> On Mar 11, 2017, at 10:31 AM, Ralph Goers <ralph.goers@dslextreme.com <
> mailto:ralph.goers@dslextreme.com <ra...@dslextreme.com>>> wrote:
>
> Log4cxx was originally a sub-project of the Logging Services. In 2013
> several users became frustrated that they were submitting patches but there
> were no committers who could apply them. The Logging Services PMC was not
> comfortable making them committers as that would have given them commit
> rights to all the Logging Services projects, which at that time were all
> hosted in Subversion. As a consequence Log4cxx became an incubator project
> in hopes those who had expressed interest would start actively contributing
> to the project. After 3 1/2 years this has not had the hoped for result,
> although it does have more activity than it did prior to entering the
> incubator.
>
> The Logging Services PMC believes there is no longer a point to having
> Log4cxx remain in the incubator. The one active committer on Log4cxx has
> been voted in as a Logging Services committer and the PMC has voted [1] to
> move the project back to Logging Services. This is a vote for the incubator
> to affirm that move.
>
> [] +1 Move the project back to Logging Services
> [] +0 I don’t care where the project resides
> [] -1 The project should remain in the incubator because …
>
>
> [1] https://mail-search.apache.org/pmc/private-arch/logging-
> private/201703.mbox/browser <https://mail-search.apache.
> org/pmc/private-arch/logging-private/201703.mbox/browser> <
> https://mail-search.apache.org/pmc/private-arch/logging-
> private/201703.mbox/browser <https://mail-search.apache.
> org/pmc/private-arch/logging-private/201703.mbox/browser>>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org <
> mailto:general-unsubscribe@incubator.apache.org
> <ge...@incubator.apache.org>>
> For additional commands, e-mail: general-help@incubator.apache.org <
> mailto:general-help@incubator.apache.org
> <ge...@incubator.apache.org>>
>
>
>
>
>
--
Matt Sicker <bo...@gmail.com>
Re: [RESULT][VOTE] Return Log4cxx to the Logging Services project
Posted by Ralph Goers <ra...@dslextreme.com>.
I created https://issues.apache.org/jira/browse/INFRA-13831 <https://issues.apache.org/jira/browse/INFRA-13831> for the move from svn to git.
Ralph
> On Apr 5, 2017, at 10:14 PM, Ralph Goers <ra...@dslextreme.com> wrote:
>
> I figured out how to see the issue - https://issues.apache.org/jira/browse/INFRA-13651 <https://issues.apache.org/jira/browse/INFRA-13651>. It seems it is in a status of waiting for user but the reporter has no way to kick it back to infra. It has been sitting there for over a week.
>
> Ralph
>
>
>> On Apr 5, 2017, at 10:10 PM, Ralph Goers <ra...@dslextreme.com> wrote:
>>
>> No. To be honest, I’m not 100% sure if the community wants to move to git or not and I am not quite sure what the process is to move from svn to git without losing history. I guess I will just create a Jira issue for infra and find out.
>>
>> Also we have an outstanding infra request to combine all the logging dev lists but I don’t seem to have permission to view the status of it.
>>
>> Ralph
>>
>>> On Apr 5, 2017, at 8:19 PM, John D. Ament <johndament@apache.org <ma...@apache.org>> wrote:
>>>
>>> Ralph,
>>>
>>> Have you completed the process? I see log4cxx is still listed as active in the incubator records.
>>>
>>> John
>>>
>>> On Thu, Mar 16, 2017 at 10:45 PM Ralph Goers <ralph.goers@dslextreme.com <ma...@dslextreme.com>> wrote:
>>> This vote has been open for more than 5 days. It received 5 +1 votes and no other votes. So we will begin the process of moving the project back to Logging Services.
>>>
>>> Ralph
>>>
>>>> On Mar 11, 2017, at 10:31 AM, Ralph Goers <ralph.goers@dslextreme.com <ma...@dslextreme.com>> wrote:
>>>>
>>>> Log4cxx was originally a sub-project of the Logging Services. In 2013 several users became frustrated that they were submitting patches but there were no committers who could apply them. The Logging Services PMC was not comfortable making them committers as that would have given them commit rights to all the Logging Services projects, which at that time were all hosted in Subversion. As a consequence Log4cxx became an incubator project in hopes those who had expressed interest would start actively contributing to the project. After 3 1/2 years this has not had the hoped for result, although it does have more activity than it did prior to entering the incubator.
>>>>
>>>> The Logging Services PMC believes there is no longer a point to having Log4cxx remain in the incubator. The one active committer on Log4cxx has been voted in as a Logging Services committer and the PMC has voted [1] to move the project back to Logging Services. This is a vote for the incubator to affirm that move.
>>>>
>>>> [] +1 Move the project back to Logging Services
>>>> [] +0 I don’t care where the project resides
>>>> [] -1 The project should remain in the incubator because …
>>>>
>>>>
>>>> [1] https://mail-search.apache.org/pmc/private-arch/logging-private/201703.mbox/browser <https://mail-search.apache.org/pmc/private-arch/logging-private/201703.mbox/browser> <https://mail-search.apache.org/pmc/private-arch/logging-private/201703.mbox/browser <https://mail-search.apache.org/pmc/private-arch/logging-private/201703.mbox/browser>>
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org <ma...@incubator.apache.org>
>>> For additional commands, e-mail: general-help@incubator.apache.org <ma...@incubator.apache.org>
>>>
>>
>
Re: [RESULT][VOTE] Return Log4cxx to the Logging Services project
Posted by Ralph Goers <ra...@dslextreme.com>.
I figured out how to see the issue - https://issues.apache.org/jira/browse/INFRA-13651 <https://issues.apache.org/jira/browse/INFRA-13651>. It seems it is in a status of waiting for user but the reporter has no way to kick it back to infra. It has been sitting there for over a week.
Ralph
> On Apr 5, 2017, at 10:10 PM, Ralph Goers <ra...@dslextreme.com> wrote:
>
> No. To be honest, I’m not 100% sure if the community wants to move to git or not and I am not quite sure what the process is to move from svn to git without losing history. I guess I will just create a Jira issue for infra and find out.
>
> Also we have an outstanding infra request to combine all the logging dev lists but I don’t seem to have permission to view the status of it.
>
> Ralph
>
>> On Apr 5, 2017, at 8:19 PM, John D. Ament <johndament@apache.org <ma...@apache.org>> wrote:
>>
>> Ralph,
>>
>> Have you completed the process? I see log4cxx is still listed as active in the incubator records.
>>
>> John
>>
>> On Thu, Mar 16, 2017 at 10:45 PM Ralph Goers <ralph.goers@dslextreme.com <ma...@dslextreme.com>> wrote:
>> This vote has been open for more than 5 days. It received 5 +1 votes and no other votes. So we will begin the process of moving the project back to Logging Services.
>>
>> Ralph
>>
>> > On Mar 11, 2017, at 10:31 AM, Ralph Goers <ralph.goers@dslextreme.com <ma...@dslextreme.com>> wrote:
>> >
>> > Log4cxx was originally a sub-project of the Logging Services. In 2013 several users became frustrated that they were submitting patches but there were no committers who could apply them. The Logging Services PMC was not comfortable making them committers as that would have given them commit rights to all the Logging Services projects, which at that time were all hosted in Subversion. As a consequence Log4cxx became an incubator project in hopes those who had expressed interest would start actively contributing to the project. After 3 1/2 years this has not had the hoped for result, although it does have more activity than it did prior to entering the incubator.
>> >
>> > The Logging Services PMC believes there is no longer a point to having Log4cxx remain in the incubator. The one active committer on Log4cxx has been voted in as a Logging Services committer and the PMC has voted [1] to move the project back to Logging Services. This is a vote for the incubator to affirm that move.
>> >
>> > [] +1 Move the project back to Logging Services
>> > [] +0 I don’t care where the project resides
>> > [] -1 The project should remain in the incubator because …
>> >
>> >
>> > [1] https://mail-search.apache.org/pmc/private-arch/logging-private/201703.mbox/browser <https://mail-search.apache.org/pmc/private-arch/logging-private/201703.mbox/browser> <https://mail-search.apache.org/pmc/private-arch/logging-private/201703.mbox/browser <https://mail-search.apache.org/pmc/private-arch/logging-private/201703.mbox/browser>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org <ma...@incubator.apache.org>
>> For additional commands, e-mail: general-help@incubator.apache.org <ma...@incubator.apache.org>
>>
>
Re: [RESULT][VOTE] Return Log4cxx to the Logging Services project
Posted by Ralph Goers <ra...@dslextreme.com>.
I figured out how to see the issue - https://issues.apache.org/jira/browse/INFRA-13651 <https://issues.apache.org/jira/browse/INFRA-13651>. It seems it is in a status of waiting for user but the reporter has no way to kick it back to infra. It has been sitting there for over a week.
Ralph
> On Apr 5, 2017, at 10:10 PM, Ralph Goers <ra...@dslextreme.com> wrote:
>
> No. To be honest, I’m not 100% sure if the community wants to move to git or not and I am not quite sure what the process is to move from svn to git without losing history. I guess I will just create a Jira issue for infra and find out.
>
> Also we have an outstanding infra request to combine all the logging dev lists but I don’t seem to have permission to view the status of it.
>
> Ralph
>
>> On Apr 5, 2017, at 8:19 PM, John D. Ament <johndament@apache.org <ma...@apache.org>> wrote:
>>
>> Ralph,
>>
>> Have you completed the process? I see log4cxx is still listed as active in the incubator records.
>>
>> John
>>
>> On Thu, Mar 16, 2017 at 10:45 PM Ralph Goers <ralph.goers@dslextreme.com <ma...@dslextreme.com>> wrote:
>> This vote has been open for more than 5 days. It received 5 +1 votes and no other votes. So we will begin the process of moving the project back to Logging Services.
>>
>> Ralph
>>
>> > On Mar 11, 2017, at 10:31 AM, Ralph Goers <ralph.goers@dslextreme.com <ma...@dslextreme.com>> wrote:
>> >
>> > Log4cxx was originally a sub-project of the Logging Services. In 2013 several users became frustrated that they were submitting patches but there were no committers who could apply them. The Logging Services PMC was not comfortable making them committers as that would have given them commit rights to all the Logging Services projects, which at that time were all hosted in Subversion. As a consequence Log4cxx became an incubator project in hopes those who had expressed interest would start actively contributing to the project. After 3 1/2 years this has not had the hoped for result, although it does have more activity than it did prior to entering the incubator.
>> >
>> > The Logging Services PMC believes there is no longer a point to having Log4cxx remain in the incubator. The one active committer on Log4cxx has been voted in as a Logging Services committer and the PMC has voted [1] to move the project back to Logging Services. This is a vote for the incubator to affirm that move.
>> >
>> > [] +1 Move the project back to Logging Services
>> > [] +0 I don’t care where the project resides
>> > [] -1 The project should remain in the incubator because …
>> >
>> >
>> > [1] https://mail-search.apache.org/pmc/private-arch/logging-private/201703.mbox/browser <https://mail-search.apache.org/pmc/private-arch/logging-private/201703.mbox/browser> <https://mail-search.apache.org/pmc/private-arch/logging-private/201703.mbox/browser <https://mail-search.apache.org/pmc/private-arch/logging-private/201703.mbox/browser>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org <ma...@incubator.apache.org>
>> For additional commands, e-mail: general-help@incubator.apache.org <ma...@incubator.apache.org>
>>
>
Re: [RESULT][VOTE] Return Log4cxx to the Logging Services project
Posted by Ralph Goers <ra...@dslextreme.com>.
No. To be honest, I’m not 100% sure if the community wants to move to git or not and I am not quite sure what the process is to move from svn to git without losing history. I guess I will just create a Jira issue for infra and find out.
Also we have an outstanding infra request to combine all the logging dev lists but I don’t seem to have permission to view the status of it.
Ralph
> On Apr 5, 2017, at 8:19 PM, John D. Ament <jo...@apache.org> wrote:
>
> Ralph,
>
> Have you completed the process? I see log4cxx is still listed as active in the incubator records.
>
> John
>
> On Thu, Mar 16, 2017 at 10:45 PM Ralph Goers <ralph.goers@dslextreme.com <ma...@dslextreme.com>> wrote:
> This vote has been open for more than 5 days. It received 5 +1 votes and no other votes. So we will begin the process of moving the project back to Logging Services.
>
> Ralph
>
> > On Mar 11, 2017, at 10:31 AM, Ralph Goers <ralph.goers@dslextreme.com <ma...@dslextreme.com>> wrote:
> >
> > Log4cxx was originally a sub-project of the Logging Services. In 2013 several users became frustrated that they were submitting patches but there were no committers who could apply them. The Logging Services PMC was not comfortable making them committers as that would have given them commit rights to all the Logging Services projects, which at that time were all hosted in Subversion. As a consequence Log4cxx became an incubator project in hopes those who had expressed interest would start actively contributing to the project. After 3 1/2 years this has not had the hoped for result, although it does have more activity than it did prior to entering the incubator.
> >
> > The Logging Services PMC believes there is no longer a point to having Log4cxx remain in the incubator. The one active committer on Log4cxx has been voted in as a Logging Services committer and the PMC has voted [1] to move the project back to Logging Services. This is a vote for the incubator to affirm that move.
> >
> > [] +1 Move the project back to Logging Services
> > [] +0 I don’t care where the project resides
> > [] -1 The project should remain in the incubator because …
> >
> >
> > [1] https://mail-search.apache.org/pmc/private-arch/logging-private/201703.mbox/browser <https://mail-search.apache.org/pmc/private-arch/logging-private/201703.mbox/browser> <https://mail-search.apache.org/pmc/private-arch/logging-private/201703.mbox/browser <https://mail-search.apache.org/pmc/private-arch/logging-private/201703.mbox/browser>>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org <ma...@incubator.apache.org>
> For additional commands, e-mail: general-help@incubator.apache.org <ma...@incubator.apache.org>
>
Re: [RESULT][VOTE] Return Log4cxx to the Logging Services project
Posted by Ralph Goers <ra...@dslextreme.com>.
No. To be honest, I’m not 100% sure if the community wants to move to git or not and I am not quite sure what the process is to move from svn to git without losing history. I guess I will just create a Jira issue for infra and find out.
Also we have an outstanding infra request to combine all the logging dev lists but I don’t seem to have permission to view the status of it.
Ralph
> On Apr 5, 2017, at 8:19 PM, John D. Ament <jo...@apache.org> wrote:
>
> Ralph,
>
> Have you completed the process? I see log4cxx is still listed as active in the incubator records.
>
> John
>
> On Thu, Mar 16, 2017 at 10:45 PM Ralph Goers <ralph.goers@dslextreme.com <ma...@dslextreme.com>> wrote:
> This vote has been open for more than 5 days. It received 5 +1 votes and no other votes. So we will begin the process of moving the project back to Logging Services.
>
> Ralph
>
> > On Mar 11, 2017, at 10:31 AM, Ralph Goers <ralph.goers@dslextreme.com <ma...@dslextreme.com>> wrote:
> >
> > Log4cxx was originally a sub-project of the Logging Services. In 2013 several users became frustrated that they were submitting patches but there were no committers who could apply them. The Logging Services PMC was not comfortable making them committers as that would have given them commit rights to all the Logging Services projects, which at that time were all hosted in Subversion. As a consequence Log4cxx became an incubator project in hopes those who had expressed interest would start actively contributing to the project. After 3 1/2 years this has not had the hoped for result, although it does have more activity than it did prior to entering the incubator.
> >
> > The Logging Services PMC believes there is no longer a point to having Log4cxx remain in the incubator. The one active committer on Log4cxx has been voted in as a Logging Services committer and the PMC has voted [1] to move the project back to Logging Services. This is a vote for the incubator to affirm that move.
> >
> > [] +1 Move the project back to Logging Services
> > [] +0 I don’t care where the project resides
> > [] -1 The project should remain in the incubator because …
> >
> >
> > [1] https://mail-search.apache.org/pmc/private-arch/logging-private/201703.mbox/browser <https://mail-search.apache.org/pmc/private-arch/logging-private/201703.mbox/browser> <https://mail-search.apache.org/pmc/private-arch/logging-private/201703.mbox/browser <https://mail-search.apache.org/pmc/private-arch/logging-private/201703.mbox/browser>>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org <ma...@incubator.apache.org>
> For additional commands, e-mail: general-help@incubator.apache.org <ma...@incubator.apache.org>
>