Sorry to answer late on this, got swamped by other emails and initiatives. In line answers.
2015-02-28 23:10 GMT+01:00 Dennis E. Hamilton <dennis.hamil...@acm.org>: > -- replying inline to -- > From: Rob Weir [mailto:r...@robweir.com] > Sent: Saturday, February 28, 2015 12:38 > To: dev@openoffice.apache.org > Subject: Re: Some old OOo SVN dumps, of use to anyone? > > On Sat, Feb 28, 2015 at 3:23 PM, Simon Phipps <si...@webmink.com> wrote: > > On Sat, Feb 28, 2015 at 7:22 PM, Marcus <marcus.m...@wtnet.de> wrote: > > > >> > >> IMHO this is an invaluable source of our history that we shouldn't > loose. > > > > > > I agree with this -- it's history for every derivative of OO.o, not just > > AOO. > > > > > >> Please save it at a location where it cannot be deleted by accident. So, > >> the best would be indeed somewhere on a server/disk that is > >> controlled/accessible at apache.org. > > > > > > One issue may be licensing, as the work stored on Rob's disk was not the > > one approved by Oracle to be relicensed for use by Apache. Even if that > > can be resolved, the image probably also includes portions that were not > > included in the code identified for relicensing approval. I'm no expert > on > > Apache policies but it seems possible either of those conditions could > make > > the file inappropriate for storage by Apache directly. > > > > It is not exactly the syllabic nucleus of the Vulcan language, but it > could be useful. If someone can offer a better long-term place for > this, please chime in. An SVN dump file is a text file, so I could > gzip it down to something a bit smaller, maybe 50 GB. It could be > even more useful, of course, if hosted as an actual (read-only) > repository, to consult the history of the code base. > > I'll hold on to it for now, but note that this is not currently in any > controlled data center. It is just sitting at home on a shelf, > susceptible to the whims of fire, water, wind, the fates and cats. It > would be good to get it under suitable curation. > > <orcmid> > Three prospects (worst to best?) > > 1. I just saw mention of an Apache branch on a file-sharing service, > not a code repository, but 50GB might be a reach. > > 2. I have a web hosting service that promises unlimited storage and > no bandwidth usage limit (though I think instantaneous bandwidth > is limited). They also support CVS, SVN, and GIT, but I think I > would have to install the SVN myself. I could easily create an FTP > account just for transfer and preservation of that specific > content though. Not certain about curation. Just another mirror > for preservation purposes. > > 3. I think SourceForge might be able to swallow this and set it up > as a read-only SVN. Although the Apache Extras there are set up > mainly as a download service, there is no reason that it could > not have a repo too. This would be perfect so long as it is > workable for them. > SourceForge is definitely open and willing to do so, and let me add that by doing that we would just go back to our own roots. In fact the early working name for the SourceForge site was "Cold Storage" ( http://linux.omnipotent.net/article.php?article_id=3649) and they intended it to be a permanent archive for important FOSS. Having said that, for a long-standing project like AOO, even if the "old code" will be of limited use to an end-user, but as a practical matter it's important for projects to keep these early materials in case they are needed to demonstrate code ownership or prior art. We continue to view this as part of our key mission -- where practicable we should provide service to safeguard the availability of these materials. Dave Brondsema, Apache Allura VP and SourceForge Lead Engineer, will follow up in this thread providing support or guidance if needed. Few AOO committers have already admin priv on the AOO mirror at SourceForge, and if others need to get access it could be granted easily. Hope that helps. Roberto > </orcmid> > > Regards, > > -Rob > > > S. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > >
