public inbox for gentoo-dev-announce@lists.gentoo.org
 help / color / mirror / Atom feed
From: Fabian Groffen <grobian@gentoo.org>
To: gentoo-project@lists.gentoo.org
Cc: gentoo-dev-announce@lists.gentoo.org
Subject: [gentoo-dev-announce] Council meeting summary: Tuesday 9 October 2012, 19:00 UTC
Date: Tue, 16 Oct 2012 20:33:19 +0200	[thread overview]
Message-ID: <20121016183319.GD809@gentoo.org> (raw)
In-Reply-To: <20121002113808.GA37574@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 2630 bytes --]

Gentoo council meeting summary 09 October 2012

Roll Call
=========
betelgeuse
chainsaw
dberkholz
grobian
scarabeus
ulm
williamh


Allow using EAPI5 in the tree
=============================
Portage supports EAPI 5 since version 2.1.11.19.
Vote: unanimous yes

EAPI 5 is allowed for ebuilds in the tree.  The Council likes to note
that EAPI 5 is not allowed to be used for stable ebuilds yet, for as
long as a Portage supporting it is not marked stable.


Package name specification
==========================
See [1].
Vote:
  a) Drop the limitation entirely (possibly in a future EAPI).
   -> noone voted for this option
  b) Make it stricter, i.e. disallow package names ending in a hyphen
     followed by anything that looks like a valid PVR.  This is current
     Portage behaviour, and the tree complies with it, too.
   -> vote by: betelgeuse dberkholz grobian scarabeus ulm williamh
  c) Leave the spec as it is (and make Portage comply with it).
   -> vote by: chainsaw
  d) Require a) for Package managers and b) by tree policy.
     Practically, this would mean that repoman would reject "foo-1" as
     package name, but the rest of Portage would accept it.
   -> noone voted for this option

By majority, option b) was chosen.  This means the specification (PMS)
has to be adapted to make it stricter on package names, e.g. [2].


Open bugs with council involvement
==================================
Bug 383467 "Council webpage lacks results for 2010 and 2011 elections"

grobian and scarabeus will try to sort this thing out with jmbsvicetto at
LinuxDays Prague, which will take place 20th and 21st of October 2012.


Open Floor
==========
chainsaw and williamh informed us about developments on udev at the
linux kernel mailing lists, and possible actions that follow up from
there [3].

_AxS_ requested quasi-consensus on in_iuse functionality, an EAPI6
feature was suggested.

_AxS_ asked the Council if they knew anything about a git rollout by
infra, however, since this is infra domain, the Council doesn't know or
control this.

ferringb wanted to have the Council take a look at the current unified
dependencies discussion.  It was pushed for the next agenda, to have
some preparation necessary to discuss the topic in a clear and directed
manner.


Next meeting date
=================
13 November 2012, 20:00 UTC


[1] http://thread.gmane.org/gmane.linux.gentoo.project/2152
[2] https://174536.bugs.gentoo.org/attachment.cgi?id=324680
[3] https://lkml.org/lkml/2012/10/2/303

-- 
Fabian Groffen
Gentoo on a different level

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

      reply	other threads:[~2012-10-16 21:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-02 11:38 [gentoo-dev-announce] Council meeting: Tuesday 9 October 2012, 19:00 UTC Fabian Groffen
2012-10-16 18:33 ` Fabian Groffen [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20121016183319.GD809@gentoo.org \
    --to=grobian@gentoo.org \
    --cc=gentoo-dev-announce@lists.gentoo.org \
    --cc=gentoo-project@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox