Re: [council] #1: Periodic user/contributor survey
by fedora-badges
#1: Periodic user/contributor survey
------------------------+-----------------------
Reporter: mattdm | Owner: somebody
Status: new | Priority: major
Component: component1 | Resolution:
Keywords: |
------------------------+-----------------------
Comment (by mattdm):
Replying to [comment:5 duffy]:
> Okay cool - so it seems the main goal is just to understand who is using
Fedora right now and how.
>
> I would guess the problem to solve here then - we're trying to outreach
to bring more new users in, so doing annual surveys of who is using Fedora
could help us understand if we are reaching those new users or not? So it
could be a measurement of whether or not all the changes we're making are
actually effective at bringing more folks in?
+1
In addition to demographics, I'd like to get some metrics around user
engagement.
We can do _contributor_ engagement fairly well, by looking at things like
badges (and basically everything fedmsg).
--
Ticket URL: <https://fedorahosted.org/council/ticket/1#comment:7>
council <https://fedorahosted.org/council>
Fedora Project Board Public Tickets
9 years, 3 months
Re: [council] #1: Periodic user/contributor survey
by fedora-badges
#1: Periodic user/contributor survey
------------------------+-----------------------
Reporter: mattdm | Owner: somebody
Status: new | Priority: major
Component: component1 | Resolution:
Keywords: |
------------------------+-----------------------
Comment (by sparks):
Replying to [comment:5 duffy]:
Well, specifically contributors (defined as anyone who has a FAS account).
It's incredibly difficult (okay, I'll say it, impossible) to gain any
useful information from an ill-defined group of people.
--
Ticket URL: <https://fedorahosted.org/council/ticket/1#comment:6>
council <https://fedorahosted.org/council>
Fedora Project Board Public Tickets
9 years, 3 months
Re: [council] #1: Periodic user/contributor survey
by fedora-badges
#1: Periodic user/contributor survey
------------------------+-----------------------
Reporter: mattdm | Owner: somebody
Status: new | Priority: major
Component: component1 | Resolution:
Keywords: |
------------------------+-----------------------
Comment (by duffy):
Okay cool - so it seems the main goal is just to understand who is using
Fedora right now and how.
I would guess the problem to solve here then - we're trying to outreach to
bring more new users in, so doing annual surveys of who is using Fedora
could help us understand if we are reaching those new users or not? So it
could be a measurement of whether or not all the changes we're making are
actually effective at bringing more folks in?
--
Ticket URL: <https://fedorahosted.org/council/ticket/1#comment:5>
council <https://fedorahosted.org/council>
Fedora Project Board Public Tickets
9 years, 3 months
Re: [council] #1: Periodic user/contributor survey
by fedora-badges
#1: Periodic user/contributor survey
------------------------+-----------------------
Reporter: mattdm | Owner: somebody
Status: new | Priority: major
Component: component1 | Resolution:
Keywords: |
------------------------+-----------------------
Comment (by sparks):
Replying to [comment:3 duffy]:
> so what is the problem to solve here? what questions are we trying to
answer?
This is a very old request. It came about with trying to figure out who
our contributors are, what they use (software), and other questions we
might want to track the answers to. Robyn and I had worked up a series of
questions and even met with the person that makes Red Hat's surveys. In
the end, there was little interest in doing the survey in a meaningful way
and the whole idea got dropped.
I believe some of the questions we were hoping to have answers to included
what desktop environments contributors use, where our contributors are,
other contributor traits, how satisfied they are with the Fedora Project,
etc.
--
Ticket URL: <https://fedorahosted.org/council/ticket/1#comment:4>
council <https://fedorahosted.org/council>
Fedora Project Board Public Tickets
9 years, 3 months
Fedora 12-month objective proposal: Fedora Flavors Phase 2
by Matthew Miller
A little while ago, I posted about Project objectives, and a framework which
I hope shows what we need and why we need it. (If you missed it, see
<http://fedoramagazine.org/lets-talk-about-fedora-project-objectives/>.)
Selecting a few key objectives and identifying and empowering Objective
Leads for each is one of the new Fedora Council's chief responsibilities.
(Again, if you missed it, see <https://fedoraproject.org/wiki/Council>.)
Since the initial members of the council are now in place, let's start
talking about the first of these.
This is definitely not something we want to rush into, so my first
suggestion is a continuation of work already in place -- the "Three Fedoras"
idea we launched at and after Flock in Charleston a year and a half ago,
which we have in early form in the imminent Fedora 21 release.
Specifically, something like:
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? Other user and contributor measures?
-------
This is suggested as a draft — we can work out the details. It also can
serve as a template for future objective proposals.
What do you think?
--
Matthew Miller
<mattdm(a)fedoraproject.org>
Fedora Project Leader
9 years, 3 months