include::ROOT:partial$attributes.adoc[]

= How to run the Fedora Annual Contributor Survey 

[[schedule]]
== Survey Schedule

* **Apr 1st**:
  Open link:{team_issue_tracker}/new_issue[{team_name} ticket] to track progress and collect feedback
* **Apr 1st**:
  Open https://pagure.io/fedora-badges/new_issue[Badges ticket] to request badge design & publication
* **April 1st**:
  Open https://pagure.io/design/new_issue[Design ticket] to request banner design
* **May 1st**:
  Open https://docs.fedoraproject.org/en-US/websites/[Websites and Apps Team ticket] to request banner published on Fedora sites
* **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 xref:fca.adoc[FCA] is necessary at this step.
* **June 1st**:
  Publish link:{COMMBLOG}[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 link:{COMMBLOG}/writing-community-blog-article/[Community Blog].
  Post with results, analysis, and overview of presence at Flock/Nest.

[[promotion]]
== Promotion

[[promotion-badges]]
=== Fedora Badges

Each year we generate a https://badges.fedoraproject.org/[Fedora Badge] that survey recipients can claim when they submit their survey responses.
A ticket needs to be opened on the https://pagure.io/fedora-badges/issues[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.

[[promotion-badges-past]]
==== Past Badges

* 2021
** https://badges.fedoraproject.org/badge/community-survey-taker-i[Badge]
** https://pagure.io/fedora-badges/issue/800[Ticket]

[[promotion--community-blog]]
=== 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 link:{COMMBLOG}[CommBlog], make sure to follow link:{COMMBLOG}/writing-community-blog-article/[the guidelines].
The promotional blog post should then be pinned on Discussion.fpo for the month the survey is open.

* 2021
** link:{COMMBLOG}/help-make-fedora-awesome-by-taking-the-first-annual-contributor-survey/[Survey Promotion]
** link:{COMMBLOG}/fedora-contributor-annual-survey-data-set-available/[Dataset]

[[promotion--websites-banner]]
=== 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 link:{FWIKI}/Design[Design Team] and the xref:websites::index.adoc[Websites & Apps Team].

The first step is to open a ticket on the https://pagure.io/design/issues[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 on the https://pagure.io/fedora-websites/issues[Websites & Apps Team] repo 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:

* https://lists.fedorahosted.org/archives/list/hyperkitty-devel@lists.fedorahosted.org/[Hyperkitty]
* https://docs.fedoraproject.org/en-US/docs/[Docs.fpo]
* https://accounts.fedoraproject.org/[Accounts.fpo]
* link:{FWIKI}/Fedora_Project_Wiki[Fedora Wiki]
* https://start.fedoraproject.org/[Start.fpo]

[[promotion--mailing-lists]]
=== 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.

* https://lists.fedoraproject.org/admin/lists/mindshare@lists.fedoraproject.org/[Mindshare]
* https://lists.fedoraproject.org/admin/lists/devel-announce.lists.fedoraproject.org/[Devel-announce]
* https://lists.fedoraproject.org/admin/lists/diversity.lists.fedoraproject.org/[DEI] 

[[promotion--irc-twitter]]
=== 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

[[changes]]
== Storage and process to make changes

* Take markdown file in {team_name} 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
* Take the lss-file of the previous survey
* Upload lss-file to LimeSurvey under you personal account
* Add all changes from the Markdown file as accumulated over the year using Lime Survey interface
* Export lss-file and submit it as an update to this repository
* Share the update lss-file with LimeSurvey Wrangler so that new Survey is created under Fedora account.
