public inbox for gentoo-dev-announce@lists.gentoo.org
 help / color / mirror / Atom feed
From: Donnie Berkholz <dberkholz@gentoo.org>
To: gentoo-council@lists.gentoo.org
Cc: gentoo-dev@lists.gentoo.org, gentoo-dev-announce@lists.gentoo.org
Subject: [gentoo-dev-announce] Council meeting summaries for August & September
Date: Sun, 28 Sep 2008 12:03:38 -0700	[thread overview]
Message-ID: <20080928190338.GA9010@comet> (raw)

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

Hi all,                                                                         

I just posted the summaries from August & September meetings. The 
complete summaries & logs are at http://www.gentoo.org/proj/en/council/. 
Here's the most important bits:

- EAPI=2 is approved for use in the tree. Portage 2.2_rc10 supports it. 
  The features are documented in multiple places, including:
  - http://dev.gentoo.org/~zmedico/portage/doc/portage.html#package-ebuild-eapi-2-draft
  - A list in a PMS appendix that refers to the relevant
    sections. `emerge app-doc/pms` to get it.

- PROPERTIES="interactive" is approved for use in the tree. It indicates 
  that user interaction is required during pkg_setup() or src_unpack(). 
  See http://archives.gentoo.org/gentoo-dev/msg_e145fc04e907de72e30d88285afb134c.xml 
  for details. This is outside of any individual EAPI because it is an 
  optionally handled value. It is a backwards-compatible EAPI change so 
  had to be approved by the council.

- The PROPERTIES variable will be added to the metadata cache. It will 
  be used to inform package managers of various properties of a package. 
  This is related to EAPI so it's an issue determined by package-manager 
  developers, not by the council.

- PMS is now a draft standard for EAPI=0. This means that conflicts 
  between portage behavior and the PMS are bugs to be resolved by 
  changing one of the two. Unresolvable conflicts will be escalated to 
  the council.

- Devrel sets policy on whether fired developers should be banned from 
  the places where they did the things that got them fired.

- Cardoe filled the slot left empty by flameeyes's departure for health 
  reasons.

- All our docs should be updated to refer to irc.gentoo.org instead of 
  irc.freenode.net.

-- 
Thanks,
Donnie

Donnie Berkholz
Developer, Gentoo Linux
Blog: http://dberkholz.wordpress.com

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

                 reply	other threads:[~2008-09-28 19:05 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20080928190338.GA9010@comet \
    --to=dberkholz@gentoo.org \
    --cc=gentoo-council@lists.gentoo.org \
    --cc=gentoo-dev-announce@lists.gentoo.org \
    --cc=gentoo-dev@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