He was 95, so it's no unexpected, but, you know, still. I'm going to be
traveling to be with my family this next week. I'll miss the council
meeting — hopefully that can go on without me, though, as I do want to
advance the FAmSCo transition. I'll watch it when I get back.
Fedora Project Leader
in regular intervals, members of the Fedora Council report status of
their projects. On Monday, it was my turn to report about the current
state of FAmSCo and our efforts of transitioning to FOSCo, the "Fedora
Outreach Steering Committee".
I'd like to take this opportunity to kick off a new round of
discussions about FOSCo. Here are a few links to get started:
* Recording or our hangout https://youtu.be/eOCmB1xHCqQ
* Slides I used during the hangout: https://goo.gl/cH4h4e
* Meeting minutes:
* FAmSco ticket with latest discussion:
The idea of FOSCo dates back to 2014, time for us to finally make it
happen. Our goal is to have a design ready by/at FLOCK and then make a
smooth transition as part of the next regular elections.
That's why we are looking forward to your questions and ideas. I tried
to give as much background as possible, but if you think that my
summary was quite right or have other concerns, please let me know.
P.S.: @FAmSCo members: For maximum participation and transparency,
please use one of the public mailing lists (ambassadors or
council-dicsuss, but not famsco).
We'll do a Google Hangouts meeting on monday — Christoph will do a
brief presentation on the state of FAmSCo and FOSCo transition. After
May 30 -- *skip* (Memorial Day in the US)
Jun 6 -- Open Floor (F24 release scheduled this week!)
Jun 13 -- Subproject Report (CommOps)
Jun 20 -- Open Floor
Jun 27 -- Tickets and Ongoing (Week of Red Hat Summit)
Jul 4 -- Open Floor or skip (Independence Day in the US)
Jul 18 -- Subproject Report (tbd)
Jul 25 -- Open Floor
Aug 1 -- *skip* (Week of Flock!)
Fedora Project Leader
Over in Fedora Marketing for the past few weeks, we've been working on
putting together a proposal for a new program, "Fedora Affiliates". This
is a way for organizations like schools, non-profits, or companies that
are actively using Fedora to get a little recognition and exposure as
users of Fedora. Not only does this help them, but it also provides a
record of people that are using Fedora already in all kinds of different
So, for example, if a school is unsure about whether a Linux / Fedora
computer lab is possible, you could visit the Affiliates page, see
examples of schools that are using Fedora, and reach out to them with
questions if needed.
Anyways, our team member who took this on, James, was hoping to get some
more feedback on his proposed drafts for how we explain and recruit
affiliates. The links for all of these things are in the forwarded
I am sending this to the Ambassadors and council-discuss list. If you
have feedback or comments, the preferred way to leave them is on the
Trac ticket (also linked below). However, if you want to reply back to
this thread, please do so on the Marketing mailing list.
Thanks for your time!
-------- Forwarded Message --------
Subject: [Marketing] Fedora Affiliates
Date: Tue, 17 May 2016 20:03:55 -0300
From: James Bishop <james(a)jamesbishop.ca>
Reply-To: Fedora Marketing team <marketing(a)lists.fedoraproject.org>
To: Fedora Marketing team <marketing(a)lists.fedoraproject.org>
Over the past several weeks, the marketing team has been working on a
way to publicize "Fedora Affiliates", or projects that are using Fedora
as part of their work. The ticket for this can be found here:
At this time, several wiki pages have been created, and you can find
Any thoughts or suggestions you might have would be appreciated.
P.S. Justin: Could you pass this along to the Ambassadors group,
Fedora Marketing mailing list
I'm the upstream GNOME Software maintainer, but I'm emailing now as a
Fedora package maintainer. Upstream gnome-software is soon to add
support for paid software, driven by Canonical for the snappy work
they are doing. One upside for us is that it now makes it possible to
provide a way for end users to donate to specific projects, and after
talking to Peter Robinson he suggested I should email here for advice.
The options we have are basically:
* Disable all support for paid applications and donations from the UI
* Enable the "Donate" button that takes you to the upstream-defined
donation link (e.g. GIMP -> https://www.gimp.org/donating/)
* Hijack the donate button to take people to
https://fedoraproject.org/wiki/Contribute or something more beautiful
We could also enable/disable the button depending on the non-freeness
or 3rd-party-ness of the application, but then my worry would be that
would actually _dissuade_ otherwise free software projects from being
shipped by Fedora as the revenue stream would be stopped when they
move from a COPR to core.
I'm not sure what the Fedora requirements are here, and I wanted some
advice from the Council about what is acceptable. Thanks!
I'm going to be at CLS this weekend, which means I'll be traveling
tomorrow and Monday, with intermittent checkins to the 'net. I'll
definitely miss the meeting on Monday.
Fedora Project Leader
This came up in our Council meeting yesterday¹. Specifically, the
"Growth Model for the Fedora Project. What is it? Do we have one? There
was a fair amount of feedback stating that without specifcs. There is
So, there *is* a plan, with several components. Since the first Flock
in Charleston, much of it has been under the "Fedora.next" umbrella.³ I
feel like we've talked about it quite a lot, but I'm definitely happy
to do more.
The _basic_ strategy FESCo and the (pre-Council) Board chose is what we
now call "Three Editions". Rather than pushing Fedora as an amorphous
operating system which doesn't necessarily fit any purpose specifically
but which can be good for anything, we decided to intentionally create
three targetted editions. This doesn't mean that the Fedora OS we're
all familiar with is anything less, but to concentrate our marketing
and "selling"⁴ efforts around specific areas. We don't give up on
everything else — but we *really* win in these places, and then grow
out from there.
At and after Charleston, the rough idea was that we needed something
technical-user desktopy, something servery, and something
emerging-modely (which, in 2013, definitely meant _cloudy_). We asked
volunteer groups with interest in these particular areas to identify a
target subset of that area to aim for. And from that, we arrived at:
* Fedora Workstation: Here, the target is software developers — not
of Fedora, but as end-users.⁵
* Fedora Server: Linux server with push-button deploy of preconfigured
best-practices setups for specific tasks.⁶
* Fedora Cloud: a base platform for building scale-out cloud computing
applications (as opposed to the many other buzzwordy uses of
We're probably going to replace Fedora Cloud with Fedora Atomic Host,
because we _weren't_ really succeeding in growth with that one. (Fedora
Cloud base image won't go away; it just won't be the focus from this
"growth plan" perspective.)
So, Three-Editions is the basic strategy for the OS we produce — which
is the primary activity through which we aim for our mission. But it's
not all on the making-an-OS side. We also have two other "Objectives"⁸
on deck which are related to growth.
The first is the University Involvement Initiative⁹, which didn't get
much traction this year but which Remy is planning to revitalize for
the next one. This calls for user and contributor growth specifically
The second is in draft form — and has basically been waiting for us to
work through the budget stuff to give us time to talk more. This is
Fedora Python Marketing¹⁰. While Fedora Workstation focuses on
developers, this idea is to aim some resources even more narrowly and
to promote Fedora specifically as the distro-of-choice in the Python
community over the next year. Again, the goal isn't for Fedora to end
up as Python-specific, but to build that base (and to build on the
already strong Python connections we have) to grow from.
And, here is perhaps the most important thing. The Council has slots
for 2 to 4 objectives like this at a time. Sometimes these will be
technical (like Modularization¹¹), but I think it's good for us
generally to have at least one focused on user and/or contributor
growth at all times. Each objective comes with a 12-18 month lifespan,
so we can judge how each worked, and figure out something even better
for the next time. So, we don't just have some short-term plans, but
also an engine for continuous reexamination and mid-range planning.
Notes and links:
2. From Mark Terranova (Hi Mark!), but this message isn't really to him
3. From 2014, see: https://fedoramagazine.org/fedora-present-and-future-a-fedora-next-2014-u...
4. In the metaphorical sense — we're absolutely not and will not be
literally selling anything.
8. What's a capital-letter-O "Objective?" see
Fedora Project Leader
Last Regional Best Guess
Official FY17 at Actual
Budget Request FY16 Spending⁵
APAC 12650 (12.7%) 33025¹ (22.1%) 7600 (13.1%)
EMEA 27000 (27.0%) 33250 (22.2%) 15000 (26.0%)
LATAM 16500 (16.5%) 23180 (15.5%) 11000 (19.0%)
NA 43850 (43.9%) 60000² (40.1%) 24200 (41.9%)
total 100000³ 149455⁴ 57800
1. Based on totaling the wiki page
3. Remember, this year's budget excluded FADs, which is not something
we want to repeat; FADs were actually paid for from underspend
4. Yeah, that'd be nice....
5. This may not account for everything, but here's what we have from
So, as a semi-arbitrary starting point, if we average the percentages
from each of the categories, that gives us:
If we give EMEA a 5 percentage-point "credit" for having a nice
spreadsheet in early, that works out to:
If we allocate the $73500 in total regional funding, that looks like
this (rounded slightly for prettiness):
Adjusted Percent of Percent of
FY17 Asked for Recorded FY16
Allocation Amount Spending
APAC: $11500 34.8% 151.3%
EMEA: $21650 65.1% 144.3%
LATAM: $10950 47.2% 99.5%
NA: $29400 49.0% 121.5%
Like I said, here's a starting point. What do you think?
Fedora Project Leader