From: Gaute Hope <eg@gaute.vetsj.com>
To: Hamish D <dmishd@gmail.com>
Cc: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] replacement sup wiki
Date: Fri, 01 Feb 2013 10:54:02 +0100 [thread overview]
Message-ID: <510B90BA.30007@gaute.vetsj.com> (raw)
In-Reply-To: <CAOxvSbeLBiP9pGgpLek0AKfSSdUvG8Zix+Ly5wrNTDLQ-XuUZQ@mail.gmail.com>
On 13. jan. 2013 16:22, Hamish D wrote:
> Hello
>
> I've set up a wiki we can use as a replacement for the old unloved
> wiki - http://foobacca.co.uk/sup/
>
> Unfortunately, most of the old wiki appears to be lost. The wiki
> software (usemod) only appears to keep the last 10 revisions of each
> page. But most pages have been vandalised far more than that, and so
> the content appears lost. I have checked the wayback machine but it
> doesn't have anything from the wiki. I also note that the wiki is
> covered by a Disallow line in the robots.txt - not sure how long
> that's been there.
>
> Anyway, please feel free to go and recreate the lost pages, or add new
> content. The new wiki is ikiwiki, which is based on git, so all
> history will remain available. At some point the spammers will start
> hitting it, at which point I'll disable registration, but try
> publishing an account on the front page and see if that foxes the
> spammers. We'll see.
>
> Hamish
Sup,
I just tried to edit an page and got an Internal Server Error. I think
we should make the decision as soon as possible about where to keep the
wiki to avoid the extra work and de-motivating/confusing moving/re-creation.
Then direct people to the wiki from the README and either remove the
WIKI tab on github or use it.
Great work on setting up a new wiki, but I think it is even better to
keep it all in one place so I vote for using the github wiki and to set
up a sup/heliotrope site there when the time is ripe. What do you think?
By the way.. at the moment I am the only public member of the github
organization, is that by design.. ? And you could also make me an owner
(as you previously mentioned) if that gives me the possibility to manage
more of those things!
Regards, Gaute
next prev parent reply other threads:[~2013-02-01 9:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-13 15:22 Hamish D
2013-01-13 21:06 ` Matthieu Rakotojaona
2013-01-13 23:40 ` Hamish D
2013-01-14 8:51 ` Gaute Hope
2013-01-14 13:20 ` Philippe LeCavalier
2013-02-01 9:54 ` Gaute Hope [this message]
2013-02-03 19:10 ` Hamish D
2013-02-04 13:35 ` Matthieu Rakotojaona
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=510B90BA.30007@gaute.vetsj.com \
--to=eg@gaute.vetsj.com \
--cc=dmishd@gmail.com \
--cc=sup-talk@rubyforge.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox