public inbox for gentoo-science@lists.gentoo.org
 help / color / mirror / Atom feed
From: Christopher Schwan <cschwan@students.uni-mainz.de>
To: <gentoo-science@lists.gentoo.org>
Subject: Re: [gentoo-science] moving the science overlay to github?
Date: Wed, 8 Feb 2012 11:46:37 +0100	[thread overview]
Message-ID: <1575152.uvKFD9n5Pn@cschwan-laptop> (raw)
In-Reply-To: <20120208095225.0gcs88kgggs8wwg0@webmail.slingshot.co.nz>

On Wednesday 08 February 2012 09:52:25 fbissey@slingshot.co.nz wrote:
> Quoting Sébastien Fabbro <bicatali@gentoo.org>:
> > Hi,
> > 
> > We are contemplating the idea of switching the official science overlay
> > to an external repository such as github. Here are some of the
> > advantages we would like to
> > get:
> > 1. easier to contribute
> > 2. specific issue tracker
> > 3. wiki
> 
> Other people have made useful comments already. The only point that I think
> is interesting about github is the possibility to clone the overlay and have
> pull requests.
> Effectively that means people can contribute without ever getting infra
> involved and an external contributor can send a pull request even if they
> are not a member of the github science team.
> 
> Francois

Thats right - pull requests are a very nice feature of github. For example, if 
I am not content with what the pull request contains, I can write that and 
make a suggestion how to do it better. The user can now add more commits and 
adapt to my suggestions (see for example [1]). That is IMO a very good example 
why github is better than bugzilla+bare git repo+wiki - everything is in one 
place and you can discuss it together. It makes things very active, maybe a 
move to github could also attract more contributors.

[1]  https://github.com/cschwan/sage-on-gentoo/pull/103

Cheers,
Christopher



  parent reply	other threads:[~2012-02-08 11:02 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-07 17:24 [gentoo-science] moving the science overlay to github? Sébastien Fabbro
2012-02-07 17:51 ` My Th
2012-02-07 18:26   ` Andrea Arteaga
2012-02-07 18:34 ` Alexey Shvetsov
2012-02-07 18:41   ` Christoph Junghans
2012-02-07 21:13     ` Sébastien Fabbro
2012-02-07 21:35       ` My Th
2012-02-08  8:23         ` Kacper Kowalik
2012-02-08  9:38         ` Thomas Kahle
2012-02-07 20:52 ` fbissey
2012-02-08  0:31   ` Alexey Shvetsov
2012-02-08  0:45     ` Christoph Junghans
2012-02-08  8:28     ` Kacper Kowalik
2012-02-08  9:35     ` Thomas Kahle
     [not found]       ` <201202081302.17255.marten@xtal.rwth-aachen.de>
2012-02-08 16:25         ` Christoph Junghans
2012-02-09  7:04           ` justin
2012-02-08 10:46   ` Christopher Schwan [this message]
2012-02-09  7:08 ` justin
2012-02-19 14:07 ` Kacper Kowalik
2012-02-19 14:42   ` Thomas Kahle
2012-02-19 21:54     ` Andrea Arteaga
2012-02-25 12:52   ` Kacper Kowalik
2012-02-25 19:38     ` Kacper Kowalik
2012-02-25 19:46       ` Kacper Kowalik

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=1575152.uvKFD9n5Pn@cschwan-laptop \
    --to=cschwan@students.uni-mainz.de \
    --cc=gentoo-science@lists.gentoo.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