public inbox for gentoo-dev-announce@lists.gentoo.org
 help / color / mirror / Atom feed
From: Donnie Berkholz <dberkholz@gentoo.org>
To: gentoo-council@lists.gentoo.org
Cc: gentoo-dev@lists.gentoo.org, gentoo-dev-announce@lists.gentoo.org
Subject: [gentoo-dev-announce] Council meeting summary for 23 October 2008
Date: Thu, 23 Oct 2008 14:10:14 -0700	[thread overview]
Message-ID: <20081023211014.GA4465@comet> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 253 bytes --]

Hi all,

Here is the summary from Thursday's council meeting. The complete log
will show up at http://www.gentoo.org/proj/en/council/ shortly.

-- 
Thanks,
Donnie

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

[-- Attachment #1.2: 20081023-summary.txt --]
[-- Type: text/plain, Size: 1198 bytes --]

Roll call
=========
betelgeuse here
cardoe     here
dberkholz  here
dertobi123 here
halcy0n    here
jokey      slacker
lu_zero    here

Running through open bugs
=========================

Process: For each bug, come up with a concrete next step and who's going 
to do it. If it's the council, a specific member should take 
responsibility. The bug should be assigned to whoever needs to take the 
next step and council@ should be in CC.

Bugs handled:
185572 - As the proctors no longer exist the code of conduct needs an upate
234705 - Document of being an active developer
234706 - Slacker arches
234708 - Can the council help fewer bugs get ignored by arm/sh/s390 teams?
234710 - as-needed by default
237381 - Document appeals process

Bugs remaining:
234711 - GLEP 54: scm package version suffix
234713 - GLEP 55: Use EAPI-suffixed ebuilds (.ebuild-EAPI)
234716 - Extent of Code of Conduct enforcement

Meeting scheduling conflicts
============================ 
The 2nd meetings in November and December 
conflict with holidays. If there are open bugs, we will hold them on the 
3rd Thursday instead of the 4th Thursday; otherwise, they will be 
canceled.

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

                 reply	other threads:[~2008-10-23 21:10 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=20081023211014.GA4465@comet \
    --to=dberkholz@gentoo.org \
    --cc=gentoo-council@lists.gentoo.org \
    --cc=gentoo-dev-announce@lists.gentoo.org \
    --cc=gentoo-dev@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