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 54A57138E20 for ; Fri, 21 Feb 2014 04:02:30 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id E3EDDE0B6C; Fri, 21 Feb 2014 04:02:24 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 82A76E0AEC; Fri, 21 Feb 2014 04:00:47 +0000 (UTC) Received: from localhost (c-75-73-165-249.hsd1.mn.comcast.net [75.73.165.249]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: dberkholz) by smtp.gentoo.org (Postfix) with ESMTPSA id 963FE33FC76; Fri, 21 Feb 2014 04:00:46 +0000 (UTC) Date: Thu, 20 Feb 2014 22:00:44 -0600 From: Donnie Berkholz To: gentoo-dev-announce@lists.gentoo.org, gentoo-project@lists.gentoo.org Subject: [gentoo-dev-announce] Agenda for Gentoo Council meeting on 2014-02-25 Message-ID: <20140221040044.GG8819@comet.hsd1.mn.comcast.net> Reply-To: gentoo-project@lists.gentoo.org Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo development announcement list X-BeenThere: gentoo-dev-announce@lists.gentoo.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="uJrvpPjGB3z5kYrA" Content-Disposition: inline User-Agent: Mutt/1.5.22 (2013-10-16) X-Archives-Salt: 0684faf8-8ae3-430f-8b97-0030cdeb0777 X-Archives-Hash: 54fc023f023beefcd2a52c5344a3d0bf --uJrvpPjGB3z5kYrA Content-Type: multipart/mixed; boundary="MrRUTeZlqqNo1jQ9" Content-Disposition: inline --MrRUTeZlqqNo1jQ9 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable I've attached a draft agenda for Tuesday's meeting. Suggestions welcome! --=20 Thanks, Donnie Donnie Berkholz Council Member / Sr. Developer, Gentoo Linux Analyst, RedMonk --MrRUTeZlqqNo1jQ9 Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="council_agenda_20140225.txt" Content-Transfer-Encoding: quoted-printable Roll call =3D=3D=3D=3D=3D=3D=3D=3D=3D blueness dberkholz dilfridge rich0 scarabeus ulm=20 williamh Open bugs/issues =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D (5 minutes) Update: GPG signing GLEP is now draft and has a number assigned.=20 - https://wiki.gentoo.org/wiki/GLEP:63 EAPI deprecation =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D (20 minutes) Based on the summary of our 2013-04-09 meeting, we could take the=20 following votes: - "EAPI 3 is deprecated. Repoman should warn about this." - "EAPI 0 is deprecated. Repoman should warn about this." - "EAPI 1 is long deprecated and now banned. Repoman should refuse=20 committing a new EAPI 1 ebuild." - "EAPI 2 is long deprecated and now banned. Repoman should refuse=20 committing a new EAPI 2 ebuild." QA has recommended banning EAPI 1 and deprecating EAPIs 0 and 3, as=20 three of the above votes propose. The agenda additionally proposes=20 banning EAPI 2. Portage 2.1.9.42 (supporting EAPI 4) went stable on the last architecture on 2011-03-17 which was almost three years ago. References: - http://article.gmane.org/gmane.linux.gentoo.project/3303 - http://article.gmane.org/gmane.linux.gentoo.devel/90291 Stable keywords on testing architectures =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D (10 minutes) Problem: They're screwing up workflows of other devs Proposed solution: Mark minor archs 'exp' so repoman ignores them by=20 default and so 'dev' profiles are reasonably useful as well Vote on proposed solution References: - http://article.gmane.org/gmane.linux.gentoo.project/3311 - https://bugs.gentoo.org/show_bug.cgi?id=3D498332#c5 - https://bugs.gentoo.org/show_bug.cgi?id=3D498332#c11 gtk USE flags =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D (20 minutes) chithanh has asked whether QA can make decisions about USE flag naming=20 and usage. I interpret that to mean whether QA has authority over tree=20 policy. Vote: Confirm whether QA has authority over tree policy, including USE=20 flag naming and usage. References: - http://article.gmane.org/gmane.linux.gentoo.devel/90291 - http://article.gmane.org/gmane.linux.gentoo.project/3321 - https://wiki.gentoo.org/wiki/GLEP:48 ulm requested that the council examine QA's decision. Vote: Do we affirm QA's decision? If not: Vote: What should the USE flag usage be? - 'gtk' only (maintainer chooses optimal version) - 'gtk2', 'gtk3' etc but without 'gtk' - subpoint: 'gtk' =3D=3D 'gtk2' for ease of porting - 'gtk' is a USE_EXPAND like python versions - 'gtk' is mandatory for *any* version, gtk2/gtk3 pick which References: - http://article.gmane.org/gmane.linux.gentoo.project/3319 - http://article.gmane.org/gmane.linux.gentoo.devel/90291 - (2005) http://marc.info/?l=3Dgentoo-dev&m=3D111212920310822&w=3D2 Open floor =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D (5 minutes) --MrRUTeZlqqNo1jQ9-- --uJrvpPjGB3z5kYrA Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQJ8BAABCgBmBQJTBs9sXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQxNzkxRTlGNzM0M0VCNzE1ODBBQzJEQjAx QzRBMjY4OUE2RENCMjQyAAoJEBxKJomm3LJCX+wQAKDfRXLjl+ZSEpHvMWOUwzuJ EEx7v051+OmocPgH6PcE+idfKyJg92Xv2NMU6/FNw63zkBaMx1luJ/YPh3YSzwG/ 5hox7tgvnRpOswCKHXeZjzknZLGJXr4JWIZWSeotftaMp2lDO8ebo0CpUmafomb/ fNw1ngSmLIckWmMbYh1oAwUH1dPdOjsZeFOV3AVI3C7AKNv1HZnfleYo6Z2n7N/D rUAxDna+EOfpKt2IKly0owdW6DniJIEaNsyj/vbuOEpjIRQopPhNgI0pjvP6x5Lq BoT0FexcQt0sZab68Dak3hQwBGxcVxhWcWdY0g0MHIbp0COhn45wbiMTtceaUKRj 8b70h4qle+veydiRS08qH5d74wxHaQDm1L7GZ4TxnmG1GDmwpBqRLsKwbPaKMC5O SA3BhmSiOinkAuvfCD0EcUM2KT3UPMs6V5cPFk6nnnUZbdwpT7PEY40evZAMqs0J cr9Viy7dXDdQgUhWaYuSXTbbCTFGoW9Kn7fNRP9y67uVPYw5tQIQQgV103t13fHG L0keFTWY+G5q+6Ieo/koDb8MQtGbqFmvGg74CJs5NfbFHG/iGuRUrkMhO3xcbVlZ 06GVvT7TwZHR44n/1fea5L6+zGVO2UAllkIp6F/mh8E0XhgYspJ5KkKTppS7inUk d5ABYRAs1uEANVdYr9V8 =KK1w -----END PGP SIGNATURE----- --uJrvpPjGB3z5kYrA--