From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id F1B941387FD for ; Tue, 10 Jun 2014 10:30:23 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 6113EE09F4; Tue, 10 Jun 2014 10:30:17 +0000 (UTC) Received: from mailgate-01.zdv.uni-mainz.de (mailgate-01.zdv.uni-mainz.de [134.93.178.241]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 2316FE0867 for ; Tue, 10 Jun 2014 10:30:15 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=uni-mainz.de; i=@uni-mainz.de; q=dns/txt; s=ironport; t=1402396216; x=1433932216; h=from:to:subject:date:message-id:in-reply-to:references: mime-version; bh=HvMNv/C8oo5D6iiz6X/Afp7IiYLwNKf2hEHjVDQ32E0=; b=G09N1HGmu/MUgBhaxAnxx64/yEklxphaQugEjLJ+QIjT94UvNSMe7jmS EAvu0IEJ3+lno6y1AVGlrI48ImWFV1gqsDyJHGvK/oifxYIsol7JaDlQu lqYGBks89O7SIIG1C4pLfzeE/8P2vtxLnrW5gpYFKt2iTvB+1nv4Y6u2R I=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AlEKAN7cllMKXgZQ/2dsb2JhbABZg19ZqmEBAQEBAQEGijSOXAGBIXWEAwEBBW4bCxgJJQ8BRwaIVQ3LHxMEhV2JFhaEKwShEoQ8BIgUgz6CLQ X-IPAS-Result: AlEKAN7cllMKXgZQ/2dsb2JhbABZg19ZqmEBAQEBAQEGijSOXAGBIXWEAwEBBW4bCxgJJQ8BRwaIVQ3LHxMEhV2JFhaEKwShEoQ8BIgUgz6CLQ Received: from e14hub-01.zdv.uni-mainz.de ([10.94.6.80]) by mailgate-01.zdv.uni-mainz.de with ESMTP/TLS/AES128-SHA; 10 Jun 2014 12:30:14 +0200 Received: from cschwan-laptop.localnet (134.93.93.96) by mail.uni-mainz.de (10.94.6.82) with Microsoft SMTP Server (TLS) id 14.3.181.6; Tue, 10 Jun 2014 12:30:13 +0200 From: Christopher Schwan To: Subject: Re: [gentoo-dev] The state and future of the OpenRC project Date: Tue, 10 Jun 2014 12:30:09 +0200 Message-ID: <3439561.dz4noWu4c3@cschwan-laptop> User-Agent: KMail/4.13.1 (Linux/3.12.21-gentoo-r1; KDE/4.13.1; x86_64; ; ) In-Reply-To: <53962AF6.1050500@gentoo.org> References: <20140607201920.0e0ccd5c@gentoo.org> <5396106A.4010209@gentoo.org> <53962AF6.1050500@gentoo.org> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart28050240.PJHdgx1N8u"; micalg=pgp-sha512; protocol="application/pgp-signature" X-Originating-IP: [134.93.93.96] X-Archives-Salt: a7d683d7-9c19-4729-8ac2-eda9b45b33bd X-Archives-Hash: 5b5d41e1086279d59aa566ba7e06ec8d --nextPart28050240.PJHdgx1N8u Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" On Monday 09 June 2014 21:45:26 hasufell wrote: > Probably because no one mentored them on how to fix these QA issues. > Otherwise... if that's attitude, then that's just sad and has to be > fixed by those who run that overlay (review, contribution guidelines). > > And I still think that the top 1 reason people run an overlay is because > it's easier than contributing directly. > A lot of overlay maintainers I tried to convince on getting more > involved even said that. > > Even sunrise workflow has proven too slow and cumbersome... look at the > commit history, it's constantly decreasing. > > Sure, reasons may vary, but there is not much positive to say about > current gentoo workflow. Since I was mentioned here - I am one of sage overlay[1] developers - it is maybe worth sharing my point of view as someone that is not a Gentoo developer. The recent discussion[2] with hasufell on our overlay might also be interesting. I have to agree that indeed it is easier to contribute to an overlay, in my case because of a) git and b) github. As far as I am up-to-date the main Gentoo repository is still managed by cvs, right? Thats something I really would not like to work with. Not because cvs is inferior to git (I hope no one feels offended) but because now I am so used to and pleased with the workflow that comes with git that I can not even think of changing that. What I really love about github (and I don't think that similar platform differ much here) is the fact that it allows me to comment on /everything/. I can comment on commits that maybe lack something, which could then result in a new Issue; a user could be faster than I and create a pull request that fixes this problem. Maybe there is another mistake which I tell him there so he adjusts his commit and I finally accept it. Sometimes, after some months I wonder why we decided about some things the way we did and I can look it up in the Issue. There is the _complete_ discussion with direct references to the code and all people involved. If there is a lession that I learned here, than that centralizing communications and development in one place was beneficial for us. Whether this also applies to the Gentoo project - well, I don't know. Right now there are several mailing lists, IRC channels and the Bugzilla so in comparison to our little overlay it is quite decentralized. Adding another way, e.g. via github, could complicate the situation but it will defintely get the project more user contributions (if that is needed). In any case, I believe that the migration to git would be a huge step forward and it would attract at least one pontential new developer ;). Any update on this? [1] https://github.com/cschwan/sage-on-gentoo [2] https://github.com/cschwan/sage-on-gentoo/issues/294 --nextPart28050240.PJHdgx1N8u Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part. Content-Transfer-Encoding: 7Bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQEcBAABCgAGBQJTlt41AAoJEAeHQ0RVxNInoQYH/0rjxziA0P/r35V0ZwCojEds 23h7S4oMbhbsefUpUxw96qUaK3ljRsJAn1QEQP1IB6UmZnWxd9NrISWnHASbDmPR ysvG3XGBhaI4CvIwBD7+tCx2FlQ+MsyOF+CpghjMZQQ6bqbwRl+uTew3lMiOSzax rqAh2Vsi3+CPmc35VkpmOW2TlHWsbxh1npW493aDh6XNyA2q2ik4dpbDYOZznzyI 0UP7SkZnwsxKszeFCThJ+wfPJAVvu1xCKkj7IfhegK14tnrmlVUCtLTPNib1kcQl 2oHTAN6psEhpTjPlnpLxRrwXXVu5NyxQ/07Fy1TJpoB2H8O+V+i5C/bjViYcERY= =tUr3 -----END PGP SIGNATURE----- --nextPart28050240.PJHdgx1N8u--