From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([69.77.167.62] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1JEOaU-0001u5-Qj for garchives@archives.gentoo.org; Mon, 14 Jan 2008 12:38:47 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id D2574E0CB5; Mon, 14 Jan 2008 12:38:45 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id 58015E0CF2; Mon, 14 Jan 2008 12:34:17 +0000 (UTC) Received: from [192.168.209.100] (e177135245.adsl.alicedsl.de [85.177.135.245]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTP id DEABEB477D; Mon, 14 Jan 2008 12:34:15 +0000 (UTC) Message-ID: <478B56C0.2070003@gentoo.org> Date: Mon, 14 Jan 2008 13:34:08 +0100 From: Markus Ullmann User-Agent: Thunderbird 2.0.0.9 (X11/20071129) 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 To: gentoo-council@lists.gentoo.org CC: gentoo-dev@lists.gentoo.org, gentoo-dev-announce@lists.gentoo.org Subject: [gentoo-dev-announce] Council meeting summary 20080110 X-Enigmail-Version: 0.95.6 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig59C1B277DA5398ACE8E7178D" X-Archives-Salt: be3c4032-db57-499b-a757-c4a777ff2a15 X-Archives-Hash: c29322709c390a809cd49f7cc82cfbc2 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig59C1B277DA5398ACE8E7178D Content-Type: multipart/mixed; boundary="------------040306040202050409010709" This is a multi-part message in MIME format. --------------040306040202050409010709 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: quoted-printable Hi all, here is the summary from last week's council meeting. The complete log can be found at http://www.gentoo.org/proj/en/council/ Thanks, Markus --------------040306040202050409010709 Content-Type: text/plain; name="20080110-summary.txt" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline; filename="20080110-summary.txt" Roll call --------- (here, proxy [by whom] or slacker?) amne here betelgeuse here dberkholz proxy [musikc] flameeyes here lu_zero here=20 vapier here jokey here=20 Agenda ------ GLEP 54: scm package version suffix http://www.gentoo.org/proj/en/glep/glep-0054.html GLEP 55: Use EAPI-suffixed ebuilds (.ebuild-EAPI) http://www.gentoo.org/proj/en/glep/glep-0055.html Code of Conduct enforcement=20 http://thread.gmane.org/gmane.linux.gentoo.council/82 http://www.gentoo.org/proj/en/council/meeting-logs/20071108-summary.txt http://www.gentoo.org/proj/en/council/meeting-logs/20071213-summary.txt - What needs to happen for us to make a decision? Last week, we agreed to just add moderators to #gentoo-dev and the gentoo-dev list. Other places with their own moderation should enforce t= he CoC themselves. We also agreed that moderation must be handed over to de= vrel or userrel after 2 days. Ferris asked some questions: 1) Do we have an implementation schedule? ; 2) Have we identified some warm bodies for it?; 3) Most devrel requests seem really to relate to CoC violations. Woul= d you like us to bounce those to the CoC people, process them using CoC rules, or keep doing what we are doing now (generally, close them with = a note explaining why or mediate them)? (I'm talking about the "He's being rude/sarcastic/disrespectful" sorts of things which really need t= o be processed immediately and merit a warning or brief suspension if anything.) Slacker arches See Caleb's post on -dev and subsequent thread Calebs post: http://article.gmane.org/gmane.linux.gentoo.devel/53933 Kumba's comment on mips status: http://article.gmane.org/gmane.linux.gentoo.devel/54168 Rich0's proposal: http://article.gmane.org/gmane.linux.gentoo.devel/54103 Document of being an active developer Araujo raised that he needs some kind of written document of being an active developer. Argument being that mentioning in CV in his environment is only accepted if there is some kind of proof. Our trustee grant deferred it back to council+infra as Foundation only handles IP, but suggested it could be some kind of generated document. =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=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 GLEP 54 : Postponed to -dev ML ------- Comment from portage maintainer: - no statement about compatibility/implementation plans - more subjective: - while a distinction between CPV and atom may not be technically required, I might be useful to have - (minor) if the version part is optionl there could be some complications So is this something we'd like to have? Other ideas that came up during discussion: - -scm or _scm ? - handling as (-|_pre)9999) versions per definition - implement as dynamic package sets Related bugs: - bug #9202 - Better support for CVS Ebuilds... Pushed back to -dev ML as there are too many unresolved questions at the moment. peper is given the task to repost it and expand on usefulness / use cases as well as compatibility issues. GLEP 55 : Postponed to -dev ML ------- - Agreement on eapi subdirectories are not feasible Ideas during discussion: - moving from EAPI=3D to eapi function and using repository bashrc for compatibility Pushed back to -dev ML as there are too many unresolved questions at the moment. Slacker arches -------------- vapier will work on rich0's suggestion and repost it for discussion on -dev ML Code of Conduct enforcement --------------------------- Council members agreed on the direction, dberkholz will provide additional details on -council ML Document of being an active developer ------------------------------------- Suggested options: - Log in to dev.g.o and automatically generate there signed by infra-maintained key, put userinfo.xml website in the doc as reference. =09 dberkholz and araujo will look into a scribus based template. devrel will have to generate a signing key for these purposes. --------------040306040202050409010709-- --------------enig59C1B277DA5398ACE8E7178D 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.0.7 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHi1bDz974XjDVpbkRAsWGAJ4m/D7brf7Yu6QMTc2N3poEYltqOgCgjQfm WmwKeALVAkeVNf/J8+SAfcQ= =M6gf -----END PGP SIGNATURE----- --------------enig59C1B277DA5398ACE8E7178D-- -- gentoo-dev-announce@lists.gentoo.org mailing list