From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.182.180.80 with SMTP id dm16csp37825obc; Thu, 17 Jan 2013 12:15:48 -0800 (PST) X-Received: by 10.60.3.40 with SMTP id 8mr4960848oez.41.1358453748239; Thu, 17 Jan 2013 12:15:48 -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 xa10si2741104obb.98.2013.01.17.12.15.47; Thu, 17 Jan 2013 12:15:48 -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 CBE0B2E09E; Thu, 17 Jan 2013 20:15:48 +0000 (UTC) Received: from mail-wg0-f43.google.com (mail-wg0-f43.google.com [74.125.82.43]) by rubyforge.org (Postfix) with ESMTP id BC01C2E096 for ; Thu, 17 Jan 2013 20:15:23 +0000 (UTC) Received: by mail-wg0-f43.google.com with SMTP id e12so556920wge.10 for ; Thu, 17 Jan 2013 12:15:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:from:date:message-id:subject:to :content-type; bh=d5jfqMkGjEoW15jk6cCg5S6C1eg7SjsU0AH6Ouprb64=; b=U7y0PBGsCPF6Luogl+jwNh8kauW3pYCWrcTrbsWuBZZhHOa+v5SDJ8Vr0SqS59DvOw 1iUrg5zx0zfzBML1jDKHQnjL5Bj0Xors9Rtp3hPaqqUqs07BdrscNH1FpvHSQCj5bUXS VG/2ggAavNgogHKw62k4lMpJZvWZoNNV/T0ia85qxDKFp71Iq6DrXsrbEGVO4N8w/YEv tEZL96htZ7JWMMA5TxGeMqW++DdSg50bi+9TI4cOS4R4oe4678pcuAuELEaR2PA5z9ie zbtKc1M6eagjQpatRa3n0chKsOe7kFb5L4lQ1QB3LLvknpGZRbAqK+i1apCDv5U8Kv8S pFgQ== X-Received: by 10.180.19.136 with SMTP id f8mr186235wie.0.1358453721385; Thu, 17 Jan 2013 12:15:21 -0800 (PST) MIME-Version: 1.0 Received: by 10.194.152.166 with HTTP; Thu, 17 Jan 2013 12:15:01 -0800 (PST) From: Matthieu Rakotojaona Date: Thu, 17 Jan 2013 21:15:01 +0100 Message-ID: To: sup-talk , sup-devel Subject: [sup-talk] Github organization for sup and heliotrope 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 Hello, I've set up a github organization at https://github.com/sup-heliotrope for managing sup, heliotrope, turnsole and any needed bit in the future. I've already added Hamish Downer (known as foobacca on github) as an administrator; he has the rights to do whatever is needed on the organization. Feel free to give me your github account names and I will add you to the administrators team. I believe this is doable for the moment because we are only a few people interested in sup/heliotrope. If (when !) the popularity grows, we might want to change the governance model. I've been quite hesitant to use github because of the closed model (I like running my own thing if possible) and wanted to run my own redmine. However, github offers many advantages (uptime, speed, quick visibility) and the data isn't that closed : wiki are just plain text in git that can be exported, and there are more than complete APIs [0] for issues. However, I'd like to keep the wiki in Hamish's ikiwiki because I like it much better (but this is just personal preference) I took the liberty of creating a repo for sup, which is just a straight copy of git://gitorious.org/sup/mainline.git. I must admit I don't follow sup's development that much, so feel free to do what you want there. I've also set up a repo for sup with master being William's master branch. I'm quite attracted to the git-flow [1] model; I propose we follow it, and have therefore created a develop branch which is just a branch at the same level as master. Please, feel free to fork develop and code/test over it. I already have a bunch of propositions to do and will soon put them in the repo (I just realized my own repo was way too dirty to put it up now) William, I know you are alive and well thanks to your tweetstream; If you read this, I hope you won't take this organization as a treason of any sort. It's just that the lack of activity on your repo is too saddening for the development of heliotrope. I'm sure we can do it. See you soon, [0] http://developer.github.com/v3/issues/ [1] http://nvie.com/posts/a-successful-git-branching-model/ -- Matthieu RAKOTOJAONA _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk