public inbox for gentoo-council@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Chrissy Fullam" <musikc@gentoo.org>
To: <gentoo-core@lists.gentoo.org>,
	"'gentoo-council'" <gentoo-council@lists.gentoo.org>
Subject: [gentoo-council] RE: [gentoo-core] Freenode bans
Date: Mon, 28 Jul 2008 18:44:10 -0700	[thread overview]
Message-ID: <521401c8f11c$9f0851c0$dd18f540$@org> (raw)
In-Reply-To: <51d801c8f106$dd1bbee0$97533ca0$@org>

> > > >> Sounds like it's beyond time to leave freednode for another. More
> > > >> than likely oftc. It will be a PITA but at least self inflicted. Or
> > > >> we can wait it out till we get hit something that is not self
> > > >> inflicted.
> > > >>
> > > >> Maybe something for the council to discuss and vote on at next
> > meeting?
> > > >>
> > > > I second that.
> > >
> > > Same here. It's time we said "enough".

Further discussion with Freenode staff, to include dmwaters and tomaw as christel (Freenode president) was unavailable for response, indicates that there is an internal Freenode policy, not publically documented on http://freenode.net/policy.shtml, that dictates that Freenode staff cannot relay the justification for a ban to anyone other than the individual banned. Gentoo is referred to as 'third party' and not considered a direct party though we use Freenode as an official means of communication and forcibly removing any developer has direct consequences in how we function. Dmwaters stated that she assumes wolf31o2 was banned for being off topic to the Freenode network as such I highly encourage all to review the section in Freenode policy regarding what is deemed off topic just in case.

I'm advised from wolf31o2 that he received no previous communication from any Freenode staffer regarding his alleged violations so he was banned for his first alleged offense and he noted that he has not spoken directly to a Freenode staffer prior to today in months so has no justification for this action.

As a result of lack of communication from numerous angles (read above) I do agree that consideration is warranted as to whether Freenode is the right network for Gentoo. The conversation with tomaw and dmwaters indicates that this is not likely to change so I see little hope for improved communication in the future.

I've included Gentoo-council as I too would like this to be a topic of discussion there to be voted on in the upcoming Council meeting on August 14th.


Kind regards,
Christina Fullam
Gentoo Developer Relations Lead | Gentoo Public Relations 








           reply	other threads:[~2008-07-29  1:44 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <51d801c8f106$dd1bbee0$97533ca0$@org>]

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='521401c8f11c$9f0851c0$dd18f540$@org' \
    --to=musikc@gentoo.org \
    --cc=gentoo-core@lists.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