From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.182.180.80 with SMTP id dm16csp31334obc; Sun, 13 Jan 2013 15:41:00 -0800 (PST) X-Received: by 10.182.144.7 with SMTP id si7mr51611515obb.94.1358120460411; Sun, 13 Jan 2013 15:41:00 -0800 (PST) Return-Path: Received: from rubyforge.org (50-56-192-79.static.cloud-ips.com. [50.56.192.79]) by mx.google.com with ESMTP id ke9si9120175obc.195.2013.01.13.15.41.00; Sun, 13 Jan 2013 15:41:00 -0800 (PST) Received-SPF: pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 50.56.192.79 as permitted sender) client-ip=50.56.192.79; Authentication-Results: mx.google.com; spf=pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 50.56.192.79 as permitted sender) smtp.mail=sup-talk-bounces@rubyforge.org; dkim=neutral (body hash did not verify) header.i=@gmail.com Received: from localhost.localdomain (localhost [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id 50B792E0B6; Sun, 13 Jan 2013 23:41:01 +0000 (UTC) Received: from mail-we0-f179.google.com (mail-we0-f179.google.com [74.125.82.179]) by rubyforge.org (Postfix) with ESMTP id 2DF612E069 for ; Sun, 13 Jan 2013 23:40:42 +0000 (UTC) Received: by mail-we0-f179.google.com with SMTP id r6so1790241wey.24 for ; Sun, 13 Jan 2013 15:40:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=rn12jd0IPCJM7gB4Grb9R0CRrJDmIjMtTU+HG78SaLw=; b=eIBTs76EWC6EwNgirc+or93JWYu7Wi55XbkXRMWTz1kApTOhw89D+fOCNjFYgjD9NT Hmu88n3MoL7r/XMj3TJp0LZWgRyT14ZAGC8CqOrZiMlIoWrfPBNXSYsRpifjKRilXDji VEQlEGB4k+dpPWz3NEjSOjvZtzPlOmccJsEaz1/prkSsB02fNcQ0Egw9AfNERKSrNa1P HZhSmh/BpWVMhKvpPf17GG4m+iHHgpyWA1cGw/nkxc6gJ7bF32kfpyJHyemLhpwQmA/H wa03aBMK4FsnB3v0+9ykAYipfBTvPtLyzGflFkZxhbujEfih6iXRrx9a7pzJE2Zem+S4 wZWg== Received: by 10.194.240.233 with SMTP id wd9mr13902933wjc.54.1358120439836; Sun, 13 Jan 2013 15:40:39 -0800 (PST) MIME-Version: 1.0 Received: by 10.194.44.99 with HTTP; Sun, 13 Jan 2013 15:40:19 -0800 (PST) In-Reply-To: References: From: Hamish D Date: Sun, 13 Jan 2013 23:40:19 +0000 Message-ID: To: Matthieu Rakotojaona Cc: sup-talk Subject: Re: [sup-talk] replacement sup wiki X-BeenThere: sup-talk@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: User & developer discussion of Sup List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sup-talk-bounces@rubyforge.org Errors-To: sup-talk-bounces@rubyforge.org > 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. Hamish _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk