Subject: Re: [sup-talk] replacement sup wiki

From: Gaute Hope <[email-masked]>
Date: Mon, 14 Jan 2013 09:51:40 +0100

On 14. jan. 2013 00:40, Hamish D wrote:
>> This is excellent news, thank you for the move! I was myself considering
>> running our own bugtracker, seeing that wmorgan's github hasn't been updated
>> in the last 7 months and he is the only one being able to act on them. Same
>> thing would have to be done for the mailing-lists.
> 
> I have access to the gitorious account (can't remember if it is full
> admin rights or just push access). But I would be equally happy for
> there to be a github organisation account that a few of us were admins
> for (including wmorgan if he wanted). It would definitely be nice to
> have a working issue tracker.
> 
> Before doing more than this, might be worth seeing if wmorgan wants to
> say if he has preferences on this. My impression is that he has left
> sup behind, but would want to give a little time (a week, say) for him
> to say what he'd like before doing a load of work. I guess one key
> thing wmorgan has is the ability to push new sup gems to rubyforge.
> 
> I'd also be happy for the wiki to live elsewhere if there was some
> collective decision that it would be better elsewhere. I just thought
> I'd set it up for now.
> 
>> Speaking of the mailing list, is it okay if we hijack the wiki with
>> heliotrope content ? I read too many complaints about it being too hard to
>> install/use, and would love to fix it.
> 
> Please do put heliotrope stuff up there.

Great! I agree with the organization-plan (github or whatever with a
full project page: repository, issues, wiki..) - it really strains the
project with these administrational bumps.

Most importantly: A admin group with full access to the organization to
allow for admins/devs to go off for a while without the project staggering.

Personally I think the best is to keep everything on the same place.

Regards, Gaute

---

From: Philippe LeCavalier <[email-masked]>
Date: Mon, 14 Jan 2013 05:20:56 -0800

> Personally I think the best is to keep everything on the same place.

I second that!

Phil

---

From: Matthieu Rakotojaona <[email-masked]>
Date: Mon, 4 Feb 2013 14:35:52 +0100

On Sun, Feb 3, 2013 at 8:10 PM, Hamish D <[email-masked]> wrote:
> Matthieu - do you still have a strong preference for ikiwiki?

I've been convinced : centralizing all the resources is the best move
at the moment. My only complaint was about the lack of a search
engine. Let's hope it won't be that bad.

--
Matthieu RAKOTOJAONA

---

From: Matthieu Rakotojaona <[email-masked]>
Date: Sun, 13 Jan 2013 22:06:03 +0100

This is excellent news, thank you for the move! I was myself considering
running our own bugtracker, seeing that wmorgan's github hasn't been
updated in the last 7 months and he is the only one being able to act on
them. Same thing would have to be done for the mailing-lists.

-- 
Matthieu RAKOTOJAONA
_______________________________________________
sup-talk mailing list
[email-masked]
http://rubyforge.org/mailman/listinfo/sup-talk

---

From: Hamish D <[email-masked]>
Date: Sun, 13 Jan 2013 23:40:19 +0000

Hamish

---

From: Hamish D <[email-masked]>
Date: Sun, 13 Jan 2013 15:22:03 +0000

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

---

From: Gaute Hope <[email-masked]>
Date: Fri, 01 Feb 2013 10:54:02 +0100

> publishing an account on the front page and see if that foxes the

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

---

From: Hamish D <[email-masked]>
Date: Sun, 3 Feb 2013 19:10:12 +0000

> 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.

> 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

> (as you previously mentioned) if that gives me the possibility to manage

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