From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: devmanual moved to github
Date: Sun, 12 May 2013 15:02:38 +0000 (UTC) [thread overview]
Message-ID: <pan$d0561$ed8840a1$e7bbb6e7$5783bcc@cox.net> (raw)
In-Reply-To: CAGfcS_mPekOW7pJ3w_knrA-aMjojV=tWxbC1ZDw1AsN0hFhQwQ@mail.gmail.com
Rich Freeman posted on Sun, 12 May 2013 09:12:03 -0400 as excerpted:
> On Sun, May 12, 2013 at 7:32 AM, Markos Chandras <hwoarang@gentoo.org>
> wrote:
>> The devmanual git repository[1] moved to github[2].
>
> No objections to mirroring it there, and accepting pull requests there.
> However, would an outright move be contrary to our social contract?
> [quoted]
>
> That said, git itself is FOSS, and moving it back is not difficult
> should bad things happen (though any in-progress pull-requests/etc would
> be lost). The only thing that isn't FOSS is github itself. Not sure if
> others feel strongly about it.
To me it depends upon how dependent upon github people actually become.
If the primary workflow remains in people's distributed git repos, in
git, then more copies "out there" including on github is simply more
redundancy, As Linus likes to say, "real men" don't make backups, they
post it to the net and let the dozens (in his case, likely tens of
thousands, but...) of net copies be their backups.
As soon as github going down becomes a problem, however, or as soon as
pull requests need to go thru github, then it's a problem, "depending
upon" according to the social contract.
Arguably, letting github be the primary/only public link is problematic
in that very way, since at that point github going down is a problem for
those using the public link. OTOH, just having a mirror there and
letting people submit pull requests via github as well as directly,
shouldn't be a problem. IMO of course.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2013-05-12 15:03 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-12 11:32 [gentoo-dev] devmanual moved to github Markos Chandras
2013-05-12 13:12 ` Rich Freeman
2013-05-12 13:27 ` Peter Stuge
2013-05-12 15:02 ` Ben de Groot
2013-05-12 15:15 ` Markos Chandras
2013-05-12 15:12 ` Diego Elio Pettenò
2013-05-12 15:02 ` Duncan [this message]
2013-05-12 13:15 ` [gentoo-dev] " Ulrich Mueller
2013-05-12 15:04 ` Markos Chandras
2013-05-12 15:17 ` Peter Stuge
2013-05-12 15:48 ` Ulrich Mueller
2013-05-12 15:54 ` Markos Chandras
2013-05-12 16:08 ` Rich Freeman
2013-05-12 16:12 ` Michael Palimaka
2013-05-14 15:44 ` William Hubbs
2013-05-14 17:51 ` Rich Freeman
2013-05-12 16:55 ` Ulrich Mueller
2013-05-12 16:04 ` Mike Gilbert
2013-05-12 17:20 ` Peter Stuge
2013-05-12 17:32 ` Michael Palimaka
2013-05-12 18:24 ` Peter Stuge
2013-05-12 18:31 ` Michael Palimaka
2013-05-12 22:12 ` Alexander Berntsen
2013-05-12 22:21 ` Peter Stuge
2013-05-12 22:24 ` Alexander Berntsen
2013-05-12 22:37 ` Peter Stuge
2013-05-13 7:09 ` Alexander Berntsen
2013-05-12 22:38 ` W. Trevor King
2013-05-13 6:32 ` Ralph Sennhauser
2013-05-13 7:07 ` Alexander Berntsen
2013-05-13 7:40 ` Ralph Sennhauser
2013-05-13 7:47 ` Alexander Berntsen
2013-05-13 13:28 ` Ciaran McCreesh
2013-05-14 15:55 ` William Hubbs
2013-05-13 12:38 ` Greg KH
2013-05-13 12:42 ` Alexander Berntsen
2013-05-13 21:59 ` Duncan
2013-05-12 17:33 ` Theo Chatzimichos
2013-05-12 18:22 ` Peter Stuge
2013-05-12 19:18 ` [gentoo-dev] GitLab Feature-Set / Was: " sascha-ml
2013-05-14 13:59 ` Rich Freeman
2013-05-14 14:19 ` Peter Stuge
2013-05-14 14:40 ` Rich Freeman
2013-05-13 3:38 ` [gentoo-dev] " Arun Raghavan
2013-05-12 15:13 ` Richard Yao
2013-05-12 15:38 ` Ulrich Mueller
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='pan$d0561$ed8840a1$e7bbb6e7$5783bcc@cox.net' \
--to=1i5t5.duncan@cox.net \
--cc=gentoo-dev@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