1 |
On 07:53 Thu 12 Feb , Tiziano Müller wrote: |
2 |
> That's true. But just deciding that we need people to discuss it and |
3 |
> then not fostering that discussion ourselves actively is not |
4 |
> acceptable. Once we get the task to take care of a matter we have to |
5 |
> take care of it until it's done completely. This involves bringing the |
6 |
> subject up on the mailinglist (and not just publish the summary and |
7 |
> wait for people to read through it and then start a discussion |
8 |
> depending on what they may find in the summary), get the information |
9 |
> we need to be able to decide somewhere else, etc. |
10 |
> |
11 |
> Why don't we assign each task to one of us council members to do that, |
12 |
> so we get for every task someone who's taking care of it, making sure |
13 |
> it gets on the agenda again, maybe even preparing a summary of the |
14 |
> matter for the rest of the council (in complicated cases), posting on |
15 |
> the mailing-list, commenting on the corresponding bug, etc.? I guess |
16 |
> that's what Ciaran meant in the "Secretary"-Thread. |
17 |
|
18 |
I agree that it's a great idea to assign someone responsibility for |
19 |
following up, and I think that the person who brings up the topic is |
20 |
best qualified and motivated to do so. I don't see any reason to require |
21 |
it to be a council member. |
22 |
|
23 |
-- |
24 |
Thanks, |
25 |
Donnie |
26 |
|
27 |
Donnie Berkholz |
28 |
Developer, Gentoo Linux |
29 |
Blog: http://dberkholz.wordpress.com |