public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Donnie Berkholz <dberkholz@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Gentoo Council Reminder for February 26
Date: Tue, 24 Feb 2009 23:12:35 -0800	[thread overview]
Message-ID: <20090225071235.GA3923@comet> (raw)
In-Reply-To: <20090223072648.GK12339@hermes>

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

On 23:26 Sun 22 Feb     , Donnie Berkholz wrote:
> This is your friendly reminder! Same bat time (typically the 2nd & 4th 
> Thursdays at 2000 UTC / 1600 EST), same bat channel (#gentoo-council @ 
> irc.freenode.net) !
> 
> If you have something you'd wish for us to chat about, maybe even vote 
> on, let us know! Simply reply to this e-mail for the whole Gentoo dev 
> list to see.

Here's the preliminary agenda. I'm running a bit behind on -dev, so it's 
a little out of date re GLEPs 54/55. People including lu_zero, cardoe, 
dev-zero, and tanderson should fill us in on things below that they've 
taken responsibility for. Anyone else can chime in anywhere!


Open council spot
-----------------

leio is next on the list. He's willing to join the council. A few of us 
already voted to confirm him on-list, and we're waiting on the others.

Goal: Vote to confirm him, if necessary.


GLEP 55 / bash version
----------------------

Crazy amounts of discussion on-list. Cardoe & Tiziano, you took 
responsibility for this -- can you sum up the current state of things? 
Pending something better, here's what I'd like to see happen on-list (or 
on the wiki, whatever) before the meeting:

Goal: Come up with 3 things:
	1) Agreement that this is a problem we need to solve now;
	2) Come up with a list of potential implementations;
	3) Come up with pros & cons for each.

At that point, we should have enough information to at least rank them 
and decide out whether the top-ranked one has the right approach. We 
should then clearly define any problems with it and suggest 
improvements.


GLEP 54: handling code from SCMs better
---------------------------------------

Some discussion on list. Luca, can you sum up the state of things?


PMS compliance in Gentoo-hosted trees besides gentoo-x86
--------------------------------------------------------

ferringb requested this. We need some discussion on-list before we talk 
about it during a meeting, so please chip in and reply to his post.


Suggestions are welcome, as are any summaries from our new secretary. =)

-- 
Thanks,
Donnie

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

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

  parent reply	other threads:[~2009-02-25  7:13 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-23  7:26 [gentoo-dev] Gentoo Council Reminder for February 26 Donnie Berkholz
2009-02-24 17:47 ` Brian Harring
2009-02-24 18:01   ` Santiago M. Mola
2009-02-25 12:42   ` Gilles Dartiguelongue
2009-02-25 12:56     ` Brian Harring
2009-02-25  7:12 ` Donnie Berkholz [this message]
2009-02-25 11:06   ` Petteri Räty
2009-02-25 12:16     ` [gentoo-dev] Open council spot Torsten Veller
2009-02-26 19:02   ` [gentoo-dev] Gentoo Council Reminder for February 26 Luca Barbato
2009-02-26 19:19   ` Donnie Berkholz
2009-02-26 19:22     ` Ciaran McCreesh
2009-02-26 19:34       ` Luca Barbato
2009-02-26 19:38         ` Ciaran McCreesh
2009-02-26 20:40           ` Luca Barbato
2009-02-27 20:23             ` Ciaran McCreesh
2009-02-28 13:04               ` Regarding live sources management proposals (Was: [gentoo-dev] Gentoo Council Reminder for February 26) Luca Barbato
2009-02-26 19:23     ` [gentoo-dev] Gentoo Council Reminder for February 26 Donnie Berkholz
2009-02-26 19:39     ` Brian Harring
2009-02-25 14:22 ` Nirbheek Chauhan

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=20090225071235.GA3923@comet \
    --to=dberkholz@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