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 BB532138C48 for ; Sun, 12 Apr 2015 11:22:21 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id C707DE0C0A; Sun, 12 Apr 2015 11:22:18 +0000 (UTC) Received: from mail-ig0-f182.google.com (mail-ig0-f182.google.com [209.85.213.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 464E0E0C09 for ; Sun, 12 Apr 2015 11:22:18 +0000 (UTC) Received: by igblo3 with SMTP id lo3so26207824igb.0 for ; Sun, 12 Apr 2015 04:22:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:content-type; bh=fowxa871FnQpEHrSA/5yttaqthX49TD25ZbWlmEUIx8=; b=H56Kl/uKGgkCEAVGFXqiSvcRfQOk+g41rfnYrrzHKAj2LDBI0Gcam3O5jNlmTULj26 p47y8NtGB7kp2Tfo3Qr7BY99Il7Eqc19q31umW3nz2FtpBep0CwO6PsDdYgBspdcbv6l Usfy+mAIwMzjLZTlAFDdSjdK0JqhVRS4HXnrDnbz2smFa955dnFJ5w+3l3KUXry+lMcE BiDuFuCXzuLq5zsk8AHuJaxKKaIz1ncydtfHONJNRR9I5TP7NuZjAL4a4nmI4bkGCVIK V/m54v+L2UUeUZLQxhgP/xu19chl9nxUr79sOa/j3Dl1910d4p4zxYng5o0q2jap6rbB VWSQ== Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Project discussion list X-BeenThere: gentoo-project@lists.gentoo.org Reply-To: gentoo-project@lists.gentoo.org MIME-Version: 1.0 X-Received: by 10.107.38.17 with SMTP id m17mr14021123iom.84.1428837737545; Sun, 12 Apr 2015 04:22:17 -0700 (PDT) Sender: freemanrich@gmail.com Received: by 10.107.48.66 with HTTP; Sun, 12 Apr 2015 04:22:17 -0700 (PDT) In-Reply-To: <552A41ED.7070103@gentoo.org> References: <5526CB7F.2050302@gentoo.org> <5527F6D7.7010404@gentoo.org> <5528F375.30009@gentoo.org> <552A41ED.7070103@gentoo.org> Date: Sun, 12 Apr 2015 07:22:17 -0400 X-Google-Sender-Auth: McOlHQ3qYMkzF_3EVHr2ClOdoJc Message-ID: Subject: Re: [gentoo-project] Status update of Sunrise project? From: Rich Freeman To: gentoo-project@lists.gentoo.org Content-Type: text/plain; charset=UTF-8 X-Archives-Salt: 7a5999ae-e97f-42d2-b7c5-b2e030fec4da X-Archives-Hash: c7800f4d844658cde2e1d9d504d54890 On Sun, Apr 12, 2015 at 5:59 AM, hasufell wrote: > On 04/11/2015 01:54 PM, Rich Freeman wrote: >> >> 1. What does proxy-maintainers lack in comparison to sunrise >> exclusively. The immediate question is whether sunrise should be >> migrated to proxy-maintainers, so this specific comparison is >> important. >> > > proxy-maintainers lack: > 1. a repository with a usable VCS proxy-maintainers is using git. Am I missing something? > 2. an actual review workflow... @proxy-maintainers are just some sort of > backup committers. it's not a hub for contributors to gather, discuss, > get reviews and improve skills My understanding is that github pull-requests are being used. I'll buy that the project is still fairly immature but it seems like they have a decent foundation for a review-oriented workflow. Perhaps you might consider getting involved and building improvements? > 3. means to ensure the tree doesn't break Well, we don't even do this well in the main repository. proxy-maintainers can use repoman, as can committers, but I'll buy that those aren't the best solution. There are already efforts to get travis-ci working on the main tree, and presumably this could be applied to proxy-maintainers as well. > 4. actively look for and educate potential developers, even before the > recruitment process Sure, but I don't see this as an issue with proxy-maintainers, but more of another layer to add. Honestly, I see many of the seeds of things that you're looking for in the project already. Change has been slow, but the number of people doing the work has also been small. We don't have a huge number of new devs in general, and most of those new devs are interested in being package maintainers, not "Gentoo Maintainers" helping to change how we do things. I'd be interested in suggestions as to how to recruit the latter, but I think the nature of our distro tends to appeal more to users who are more interested in the nuts and bolts than the organization. I get your frustration, but I think you should look more at the trend direction. Sure, we're not doing a lot in terms of a workflow not centered around having cvs commit rights, but we're doing a lot more than we were even a year ago. If there are others who would like to make it happen but see barriers to this, I'd be interested in hearing from them. -- Rich