From: Gaute Hope <eg@gaute.vetsj.com>
To: sup-talk@rubyforge.org
Subject: Re: [sup-talk] replacement sup wiki
Date: Mon, 14 Jan 2013 09:51:40 +0100 [thread overview]
Message-ID: <50F3C71C.1070807@gaute.vetsj.com> (raw)
In-Reply-To: <CAOxvSbdGF01FpdGnaYM43jTzz=mtwigAjfC_QGiRTgj+_eEiXA@mail.gmail.com>
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
next prev parent reply other threads:[~2013-01-14 8:51 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 [this message]
2013-01-14 13:20 ` Philippe LeCavalier
2013-02-01 9:54 ` Gaute Hope
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=50F3C71C.1070807@gaute.vetsj.com \
--to=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