Re: [Savannah-hackers-public] our wiki status
- the ikiwiki package is installed and basically configured on frontend. Thank you Karl for doing this work! It's awesome! Belated, but I just have to chime in: Thanks, Karl!
Re: [Savannah-hackers-public] our wiki status
I thought the copyright line was still needed to prepare for the case You may be right, but then it seems like there should be some text about that. I find CC0 extremely confusing in many ways, and its usage is never clearly spelled out, that I've seen ... k
Re: [Savannah-hackers-public] our wiki status
Am Montag, den 26.08.2013, 22:24 + schrieb Karl Berry: I'm fine with some savannah-ish style in theory, but I'd like to concentrate on getting the basic functionality working first. I'll come back to this. Thanks! BTW, stating Copyright and CC0 are mutually exclusive. The whole point of cc0 is waiving copyright. CC doesn't make it easy to find (last time I looked), but I believe the recommended text is: To the extent possible under law, Your Name has waived all copyright and related or neighboring rights to Your Program. This work is published from: Your Country. http://creativecommons.org/publicdomain/zero/1.0/ I thought the copyright line was still needed to prepare for the case when section 2 is invalidated somewhere and that section 2 overrides the copyright line (where the waiver is applicable). I guess I've been wrong. I just changed the license header, so you can come back to the file whenever you come back to it: http://codepad.org/O1A9Cc5y Best regards. -- GPG: 4F20BC96 - the public key can be found here: http://rpapsch.de/gpg.asc signature.asc Description: This is a digitally signed message part
Re: [Savannah-hackers-public] our wiki status
Am Montag, den 26.08.2013, 00:36 + schrieb Karl Berry: As Aljoscha pointed out, ikiwiki has lots of bells and whistles. I haven't done anything along those lines. About that: I remade the little stylesheet: http://codepad.org/haLiNIHY It's not much, just a few lines of border, spacing, color settings (imo this is trivial work, but I added the copyright line nevertheless). It resembles the default Savannah style, so it would be nice to see it used (and/or improved). style.css says: /* Note that instead of modifying this style sheet, you can instead edit * local.css and use it to override or change settings in this one. */ local.css can also reside in the repository, if desired. Best regards. -- GPG: 4F20BC96 - the public key can be found here: http://rpapsch.de/gpg.asc signature.asc Description: This is a digitally signed message part
Re: [Savannah-hackers-public] our wiki status
Karl Berry wrote: - the ikiwiki package is installed and basically configured on frontend. Thank you Karl for doing this work! It's awesome! Bob
Re: [Savannah-hackers-public] our wiki status
Current status: I've converted and imported all the substantive content into the ikiwiki. I don't doubt that there are plenty of broken links around, mostly but not entirely broken in the original wiki too. You can get at the pages by checking out the subversion (yes, subversion) repository from the administration project. The basic format is markdown. There's no automatic update on commit yet. Hence there is also no web editing. After doing a commit, I've been manually refreshing the wiki on frontend, like this (as myself; presumably it works as root too): ikiwiki --setup /usr/local/share/sviki/ikiwiki.setup --refresh I'll see what I can do about those things tomorrow, and try to describe more of the basic setup. Meanwhile, let me know if you see any unexpected problems. As Aljoscha pointed out, ikiwiki has lots of bells and whistles. I haven't done anything along those lines. karl
[Savannah-hackers-public] our wiki status
Bob and I have been working on the wiki breakdown. Here's what's done: - the ikiwiki package is installed and basically configured on frontend. - it is connected to the subversion source repository in the administration project, https://savannah.gnu.org/svn/?group=administration. (More details another time.) - the html for our pages (there are about 150, most short) are saved in that svn repo; they aren't visible on our web site yet, though. I retrieved them by hand from the Wayback Machine, starting from http://web.archive.org/web/20130818055223/http://savannah.gnu.org/maintenance/FrontPage It had all the actual content that I remember ever being there. Here are my next steps: - write something to convert that dumped html to markdown; then at least we'll have the documentation online again. I hope to get the basic task done in the next day or two. - set up a post-svn-commit hook so that commits automatically cause the wiki to be updated. Also set up email on commit. - enable editing through the web. Obviously much more to say/document eventually, but that's the current state. The wiki content itself is also badly, sadly, madly stale. By the way, neither Bob nor I could find a way to extract the actual text from Zope's Data.fs file. The provided fsdump tool gives a text transcription of it: env PYTHONPATH=/usr/lib/zope2.10/lib/python \ /usr/lib/zope2.10/bin/fsdump.py \ /var/lib/zope2.10-20120719/instance/default/var/Data.fs | head But this seemed to just report transactions, referring to opaque data pointers. No actual content. We found lots of people asking questions about it on the web, but no usable answers. If Zope was actually running, it would be possible to export the objects (pages) in various ways, but of course, we can't get Zope to start. Hence the brute force save from wayback. Yay for wayback. They did better backups than anything we had ... karl
Re: [Savannah-hackers-public] our wiki status
Can pandoc help you with the conversion? -- Sent from my Replicant phone with K-9 Mail.
Re: [Savannah-hackers-public] our wiki status
Can pandoc help you with the conversion? Nice thought, but when I tried it, it seems pandoc does too good of a job :). There is lots of zwiki boilerplate in the dumps that we just want to ignore, and conversely, we want to add [[WikiLinks]] and such. Ok, I could preprocess it away, but ... overall, the dumps are quite regular, so I think regexps will do the job. I'll keep pandoc in mind for complicated pages though. Thanks.
