From: Corey Shields <cshields@gentoo.org>
To: gentoo-trustees@lists.gentoo.org
Subject: Re: [gentoo-trustees] irc stuff
Date: Sun, 29 May 2005 07:59:15 -0700 [thread overview]
Message-ID: <200505290759.15343.cshields@gentoo.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0505281619550.12228@shell.osuosl.org>
On Saturday 28 May 2005 04:36 pm, Deedra Waters wrote:
> I'm guessing this should go to the board, but dunno. I've been gentoo's
> main contact with freenode for a while now. Earlier I closed down
> #gentoo-pub, and made them move it to an unofficial channel after a
> couple of complaints from developers about the behavior in the channel
> which basically consisted of script kiddie like behavior and general
> gentoo developer bashing.
Unless it is a trademark infringement, there is not much we can do about it.
It's more of a devrel or managers issue.
Cheers,
-C
--
Corey Shields
Gentoo Linux Infrastructure Team and Devrel Team
Gentoo Foundation Board of Trustees
http://www.gentoo.org/~cshields
--
gentoo-trustees@gentoo.org mailing list
prev parent reply other threads:[~2005-05-29 14:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-28 23:36 [gentoo-trustees] irc stuff Deedra Waters
2005-05-29 9:42 ` Sven Vermeulen
2005-05-29 14:59 ` Corey Shields [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=200505290759.15343.cshields@gentoo.org \
--to=cshields@gentoo.org \
--cc=gentoo-trustees@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