From 9132f648120d6df8c1aba26d1be75506ac74c05e Mon Sep 17 00:00:00 2001 From: Marie Nordin Date: Mar 10 2022 14:31:34 +0000 Subject: Adding links --- diff --git a/council/modules/ROOT/pages/procedures/survey/how-to.adoc b/council/modules/ROOT/pages/procedures/survey/how-to.adoc index f71f4be..069e7e4 100644 --- a/council/modules/ROOT/pages/procedures/survey/how-to.adoc +++ b/council/modules/ROOT/pages/procedures/survey/how-to.adoc @@ -2,27 +2,27 @@ ### 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 +* **Apr 1st** Open https://pagure.io/Fedora-Council/tickets/new_issue[Council 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 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 +* **May 24-31st** Review of actual survey in LimeSurvey. Approval from https://docs.fedoraproject.org/en-US/council/fcaic/[FCAIC] is necessary at this step. +* **June 1st** Publish https://communityblog.fedoraproject.org/[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. +* **By end of August** Publish https://communityblog.fedoraproject.org/writing-community-blog-article/[Community Blog] Post with results, analysis, and overview of presence at Flock/Nest. ### Promotion #### Fedora Badges -Each year we generate a Fedora Badge that survey recipients can claim +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 Badges repo requesting the badge. The panda graphic stays the +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 @@ -30,15 +30,15 @@ claim link to the Survey team. ##### Past Badges * 2021 -** Badge -** Ticket +** https://badges.fedoraproject.org/badge/community-survey-taker-i[Badge] +** https://pagure.io/fedora-badges/issue/800[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 +https://communityblog.fedoraproject.org/[CommBlog], make sure to follow https://communityblog.fedoraproject.org/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 @@ -49,22 +49,22 @@ Discussion.fpo for the month the survey is open. 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. +our websites. This work is done with the assistance of the https://fedoraproject.org/wiki/Design[Design Team] +and the https://docs.fedoraproject.org/en-US/websites/[Websites and Apps Team]. -The first step is to open a ticket on the Design Team pagure to get +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 with the Websites & Apps Team to get it +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: -* Hyperkitty -* Docs.fpo -* Accounts.fpo -* Fedora Wiki -* Start.fpo +* 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] +* https://fedoraproject.org/wiki/Fedora_Project_Wiki[Fedora Wiki] +* https://start.fedoraproject.org/[Start.fpo] #### Mailing Lists @@ -73,10 +73,9 @@ 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 +* 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] #### IRC & Twitter