From: Donnie Berkholz <dberkholz@gentoo.org>
To: "Tiziano Müller" <dev-zero@gentoo.org>
Cc: gentoo-council <gentoo-council@lists.gentoo.org>
Subject: Re: [gentoo-council] Preliminary Meeting-Topics for 12 February 2009
Date: Thu, 12 Feb 2009 07:50:56 -0800 [thread overview]
Message-ID: <20090212155056.GA3642@comet> (raw)
In-Reply-To: <1234421593.20307.22.camel@localhost>
[-- Attachment #1: Type: text/plain, Size: 1378 bytes --]
On 07:53 Thu 12 Feb , Tiziano Müller wrote:
> That's true. But just deciding that we need people to discuss it and
> then not fostering that discussion ourselves actively is not
> acceptable. Once we get the task to take care of a matter we have to
> take care of it until it's done completely. This involves bringing the
> subject up on the mailinglist (and not just publish the summary and
> wait for people to read through it and then start a discussion
> depending on what they may find in the summary), get the information
> we need to be able to decide somewhere else, etc.
>
> Why don't we assign each task to one of us council members to do that,
> so we get for every task someone who's taking care of it, making sure
> it gets on the agenda again, maybe even preparing a summary of the
> matter for the rest of the council (in complicated cases), posting on
> the mailing-list, commenting on the corresponding bug, etc.? I guess
> that's what Ciaran meant in the "Secretary"-Thread.
I agree that it's a great idea to assign someone responsibility for
following up, and I think that the person who brings up the topic is
best qualified and motivated to do so. I don't see any reason to require
it to be a council member.
--
Thanks,
Donnie
Donnie Berkholz
Developer, Gentoo Linux
Blog: http://dberkholz.wordpress.com
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-02-12 15:51 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-10 9:12 [gentoo-council] Preliminary Meeting-Topics for 12 February 2009 Tiziano Müller
2009-02-10 21:25 ` Donnie Berkholz
2009-02-12 6:53 ` Tiziano Müller
2009-02-12 15:50 ` Donnie Berkholz [this message]
2009-02-12 15:55 ` Ciaran McCreesh
2009-02-12 16:01 ` Donnie Berkholz
2009-02-12 16:12 ` Ciaran McCreesh
2009-02-12 17:28 ` Donnie Berkholz
2009-02-12 16:47 ` Tiziano Müller
2009-02-12 17:20 ` Donnie Berkholz
2009-02-10 23:11 ` [gentoo-council] Website changes [WAS] " Donnie Berkholz
2009-02-11 15:51 ` Tiziano Müller
2009-02-11 19:19 ` Donnie Berkholz
2009-02-11 20:01 ` Luca Barbato
2009-02-10 23:13 ` [gentoo-council] GSoC results from 2008 " Donnie Berkholz
2009-02-12 5:48 ` Alec Warner
2009-02-12 14:53 ` [gentoo-council] " Tiziano Müller
2009-02-12 16:00 ` Donnie Berkholz
2009-02-12 16:16 ` Donnie Berkholz
2009-02-12 16:21 ` Ciaran McCreesh
2009-02-12 17:10 ` Donnie Berkholz
2009-02-12 17:21 ` Ciaran McCreesh
2009-02-12 17:37 ` Donnie Berkholz
2009-02-12 18:03 ` Ciaran McCreesh
2009-02-12 19:01 ` Alistair Bush
2009-02-12 19:08 ` Ciaran McCreesh
2009-02-12 19:54 ` Luca Barbato
2009-02-12 20:01 ` Ciaran McCreesh
2009-02-19 10:06 ` Peter Volkov
2009-02-19 12:51 ` Ciaran McCreesh
2009-02-19 13:30 ` Luca Barbato
2009-02-19 15:23 ` Ciaran McCreesh
2009-02-19 21:11 ` Peter Volkov
2009-02-19 21:21 ` Ciaran McCreesh
2009-02-22 23:16 ` [gentoo-council] " Ryan Hill
2009-02-22 23:37 ` Luca Barbato
2009-02-22 23:48 ` Ciaran McCreesh
2009-02-23 2:15 ` Issues regarding glep-55 (Was: [gentoo-council] Re: Preliminary Meeting-Topics for 12 February 2009) Luca Barbato
2009-02-23 8:38 ` Tiziano Müller
2009-02-23 13:21 ` [gentoo-dev] " Luca Barbato
2009-02-23 13:40 ` Thomas Anderson
2009-02-23 13:57 ` Ciaran McCreesh
2009-02-23 14:46 ` Luca Barbato
2009-02-23 14:59 ` Ciaran McCreesh
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=20090212155056.GA3642@comet \
--to=dberkholz@gentoo.org \
--cc=dev-zero@gentoo.org \
--cc=gentoo-council@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