public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Rick \"Zero_Chaos\" Farina" <zerochaos@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: [gentoo-dev-announce] Council constituent meeting 30 July 2013 at 19:00 UTC
Date: Mon, 22 Jul 2013 18:35:31 -0400	[thread overview]
Message-ID: <51EDB3B3.1050902@gentoo.org> (raw)
In-Reply-To: <CAGfcS_kwEF2t9aV2nB8tXsJHdmgvFryxZ4b6fcS+yY6LmNzXhw@mail.gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 07/22/2013 05:51 PM, Rich Freeman wrote:
> On Sun, Jul 21, 2013 at 4:20 PM, Roy Bamford <neddyseagoon@gentoo.org> wrote:
>>> - vote for holding meetings every 2nd Tuesday of the month at 2000
>>> UTC
>>> (or
>>> 1900 UTC depending on daylight savings)
>>
>> In any timezone in particular?
>>
> 
> Don't care much, but agree we should pick one.
> 
>>
>> The open floor is a part of the openness and approachability of the
>> council.  Its 60 seconds well spent, even if nobody says anything.
> 
> The concern that was raised was that when it does get used it is rare
> for anything to get accomplished.  The desire is to have issues raised
> and debated on the lists first.
> 
> I don't have a big problem with open floor - I just think it is a bit
> of a waste of time.  If somebody wants to raise an issue they need
> only ask.
> 
>>> - vote on meeting format 2: "shift council votes to mail instead of
>>> IRC"
>>
>> Please keep voting in public.  Its good for accountability.
>> If not in IRC, find a way to publish who voted and now.
>> Council do not get a secret ballot.
> 
> Agreed.  I don't think the intent of that item was ever to REPLACE
> in-person voting with email.  I think the intent was to allow for it
> so that when a critical issue comes up a week after the agenda is
> already set that everybody doesn't have to wait 5 weeks for the
> following council meeting.  It seems really odd to have a 100-post

The council really doesn't have the ability to just instantly vote on
things outside of a meeting.  The transparency of the body requires
announcements about meetings, and their topics, with a reasonable amount
of notice.  It simply isn't possible to maintain these things and have
the flexibility to instantly vote on things.  Emergency action can be
taken by many bodies, devrel, userrel, but the council is not expected
to be the "quick fix" for things.

- -Zero

> flamewar with no immediate action, and then to dredge up the topic a
> month later and vote, and then have another 100-post flameware to talk
> about the outcome.  I don't think we need off-the-cuff decisions, but
> if a topic is ripe for a decision we should have a way to actually
> take care of it.
> 
> Public debate and votes only make sense.  Bugs might be a useful way
> to record this (much as is done with the trustees).
> 
> Rich
> 
> 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBAgAGBQJR7bOzAAoJEKXdFCfdEflK82cQAK+f6sdWek9P2b23JYWb8Xm9
HzH+rc+NrfvbLo6pwINdzuVkNQnvIWwKZbyl9/03kuZeB3PytvVFLMAEk9pMlRnk
rBVvcpuYU8m4OHWWQBPRyNw7qKlGW15AkVZ1+syCaBQiVyj6atniKUf3xV97IKVe
GE9frmWp3mQeeDbFu78+PrKBs6jIPf7D6QJNSjPYrntK+vg90G53zqXOvOvFUPji
StldpXAfRK4GTsdDChf8HPOtMB3IsFvnLuO91U16AQqgb5ydw4AlCT+0WEeZCoUR
fgXe5QdvMEoWiFsVB17fE2foyFVGHnq72/oXJwvued2D47D+1SQxmo1fYb+OOwbi
KgSFIWK3DYgC1QbH8l96QRxFfEPbiwO19ATJT2ed5ak8E7a829FQOBcOOCZZ8FeT
qbqaPVwfWpKh2xjYXBhczsOZyPjYSL3UMH276HjujUPsFJGoTgiQjhLYdZ4ofkL3
bsmC3ZxufLesl3cPSxCkJ58WQeSK/jF4kGxUvj5FaD2GkHs03z3/2nHQ82jUgb4s
flfkaQICLFljt65574zNNLCh2UQVvvIf0UKNjiq1BoIZVg4cuzjUYVlmTJ6fXXDA
qiHffsusKdD9rToBYGCdQuO9RfZCUj9kAlVqvX92U27jn+vyb59ImnteeGML1wNs
SoNwdjL8XHhxPyf+SJKP
=7jYm
-----END PGP SIGNATURE-----


  reply	other threads:[~2013-07-22 22:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <201307211630.22711.dilfridge@gentoo.org>
     [not found] ` <1374438041.2783.2@ NeddySeagoon_SSD>
2013-07-21 20:20 ` [gentoo-dev] Re: [gentoo-dev-announce] Council constituent meeting 30 July 2013 at 19:00 UTC Roy Bamford
2013-07-22 21:51   ` Rich Freeman
2013-07-22 22:35     ` Rick "Zero_Chaos" Farina [this message]
2013-07-22 23:05       ` Rich Freeman
2013-07-23  0:57         ` Rick "Zero_Chaos" Farina
2013-07-23 19:37           ` Roy Bamford
2013-07-23 19:51             ` Rick "Zero_Chaos" Farina
2013-07-23 19:24     ` Roy Bamford
2013-07-25 21:20     ` Steven J. Long

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=51EDB3B3.1050902@gentoo.org \
    --to=zerochaos@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