[Not cross-posted] This is not about the governance issues raised in the discussion.
Technically, I do not understand what is difficult about creating working copies of a project's portion of the ASF SVN repository. It is done all of the time, for presumably much larger projects. If you mean a full backup with all history, that is a different matter. An attic SVN would still have all of that though. In any case, projects now have the option of creating a read-only Git mirror of their SVN, and there are a number of those hosted on GitHub, cloned, forked, etc. That could clearly be done for a project with its SVN in the attic. (I have no idea whether the history is as complete as what abides in the SVN.) These are not Gits of the entire ASF repo. The Git mirror has just the project's slice. What is not part of the current use of Git mirrors (whether on an ASF SVN or Git) is a way to accept Git push requests at the mirror in a manner that sustains ASF requirements for provenance and auditability of contributions, with assurance that IP matters are dealt with in accord with policy. My impression is that there is work underway to address that. However, this relates to ASF project governance policies and practices and that may not be helpful in how log4xx might be sustained. It would not apply to a project in the attic regardless. > -----Original Message----- > From: Thorsten Schöning [mailto:tschoen...@am-soft.de] > Sent: Friday, January 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 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. [ ... ] --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
