Re: [sup-talk] Github organization for sup and heliotrope

From: Gaute Hope <eg@gaute.vetsj.com>
To: Matthieu Rakotojaona <matthieu.rakotojaona@gmail.com>
Cc: sup-talk <sup-talk@rubyforge.org>,  sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-talk] Github organization for sup and heliotrope
Date: Thu, 17 Jan 2013 21:52:01 +0100	[thread overview]
Message-ID: <50F86471.3000900@gaute.vetsj.com> (raw)
In-Reply-To: <CAMiZLn0QPzDPTxAuR9BcdWv2KPU4Zw-8wCQSSnLrYkq-tGSvow@mail.gmail.com>

Hi,

I think this is a step in the right direction - given that there has 
been silence on wmorgans part so long.

Kepping things in one place does work alot better, even if it means 
sacrificing a few features - I think that keeping the wiki along with 
the rest of the organization is the best.  Also github is not linked or 
dependant on any one admin / developer, so I think for this kind of 
project it is ideal - expanding to a proper web site is no biggie with 
github either, making future possible migration even easier.

I'd like to be part of the organization, but I am probably not going to 
be active enough to be an administrator, github name: gauteh.

Cheers, Gaute

On to. 17. jan. 2013 kl. 21.15 +0100, Matthieu Rakotojaona wrote:
> 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