#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

#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

#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

#19: new terminology for cloud/server/workstation
-------------------------+-------------------
Reporter: mattdm | Owner:
Status: new | Priority: normal
Component: Fedora.next | Keywords:
-------------------------+-------------------
We've been using the term "product" to refer to the different Fedora
variants produced and marketed as part of the new (or by now, not so new)
Fedora.next plan. This has a number of problems -- we're not actually
selling anything, and we don't want to give that impression. And some
spins users have expressed that it doesn't carry the meaning that we did
intend very well. So, we're looking for something new.
I had suggested "flavors", but that has its own problems: it's idiomatic,
doesn't translate well, and apparently I'm the only one that likes it. :)
So let's find something else.
--
Ticket URL: <https://fedorahosted.org/council/ticket/19>
council <https://fedorahosted.org/council>
Fedora Council Public Tickets

#20: Request to extend the mandate of current members of FAmSCo
-----------------------+------------------
Reporter: eischmann | Owner:
Status: new | Priority: major
Component: Other | Keywords:
-----------------------+------------------
Hi,
we're currently figuring out how to reorganize the outreach part of the
Project to meet today's needs better. FAmSCo most likely will be dissolved
and replaced by FOSCo. In FAmSCo [1], we agree that it doesn't make much
sense to organize elections to a body that is going to cease to exist in a
couple of months. Instead we'd like to ask the Council as a higher
authority to extend our mandate till the F22 release to figure out a new
governance model and make a transition from FAmSCo to FOSCo. The new
elections should already be to the new body after F22.
[1] http://meetbot.fedoraproject.org/fedora-
meeting-2/2014-11-25/famsco_2014-11-25.2014-11-25-16.00.html
--
Ticket URL: <https://fedorahosted.org/council/ticket/20>
council <https://fedorahosted.org/council>
Fedora Council Public Tickets