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 11E28138262 for ; Sat, 21 May 2016 02:35:41 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id B221C21C06B; Sat, 21 May 2016 02:35:32 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 9FA1221C060 for ; Sat, 21 May 2016 02:35:31 +0000 (UTC) Received: from nemesis.wraeth.lan (unknown [103.6.188.92]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: wraeth) by smtp.gentoo.org (Postfix) with ESMTPSA id 902AF340A6A for ; Sat, 21 May 2016 02:35:29 +0000 (UTC) Date: Sat, 21 May 2016 12:35:31 +1000 From: Sam Jorna To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] new developers' keyword requests Message-ID: <20160521023529.GA10821@nemesis.wraeth.lan> Mail-Followup-To: gentoo-dev@lists.gentoo.org References: <20160519165130.7e9bc385@wim.fritz.box> <20160520160002.2aace085@wim.fritz.box> <20160521100904.736a044a@archtester.homenetwork> 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; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="YiEDa0DAkWCtVeE4" Content-Disposition: inline In-Reply-To: <20160521100904.736a044a@archtester.homenetwork> User-Agent: Mutt/1.6.1 (2016-04-27) X-Archives-Salt: 3d8f0ad9-bff5-40f0-bae0-4e3a789e11c4 X-Archives-Hash: d23b43a3cb173a7052b4a50a941af7bd --YiEDa0DAkWCtVeE4 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, May 21, 2016 at 10:09:04AM +0800, Ian Delaney wrote: > On Fri, 20 May 2016 16:00:02 +0200 > Jeroen Roovers wrote: >=20 > > On Thu, 19 May 2016 18:36:22 -0700 > > Daniel Campbell wrote: > >=20 > > > To make sure I understand what you're getting at, are you saying > > > some devs get on board and then request to add keywords to packages > > > that they already maintain? If said arches are already supported in > > > Gentoo I see little problem with that, especially if they intend on > > > being part of the arch testing team for that arch or have access to > > > the hardware. =20 > >=20 > > I am not talking about adding architecture keywords to profiles/. > > I am talking about adding architecture keywords to ebuilds. > >=20 > >=20 > > Regards, > > jer > >=20 >=20 > Firstly I think previous replies have been de-railed on talking about > new alternate arches, which personally I think is the last thing we > need. If there is any confusion it is because the term keyword, like > most terms in I.T. gets pushed and pulled and stretched until it breaks. > To my understanding, KEYWORDS are arches. But being told to 'keyword' a > package could mean perhaps, well, Hu knows.=20 I don't know of any other usages of "KEYWORDS" within Gentoo - to my knowledge the only definition is a list of which architectures a package is known to work or not work on, and an indication of the level of testing and expected usability on that architecture. Is there some other definition that I'm missing? > Supporting users doing just this lately, I have come across this a few > times. Users and new devs are expected to be very ignorant of minor > arches, and despite having docs already informing them that they are > short staffed and have enough to do, the practicalities of how and why > to keyword request or not are still veiled in mystery. Users want to > keyword according to what they see supported upstream just because > they can. They appear to need it made manually clear to them that there > are qualifiers and conditions for putting something up for keywording. > These also I believe are as much as mystery to users as they are to > devs. =20 Appropriate use of KEYWORDS is actually covered in the Developer quizzes, so I would have instead expected new developers to be more acutely aware of the fact that keywording on minor arches should be generally reserved for an as-needed basis. > How to establish a level of desire form userland to have gentoo > support the arch in the package?? > How to establish sane rationale for it being put up for stable?? > The last I heard was along the lines of, well, only put it up if it has > already been put up in the past.(someone in the past had a check list?) >=20 > If anyone, the members of the arch teams might have some insights based > upon first hand dealing with packages and their categories. Frankly, > how you can expect or achieve users and new devs to assess these is > more the issue, and I do not see there is any obvious path of becoming > informed of the interest of an invisible audience; userland As far as I know, users (as in non-maintainers - those out "in the wild") can file keyword request bugs and it's up to the maintainer to then determine relevancy and CC appropriate arch teams; and Bugzilla has a voting feature[0] allowing users to indicate the strength of community demand by voting on those bugs (which I have seen done previously). [0] https://bugs.gentoo.org/page.cgi?id=3Dfields.html#votes --=20 Sam Jorna GnuPG Key: D6180C26 --YiEDa0DAkWCtVeE4 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.1 iQJ8BAEBCgBmBQJXP8ltXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ5MEUzODI4QUYzQ0Y2RTc1M0Y0MDBCRkZG NUFDRTY4OUM5QTc1NzNDAAoJEPWs5onJp1c8CbwP/j8U0xdOkZuQr+D5QGl1fhV8 etErotyYObGlHBPh588FMYSo5oZwmAeh8/v49umuouJHJ2BXaiTxpfSerz602aTs 41MG32zpG5DJkxv0aCTFn4gdP4YIVrchkcAAIIlcjc/ykXnUKa9KS1ViGYEGJZT5 xacBqma1UTmrBui8LuY4dYaf/if6M6HMrcm7Vku7WkjmeFUCESjMCBTT6GUCrmNf Z7YY6IePuWJbIyA9mBjU2c6Lxc4lWpRNwLAp/qZLC3MuuH5LDCCnrweP1aPNrBmi +BG7f5deDYvZg68DlKQPomSm7EHTVv1Y8ZT2hRP/+kDZgL8HxY+VzPTv+h7Iooaj RI6xEGBvpp/945lFdjxPwcG1VC3y25G7/kpPVmVlgkhU/+WkKYwGEf7d3wgmTB7b wkLS4wu/fK0pit7GwZhlqi4A6qRVBYPw4SQAoruJP3og4lHJ8XA6xgo6gkxknrBi Fk2SX6GhOMpSGYq2/VcSHeuCUh0TIwUlQmuOfZdVmUeSvJcMBSYBxevVNksyzsdi XqK57AbR+S1jz8BBbStZYICkuaDu8dw4N6k4SEBu1hW8Y+EajY/YFFHMjZDvliwO ij3FkgOIS5S7vNzNan2MI9CLga2oDPRnmY18dKhdUfeHUZajE8OlAunxgOT3UI86 Tq9IeJzzoCmcuJqR+GBN =KXb7 -----END PGP SIGNATURE----- --YiEDa0DAkWCtVeE4--