From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <gentoo-project+bounces-4233-garchives=archives.gentoo.org@lists.gentoo.org> Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id D958C138A1A for <garchives@archives.gentoo.org>; Wed, 28 Jan 2015 22:30:35 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id D9259E07D0; Wed, 28 Jan 2015 22:30:34 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 246AEE07A7 for <gentoo-project@lists.gentoo.org>; Wed, 28 Jan 2015 22:30:34 +0000 (UTC) Received: from pomiot.lan (unknown [81.219.202.249]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: mgorny) by smtp.gentoo.org (Postfix) with ESMTPSA id 81629340707; Wed, 28 Jan 2015 22:30:32 +0000 (UTC) Date: Wed, 28 Jan 2015 23:30:22 +0100 From: =?UTF-8?B?TWljaGHFgiBHw7Nybnk=?= <mgorny@gentoo.org> To: Markos Chandras <hwoarang@gentoo.org> Cc: gentoo-project@lists.gentoo.org Subject: Re: [gentoo-project] Official rsync->git mirror & 'Git mirror' project announcement Message-ID: <20150128233022.3e5d3d29@pomiot.lan> In-Reply-To: <54C95935.5000202@gentoo.org> References: <20150126211234.652bbbb9@pomiot.lan> <54C95935.5000202@gentoo.org> Organization: Gentoo X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.25; x86_64-pc-linux-gnu) Precedence: bulk List-Post: <mailto:gentoo-project@lists.gentoo.org> List-Help: <mailto:gentoo-project+help@lists.gentoo.org> List-Unsubscribe: <mailto:gentoo-project+unsubscribe@lists.gentoo.org> List-Subscribe: <mailto:gentoo-project+subscribe@lists.gentoo.org> List-Id: Gentoo Project discussion list <gentoo-project.gentoo.org> X-BeenThere: gentoo-project@lists.gentoo.org Reply-To: gentoo-project@lists.gentoo.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; boundary="Sig_/XNCCar+lyrqNFj_M38z.k=B"; protocol="application/pgp-signature" X-Archives-Salt: 8b99abd8-34ca-41cd-8881-173287d7d7c3 X-Archives-Hash: b8c4f6ae7d0d0649ea9b81736f2b01b4 --Sig_/XNCCar+lyrqNFj_M38z.k=B Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Dnia 2015-01-28, o godz. 21:48:37 Markos Chandras <hwoarang@gentoo.org> napisa=C5=82(a): > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA512 >=20 > On 01/26/2015 08:12 PM, Micha=C5=82 G=C3=B3rny wrote: > > Hello, everyone. > >=20 > > I have the pleasure to announce that the official rsync2git mirror > > is up and running [1] thanks to Sven Wegener. It is updated from > > rsync every 30 minutes, and can be used both to sync your local > > Gentoo installs and to submit improvements via pull requests (see > > README [2] for some details). > >=20 > > At the same time, I have established the 'Git Mirror' [3] project > > which welcomes developers willing to help reviewing the pull > > requests and helping those improvements reach package maintainers. > >=20 > > For users, this means that we now have a fairly efficient syncing=20 > > method and a pull request-based workflow for submitting fixes. The > > auto-synced repository can also make proxy-maint workflow easier. > >=20 > > For developers, this either means: > >=20 > > a. if you want to help us, join the team, watch the pull requests.=20 > > CC maintainers when appropriate, review, even work towards merging=20 > > the changes with approval of the maintainers, > >=20 > > b. if you want to support git users, just wait till we CC you and > > then review, help, merge :), > >=20 > > c. if you don't want to support git users, just ignore the repo. > > We'll bother you directly after the changes are reviewed and ready > > :). > >=20 > > [1]:https://github.com/gentoo/gentoo-portage-rsync-mirror=20 > > [2]:https://github.com/gentoo/gentoo-portage-rsync-mirror#README=20 > > [3]:https://wiki.gentoo.org/wiki/Project:Git_mirror > >=20 > Hi, >=20 > First of all let me express my gratitude on what you did! It's a > really nice effort towards the right direction. However, I feel there > is a bit of overlap with the proxy-maintainers[1] repository. On the > readme file you suggest to not commit anything to this git repository > (not even merge pull requests). So what's the purpose of having the > pull requests in the first place? I believe, in order to avoid > confusion, users should use the proxy-maintainers repository for pull > requests for the packages they maintain. Otherwise, just stick to the > bugzilla for ebuilds that have developers as maintainers. I believe we > are running into the risk of having too many places for user > contributions, and that will make maintenance a nightmare because you > will have devs taking care of proxy-maint pull requests, and then > others taking care of the rsync-git mirror pull requests. I believe > you need to rethink the proposed workflow. >=20 > [1] https://github.com/gentoo/proxy-maintainers I have talked to some of the team members and they expressed interest in using this repository instead of proxy-maint one. The main advantage is that the repository is synced to gx86, so users don't have to copy/sync ebuilds manually to work on them. The pull request workflow still has advantages, even if you don't use the github's built-in merge mechanism. Developers can easily pull the changes to their local repo and test them, and then copy over to CVS. Plus github provides a simple review workflow with comments and updates. As I see it, it's both better for users and developers. More points of contribution can be a bit confusing but also go towards a more distributed workflow. If user can help me by contributing to Gentoo, I don't think we should require him to match our fancy tools but let him use the tools he finds helpful. And a lot of people find github this way. That said, I still think the workflow is easier. Cloning and creating the pull request is more console-friendly than opening a bug and attaching few files. Reviews can be more dynamic, and updating the pull request is much easier than deprecating and attaching new files. Not to mention downloading and testing those files... --=20 Best regards, Micha=C5=82 G=C3=B3rny --Sig_/XNCCar+lyrqNFj_M38z.k=B Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQJ8BAEBCgBmBQJUyWL+XxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2REJCMDdDQzRGMERBRDA2RUEwQUZFNDFC MDdBMUFFQUVGQjQ0NjRFAAoJELB6GurvtEZOTNIP/iK0DGPYkk2rG1wYfGtgCq+y CVYQ0BIMdo7FlzgB/06kgtAO4XEe592fJK+JTXf9hcBFaceUT+JJksIfJeYkhBtl XoMIw+p7UkLuNpcF5lW5zXOynBFoZlmoXK548TVMA1YoZfhOKGPN5OBoVl04P0oR 4/KaFgTlGgJ0Usbjh6tJj2pdF6GnmMkIVdXLmvGztCdw2S1u2xlOxbLUa4oZWNUq dxDSjIZebrC6eYncCJBNHXnjm0ceU75hqjVZMDM1Ot5ZzsiVjVWY6jQVg3QCP31z AKVF3Q5syvfMSarTgnCc18pkdV0DP20s7yUU6chSl1HPm8i6r1rnRhRkDTxeBM4z rJD7jmlYhSgo2vnw5vDkDjMNHM2eTptLbJNkyYRZeOBDyafe+O4sh1K+RHxxiNop /HpYwzF7KPWc/o4+LS0HDIaDkS8gNJlQlBFXBBAwwNlJnZJu107mxboJhuuOi/Un EWJuT1GuMpUAvySypXMLrIYggDX75cGOP400kUZNw5nLgCvFmZvAT3IZlybU0Zus DyyMMhbodUKgjNqAG529/ZMbNh020QiWQlAD0DE8498SwnxN2+/rsjSSS4mB7igr WGKvrMRx3L9FTnvaLOZG9mi1G2oYnZ/GWQk/p/voe524fpkIym4nhoDF2rQfHhVF yWCp0JTpJWwNWzpbSFyu =tD00 -----END PGP SIGNATURE----- --Sig_/XNCCar+lyrqNFj_M38z.k=B--