From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from [129.177.117.51] ([129.177.117.51]) by mx.google.com with ESMTPS id mb2sm4825924lab.7.2013.01.14.00.51.34 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 14 Jan 2013 00:51:34 -0800 (PST) Message-ID: <50F3C71C.1070807@gaute.vetsj.com> Date: Mon, 14 Jan 2013 09:51:40 +0100 From: Gaute Hope User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: sup-talk@rubyforge.org Subject: Re: [sup-talk] replacement sup wiki References: In-Reply-To: X-Enigmail-Version: 1.5 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit 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