Re: [council] #1: Periodic user/contributor survey
by fedora-badges
#1: Periodic user/contributor survey
---------------------+-----------------------
Reporter: mattdm | Owner: somebody
Status: new | Priority: major
Component: General | Resolution:
Keywords: |
---------------------+-----------------------
Changes (by mattdm):
* component: component1 => General
Old description:
> We have little consistent data on our user and contributor base. It would
> be nice to have more.
>
> There have been several discussions of an annual user survey in the past,
> but for various reasons they haven't gone very far.
>
> From a board level, this ticket isn't necessarily about the details of
> doing the survey, but about finding the right interested people and
> enabling them (and supporting their efforts as necessary so the survey
> can happen consistently and regularly).
New description:
We have little consistent data on our user and contributor base. It would
be nice to have more.
There have been several discussions of an annual user survey in the past,
but for various reasons they haven't gone very far.
From a board level, this ticket isn't necessarily about the details of
doing the survey, but about finding the right interested people and
enabling them (and supporting their efforts as necessary so the survey can
happen consistently and regularly).
----
This is a companion to https://fedorahosted.org/council/ticket/16. The
desired goals, methodology, and basically everything else are really
different between users and contributors it will be better to track them
separately.
--
Comment:
Sounds good. Let's focus this one on users, and I've created
https://fedorahosted.org/council/ticket/16 as well.
--
Ticket URL: <https://fedorahosted.org/council/ticket/1#comment:15>
council <https://fedorahosted.org/council>
Fedora Project Board Public Tickets
9 years, 4 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):
If we want to survey contributors, what is the point? What questions do we
want to answer? What problems do we want to solve?
I think something contributor-focused is a very different beast than user
focused and we should probably have two tickets if we want to investigate
both.
--
Ticket URL: <https://fedorahosted.org/council/ticket/1#comment:13>
council <https://fedorahosted.org/council>
Fedora Project Board Public Tickets
9 years, 4 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:11 mattdm]:
What kind of people? Are these potentially not Fedora users? How will we
know?
The biggest problem with surveys, and by extension statistics, is being
able to say after what the information *actually* means. When we were
originally discussing this we knew that the we couldn't say that we
surveyed all Fedora contributors because we were actually surveying
everyone with a FAS account. There's a big difference there.
No matter how we do it we'll always have a certain amount of uncertainty
in the results. You'll always get people who aren't, or are no longer, a
user/contributor but are just bored or vindictive. The hope is that
you'll overshadow those people with people that you actually want to hear
from.
The plan was to use an instance of LimeSurvey I had running at one point
and sending out individualized invitations to all FAS account holders.
Each person would receive a unique URL that would prevent the person from
completing the survey multiple times. We could also track the percentage
of FAS account holders that completed the survey so we'd know if we had
statistically viable numbers.
I still have, somewhere, the questions we were to ask in the language that
the survey specialist said would be best (non-leading, complete, etc).
--
Ticket URL: <https://fedorahosted.org/council/ticket/1#comment:12>
council <https://fedorahosted.org/council>
Fedora Project Board Public Tickets
9 years, 4 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 mattdm):
We can ask people if they want to sign up to be included in periodic user
surveys, and then every six months or whatever select a randomized subset
of those. It's not perfect, but much better than an open internet poll.
--
Ticket URL: <https://fedorahosted.org/council/ticket/1#comment:11>
council <https://fedorahosted.org/council>
Fedora Project Board Public Tickets
9 years, 4 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:9 mattdm]:
> Replying to [comment:8 yn1v]:
> > I am unsure how this will reach in a meaningful way those users that
are not collaborators.
>
> Without spending (possibly considerable) money, it's going to be self-
selected. But we can do a number of things, including putting the survey
on start.fpo, or even including it as a link we ship as a webapp in the
desktop variants of the distro, as well as having ambassadors publicize
it. And we have a fairly good social media reach.
The only way to obtain useful results is to have an inclusive group.
Generally throwing a survey out to the Internet will not result in useful
results.
--
Ticket URL: <https://fedorahosted.org/council/ticket/1#comment:10>
council <https://fedorahosted.org/council>
Fedora Project Board Public Tickets
9 years, 4 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 mattdm):
Replying to [comment:8 yn1v]:
> I am unsure how this will reach in a meaningful way those users that are
not collaborators.
Without spending (possibly considerable) money, it's going to be self-
selected. But we can do a number of things, including putting the survey
on start.fpo, or even including it as a link we ship as a webapp in the
desktop variants of the distro, as well as having ambassadors publicize
it. And we have a fairly good social media reach.
--
Ticket URL: <https://fedorahosted.org/council/ticket/1#comment:9>
council <https://fedorahosted.org/council>
Fedora Project Board Public Tickets
9 years, 4 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 yn1v):
I am unsure how this will reach in a meaningful way those users that are
not collaborators. Anyway, I think that if we measure how we are doing to
serve our own people will help us. Bad response means that we are likely
to lose some contributors. Good responses may be not as useful as this is
a health metric. If we are serving well our own people, they will be worry
about other stuff.
--
Ticket URL: <https://fedorahosted.org/council/ticket/1#comment:8>
council <https://fedorahosted.org/council>
Fedora Project Board Public Tickets
9 years, 4 months
RE: Fedora 12-month objective proposal: Fedora Flavors Phase 2
by Máirín Duffy
usability tesing! that should definitely be one of the measures.
Sent from my phone, which is not an iphone.
<div>-------- Original message --------</div><div>From: Matthew Miller <mattdm(a)fedoraproject.org> </div><div>Date:12/03/2014 11:32 AM (GMT-05:00) </div><div>To: Discussions with the Fedora Council and community <council-discuss(a)lists.fedoraproject.org> </div><div>Subject: Fedora 12-month objective proposal: Fedora Flavors Phase 2 </div><div>
</div>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
_______________________________________________
council-discuss mailing list
council-discuss(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/council-discuss
9 years, 4 months