public inbox for gentoo-dev-announce@lists.gentoo.org
 help / color / mirror / Atom feed
From: Denis Dupeyron <calchan@gentoo.org>
To: gentoo-council <gentoo-council@lists.gentoo.org>
Cc: gentoo-dev-announce <gentoo-dev-announce@lists.gentoo.org>
Subject: [gentoo-dev-announce] Next council meeting on Tuesday 9th 2010 at 2000UTC
Date: Thu, 28 Jan 2010 21:35:30 -0700	[thread overview]
Message-ID: <7c612fc61001282035x741fbf63o2d771983027ed202@mail.gmail.com> (raw)

The next council meeting will be on Tuesday 9th at 2000UTC. Please
note the slightly unusual day and time. It's on a Tuesday and it's one
hour later than usual. That's 21:00 for those of us in western Europe,
3:00PM for US east coast and 12 noon for US west coast.

Please make sure you discuss the topics before the meeting because we
will likely not have time for much more than voting. On top of that
council meetings are not the right place for technical discussions and
heated debates (both have a 100% chance of going nowhere). The place
where ideas should be proposed and discussed, where consensus need to
be reached, is the mailing lists. Don't count on your council members
to be creative, they're way too lazy and clueless for that.

I'm just now starting to work on the agenda with the target of
proposing it for review to the council over the coming weekend, but I
already know it's again going to be packed. What will for sure be on
the agenda are GLEPs 58 to 61 and the VDB issue (although I still have
to sort out this mess of a thread and bug). So, again, please make
sure you get all the answers you need on the mailing lists before the
meeting.

If you want to propose topics just post them to this thread. There's
no point asking us to discuss your half-baked project or idea though
because we'll end up canceling it due to disagreeing on the colors in
the output log.

Denis.



                 reply	other threads:[~2010-01-29  4:46 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=7c612fc61001282035x741fbf63o2d771983027ed202@mail.gmail.com \
    --to=calchan@gentoo.org \
    --cc=gentoo-council@lists.gentoo.org \
    --cc=gentoo-dev-announce@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