From: Donnie Berkholz <dberkholz@gentoo.org>
To: gentoo-council@lists.gentoo.org
Cc: gentoo-project@lists.gentoo.org
Subject: [gentoo-council] Re: [gentoo-dev] Special meeting [WAS: Council meeting summary for 8 May 2008]
Date: Thu, 15 May 2008 13:49:14 -0700 [thread overview]
Message-ID: <20080515204913.GA22285@comet> (raw)
In-Reply-To: <20080508233328.GA8896@comet>
On 16:33 Thu 08 May , Donnie Berkholz wrote:
> Enforced retirement: After 2.5 hours on the previous topics, people had
> to go to sleep and jokey's computer broke. Instead of waiting till the
> next regular meeting, because of its urgency, we scheduled a special
> session next week at the same time. The appeals will *not* be decided
> then -- it's about figuring out the validity and the process.
2 of us have shown up -- amne and me. That's really pathetic, guys. What
happened? Did the rest of you miss the announcement in the summary? I
was looking at the IRC log from last week, and here's what I saw
(relevant parts only):
< FlameBook+> I'm fine with the reschedule, as I'm probably going away soon, too
< dberkholz@> amne, Betelgeuse, FlameBook, solar -- rescheduling to a special session work?
< dberkholz@> ah, FlameBook already said yes
<Betelgeuse@> o
<Betelgeuse@> k
< dberkholz@> looks like amne went to bed
< dberkholz@> enough of us agree on that, so let's do it
lu_zero said on IRC last night that he was going to be traveling today,
but nobody's shown up to proxy for him:
< lu_zero@> dberkholz today we'll the extended council meeting, isn't it?
< dberkholz@> i optimistically hope it's not "extended" in the "taking a long time" sense
< dberkholz@> but the postponed topics from last week, yes
< lu_zero@> dberkholz again I'll be travelling
< dberkholz@> lu_zero: oh, did it just come up?
< lu_zero@> dberkholz pretty much =_=
< lu_zero@> lately my time-space position is quite random
< lu_zero@> _Hopefully_ I'll be there
< lu_zero@> but 4 hours of travel can be extended =_=
That means that it's conceivable that if solar (vapier's proxy), vapier
and jokey didn't check IRC again or read the council summary, they
could've missed the announcement. I guess I can see how people who are
at the meeting might not read the summary, because they sat through it.
I blame myself for not sending a standalone announcement outside of the
summary.
tove brought up an interesting point from GLEP 39:
If any meeting has less than 50% attendance by council members, a
new election for all places must be held within a month. The 'one
year' is then reset from that point.
musikc questioned whether that was only intended for the regular
meetings or also irregular ones like this.
Open up the floodgates, folks. What do you think, what should we do? I
look forward to hearing your advice.
Thanks,
Donnie
--
gentoo-council@lists.gentoo.org mailing list
next prev parent reply other threads:[~2008-05-15 20:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-08 23:33 [gentoo-council] Council meeting summary for 8 May 2008 Donnie Berkholz
2008-05-15 20:49 ` Donnie Berkholz [this message]
2008-05-15 21:27 ` [gentoo-council] Re: [gentoo-project] Re: [gentoo-dev] Special meeting [WAS: Council meeting summary for 8 May 2008] Roy Bamford
2008-05-16 2:22 ` [gentoo-council] " Luca Barbato
2008-05-16 14:59 ` Paul Varner
2008-05-16 15:09 ` Ferris McCormick
2008-05-16 20:10 ` Paul Varner
2008-05-22 1:09 ` [gentoo-council] RE: [gentoo-project] " Chrissy Fullam
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=20080515204913.GA22285@comet \
--to=dberkholz@gentoo.org \
--cc=gentoo-council@lists.gentoo.org \
--cc=gentoo-project@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