public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Donnie Berkholz <dberkholz@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: council@gentoo.org
Subject: Re: [gentoo-dev] One-Day Gentoo Council Reminder for May
Date: Thu, 8 May 2008 02:03:45 -0700	[thread overview]
Message-ID: <20080508090345.GA29904@comet.had1.or.comcast.net> (raw)
In-Reply-To: <20080507070448.C2C7366AC1@smtp.gentoo.org>

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

On 03:04 Wed 07 May     , Mike Frysinger wrote:
> This is your one-day friendly reminder !  The monthly Gentoo Council
> meeting is tomorrow in #gentoo-council on irc.freenode.net.  See the
> channel topic for the exact time (but it's probably 2000 UTC).
> 
> If you're supposed to show up, please show up.  If you're not supposed
> to show up, then show up anyways and watch your Council monkeys dance
> for you.
> 
> For more info on the Gentoo Council, feel free to browse our homepage:
> http://www.gentoo.org/proj/en/council/

Here's the suggested agenda. Please feel free to respond to some of the 
commentary within, because it's hard for me to usefully summarize a 
topic's background in an entirely objective manner.

Thanks,
Donnie

[-- Attachment #2: 20080508-summary.txt --]
[-- Type: text/plain, Size: 3658 bytes --]

Requested attendees
===================

Active developer: araujo, anyone who could talk about how to get this 
	script running on Gentoo infra
PMS: ciaranm, pkgcore dev, portage dev, any other tools that care about 
	versions
Enforced retirement: fmccor, musikc
	musikc has already informed us that she can't make it until an hour 
	later, so this is the final topic.

New process
===========

The last few meetings have dragged out for hours unnecessarily. This 
time, let's return to moderating the channel. Let's try moderating 
during discussion of each topic, then temporarily opening the floor for 
that topic before a vote so anyone can contribute.


Updates to last month's topics
==============================

	http://www.gentoo.org/proj/en/council/meeting-logs/20080410-summary.txt

	Document of being an active developer
	-------------------------------------
	Last month:
		No updates
	Updates:
		araujo made http://dev.gentoo.org/~araujo/gcert1.pdf in Scribus. 
		He'd like to ask for approval of this design and discuss the 
		script, in particular its infrastructure requirements.

	Slacker arches
	--------------
	4 months ago:
		vapier will work on rich0's suggestion and repost it for 
		discussion on -dev ML
	2 months ago:
		vapier said he was going to work on it that weekend.
	Last month:
		No updates
	Updates:


New topics
==========

	When are ChangeLog entries required?
	------------------------------------
	This question mainly relates to arch stabilizations.


	Can the council help fewer bugs get ignored by arm/sh/s390 teams?
	-----------------------------------------------------------------
	The work happens, but Mart says it's not communicated to anyone and 
	has no relationship to whether bugs are open.


	PMS: Are versions allowed to have more than 8 digits?
	-----------------------------------------------------
	http://archives.gentoo.org/gentoo-dev/msg_db2f5c09c2c0c8b042ca3d0dcec7cdaf.xml
	https://bugs.gentoo.org/show_bug.cgi?id=188449

	What do various PMs/tools support?


	Enforced retirement
	-------------------

		What was the council's role in the recent enforced retirement of 
		3 developers?
		----------------------------------------------------------------
		The council received numerous complaints, agreed that the devrel 
		lead could take action and discussed the problems with her. The 
		council did not "force" her to claim its actions were hers.


		Why does the council permit such actions in apparent violation of 
		Gentoo's policy of openness?
		-----------------------------------------------------------------
		http://www.gentoo.org/foundation/en/#doc_chap2 says this:

		"Every aspect of Gentoo is and remains open. Gentoo does not 
		benefit from hiding any of its development processes (whether it 
		is source code or documentation, decisions or discussions, 
		coordination or management)."

		Chris (wolf) noted that it does specifically refer to 
		development process. Devrel's current process document
		<http://www.gentoo.org/proj/en/devrel/policy.xml> also makes 
		specific note of the lack of transparency, and disciplinary 
		actions have historically been discussed in a closed 
		environment, in part because of the potential harmful effects of 
		the discussions if action is not taken.


		What is the council's role in an appeal?
		----------------------------------------
		How should we proceed with the current appeals?

		If the council is directly involved in disciplinary action, 
		Ferris requests that we amend GLEP 39 to explain how the council 
		handles appeals and whether the council can take direct 
		disciplinary action.


	Open floor
	----------

  reply	other threads:[~2008-05-08  9:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-07  3:04 [gentoo-dev] One-Day Gentoo Council Reminder for May Mike Frysinger
2008-05-08  9:03 ` Donnie Berkholz [this message]
2008-05-08 10:57   ` Brian Harring
2008-05-08 11:01     ` Ciaran McCreesh
2008-05-08 11:15       ` Brian Harring
2008-05-08 11:23         ` Ciaran McCreesh
2008-05-08 12:01           ` Brian Harring
2008-05-08 11:44         ` Santiago M. Mola
2008-05-08 12:01           ` Brian Harring
2008-05-08 12:52             ` Santiago M. Mola
  -- strict thread matches above, loose matches on Subject: below --
2009-05-13  3:06 Mike Frysinger
2007-05-09  4:44 Mike Frysinger

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=20080508090345.GA29904@comet.had1.or.comcast.net \
    --to=dberkholz@gentoo.org \
    --cc=council@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