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
Cc: council@gentoo.org
Subject: Re: [gentoo-dev] Gentoo Council Reminder for February 26
Date: Thu, 26 Feb 2009 11:19:20 -0800	[thread overview]
Message-ID: <20090226191920.GB3820@comet> (raw)
In-Reply-To: <20090225071235.GA3923@comet>

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

On 23:12 Tue 24 Feb     , Donnie Berkholz wrote:
> 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!

I'm not prepared to decide on the whole set of solutions related to GLEP 
55 yet. I need more time to think about them, and since new options are 
showing up frequently, it makes that pretty hard. Here's what action I'd 
like to see regarding the whole thing:

Petteri, Tiziano, and Alec agree to work together to update & maintain a 
single document describing our requirements, the potential solutions, 
how well they address the requirements, and what the downsides (and any 
other upsides) are. If just 1-2 of them want to do this, that's fine 
too. All 3 of them have written something along these lines already, 
which is why I suggest them.


> GLEP 54: handling code from SCMs better
> ---------------------------------------
> 
> Some discussion on list. Luca, can you sum up the state of things?

Still waiting on a summary ... perhaps if Luca's too busy, our wonderful 
new secretary could do something along the lines of the above doc?



Making choices without a clear and straightforward comparison of options 
right next to each other is not the greatest. So the actions I propose 
for today's meeting are:

- Approve new council member

- Get people to agree to get a doc w/ requirements & comparisons for:
	- GLEP 54 (Luca or Thomas?)
	- GLEP 55 (Petteri/Tiziano/Alec)


-- 
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-26 19:19 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
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 [this message]
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=20090226191920.GB3820@comet \
    --to=dberkholz@gentoo.org \
    --cc=council@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