Please join us for our weekly FAmNA meeting this Tuesday at 9:00pm
Eastern in #fedora-meeting on irc.freenode.net.
Feel free to add to the agenda. Especially if you have an event coming
up that needs some attention.
Our main agenda for this week will be to consider funding a variety of
swag and media for the F17 release events.
== Meeting Agenda ==
=== Announcements ===
Time for brief announcements.
=== Tickets ===
Tickets scheduled for discussion at this meeting can be found at
Please read through each ticket in advance so you can be prepared to
discuss them at the meeting.
=== Open Floor ===
Unscheduled topics can be raised during the open floor if time
permits. Discussion of any topic will generally be more productive if
participants know about the topics in advance and have some time to
think about them, so please add your topics to the meeting agenda in
the ticket system when possible.
If you would like to add a topic for discussion at our meetings please
open a ticket at
and set its milestone to meeting.
This mail is a reminder for today's meeting for the French speaking community.
2012-04-23 / 20:30 (hour of Paris)
Ce mail est un rappel pour la réunion de la communauté francophone, qui aura lieu ce lundi (23 avril) à 20h30 heure de Paris sur IRC (freenode) #fedora-meeting-1 .
L'ordre du jour est disponible depuis cette page :
N'hésitez pas à le modifier pour rajouter des sujets qui vous semblent intéressants.
Merci de répondre à ce message en cas d'indisponibilité.
A friendly reminder, the next weekly APAC meeting is on Saturday, April 21st, 2012 at 04:00 UTC. :)
The main priority of this weekly meeting is to show our continued support of FUDCon APAC in Kuala Lumper. :)
* Please be prompt and we will address priority issues first in order to save time.
Afterwards, we will review our APAC Plan for 2012 as well as what SWAG
for example, such as F17 media and others that you need for the future.
Our APAC Team as always fully supports you and I hope that your schedule permits attending our APAC meeting. :)
you are not able to attend the meeting, then please, update the meeting
wiki and let the wiki "speak" of updates on your behalf. That is what I
do and I strongly suggest this as an option for you. :)
Day : Saturday, April 21st, 2012
Time : 04:00 UTC
See the following URL to check and verify your own timing based on your location -
For any proposed changes to the agenda, then please update -
If you are not able to join us, then please update the agenda, in order to show your updates. :)
On Freenode IRC Channel : #fedora-meeting
Help on IRC -
We hope that you may be able to attend and join us. :)
Sending positive Fedora 16 & 17 energy to your computers now!!! :v)
Please have a Great Fedora day and/or evening! :~)
- David -
10 people 10 colors
Different strokes for different folks
Fedora Project's Japan & Maryland Ambassador dramsey(a)fedoraproject.org
With sixteen (16) x86_64 computing cores, 80 GB of RAM and eight SATA Seagate 7200.12 - 500 GB harddisks.
The system definitions are at the following URL:
I hereby respectfully petition the Fedora Board to dissolve the current
FAmSCo and call new elections.
FAmSCo voted in their meeting tonight to shorten the term of the lowest
vote-getters from the last election and to have those as the seats that
get re-elected next to start the new staggered terms. It also just so
happens that the ones that voted for that proposal are the ones that would
benefit by that proposal by not having to stand for reelection at the next
election. This is a conflict of interest and thus they should not be
allowed to vote on that matter. If they want to implement the staggered
terms starting with the next election, all members of FAmSCo should stand
for reelection, and have it noted that the top voted people would serve
two releases and the others would serve one. This way the voters would
know what we are voting for.
Also, our current FAmSCo seems unwilling to vote gbraad out, despite his
repeated failure to attend meetings, or participate in any discussions.
Nicholas E. Bebout
Thank you all for having brought back this important topic.
I am one of those who haven't not paid too much attention to it,
because many things move to slowly I haven't seen this coming so
Yes there are meeting (and meeting minutes), but we can't expect all
contributors to know what is going on every teams they are involved
That said, important information or when contributors are asked to
give their voice, should come on a really low traffic mailing list
(like announce@), to be able to target the thread more efficiently
(CCing amba at the announce email should do it).
> With all of that in mind, I do not think the Board's first reaction to this
> should be to "dissolve FAMSCo". However, I would definitely ask that FAMSCo
> reconsider their decision on how to implement the new Guidelines. Option #2
> (I believe it was the same in the meeting. I'm going by the email right
> now_) was to have all seats re-elected at the F18 election with the
> 4 highest vote getters serving 1 year and the other 3 seats serving for
> 6 months. This would make the transition swiftly while also taking care of
> the perception of unfairness. This, I think, might be a good compromise
> between Option 1 and 3 which received votes at the meeting.
This would have my +1.
BTW, thanks to the actual FAmSCo members for their work, having a seat
imply responsibilities and so much time!
As said previously, having things done quickly could hurt but
sometimes we need to take decisions (last time it was with the trans
team about Transifex.net ^^).
And thanks for amba who are able to bring hot topic to other amba missing them…
On 19.04.2012 15:04, Rex Dieter wrote:
> The whole point of the election rules change(s) was to stagger
> replacements, no?
the motivation - imho - was, to shorten the constitutional delays who
came with a complete new elected FAmSCo, to have more continuity and
avoid discussing the same things again and again.
Yes, re-elect all members, would mean they would start again with a
complete new elected FAmSCo. (this also has benefits if you want "cut
All has pro´s and contras so i look forward what happens next ;)
Joerg (kital) Simon
3691 0989 2DCA 58A2 8D1F 2CAC C823 558E 5B5B 5688