OK, Now we need volunteers.  No programming experience is required.
There was a problem with our confluence installation: apparently no
one realized that backup dumps were not being made, and then when
data corruption hit on the storage, we ended up with a uselessly
corrupt database.  (We will not repeat this error.)

While confluence is off-line, web caches have content.  It seems
that the wayback machine didn't index our confluence, but google
certainly did.  So, visit:
http://www.google.com/search?q=foresight+site%3Awiki.foresightlinux.org
and start following the "Cached" links and cutting and pasting content.

We will use mercurial to work on this together, putting content into
a shared repository.  Please visit:
https://bitbucket.org/johnsonm/foresight-confluence-recovery
Note that the "website" for this repository is the link for
pulling up cached pages.

Both António and I can add you as a writer in that repository.
Just ask in #foresight-devel.

Speaking of which: while you are doing this work, join
#foresight-devel on IRC to collaborate.

For each page you find, create a file with the name of the page -- use
the part after "display/" in the link, and change subdirectories to use
_ instead of / because in the filesystem we cannot have a single name
be both a file and a directory (whereas DEV can be a node and a directory
in confluence).

Add the contents of the page to that file.

Add that file to the repository and commit.

After you clone foresight-confluence-repository:

    cd foresight-confluence-repository
    ls -l

Then, for each page you are going to copy, follow the pattern here.
This is what I did to add the content of the main DEV page -- the
first link on that google search:

    hg pull -u
    $EDITOR DEV
    hg add DEV
    hg ci -m 'DEV'
    hg push

If hg push tells you that it would create "new heads", then do the following:

    hg pull -u
    hg merge
    hg ci -m 'branch merge'
    hg push

If you have questions, ask on #foresight-devel
_______________________________________________
Foresight-devel mailing list
[email protected]
http://lists.rpath.org/mailman/listinfo/foresight-devel

Reply via email to