Following discussions we had on the list I am suggesting the usage of
tags on our email subjects to specify region-specific affairs
So we shall use [EMEA] [NA] [LATAM] and [APAC] accordingly.
Remember this is done solely for the sake of clarity of our mailing list.
Thanks for your understanding
PGP key: 0x6130DBF8
liknus @ GRnet , Freenode
This mail is a reminder for today's meeting for the French speaking community.
2010-12-20 / 18:30 UTC
Ce mail est un rappel pour la réunion de la communauté francophone, qui aura lieu ce lundi (20 décembre) à 20h30 heure de Paris sur IRC (freenode) #fedora-meeting .
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é.
Hi there !
I am happy to announce you that we had a release party on Saturday
December 4th in Paris!
There where about 70 people, 2 talks (Puppet and LaTeX) and one
workshop (our accessibility group manage to fill some Paris
We were also interviewed by a french radio during more than 1 hour
about Open Source, GNU/Linux and Fedora.
We distributed many Live CD and dispatch many other to french
ambassadors (about 300 Live CD). Pictures could be seen here and
Our goal was to interact with interested people, to install Fedora
when they brought their laptop or showing them how to make a LiveUSB
(and how to use it).
We also had people interested in OLPC, it was a pleasure to explain
the project, speak about the XO, and of course Sugar on a stick!
For this event, Renaudt has joined us. It is studying communications,
therefor we had some good tools:
* The event page was there to organize the event,
* The communications plan was there to focus our communication
* we have just added the results of our communications plan on its page
We also wrote a press release targeting the written press, and a press
kit which was sent to very famous french blogs (followed by *many*
peoples). Alright, we sent this too late to be very efficient, but we
have got the template for next release!
Next time, we will start communicating 3 months before the event,
using a new communications plan based based on this one.
We also plan to have a two days event, where the second day would be
mostly contributors and experienced users oriented.
Kévin Raymond (shaiton)
I will like to receive some feedback about a topic that has been runing in
my head for a while already and brings the matter of "What's really needed
to be a Fedora Ambassador?". Several times we repeat ourselves "we must
encourage people to join our comunity" and also things like "we accept
everyone, so everyone can be an Ambassador" but I consider this a lie to
them and to us. Not everyone can be an ambassador, and this are some of the
points I have consider to think like that:
we often receive request of applicants for the ambassadors team of users
1.- Have never contribute to the project
2.- Have never been at any FOSS activity
3.- Have been rejected of X communities with a not-good record
But we also have to face that, those who get the "Ambassadors title" often:
1.- Dissapear without say anything
2.- Dissapear without help our community
3.- Claim to be "Fedora workers"
4.- Dissapear but keep using the @fedoraproject.org
So, Do we really have an obligation to accept everyone? if not... Should we
keep telling people that we will accept everyone to be Ambassador if we
will/won't do it? I think that the Ambassadors admission process need some
rules besides the one that has (without be too excesive) to make a filter
that can help us, Mentor, to provide a better guidance to those contributors
that really deserve and want to be Fedora Ambassadors. So, I will write some
few ideas and if you guys/girls are interested on give some feedback would
be nice. (If you don't and the topic die here don't feel bad :) )
1.- Applicants must help to one of our 6 top teams 
2.- Applicants must help their local community, in case his/her city doesn't
have a local community, she/he should try to build it.
3.- Applicants should at least attend to one FOSS event per year. (right now
in all the country there are events, so this is not so crazy at all)
4.- Applicants should at least organize or help to organize a FOSS event.
Here are some ideas, as I say feel free to comment, aproove or deny the
suggestions I gave :)
Maria Gracia Leandro
GPG Public Key: E1CDCC56
"Be yourself... Don't be anyone else"
A friendly reminder that the APAC meeting will be on Sunday, December 19th 2010 at 03:00 UTC. :)
See the following URL to check and verify your own timing based on your location -
For any proposed changes to the draft agenda, then please update -
On Freenode IRC Channel : #fedora-meeting
Help on IRC -
I hope that you may be able to join us. :)
Sending positive Fedora 14 and Fedora 15 energy your computer now. :v)
Please have a great day and/or evening! :~)
- David -
Even monkeys fall from trees.
Even experts make mistakes.
Fedora Project's Japan & Maryland Ambassador dramsey(a)fedoraproject.org http://fedoraproject.org/wiki/User:Dramsey
* Two (2) dual core systems with 3.0 GB of RAM running the Fedora 12 (Constantine) kernel - 22.214.171.124-115.fc12.i686.PAE
* Two (2) dual core systems with 3.0 GB of RAM running the Fedora 13 (Goddard) kernel - 126.96.36.199-131.fc13.i686.PAE
* Two (2) dual core systems with 3.0 GB of RAM running the Fedora 13 (Goddard) and Security Spin kernel - 188.8.131.52-112.fc13.i686.PAE
* Two (2) dual core systems with 3.0 GB of RAM running the Fedora 14 (Laughlin) kernel - 184.108.40.206-65.fc14.i686.PAE
* One (1) dual core system with 3.0 GB of RAM running the Fedora 15 (Lovelock) kernel - 220.127.116.11-7.rc1.fc15.i686
* One (1) dual core system with 3.0 GB of RAM running the Red Hat 6 (Beta) kernel - 2.6.32-19.el6.i686
With eight (8) x86_64 computing cores, 16 GB of RAM and four SATA Seagate 7200.12 - 500 GB harddisks.