From: Mark Loeser <halcy0n@gentoo.org>
To: gentoo-council@lists.gentoo.org
Cc: gentoo-dev-announce@lists.gentoo.org
Subject: [gentoo-dev-announce] Council meeting summary for 24 July 2008
Date: Mon, 28 Jul 2008 11:01:29 -0400 [thread overview]
Message-ID: <20080728150129.GA10272@aerie.halcy0n.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 991 bytes --]
A little late, but as promised, here is a summary of the meeting
(I will post the complete log and summary on the site later):
Item 1: userrel authority: Does userrel have the ability to enforce the
CoC on users like devrel does for developers?
It was decided that userrel does have this authority.
Item 2: coc extent
All council members will review the CoC thread and comment on it by the
next meeting (7 August 2008). We will get a status update in that
meeting to see if we can vote on any of the proposals brought up in that
thread.
Roll call:
dberkholz proxied by musikc
jokey here
dertobi123 here
betelgeuse proxied by caster
halcy0n here
lu_zero here
flameeyes absent (no slacker mark because of him being in the
hospital?)
--
Mark Loeser
email - halcy0n AT gentoo DOT org
email - mark AT halcy0n DOT com
web - http://www.halcy0n.com
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
reply other threads:[~2008-07-28 15:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20080728150129.GA10272@aerie.halcy0n.com \
--to=halcy0n@gentoo.org \
--cc=gentoo-council@lists.gentoo.org \
--cc=gentoo-dev-announce@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