public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Markos Chandras <hwoarang@gentoo.org>
To: Ulrich Mueller <ulm@gentoo.org>
Cc: gentoo-dev@lists.gentoo.org, devmanual@gentoo.org
Subject: [gentoo-dev] Re: devmanual moved to github
Date: Sun, 12 May 2013 16:04:11 +0100	[thread overview]
Message-ID: <518FAF6B.80501@gentoo.org> (raw)
In-Reply-To: <20879.38369.270576.25249@a1i15.kph.uni-mainz.de>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 05/12/2013 02:15 PM, Ulrich Mueller wrote:
>>>>>> On Sun, 12 May 2013, Markos Chandras wrote:
> 
>> The devmanual git repository[1] moved to github[2]. Please update
>> your local trees using the following command:
> 
>> Developers: git remote set-url origin 
>> git@github.com:gentoo/devmanual.gentoo.org
> 
>> Read-only: git remote set-url origin 
>> git://github.com/gentoo/devmanual.gentoo.org
> 
> Earlier you said: "Just to clarify, i never said I wanted to 
> deprecated the git.overlays.gentoo.org repo."
> 
> Have I missed something? Last time I looked, github's server
> software wasn't open source. Why should we use non-free tools for a
> central piece of Gentoo documentation?
> 
> Ulrich
> 
>> [1]
>> http://git.overlays.gentoo.org/gitweb/?p=proj/devmanual.git;a=summary
>>
>> 
[2] https://github.com/gentoo/devmanual.gentoo.org
> 

The repository is still accessible in http://git.overlays.gentoo.org
and read-only access is still available. However, the write access
removed because of potential conflicts between g.o.g.o and github. If
you can guarantee me that people will not mess things up and not
commit only to one of the to remotes, then we can enable write access
again.

Besides, most fixes come from users (maybe not the actual patches but
they spot most of the problems) so providing an easier way for them to
contribute is preferred. Moreover, github provides other facilities
such as code reviews, which the Gentoo's gitolite interface does not have.

- -- 
Regards,
Markos Chandras - Gentoo Linux Developer
http://dev.gentoo.org/~hwoarang
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)

iQJ8BAEBCgBmBQJRj69qXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzNTVDNDczOUYzRjJEMTRGNDRGMzU2RkMw
OUJGNEY1NEMyQkE3RjNDAAoJEAm/T1TCun88UEoP/005Z4Oabo5R0OpHI+wWEABx
cRNkRqg9CJGqsyvPkO5ln94bYjpwgV/fg26snQOS3yFEO2E4PTBmXXkyWVYwhXZX
NcBpqevFu0fTMt0p54zWq/zWse7rot/iZPcNeGtr/N6CV5lsrEjH+LjJpp3LMNfQ
+WVgY2Iv3T7nmvCh4iSZbHYMar1vBVXLsDyxE2pGwcJauE5i7fZpVhx8f2Ma8tB3
yLObZh3Nx3v6IB6//lfWhytfF1QRpvHLgI5MsFjzVnWtRKenXnsFrApu+rUQPMR3
qIVzK+QjgLXxWbiT4CIs71utmamsJUvUhxvVOPJbVrz1JjO7bOolP+E7PlU7guu3
iARFcyOyHqzMxVLopgm7IKnrzKosBtp8r336pnJl+cTev3Xgrc6FMRUfkXeUPlFX
rXP4MSGu1/Ab4tdVVakpa0KvXG8OCrPB/2bBCl7N5KRVYFpSQrGkkP/dAVupZTZh
uPXnrqzHkRDcdTH0GN0L1/NmJe5IdsPCX7RFS28FOL/wEf6WIewOBZgTGvuNaahT
mqONBO9VXGu2w4nQtCVK0lWfyNIsHB2nJyOKDtQZWuajbQYihkpS86IHhNMvS0aU
v0qDs0yEkjpeSHb73T9xkDpN1amTo8l4IWmWz8vruPTZbjXldiBGGhgobM+K5tM2
auZWwWx3srwbl5aSZx1a
=qF97
-----END PGP SIGNATURE-----


  reply	other threads:[~2013-05-12 15:04 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   ` [gentoo-dev] " Duncan
2013-05-12 13:15 ` Ulrich Mueller
2013-05-12 15:04   ` Markos Chandras [this message]
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=518FAF6B.80501@gentoo.org \
    --to=hwoarang@gentoo.org \
    --cc=devmanual@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=ulm@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