which means that "Modules Working Group" is now a Thing.
I went back to
look at how we formed the existing working groups in the first place,
and it turns out the process started with me sending this message:
I suggest that we start with the same process now -- I'll send out a
similar message and people can self-nominate. We can follow the same
one month timeframe, for formalization (while Langdon does his Grand
Tour), but of course that needn't stop interested people getting
Previously, the members were selected by FESCo from the list of
nominees. I suggest this time we have Langdon as Objective Lead do that
selection submit that to the Council for approval (which will include
FESCo voice through Josh as the Engineering lead, if necessary).
Also, now is the time to nail down any bikeshed painting anyone has on
Modules WG vs Modularity WG vs Modularization WG. (Modularizing WG?
Modulatory WG? Modulating WG? Okay time for some coffee.)
Fedora Project Leader
I'd like to discuss an idea:
in the past (after F19 and F20) we gave t-shirts to contributors that
were nominated by respective teams for their work on the last Fedora
release. We packaged them with a "Thank you" message.
It was a nice touch and a lot of contributors were very happy about, we
received very positive feedback which proves that this kind of
recognition makes sense.
I'd like to repeat it after F24. I've asked Maria Leonova to create
artworks. She developed two difference artwork ideas:
One emphasizes that the owner of the t-shirt is a member of Fedora
family (the "People" aspect of Fedora Project), the other emphasizes
the work (the "Feature" aspect of Fedora Project). Which one do you
What we need to make this happen:
1. Artwork (checked)
2. Budget (one t-shirt is ~$5, last time we produced 200-250 of them, +
3. Nominations from teams
4. Collected mail addresses
5. Production, packing, shipping
The agenda is to:
0. Intro, Welcomes, Agenda (5 minutes)
1. Review proposal to refresh Modularity Objective (15 minutes)
See mail from Langdon to devel-announce today about this, and review
the draft proposal at
2. Review University Involvement Initiative (15 minutes)
I think this is a great idea with high hopes, but we didn't actually
get very far. We should decide if we want to try again for the
2016-2017 academic year.
3. Proposals for other new objectives (15 minutes)
We have "slots" for up to four, and should have at least two.
Not expecting to decide on anything -- goal is to list possibilities
and gauge interest. Ideas I've heard so far:
- Python Developer Marketing for 2016
- Make Fedora Hubs an objective to help coordinate across the
- OpenShift/Fedora — as I proposed earlier, but if only _I_ am
excited about it, doomed to failure.
4. Open Floor (10 minutes, if that's actually left)
Identifying and supporting objectives is the _primary_ role of the
council, so this is an important meeting. I hope everyone can make it.
Note that Daylight Saving Time kicks in in the US, making this
nominally an hour later. Use date -d '2016-03-14 18:00 UTC' to convert
to your local time.
Fedora Project Leader
After working for the past couple of weeks with the websites and
infrastructure teams, I'm pleased to share with you all
Thank you nb, robyduck, nirik, puiterwijk, and threebean for your patience
and mentorship :)
So now, budget stakeholders and leaders (Ambassadors, Council, and FAmSCo)
you can visit the site and provide feedback and input.
The actual budget numbers for this year ARE NOT ACTUALLY ZERO, so don't
panic or anything, they just haven't been reported yet ;) When they are, I
will update the website accordingly.
Contributing to Budget.fp.o
If you would like to help work on the budget site itself (PR's are
certainly welcome) please join #fedora-websites on Freenode and talk to the
team there first. The team is transitioning where our repositories are
hosted, and are making some changes to the fedora-web workflow (while
branching for F24-alpha.) In the future, you should be able to clone the
source for the budget site (and the other Fedora Websites) at
https://pagure.io/fedora-websites. ***WARNING*** Since our production
environment is built from the master branch, be sure to be working in an
alternate branch (git branch budget, for example) Starting now, you can
file tickets for the budget site on the Fedora-websites repo on pagure:
Budget Tracking -- Still a Regional Responsibility
I will be relying on ambassadors to be tracking your expenditures (like you
always have) so I can be updating the budget numbers section on a quarterly
basis, with reimbursements depending on event reports from regional
delegates. I will help report your budgets on
http://budget.fedoraproject.org (coming soon), but it is still up to the
REGIONS to keep as budget is spent. The good news though, is that now you
have The Community Operations (CommOps) team here to help support
publishing event reports and gathering and reporting metrics.
Budget Data and Files
When there are working budget documents, data, and information fit for
public consumption, I have created a new repo for sharing such files at:
https://pagure.io/budget (it is mostly empty for now, but feel free to
start putting your proposed budgets there if you have them Ambassadors.)
There is in the plans (but not yet implemented) the idea that we can use
webhooks or other git-magic to have the budget numbers and contacts on
budget.fp.o update automatically based on the data in this repo, but that
will likely be a feature for v2.0. For now, I'm OK with starting manually
until we hammer out the details and settle on a process.
I would like to start adding all the Regional Delegate selections to our
staging instance in preparation for the site hitting production in the next
week or two, starting now. So, if your region has chosen delegates already,
you can respond here with their names and email addresses, and I will add
them to the site. Alternatively, you could also file tickets on the budget
repo in pagure, (or file pull requests updating your regional delegation's
.yaml file) and I will merge/close them as I update the site.
***The budget process is going to move quickly from here, so Ambassadors
please have your delegation choices sent to me, filed into tickets, or
included in a pull-request by Friday March 4th.***
Budget.next and The Future
I'm excited to help Ambassadors and Project Leadership bring more
transparency to the budget process--one of my core charters as the first
ever Fedora Community Lead. I am hopeful we can develop a process that will
improve reimbursement turn-around, while creating metrics on action and
impact we can use to strategically adjust and improve our financial
situation in the future.
P.S. - I've cc'd a number of public lists in this email, so take special
care when replying to this post.
Fedora Community Lead & Council
as Matthew announced at DevConf.cz our primary marketing focus for this
year are Python developers.
In EMEA, we've reacted and increased the number of Python events in the
list of planned events (several PyCons, planning to be at EuroPython
again...), but I realized we're not ready for that at all, or at least
I'm not aware of anything.
We have no marketing materials. Miro created a "Fedora loves Python"
sticker for Python CZ, but that's all we have in EMEA. Today, we were
offered an opportunity to add our swag in conference bags at PyCon SK,
but we don't have anything usable. Something like a flyer that explains
why Fedora is the right system for a Python developer would be great.
And it's not only about marketing materials, ambassadors should get
instructions what to show Python developers, so that it won't end up
like showcasing a la "hey, Fedora is cool, it has Firefox,
LibreOffice,... and look it has windows just like Windows or Mac". So
we would definitely need at least some talking points.
Is it something that is already being worked on or we have to start it?
If we spend a sizable amount of money to send people to Python
conferences, we should get maximum out of it.
Please accept our apologies. Earlier today, you may have received a
notification of non-acceptance for a session we did actually intend to
To clarify, we look forward to hosting the following session(s) at Red Hat
- SB44549: Fedora Friends!
The Red Hat Summit team
Add this to the pile for Good News Leap Day Monday!
Fedora Community Lead & Council