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 6B2171382C5 for ; Sun, 15 Apr 2018 17:22:59 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id B3361E0875; Sun, 15 Apr 2018 17:22:57 +0000 (UTC) Received: from avasout05.plus.net (avasout05.plus.net [84.93.230.250]) (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 688D3E086F for ; Sun, 15 Apr 2018 17:22:57 +0000 (UTC) Received: from [192.168.6.147] ([212.159.46.162]) by smtp with ESMTP id 7lMaf8H0n1fhE7lMcfCJs9; Sun, 15 Apr 2018 18:22:55 +0100 X-CM-Score: 0.00 X-CNFS-Analysis: v=2.3 cv=J9KEEjvS c=1 sm=1 tr=0 a=RuViaDnnNG9rfPLW4VJocg==:117 a=RuViaDnnNG9rfPLW4VJocg==:17 a=13zjGPudsaEWiJwPRgMA:9 a=7mOBRU54AAAA:8 a=AFpmWziVblWYsT8hMx4A:9 a=QEXdDO2ut3YA:10 a=XAaABn8v0xflId1S26QA:9 a=ONNS8QRKHyMA:10 a=wa9RWnbW_A1YIeRBVszw:22 Subject: Re: [gentoo-project] pre-GLEP: Gentoo Developer status To: gentoo-project@lists.gentoo.org References: <1523640697.5139.2.camel@gentoo.org> <1523690669.1482.5.camel@gentoo.org> <6b94d416-5521-2719-30db-993babefd04c@gentoo.org> <1523794944.1347.18.camel@gentoo.org> From: "M. J. Everitt" Openpgp: id=BA266E0525CFAB101523351B4C30334F93C22371 Message-ID: <24012268-8b6e-5df9-bf28-c96955e92ed1@iee.org> Date: Sun, 15 Apr 2018 18:22:48 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 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 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="nblDYfUHTOQtpFRkmRB7htbF12LtKKQFR" X-CMAE-Envelope: MS4wfBDcmzJqoIIo14DT4GINciEl/fKxobZhlZA4uXYcB5KaQsrmLoP2yNWLpUDtha6h4o6vld5pa16Z0ltzWJMlrunOLtdaMGmT3DvsuA1+jLT9VAmwEgu9 TENgXCr2JhmWspIupgm3Od+sEhqUB1WV2j/29zLlTaNPQs9uRzjKa7a26ppLU7kxPdv8vKGg16dmGw== X-Archives-Salt: 8f2deae3-68b5-4593-9027-96248e48c9cd X-Archives-Hash: 780576cdc8f79eb393acd49f32b8c9d1 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --nblDYfUHTOQtpFRkmRB7htbF12LtKKQFR Content-Type: multipart/mixed; boundary="brdBkmkvrw17kdov89dnmZmRGix86wMAz"; protected-headers="v1" From: "M. J. Everitt" To: gentoo-project@lists.gentoo.org Message-ID: <24012268-8b6e-5df9-bf28-c96955e92ed1@iee.org> Subject: Re: [gentoo-project] pre-GLEP: Gentoo Developer status References: <1523640697.5139.2.camel@gentoo.org> <1523690669.1482.5.camel@gentoo.org> <6b94d416-5521-2719-30db-993babefd04c@gentoo.org> <1523794944.1347.18.camel@gentoo.org> In-Reply-To: --brdBkmkvrw17kdov89dnmZmRGix86wMAz Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Content-Language: en-GB On 15/04/18 17:55, Francisco Blas Izquierdo Riera (klondike) wrote: > This is not what I'm saying. In fact current practice is different from= > what you purvey: > * Ebuild developers are usually asked about reassignment: see > https://bugs.gentoo.org/show_bug.cgi?id=3Dvapier or > https://bugs.gentoo.org/show_bug.cgi?id=3Dhwoarang > * If they state they are interested in maintaining the packages they ar= e > allowed to do so (I guess unless the council decides to reassign them).= > > Here is a similar approach that would work for both: > * Once a developer has been inactive for x time (for example not having= > voted on two consecutive council electiions), the developer is contacte= d > by undertakers and asked whether he/she/it is still interested in Gento= o > and has contributed soomething that went missing in this period. > Undertakers also give a deadline for a reply. > ** If the answer is afirmative and the developer sends some > contributions the undertakers close the issue. > ** If the answer is negative but the developer wants to continue > contributing, the undertaker can provide advice on how to do so and > extend the deadline a bit (after which the developer will be retired an= d > invited to take the tests). > ** If the answer is negative and the developer is okay with retiring, > retirement is done. > ** If no reply is obtained before the deadline, retirement is done. > > Turns out that this is, in a way, the process documented on the > Undertakers project itself: https://wiki.gentoo.org/wiki/Project:Undert= akers > I have long thought there could be improvements to the Undertakers process, and I think developers that have been MIA for some time (for whatever circumstances) have some checks made that they are indeed up-to-speed with any policy changes that may have happened since their last 'active' period. This would be not to penalise them, but ensure that the Quality standards that Gentoo holds, are upheld, and devs don't get to run riot once their initial 'assessment' and recruitment phases are over. It would provide a better 'continual development' track that could be expanded into other areas if proven and desirable. My ideas went so far as: -- if Dev does not set Devaway, and/or devaway period is over ~6months (say) and activity has fallen to zero .. commit privs get automatically revoked (by script, not by human). An automated email is sent out to that Dev, encouraging them to contact [insert project here] (eg. Council, ComReS, DevRel, etc) if there is good reason for the absence, the privs can be reinstated after a petition has been received and review= ed. -- A fast-track re-fresher training is provided by Recruiters, which brings an existing or elapsed dev back up to current standards. Such topics as new EAPIs, QA tracks, and policy updates could be covered in a couple of 'sessions' and then commit privs can be reinstated. I think this would improve the situation where some devs commit in large 'bursts' in between significant lapses in activity, causing a lot of distress to other more regular contributors and disrupting some of the more consistent ongoing efforts. --brdBkmkvrw17kdov89dnmZmRGix86wMAz-- --nblDYfUHTOQtpFRkmRB7htbF12LtKKQFR 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 iQIcBAEBCAAGBQJa04psAAoJEGPnxnn01DHdjBIQALFlcXnM/9+ji1m7h5Cf+R1b cm9dTXVLGJvrTPMkYVAsvk3aWx6rp6dd0mXNlUAI2M2ZiE0gsSbT5PZk3wTxU+tw mJQCq4xRf+OshNrl+5ZA0QeHwxw26tZX0YouMBa/76oMgq0AzCRKKa+oNcInEf76 N2RM+H25bdpdZWJ2W7Ecj8SzOd1JbYEtSI8mD5DEH+kS/R1D2GiBsJPUn6C49WXr wFvfogzbIfQYdXmE+povfuDMF9Kc8a7C0YWCjN4jWTl51Mb22oZv/EnWelwpjEI0 riweMe0AjdpU0zM4vb65XXbFqBmadbwvXIp5EXuJRPJx4TpFuwuDzJ0x8r0HNbwY ojV0qzikyv6/Tmq5AjJR2SArCuhuvAN04zHUYu0yReTHjouMNtZdHGrUttmNF99L FS5DBq3u71tsPqFKOsCpRHvM8QGIJ8tRF1bB1JgqISYB9zbIEZ+V8/bFHXB8so0m 2xI479YrWLhHim2omg7mSZOozYeWtSYVLqe3XglnE3QlDHnQRexmKlsT+rRvO4X8 Tg+pGkZ2vrob6+8lORLWNLXo4zaxRLwcl7Fox26kLMkNA/mVvw+rQUT4Skex0DtI jHUvKwnp4vRyFGqJ0YbTgXxp1HmfQ0jMFHDQkHzB5foMLV/eFrvTOadj/OSf9Z3q 7u1y/3DkNySPFdTYOFN0 =3tX6 -----END PGP SIGNATURE----- --nblDYfUHTOQtpFRkmRB7htbF12LtKKQFR--