Re: [gentoo-dev] Agenda [WAS: One-Day Gentoo Council Reminder for June]

[Donnie Berkholz <dberkholz@gentoo.org>]

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

On 03:06 Wed 11 Jun     , 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).

Here's the proposed agenda. I intend to get every requested topic on the 
agenda so there is no need for an open floor afterwards.

Carefully note the Preparation sections. If they aren't completed, we 
will postpone the topic to the -council mailing list or the next meeting 
instead of waste time during the meeting doing things that should've 
happened in advance.

Please respond with any suggestions, including suggested order of the 
topics by urgency (within "old topics" and "new topics"). Unfortunately 
not all of the topics were posted to the council meeting reminder 
thread, so it was hard to dig them out.


More meeting optimization
-------------------------

I'd like to also set a 2-hour limit on the meeting. Anything we don't 
hit during that timeframe will be postponed to the list or the next 
meeting.

We can also take an idea from http://en.opensuse.org/Meetings/About and 
set the +zmn channel modes:

  * +m - Moderated - People who don't have voices (+v) can't send 
    messages to the channel.
  * +n - No external messages - With this mode, no one can send messages 
    to the channel without even being joined.
  * +z - Relaxed moderation - When +z is set each message that would be 
    blocked by +m is sent to all the users who are currently operator.

That will allow council members to see everything said by everyone, but 
non-council people will not be able to see things said by other 
non-council people. Then +v can be given to anyone with good 
contributions. What do you think?

Thanks,
Donnie

[-- Attachment #2: 20080612-agenda.txt --]
[-- Type: text/plain, Size: 3494 bytes --]

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

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


Document of being an active developer
-------------------------------------
Requested attendees: araujo

Last month: Numerous suggested improvements to info on the certificate.

Preparation: araujo needs to post progress, an updated certificate and 
any new requests to the gentoo-council or gentoo-project list 2+ hours 
before the meeting.

Goal: Suggest changes. This should happen on-list. No discussion 
expected.


Slacker arches
--------------
Preparation: vapier needs to send the post 2+ hours before the meeting.

Goal: Suggest changes. This should happen on-list. No discussion 
expected.


Can the council help fewer bugs get ignored by arm/sh/s390 teams? 
----------------------------------------------------------------- 
Preparation: Someone on an undermanned arch team needs to describe their 
workflow on-list 2+ hours before the meeting.

Goal: Suggest changes. This should happen on-list. No discussion 
expected.


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

Preparation: Do the package maintainers with extremely long PVs need 
them? The involved packages:
	sys-process/fuser-bsd
	sys-apps/net-tools
	sys-apps/gradm
	net-im/ntame
	media-video/captury
	media-libs/libcaptury
	media-libs/capseo
	sys-block/btrace
	www-apache/mod_depends
	net-wireless/rt2500
	sys-fs/unionfs

Preparation: What's the impact of extending versionator.eclass? 

Goal: With data in hand, make a decision.


How to handle appeals
---------------------

Preparation: Post to the gentoo-council mailing list 2+ hours before the 
meeting with your opinion.

Goal: Vote on an approach that was previously posted to the list.


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

as-needed by default
--------------------
antarus requested that we vote on whether to add it to the default 
LDFLAGS.

Preparation: Post your opinion to the -dev thread "RFC: --as-needed to 
default LDFLAGS" 2+ hours before the meeting.

Goal: Vote.


GLEP 54
-------
Preparation: Post your opinion to the -dev thread "A few questions to 
our nominees" 2+ hours before the meeting.

Goal: Vote.


GLEP 55
-------
Preparation: Post your opinion to the -dev thread "GLEP 55" 2+ hours 
before the meeting. Let it attempt to come to a consensus before we 
vote.

Goal: Vote once the discussion's no longer clearly ongoing. We can hold 
this vote on the -council mailing list instead of waiting for the next 
meeting.


GLEP 56
-------
Preparation: Post your opinion to the -dev thread "[GLEP56] USE flag 
descriptions in metadata" 2+ hours before the meeting. Let it attempt to 
come to a consensus before we vote.

Goal: Vote once the discussion's no longer clearly ongoing. We can hold 
this vote on the -council mailing list instead of waiting for the next 
meeting.


Status of PMS
-------------
ferringb said:
  I'd like the council to please discuss the current status of PMS, if 
  the running of it satisfys the councils requirements of a *neutral* 
  standard, if the proposed spec actually meets said standards, and if 
  said spec is actually going to be approved sometimes this side of '09.

Preparation: Post your opinion to the -dev thread "One-Day Gentoo 
Council Reminder for June" 2+ hours before the meeting.