public inbox for gentoo-council@lists.gentoo.org
 help / color / mirror / Atom feed
From: Donnie Berkholz <dberkholz@gentoo.org>
To: Doug Goldstein <cardoe@gentoo.org>
Cc: Thomas Anderson <gentoofan23@gentoo.org>,
	gentoo-council@lists.gentoo.org
Subject: Re: [gentoo-council] Re: Bans in #-council [WAS] Council meeting summary for meeting on June 11, 2009
Date: Mon, 22 Jun 2009 09:36:44 -0700	[thread overview]
Message-ID: <20090622163644.GA27178@comet> (raw)
In-Reply-To: <eafa4c130906192135t349f517doace64aab0fb26299@mail.gmail.com>

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

On 23:35 Fri 19 Jun     , Doug Goldstein wrote:
> On Fri, Jun 19, 2009 at 10:40 PM, Donnie Berkholz<dberkholz@gentoo.org> wrote:
> > On 12:06 Wed 17 Jun     , Thomas Anderson wrote:
> >> The ban was later reversed by Doug Goldstein(Cardoe) because it had
> >> not been put to a council vote as all bans in #-council are.
> >
> > Since when? I've never heard of this. I've banned people in there with a
> > note to other council members (for the simple sake of good
> > communication) and no vote ever happened except by lack of objection.
> 
> In the past you've e-mailed all of us and told us about the situation 
> and the rest of us agreed with your action. In this case, there was no 
> e-mail and more then half of the council members didn't see 
> justification for the ban based on the conversation at hand. While 
> some of the comments at hand were snide, a lot of the confusion was as 
> a result of the language barrier. I know the language barrier has 
> caused a problem for some of us one time or another. In fact, dev-zero 
> and I have had our share of disagreements as a result of the language 
> barrier. At the same time, dev-zero and I have worked together on 
> quite a few projects and had positive experiences together. We decided 
> in the meeting to let emotions cool and toss it to e-mail. If anyone 
> wanted to see igli banned, to send an e-mail to all the council 
> members (it didn't even have to be on the ML) and we'd go from there. 
> To date, no such e-mail has come. The only e-mails are just throwing 
> fuel on a fire which no longer exists.

Thanks for the clarification. My problem is just with the wording in the 
summary, then, as it implies that banning can't happen until *after* a 
vote.

-- 
Thanks,
Donnie

Donnie Berkholz
Developer, Gentoo Linux
Blog: http://dberkholz.wordpress.com

[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]

      reply	other threads:[~2009-06-22 16:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-17 16:06 [gentoo-council] Council meeting summary for meeting on June 11, 2009 Thomas Anderson
2009-06-20  3:40 ` [gentoo-council] Re: Bans in #-council [WAS] " Donnie Berkholz
2009-06-20  4:35   ` Doug Goldstein
2009-06-22 16:36     ` Donnie Berkholz [this message]

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=20090622163644.GA27178@comet \
    --to=dberkholz@gentoo.org \
    --cc=cardoe@gentoo.org \
    --cc=gentoo-council@lists.gentoo.org \
    --cc=gentoofan23@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