#16: Periodic contributor survey
---------------------+-------------------
Reporter: mattdm | Owner:
Status: new | Priority: normal
Component: General | Keywords:
---------------------+-------------------
This is a tracking ticket for establishing a process by which we get
regular feedback from the Fedora contributor base.
This is a companion to https://fedorahosted.org/council/ticket/1. The
desired goals, methodology, and basically everything else are really
different between users and contributors it will be better to track them
separately.
--
Ticket URL: <https://fedorahosted.org/council/ticket/16>
council <https://fedorahosted.org/council>
Fedora Project Board Public Tickets

#22: Objective Proposal: University Involvement
----------------------+-------------------
Reporter: sgallagh | Owner:
Status: new | Priority: normal
Component: General | Keywords:
----------------------+-------------------
I alluded to this during the Council meeting on Monday, so I'm going to
attempt to turn this into a formal proposal.
== Objective: University Involvement ==
=== Overview ===
Increase Fedora's exposure in university environments, particularly
engineering universities.
=== Expected Impact ===
Increased user base with a specific focus on future contributors.
=== Timeframe ===
For maximum effect, if we elect to work towards this Objective, we should
kick it into gear at the beginning of the summer with the intent of having
events planned during the 2015-2016 school year.
=== Aspects ===
* Coordinate marketing, ambassador and outreach groups to focus on
university needs
* Work with universities to provide install-fests during student
orientation periods
* Work with universities to regularly run Fedora-focused hackfests
* Work with university IT departments to co-maintain one or more Fedora
computer labs (and help them upgrade them during breaks)
* Establish work-study, co-op and for-credit programs at universities
=== Metrics ===
* Increased contributions from university programs
* Increased bug reports and feature requests
* Increased mind-share among potential contributors (not easily measured)
=== Additional Notes ===
Some prototypes of this have been performed at Brno universities over the
last few years, with very positive results. We should coordinate with the
contributors involved in those efforts and learn from their successes and
failures.
There is also a University Outreach program run by Red Hat's "Open Source
and Standards" department which was involved in the RIT partnership from
which we eventually acquired Remy DeCausemaker. I assume he will have
plenty to add to this discussion as well as contacts in the university
world.
--
Ticket URL: <https://fedorahosted.org/council/ticket/22>
council <https://fedorahosted.org/council>
Fedora Council Public Tickets

#21: Permission for using Fedora trademarks for "Bantuan Fedora Indonesia"
---------------------+-------------------
Reporter: salimma | Owner:
Status: new | Priority: normal
Component: General | Keywords:
---------------------+-------------------
Some Indonesian contributors are working on utilizing [https://github.com
/fedora-id/asknot-ng asknot-ng] for providing a landing page for users
(and potential users) to get a clear picture of localized Fedora resources
and potential ways of contributing .
The main Fedora instance of asknot-ng powers
[http://whatcanidoforfedora.org/ What Can I Do For Fedora]; for ours we
have not decided yet what domain we will use.
To generate the static site from the code on GitHub, the original
instructions apply, but use this invocation instead:
````
./asknot-ng.py templates/index.html questions/bantuan.yml --theme fedora
````
We will probably create a substitute theme if permission to use Fedora
branding is not obtained; we plan on contributing translations for the
main site as well.
If this requires a discussion at an upcoming meeting, let me know and I'll
notify the others to attend as well. Thanks!
--
Ticket URL: <https://fedorahosted.org/council/ticket/21>
council <https://fedorahosted.org/council>
Fedora Council Public Tickets

#17: Objective proposal: Fedora Flavors Phase 2
------------------------+-------------------
Reporter: mattdm | Owner:
Status: new | Priority: normal
Component: Objectives | Keywords:
------------------------+-------------------
I posted this on [https://lists.fedoraproject.org/pipermail/council-
discuss/2014-December/013066.html council-discuss] a few weeks ago and
there was a little discussion. Because this is really a continuation of
something we've previously agreed to, I think this is straightforward.
Since objectives are non-trivial, we should go for the "full +3 with no
-1s" consensus, but also, since this has technical components which impact
F22 planning -- which is starting now! -- I'd like to have the final
decision as soon as possible.
= Objective: Fedora Flavors, Second Phase. =
Overview:
* Take the initial Server/Workstation/Cloud split from Fedora 21 from an
experiment into solid production. Increase autonomy from FESCo and
improve targetted outreach.
Expected Impact:
* Increased user base and user satisfaction in targetted areas. Increased
contributor community around the targets. Increased ability to adapt to
future or expanded targets as needed.
Timeframe:
* Although we expect the "Fedora flavors" concept to be ongoing, this
"second phase" is targetted for the F22 and F23 releases, making it
an approximately 12-month objective. That way, this council objective
lead slot will be open shortly after Flock 2015.
Aspects:
- Coordinate Working Groups' development of updated PRDs and changes and
features for each release.
- Work with FESCo and Fedora Program Manager to develop process whereby
flavor-specific Changes are handled primarily at the WG level.
- Work with Outreach (marketing, ambassadors, etc.) to identify and plan
representation at new conferences specific to the various target
audiences.
- Plan, coordinate, and schedule release engineering and infrastructure
changes in advance of the F22 and F23 alpha releases.
- Lay groundwork for possible different release cycles and lifespans.
- Tooling and infrastructure for spins and remixes to increase
differentiation. # _Note: perhaps this is big enough to be an
independent
objective of its own, along with better promotion for spins._
- Work with Council and community to develop concrete process for
expansion
(or possible contraction) of Fedora flavors as identified needs change,
working from the product definition previously approved by the Board
Metrics:
- PRDs updated. Changes filed, changes accepted, changes completed.
- Conference reports; user data from those conferences.
- User and contributor surveys, and other user and contributor measures
- Usability is increased as measured by user testing specific to each
target group
----
(My only regret here is that we are not up to Phase Four, for full-on
Fedora alliteration.)
----
Additionally, I would like to nominate Stephen Gallagher for the role of
Objective Lead. Stephen brought the "three products" idea to Fedora.next,
was instrumental in its realization in the F21 release, and, also, tells
me that he will have significant time to dedicate to this over the next
year.
(Please vote on this nomination as a separate +1/-1 along with any +1
votes to the proposal overall.)
--
Ticket URL: <https://fedorahosted.org/council/ticket/17>
council <https://fedorahosted.org/council>
Fedora Council Public Tickets

Council,
After much thought and input from Fedorans since I've arrived officially, I finally present for your review a proposal on the future of FOSCo.
tl;dr - Narrowly define FOSCo as a decision making body to handle budgetary requests from subprojects, and revive/revamp the Fedora Commarch Team.
There is a lot in there for sure, but I think the proposal addresses the concerns of the many Fedorans thusfar I've spoken with, gives some concreteness to what the priorities of the FCL are, and a bit of how to get there. I was hesitant to undo the consensus established around FOSCo, but I really do think this is a better vehicle for driving community action, measuring it, and storytelling after the fact.
Looking Forward,
--RemyD.
--
Remy DeCausemaker
<decause(a)redhat.com>
Fedora Community Lead & Council Member
http://whatcanidoforfedora.org

The "How to organize a FAD" page at
<https://fedoraproject.org/wiki/How_to_organize_a_FAD> previously
stated that budget is "the absolute first priority". Now, maybe this is
my hippie upbringing speaking, but I don't think it's _really_ all about
the money. I've changed this to "this needs to be a very early
priority" — it's still important, but I think the first priority in
planning a FAD should be thinking about the impact the FAD is intended
to have.
That should be both in concrete terms of "What're we gonna get done?"
but also _"What does this do for the project overall?"_ (Or, I guess,
if you _do_ want to make it all about the money, "Why should we spend
on this?")
I'm going to pull out this ASCII chart again:
/============+============+=============++=============+=============\
| | | || | |
| Resources | Activities | Outputs || Outcomes | Impact |
| | | || | |
+------------+------------+-------------++-------------+-------------+
|What we |What we do |The direct ||The specific | Mission and |
|have: time, |with our |products of ||change in the| vision; our |
|money, code,|resources |our ||world due to | long term |
|hardware... | |activities ||those outputs| effect |
+============+============+=============++=============+=============+
| Things we can affect directly || Out of our direct control |
+============+============+=============++=============+=============+
| <----- planning flows right to left ---------< |
+============+============+=============++=============+=============+
| >------ effort flows left to right ----------> |
\+===================================================================/
Starting with money is planning from the left side — it's a resource.
This doesn't result in the best use of those resources. Obviously,
there are pragmatic *limits* to those resources so that number needs to
go into the on-the-ground planning, but if we start from the change we
want to effect, we can better judge if a particular goal fits within
what we have, or is worth finding more by reallocating or fundraising.
And, it avoids overspending based on "well, we've got this budget, so
let's make sure to use it up".
Additionally, unless there is objection, and I hope there isn't, I'm
adding wording that FADs which are connected to the Council's accepted
12-18 month community goals will be given priority.
I also have another pair of changes to propose. Currently, the
procedure is to work with OSAS on the budget and with the FPL for final
approval. I have suggested tweaks to both of these.
In line with the Council plan overall, I'd like to change the "work
with the OSAS team to figure out the budget" part to "work with the
Fedora Council". As defined in the Council charter, facilitating
decision making on focusing the OSAS-provided Fedora community budget
is one of the Fedora Community Action and Impact Coordinator's roles
(hi Remy!), and this seems like a natural place to do that. (We could
also make the wording "work with the Community Action and Impact
Coordinator" rather than council at large.) Of course, the Council (and
Remy, who *is* on the OSAS team inside of Red Hat) would work with OSAS
in the determination — the change isn't in where the money comes from
ultimately, but in the contact point for organizers (and in
transparency and visibility).
Second, I'd like to change the FPL approval to Fedora Council approval.
This is largely a matter of transparency — usually, these requests are
mailed to me directly, and I think it'd be better to talk about them
here instead. (This obviously makes a lot of sense in conjunction with
talking about the budget with the council too.) Not that I have a
problem being the approver per se, but it'd be nice to have this
process be more open to community input.
Thoughts, comments, objections, refinements?
--
Matthew Miller
<mattdm(a)fedoraproject.org>
Fedora Project Leader

Okay, so, with my plan posted Monday, the coming Monday we have
> - April 27: Council business meeting
For which I will put together an agenda. Are there particular things
which are _ready_ for a meeting? Any progress, for example, on the
FOSCo idea, or on the University objective idea?
--
Matthew Miller
<mattdm(a)fedoraproject.org>
Fedora Project Leader

#18: decision on reverting start.fpo change
---------------------+-------------------
Reporter: mattdm | Owner:
Status: new | Priority: normal
Component: General | Keywords:
---------------------+-------------------
See https://lists.fedoraproject.org/pipermail/council-
discuss/2014-November/013049.html
We don't have complete project consensus, which is why the Firefox
maintainer asked for a council decision. I think, though, that we _do_
have council consensus, at least based on everyone I've heard from.
So, the proposal is:
> Please revert the Firefox start page to http://start.fedoraproject.org/.
Future improvements for usability or other enhancements can be made for
the F22 timeframe or beyond, taking both user experience design and other
Fedora stakeholders like marketing and outreach into account.
Since F21 has already shipped, the urgency has decreased, but assuming
this passes, let's get it reset for the next update for for F22 by default
in absence of another plan. I'm proposing this as a lazy approval decision
(see [http://fedoraproject.org/wiki/Council#Making_Decisions Making
Decisions], and since the holidays are upon us, let's make the timeframe
for votes be the rest of December.
--
Ticket URL: <https://fedorahosted.org/council/ticket/18>
council <https://fedorahosted.org/council>
Fedora Council Public Tickets