openoffice-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dennis E. Hamilton" <>
Subject RE: Some old OOo SVN dumps, of use to anyone?
Date Sun, 01 Mar 2015 16:12:03 GMT
In addition to the other options for preserving the old SVN dumps mentioned in the attachment,
it is also possible to supply the files to the Computer History Museum in Mountain View, California.

 This will not make them available on-line, but it will preserve them in their catalog and
have them available for use by historians and researchers.  This is a means of preservation
as a backstop to any approach that also provides access but is vulnerable to obsolescence.

Although CHM mostly collects gear and papers, they also collect software and have been known
to scrape web sites of individuals in order to preserve those and their downloads.  (They
also collect verbal history through video interviews, such as their series of interviews with
Donald Knuth.  I believe Grady Booch did their interview with John Backus, and there are doubtless
others, such as Sir Tony Hoare.)

I'm not clear what protocol is required to make a clean contribution in the case of the OO.o
SVN though.

@Rob: You put in a great effort to make the SVN that was loaded as part of the Oracle grant.
 Does this include that work or is this something else that you found in the OO.o materials?

 - Dennis

-----Original Message-----
From: Dennis E. Hamilton [] 
Sent: Saturday, February 28, 2015 14:11
Subject: RE: Some old OOo SVN dumps, of use to anyone?

 -- replying inline to --
From: Rob Weir [] 
Sent: Saturday, February 28, 2015 12:38
Subject: Re: Some old OOo SVN dumps, of use to anyone?

On Sat, Feb 28, 2015 at 3:23 PM, Simon Phipps <> wrote:
> On Sat, Feb 28, 2015 at 7:22 PM, Marcus <> 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
> 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.

  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.  



> S.

To unsubscribe, e-mail:
For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message