Some events have just finished so I think it is a good time to (re)share
this guidelines  for people who got Fedora funds for travel subsidy.
Note that you need to write N-1 blog posts (N = number of event days)
You can also find some useful information how to write and what should be
included in the reports.
Have a good time!
I think we can all agree that this idea make perfect sense!
From: "Jiri Eischmann" <eischmann(a)redhat.com>
Sent: 3/11/2014 14:07
To: "ambassadors(a)lists.fedoraproject.org" <ambassadors(a)lists.fedoraproject.org>
Subject: Re: [Ambassadors] Discussion: revoking ambassador status
Jiri Eischmann píše v Út 25. 02. 2014 v 11:07 +0100:
> yesterday we had a long discussion about whether we want to have a
> mechanism to remove completely inactive ambassadors or not. This issue
> is brought up again and again, so I think it's time to discuss it
> properly and eventually make a decision.
> You can find more in this ticket:
> Feel free to comment (ideally in the ticket to keep all discussion
> there), express your opinion, propose modifications, or even different
> solutions. You input is welcome.
I'm bringing an update on this issue. Based on the discussion in this
mailing list and in the ticket, we decided that any manual process for
removing "inactive" ambassadors is a no-go.
Pingou of Fedora Infra offered us a tool that would help us achieve what
we originally wanted to achieve.
The combination of FAS logs and datagrepper (that covers attending IRC
meetings, using tracs, sending emails to mailing lists, voting in Fedora
elections, writing blogposts in FP,...) can identify ambassadors who
haven't had any sign of online activity for the given time period (in
FAmSCo we agreed on 18 months, but it's still open) and may not be
interested in the project any more.
Those ambassadors would be notified by email that their account is going
to be flagged as inactive in e.g. 14 days. To avoid it, they can just
log in to FAS and they're fine for another 18 months.
I'd like to emphasize that no one is going to lose ambassador
membership. If someone meets the criteria and doesn't react to the
notification message his/her account will just be flagged as inactive
and his/her name won't be in the public list of ambassadors, but he/she
will keep the membership and can become active again just by logging in
to FAS and changing the status to active any time after the deadline.
It's not meant to judge someone's activity, it's more like "we haven't
seen you around online for some time, give us a wave if you're still
interested in the project".
In FAmSCo, we agreed this is a non-invasive solution with pretty much no
additional bureaucracy that would solve the problem. But we'd again like
to know your opinion.
ambassadors mailing list
just a reminder that we will have a regular EMEA ambassadors meeting
* Date: Wednesday, March 5th, 2014
* Time: 21:00 UTC
* Location: #fedora-meeting@freenode
* Meeting agenda:
If you'd like to discuss a specific topic, please add it to the agenda.
Meet you in the evening!
This mail is a reminder for today's meeting for the French speaking community.
2014-03-11 / 21:00 (hour of Paris)
Ce mail est un rappel pour la réunion de la communauté francophone, qui aura lieu ce mardi (11 mars) à 21h00 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é.
*** It is unlikely I will be available tonight but please carry on. ***
Please join us for our weekly FAmNA meeting this Tuesday at 9:00pm
Eastern in #fedora-meeting on irc.freenode.net.
I'd like to remind everyone that it is important for us to get some work
accomplished at these meetings and staying on the topic is important
to that end. All comments are welcome from ambassadors during the
meetings but please wait until the Open Floor to add any subject
matter not included in the meeting agenda via a ticket.
Feel free to add to the agenda. The easy way to add an agenda item is
described at the bottom of this announcement. Especially if you have
an event coming up that needs some attention.
This week's meeting leader: ?
== 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.
=== Select Next Meeting Leader ===
=== 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.
Finally, after a long time, we had a Fedora meetup today (March 8,
2014) in Bangalore at Red Hat's office in Bangalore.
The attendees for the event were:
- Anil Shah
- Varun Shastry
- Rejy M Cyriac
- Ratnadeep Debnath
- Sayan Chowdhury
- Sarup Banskota
Following is a summary of the discussions that took place in today's meetup:
Fedora monthly meetup
We've decided to do a local Fedora meetup every month to discuss and
act on reaching out to more and more people in and around the city to
encourage usage of FOSS tools, Fedora and contributing back.
Once in a while, we decided have FADs where fellow Fedora folks get
together to share knowledge and hack on cool projects.
Reach out to colleges
In a slow and steady manner, we'd go to colleges and local LUGs and
conduct events and workshops to educate and inspire more people to
contribute to FOSS and Fedora.
Entry point for contributors
We'd be working on creating the necessary tools to help newbies get
started with contributing to Fedora very easily. This is inspired from
Please feel free to drop your comments and opinions on the above
topics discussed in today's meetup to help us do better job in
evangelising Fedora and inspiring people to contribute.
GPG Fingerprint: 033C 8041 A0E9 CDBA 2E02 B785 2119 5486 F245 DFD6