From: Alex Alexander <wired@gentoo.org>
To: gentoo-council@lists.gentoo.org, gentoo-dev@lists.gentoo.org
Cc: gentoo-dev-announce@lists.gentoo.org
Subject: [gentoo-dev] Council Agenda proposal for upcoming 2010-07-26 meeting
Date: Sun, 25 Jul 2010 02:55:57 +0300 [thread overview]
Message-ID: <20100724235557.GA9794@linuxized.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1725 bytes --]
Hi,
following is the Council Agenda proposal for the upcoming meeting on
Monday, July 26th.
* allow all members to show up (5 min)
** vote **
add --as-needed to default profile's LDFLAGS
** discuss / vote **
- required-use: http://dev.gentoo.org/~ferringb/required-use.html
- review eclass removal policy
should it be 2 years since portage 2.1.4.4 went stable?
- should there a policy about eclass API changes?
- use of invalid DEPEND atom "EAPI_TOO_OLD" instead of calling die in
global scope on eclasses
http://archives.gentoo.org/gentoo-dev/msg_dee3aab5e8c840ed3fa4add9c7d74b97.xml
and replies
- mailing lists
should we post council agenda to -council? -dev? -project?
some devs suggest we should cross-post to -dev and -council
but not everyone likes cross-posting as it can lead to fragmentation
Petteri suggested punting -council and using -project instead
* go through bugs assigned to council@g.o
* open floor: listen to developers
---
If you have something urgent not included above, please reply to this
thread.
---
Note that I haven't added a duration to anything but the rollcall.
Instead, I recommend we follow a 10 minutes per topic rule.
If a topic's discussion passes the 10 minute mark without reaching a
decision, we move further discussion to the mailing lists.
If we need to vote for that topic, we move it to the next agenda
with a *vote* flag.
Items with a *vote* flag cannot be moved a second time (unless there's
new data to consider), so they must be settled at that agenda's meeting,
in an attempt to avoid endless discussions.
What do you think?
--
Alex Alexander :: wired
Gentoo Developer
www.linuxized.com
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
reply other threads:[~2010-07-24 23:56 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=20100724235557.GA9794@linuxized.com \
--to=wired@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