How to deactivate/delete old GitHub mirror for log4cxx?
Hi, the logging project log4cxx moved to a new GIT-repo recently, but had a mirror on GitHub already in the past at the following place: https://github.com/apache/log4cxx The new mirror is the following: https://github.com/apache/logging-log4cxx Is there any way to deactivate/delete/whatever the old mirror? I already dealt with the PRs, so there shouldn't be anything lost if deleted. Or is there at least some note in the project description and/or some redirection possible? I don't seem to have access to the project or repo. Thanks! Mit freundlichen Grüßen, Thorsten Schöning -- Thorsten Schöning E-Mail: thorsten.schoen...@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-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [RESULT][VOTE] Return Log4cxx to the Logging Services project
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.schoen...@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-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [RESULT][VOTE] Return Log4cxx to the Logging Services project
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.schoen...@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-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Code signing and WOT for releases
Hi all, the docs about release management for incubating projects make clear that the release needs to be signed[1] and in the end associated with the project AND the WOT of Apache in general[2]. Is there some way to check what the owner of a PGP key for former releases has done to get his association to the WOT, if any? I would like to understand the needed process better and e.g. found the following: http://pgp.surfnet.nl:11371/pks/lookup?op=vindex=on=0x2E114322 Are all those people/keys on this list someone who signed the key I searched for and provided association with the WOT this way? Are the mentioned possibilities in [2] the only way to get such an association to the WOT? I usually don't visit conferences or keysigning parties or such. Am I correct that releases can't be published without such an association to the WOT at all and BEFOREHAND? Else one could sign and publish a release and loose the key afterwards or else and the release would be left without the needed association. Thanks! [1]: http://incubator.apache.org/guides/releasemanagement.html#signing [2]: http://www.apache.org/dev/openpgp.html#apache-wot-link Mit freundlichen Grüßen, Thorsten Schöning -- Thorsten Schöning E-Mail: thorsten.schoen...@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-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
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 simply a matter > of preferring git to svn? Holy shit no, this is by no means the start of a SCM flamewar, I like and still prefer SVN very much, we use it at our company extensively. My problem is really only about the release and incubation part and in the end, if I'm going to keep my commit permissions to the "current" codebase and history or not. I simply won't have the time to go through the release process myself, I thought I have it when the incubation process started, but it didn't work the last 2 years, so I guess it won't work the next 2... And with that in mind, I'm just checking the possibilities to keep any somewhat writable permissions to the codebase for me. GitHub is only one possible anchor, which is simply better suited for my needs than the Attic, because I could fork with keeping the history. And if the project doesn't succeed the incubation process now, it surely won't ever leave the Attic again. > [...]but if Apache log4cxx does not have > those three people, and is not creating any releases, it simply is not > a project. And that's fine, but that doesn't necessary mean that you need to "lock away" the history. But I may completely wrong and it wouldn't be allowed to even fork a dead Apache log4cxx on GitHub to keep working on it with the history, even privately? Mit freundlichen Grüßen, Thorsten Schöning -- Thorsten Schöning E-Mail: thorsten.schoen...@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-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
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 without participating in further development too much. > Nothing is solved by "moving" > the project to github if their changes are never moved back to the ASF. I disagree: I'm doing at least some level of support and merge patches once a while, depending on their nature and such. The problem now is that such an amount of work and "community" ;-) would not be enough for your incubation rules and the Apache way, so you would need to decide that it's "better" to keep me off the repo entirely instead of just letting me do what I'm able to provide AND what is somewhat requested by at least some users. That's a decision you make based on your project/organisation rules, but it doesn't change if there's at least some demand for maintenance of any kind, it's just that the project doesn't fit to your rules anymore. 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 clone for interested persons like me for technically reasons. When I tried some years ago, you actively blocked me just because I fetched revisions a week or so... :-) So if you decide that the project is dead, with the same decision you might prevent people access to the very valuable history of the project simply for practical reasons, because we are not allowed to clone it 2 weeks or the amount of data is just to huge with all those empty revisions or whatever. If the project is additionally hosted on GitHub and not only in Attic, it would be simpler for still interested people to fork and make use of it. I see that as somewhat special to Apache's Attic concept, and maybe even the use of SVN, though I like SVN a lot: To me it looks like that hosting all Attic projects on a platform enabling easier forking of the entire project history would be a great idea. Mit freundlichen Grüßen, Thorsten Schöning -- Thorsten Schöning E-Mail: thorsten.schoen...@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-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
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 history before moving to Attic, like they did for the project before and do for other projects, even from the incubator. Same like the following: https://github.com/apache/incubator-rya Or even something like: https://github.com/apache/attic-log4cxx Getting the SVN history from the huge Apache repo is very time consuming and creates a large repo of mostly empty revisions. When I did it the last time some years ago, @infra seemed to even block my dynamic IPs after some hours of fetching. :-) That's something I would like to avoid if @infra has more efficient ways to deal with this. Mit freundlichen Grüßen, Thorsten Schöning -- Thorsten Schöning E-Mail: thorsten.schoen...@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-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
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 a read only repo. http://attic.apache.org Mit freundlichen Grüßen, Thorsten Schöning -- Thorsten Schöning E-Mail: thorsten.schoen...@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-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
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 on the APR mailing list seems to be dominated by SVN as well, e.g. some of my threads and reported bugs were ignored like those of others, they have their own Bugzilla instead of JIRA etc. I don't think this would make it any better for Log4cxx and if I remember correctly, apr-util was discussing removing e.g. expat, so I don't think they want to include another new project of our size. I wouldn't if I was them. :-) Let's focus on the main point again: Log4cxx is used, there are still users somewhat interested in the project and there are people willing to provide at least support, apply bug fixes and if needed I will report the same contents every 3 months over and over again... ;-) So even if we are to dead for the incubator, we are to alive for the attic. Mit freundlichen Grüßen, Thorsten Schöning -- Thorsten Schöning E-Mail: thorsten.schoen...@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-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
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 the majority of work on it and made users happy. Let's agree that we disagree and we have two votes for the Attic right now. :-/ Mit freundlichen Grüßen, Thorsten Schöning -- Thorsten Schöning E-Mail: thorsten.schoen...@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-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
