From: Hamish D <dmishd@gmail.com>
To: Gaute Hope <eg@gaute.vetsj.com>
Cc: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] replacement sup wiki
Date: Sun, 3 Feb 2013 19:10:12 +0000 [thread overview]
Message-ID: <CAOxvSbcpfxPrQSsMkxKqF9PFbLV8GtZvNfSKf09OfAbGaxwujw@mail.gmail.com> (raw)
In-Reply-To: <510B90BA.30007@gaute.vetsj.com>
>> I've set up a wiki we can use as a replacement for the old unloved
>> wiki - http://foobacca.co.uk/sup/
>
> I just tried to edit an page and got an Internal Server Error.
Oops - I've been moving the server and hadn't tested that - fixed now.
> 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?
Just re-checked and anyone with a github account can edit the wiki
through the front end, which was my main concern. So given using the
github wiki does mean everything is in one place I would now lean
towards the github wiki as the way to go. I have pushed my wiki
contents to the github wiki to try it out and seems fine:
https://github.com/sup-heliotrope/sup/wiki
Matthieu - do you still have a strong preference for ikiwiki?
> 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!
I've made you an owner and made myself public - the public/private
thing wasn't deliberate, just an accident of how people were added I
think.
Hamish
next prev parent reply other threads:[~2013-02-03 19:10 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
2013-02-03 19:10 ` Hamish D [this message]
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=CAOxvSbcpfxPrQSsMkxKqF9PFbLV8GtZvNfSKf09OfAbGaxwujw@mail.gmail.com \
--to=dmishd@gmail.com \
--cc=eg@gaute.vetsj.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