---
# System prepended metadata

title: Annual Contributor Survey Docs

---

# Annual Contributor Survey Docs

## Overview

### Goals
In 2021 the Council ran the first Annual Contributor Survey. We intend to improve and iterate year over year to help achieve the following goals:

- To gain an understanding of the usage patterns in various Fedora flavours and tooling
- To analyze trends based on particular tools, preferred media platforms, or role
- To understand the correlation between satisfaction of respondents and involvement in Fedora
- To analyze the accessibility of documentation, engagement, and resources
- To gain insight on awareness and visibility of teams and activities happening across Fedora

### Audience
The audience for this survey is Fedora contributors. This is inclusive of every Fedora contributor, whatever the scope of interest or activity. 

### What are we doing with the results?
- Publish open, anonymous datasets for contributors to analyze.
- Review and analysis by the Fedora Council. 
- Review and analysis by the Mindshare Committee.

## Survey Implementation Schedule

### Survey 
- (**April 1st**) Open Council ticket to track progress and collect feedback
- (**April 1st**) Open Fedora Badge ticket 
- (**May 15-24th**) Changes submitted through the year to the hackmd implemented in LimeSurvey
- (**May 24-31st**) Review of actual in LimeSurvey. Approval from FCAIC is necessary at this step. 
- (**June 1st-30th**) Survey runs
- (**July 1st-31st**) First round of survey analysis
- (**First weekend in August**) Flock to Fedora/Nest with Fedora presentation

### Promotion

#### Fedora Badges
Each year we generate a Fedora Badge that survey recipients can claim when they submit their survey responses. A ticket needs to be opened on the Badges repo requesting the badge. The panda graphic stays the same, and the year is updated accordingly. **This ticket should be opened by April 1st** in order to give the Badges team enough time to generate the artwork, push the badge to the website, and provide a claim link to the Survey team. 

##### Past Badges
- 2021
    - Badge
    - Ticket

#### Community Blog Post
Each year we need to write at least two blog posts for the survey. The first one is to promote taking the survey, the second features the released dataset and any findings. These are published on the CommBlog. The promotional blog post should then be pinned on Discussion.fpo for the month the survey is open.
- 2021
    - [Survey Promotion](https://communityblog.fedoraproject.org/help-make-fedora-awesome-by-taking-the-first-annual-contributor-survey/)
    - [Dataset](https://communityblog.fedoraproject.org/fedora-contributor-annual-survey-data-set-available/)


#### Fedora Websites Banner
To help ensure we reach the maximum number of Fedora contributors, we promote the survey across as many Fedora spaces as possible including our websites. This work is done with the assistance of the Design Team and the Websites and Apps Team. 

The first step is to open a ticket on the Design Team pagure to get any updates on artwork. **This ticket should be opened by April 1st, and closed by May 1st.** If there are no changes from the Design Team, proceed with the previous design. Once the artwork is finalized, a ticket is opened with the Websites & Apps Team to get it published. **This ticket should be opened by May 1st** and needs continuous check-ins. The websites that we aim to cover are:
- Hyperkitty
- Docs.fpo
- Accounts.fpo
- Fedora Wiki
- Start.fpo

#### Mailing Lists
A lot of folks are on multiple mailing lists so it is important to choose high level "announce" channels over team channels. A short email should be sent with a link to the Community Blog post as well as a link directly to the survey. 
- Council
- Mindshare
- Devel-announce
- DEI 

#### IRC & Twitter
For increased visibility we also promote the survey on IRC and Twitter. This should be done sparingly as their is a potential for it to feel spammy. It could potentially go to other social media platforms but the main audience for that platform should be contributors not users. Don't forget to remind people they can earn a badge!
- IRC & Twitter
    - (June 1st) Announce survey is open for month of June
    - (June 15th) Two week reminder to fill out survey
    - (June 30th) One day reminder to fill out survey

### Continuous Activities
- Survey analysis
- Edits/changes/additions requests to survey 

## Storage and process to make changes
- Storage of lss file in Council repo
- Markdown file in Council repo
    - PR's reviewed and accepted to markdown file through out the year
    - git diff to locate the differences and make changes directly in the LimeSurvey UI two weeks prior to running survey

## Who has access to the LimeSurvey account? 
The Fedora Action and Impact Coordinator and the LimeSurvey Wrangler, currently Vipul Siddharth. Access to this account is limited due to data sensitivity. 

## Past Survey CSVs
- Contributor Survey 2021 Responses CSV





--------------------------------------------

Overview


## Fedora Annual Contributor Survey Overview

### Goals

In 2021 the Council ran the first Fedora Annual Contributor Survey. We intend to improve and iterate year over year to help achieve the following goals:

- To gain an understanding of the usage patterns in various Fedora flavours and tooling
- To analyze trends based on particular tools, preferred media platforms, or role
- To understand the correlation between satisfaction of respondents and involvement in Fedora
- To analyze the accessibility of documentation, engagement, and resources
- To gain insight on awareness and visibility of teams and activities happening across Fedora

### Audience

The audience for this survey is Fedora contributors. This is inclusive of every Fedora contributor, whatever the scope of interest or activity. 

### What are we doing with the results?

- Publish open, anonymous datasets for contributors to analyze.
- Review and analysis by the Survey team. 
- Review and analysis by the Fedora Council. 
- Review and analysis by the Mindshare Committee.

### Survey maintenance

Maintenance for a survey includes continuous activities, which can be performed anytime through the entire year.

- Analysis of the data
- Edits/changes/additions requests to the content of the survey 

### Who has access to the LimeSurvey account? 

The Fedora Action and Impact Coordinator and the LimeSurvey Wrangler,
currently Vipul Siddharth. Access to this account is limited due to
data sensitivity.

### How do I get involved?

- Suggest new questions or edits to current questions with a Fedora Council ticket.
- Analyze data and publish results to the Community Blog and make sure to let the Council know.
- Provide feedback and share ideas about the survey with the Fedora Council via Discussion.fedoraproject.org and use the tag #council https://discussion.fedoraproject.org/tag/council


### Past Survey CSVs

- Contributor Survey 2021 Responses CSV



## How to run the Fedora Annual Contributor Survey

### Survey Schedule

- **Apr 1st** Open Council ticket to track progress and collect feedback
- **Apr 1st** Open Badges ticket to request badge design & publication
- **April 1st** Open Design Team ticket to request banner design
- **May 15-24th** Update LimeSurvey data according to the changes in the Survey Questions accumulated over the last year.
- **May 24-31st** Review of actual survey in LimeSurvey. Approval from FCAIC is necessary at this step. 
- **June 1st** Publish Community Blog Post promoting survey
- **June 1st-30th** Survey runs
  - **June 1st** Announce survey is open for month of June on IRC and Twitter
  - **June 15th** Two week reminder to fill out survey on IRC and Twitter
  - **June 30th** One day reminder to fill out survey on IRC and Twitter
- **July 1st-31st** First round of survey analysis
- **First weekend in August** Flock to Fedora/Nest with Fedora presentation
- **By end of August** Publish Community Blog Post results, analysis, and overview of presence at Flock/Nest. 

### Promotion

#### Fedora Badges

Each year we generate a Fedora Badge that survey recipients can claim
when they submit their survey responses. A ticket needs to be opened
on the Badges repo requesting the badge. The panda graphic stays the
same, and the year is updated accordingly. **This ticket should be
opened by April 1st** in order to give the Badges team enough time to
generate the artwork, push the badge to the website, and provide a
claim link to the Survey team.

##### Past Badges
- 2021
    - Badge
    - Ticket

#### Community Blog Post

Each year we need to write at least two blog posts for the survey. The
first one is to promote taking the survey, the second features the
released dataset and any findings. These are published on the
CommBlog. The promotional blog post should then be pinned on
Discussion.fpo for the month the survey is open.

- 2021
    - [Survey Promotion](https://communityblog.fedoraproject.org/help-make-fedora-awesome-by-taking-the-first-annual-contributor-survey/)
    - [Dataset](https://communityblog.fedoraproject.org/fedora-contributor-annual-survey-data-set-available/)


#### Fedora Websites Banner

To help ensure we reach the maximum number of Fedora contributors, we
promote the survey across as many Fedora spaces as possible including
our websites. This work is done with the assistance of the Design Team
and the Websites and Apps Team.

The first step is to open a ticket on the Design Team pagure to get
any updates on artwork. **This ticket should be opened by April 1st,
and closed by May 1st.** If there are no changes from the Design Team,
proceed with the previous design. Once the artwork is finalized, a
ticket is opened with the Websites & Apps Team to get it
published. **This ticket should be opened by May 1st** and needs
continuous check-ins. The websites that we aim to cover are:

- Hyperkitty
- Docs.fpo
- Accounts.fpo
- Fedora Wiki
- Start.fpo

#### Mailing Lists

A lot of folks are on multiple mailing lists so it is important to
choose high level "announce" channels over team channels. A short
email should be sent with a link to the Community Blog post as well as
a link directly to the survey.

- Council
- Mindshare
- Devel-announce
- DEI 

#### IRC & Twitter

For increased visibility we also promote the survey on IRC and
Twitter. This should be done sparingly as their is a potential for it
to feel spammy. It could potentially go to other social media
platforms but the main audience for that platform should be
contributors not users. Don't forget to remind people they can earn a
badge!

- IRC & Twitter
    - (June 1st) Announce survey is open for month of June
    - (June 15th) Two week reminder to fill out survey
    - (June 30th) One day reminder to fill out survey

## Storage and process to make changes

- Storage of lss file in Council repo
- Markdown file in Council repo
    - PR's reviewed and accepted to markdown file through out the year
    - git diff to locate the differences and make changes directly in the
      LimeSurvey UI two weeks prior to running survey

