public inbox for gentoo-council@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Tiziano Müller" <dev-zero@gentoo.org>
To: Donnie Berkholz <dberkholz@gentoo.org>
Cc: gentoo-council <gentoo-council@lists.gentoo.org>
Subject: Re: [gentoo-council] Secretary & President
Date: Sat, 07 Feb 2009 11:01:42 +0100	[thread overview]
Message-ID: <1234000902.24784.7.camel@localhost> (raw)
In-Reply-To: <20090206221229.GB3493@comet>

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

Am Freitag, den 06.02.2009, 14:12 -0800 schrieb Donnie Berkholz:
> On 10:26 Fri 06 Feb     , Tiziano Müller wrote:
> > While dberkholz does a great job of putting together an agenda,
> > organizing the meeting and even putting together a summary afterwards,
> > it seems that he's quiet busy lately (hence the missing logs/summary of
> > the last two meetings).
> > For my understanding this is too much of a burden for one person and I'd
> > propose that we have a changing President/Chairman (who'll prepare the
> > agenda) and a changing Secretary (who'll upload the logs and do the
> > summary). With the current ~100 meetings a year everyone of us would
> > have to do the summary and the agenda 14-15 times a year.
> 
> To provide some context, I basically began doing these two roles by 
> default when I was first elected to the council, since nobody else was 
> particularly interested.
> 
> I agree that splitting president and secretary into separate roles is a 
> great idea. I feel strongly that rotating these positions often will 
> result in both roles being ineffective, because it takes time to get 
> even decent at either of them. Does anyone want to return to the 4-hour 
> meetings we used to have?

Can you maybe outline the tasks the Secretary has to do besides
uploading the log and generate a summary and where it gets complicated?
Because I currently can't immagine where these tasks need much of a
training.
But we can also decide that everyone does it four times in a row to make
sure people don't take it in stride.

-- 
-------------------------------------------------------
Tiziano Müller
Gentoo Linux Developer, Council Member
Areas of responsibility:
  Samba, PostgreSQL, CPP, Python, sysadmin
E-Mail     : dev-zero@gentoo.org
GnuPG FP   : F327 283A E769 2E36 18D5  4DE2 1B05 6A63 AE9C 1E30

[-- Attachment #2: Dies ist ein digital signierter Nachrichtenteil --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  parent reply	other threads:[~2009-02-07 11:34 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-06  9:26 [gentoo-council] Secretary & President Tiziano Müller
2009-02-06 10:52 ` Petteri Räty
2009-02-06 22:12 ` Donnie Berkholz
2009-02-06 22:18   ` Ciaran McCreesh
2009-02-06 22:33     ` Donnie Berkholz
2009-02-06 22:37       ` Ciaran McCreesh
2009-02-07  1:04         ` Donnie Berkholz
2009-02-07 10:01   ` Tiziano Müller [this message]
2009-02-11  7:32     ` Donnie Berkholz
2009-02-06 22:17 ` Donnie Berkholz
2009-02-10  8:55   ` Tiziano Müller
2009-02-10 21:18     ` Donnie Berkholz
2009-02-07 10:20 ` Roy Bamford
2009-02-07 16:54   ` Thomas Anderson
2009-02-11  7:34   ` Donnie Berkholz
2009-02-12 16:20     ` Donnie Berkholz

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=1234000902.24784.7.camel@localhost \
    --to=dev-zero@gentoo.org \
    --cc=dberkholz@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