From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 8ECAE139694 for ; Fri, 21 Jul 2017 14:36:43 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id BCD0EE0BB2; Fri, 21 Jul 2017 14:36:42 +0000 (UTC) Received: from mx1.7thlake.com (mx1.7thlake.com [52.0.20.86]) (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 944A3E0BB2 for ; Fri, 21 Jul 2017 14:36:42 +0000 (UTC) Received: from [192.168.0.245] (cpe-67-242-57-159.twcny.res.rr.com [67.242.57.159]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mx1.7thlake.com (Postfix) with ESMTPSA id C919376012F for ; Fri, 21 Jul 2017 10:36:41 -0400 (EDT) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.99 at ip-172-30-3-20.ec2.internal DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=parallaxshift.com; s=dkim_selector_hobbes_20120412; t=1500647801; bh=pMBBusGnXvU6ppR7UCGF9mfvKETPA8cWIc5O028hm+s=; h=Subject:To:References:From:Date:In-Reply-To; b=om9PmY1hfsJi+JDe63pEAGbfcPKPNHmOHU8tpyiqTEMwj5wlabotZzXKdW4D2FwsI ATVgXHxxFgcFW9nFqS4IfmBZ/sbHnvjP0LDrTh8u+yi3Mh0PE51xG5h4S1w0LDd8LC GIxKucSc5Ook2VfgeUmmQ//rvv6llP+kbRyG2SKw= Subject: Re: [gentoo-proxy-maint] [RFC] New doc & policy To: gentoo-proxy-maint@lists.gentoo.org References: <1500537721.746.2.camel@gentoo.org> <1500584775.746.11.camel@gentoo.org> From: Philippe Chaintreuil Message-ID: Date: Fri, 21 Jul 2017 10:36:28 -0400 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Proxy Maintainers X-BeenThere: gentoo-proxy-maint@gentoo.org X-BeenThere: gentoo-proxy-maint@lists.gentoo.org MIME-Version: 1.0 In-Reply-To: <1500584775.746.11.camel@gentoo.org> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="gGjJDm8gQgVidh93j0p9W58D1oErGsfDu" X-Archives-Salt: 6e9a421f-d331-4205-a884-cbd89e45d253 X-Archives-Hash: a717c1908adedd468d870c91de93e4d9 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --gGjJDm8gQgVidh93j0p9W58D1oErGsfDu Content-Type: multipart/mixed; boundary="6cJWpaRV0bW9xhAUg98UKoSmrO1V3dUXX"; protected-headers="v1" From: Philippe Chaintreuil To: gentoo-proxy-maint@lists.gentoo.org Message-ID: Subject: Re: [gentoo-proxy-maint] [RFC] New doc & policy References: <1500537721.746.2.camel@gentoo.org> <1500584775.746.11.camel@gentoo.org> In-Reply-To: <1500584775.746.11.camel@gentoo.org> --6cJWpaRV0bW9xhAUg98UKoSmrO1V3dUXX Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 7/20/2017 5:06 PM, Micha=C5=82 G=C3=B3rny wrote: > On czw, 2017-07-20 at 10:02 +0200, Micha=C5=82 G=C3=B3rny wrote: > Here's v2, taking into account suggestions from k_f and wraeth: > =3D=3DHow to become a proxied maintainer=3D=3D This whole section seems to assume a lot of knowledge of infrastructure that I don't think someone wanting become a proxy-maintainer will have. It also seems to me that it has a lot of "all you need to do is this one simple thing", followed by 3-4 reasons there will be other things you need to do before that one simple thing. This section would do better with a checklist of steps followed by explanations of "why" as needed in my opinion. Imagine being a total neophyte and seeing "maintainer needed" on a package you have a vested interest in. What is your first step of contact? The current text makes me think that it's a cold-called Pull-Request planting your flag in the metadata.xml. Is that the intention? Or should people be joining this mailing list and getting a list of things that will need to be fixed before that pull-request? Also, if proxy-maintainers taking control of existing packages are more common than creating new packages, it would seem to me that section should come first. Additionally, I'd like to see a section on what a new proxy-maintainer should do when they need help. Especially when working in "maintainer-needed" ebuilds where it's not obvious. --6cJWpaRV0bW9xhAUg98UKoSmrO1V3dUXX-- --gGjJDm8gQgVidh93j0p9W58D1oErGsfDu Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iF4EAREIAAYFAllyEXkACgkQ19/IQVCLMWH1cQD9HkOi0I3siwu59eUz4lT+FfyK OSVVSld7WibWO6vzvokBALM3FmXhpWE9/EMAoh3FFTAMHhVgzuBF+DLAkV4PHlSQ =dCRX -----END PGP SIGNATURE----- --gGjJDm8gQgVidh93j0p9W58D1oErGsfDu--