PR#134: Add survey to Fedora Council docs - Fedora-Council/council-docs

Fedora-Council / council-docs

#134 Add survey to Fedora Council docs

Merged 2 years ago by bookwar. Opened 2 years ago by bookwar.

survey into main

Aleksandra Fedorova • 2 years ago

58dc79e

file modified

		`@@ -16,4 +16,8 @@`
		`** xref:procedures/welcome.adoc[Welcome to Council]`
		`** xref:procedures/team_directory.adoc[Team Directory]`
		`** xref:procedures/tickets.adoc[Ticket Queue]`
		`+ ** Fedora Annual Survey`
		`+ *** xref:procedures/survey/overview.adoc[Survey Overview]`
		`+ *** xref:procedures/survey/how-to.adoc[How to run a Survey]`
		`+ *** xref:procedures/survey/questions.adoc[Survey Questions]`
		`* xref:history.adoc[Council and Board Historical Membership]`

council/modules/ROOT/pages/procedures/survey/how-to.adoc

file added

+106

		`@@ -0,0 +1,106 @@`
		`+ ## 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`
		`+ ** https://communityblog.fedoraproject.org/help-make-fedora-awesome-by-taking-the-first-annual-contributor-survey/[Survey Promotion]`
		`+ ** https://communityblog.fedoraproject.org/fedora-contributor-annual-survey-data-set-available/[Dataset]`
		`+`
		`+ #### 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`
		`+`
		`+ * Take 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`
		`+ * 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.`
		`+`

council/modules/ROOT/pages/procedures/survey/overview.adoc

file added

+45

		`@@ -0,0 +1,45 @@`
		`+ ## 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 https://discussion.fedoraproject.org/tag/council[Discussion site] and use the tag #council`
		`+`
		`+ ### Past Survey CSVs`
		`+`
		`+ - https://fedoraproject.org/wiki/Fedora_Annual_Contributor_Survey_2021[Contributor Survey 2021 Responses CSV]`

council/modules/ROOT/pages/procedures/survey/questions.adoc

file added

+372

		`@@ -0,0 +1,372 @@`
		`+ # Fedora Contributor Annual Survey`
		`+`
		`+ ## Intro`
		`+`
		`+ Hello and thank you for taking the Fedora Annual Contributor Survey!`
		`+ We hope to use the data from this survey to understand the usage,`
		`+ engagement, and development patterns to further enrich our`
		`+ community. We will be sharing our findings at Nest <Year>.`
		`+`
		`+ This survey is targeted to Fedora Contributors and Community`
		`+ Members. Fedora contributors and community members are those that`
		`+ participate in the project in any way, be it coding, bug testing,`
		`+ docs, graphic design, translations, outreach, etc.`
		`+`
		`+ This survey is being ran by the Fedora Council to better understand`
		`+ our Fedora Contributors and Community Members, and to better steward`
		`+ the Fedora Project based on data.`
		`+`
		`+ Who gets to see the raw data::`
		`+ Fedora Council members and survey moderator (vsiddhar@redhat.com)`
		`+`
		`+ Who gets to see the summary data::`
		`+ Public`
		`+`
		`+ How to contact someone about issues with the survey::`
		`+ Send an email to vsiddhar@redhat.com`
		`+`
		`+ Survey open and close dates::`
		`+ June 1st - 30th`
		`+`
		`+ Don't forget to claim your Survey Taker badge after you click "Submit"!`
		`+`
		`+ ### Notes`
		`+`
		`+ - Alphabetize answers, leaving "Other" and "I don't know" at the end.`
		`+ - [M] for multi-choice and [S] for single choice questions`
		`+ - For questions with "Other" answer, we would like to have a text field where one can write their own answer.`
		`+`
		`+ ## Questions`
		`+`
		`+ ### About you`
		`+`
		`+ * What are your current role(s) in Fedora Project? [M]`
		`+ - Design`
		`+ - Diversity & Inclusion`
		`+ - Documentation`
		`+ - Infrastructure`
		`+ - Localization`
		`+ - Outreach (Ambassadors, Join, Advocates)`
		`+ - Package Maintainer`
		`+ - Quality Assurance`
		`+ - Support`
		`+ - User`
		`+ - Other`
		`+`
		`+ * What do you use Fedora for? [M]`
		`+ - Data analysis`
		`+ - Development`
		`+ - Gaming`
		`+ - Generic desktop`
		`+ - Graphics/photo/video/design`
		`+ - Office tasks`
		`+ - Operations`
		`+ - Other`
		`+`
		`+ * On a scale of 1-5 how familiar are you with Linux-based operating systems? [S]`
		`+ - Rate from 1(new to Linux) to 5(power user)`
		`+`
		`+ * Which social networks do you regularly use? [M]`
		`+ - Diaspora`
		`+ - Facebook`
		`+ - I don't use social networks`
		`+ - LinkedIn`
		`+ - Mastodon (and ActivityPub compatible apps)`
		`+ - Twitter`
		`+ - Other`
		`+`
		`+ * Which messaging services do you regularly use? [M]`
		`+ - IRC`
		`+ - Matrix/Element`
		`+ - Telegram`
		`+ - WhatsApp`
		`+ - Discord`
		`+ - Signal`
		`+ - Jabber`
		`+ - I don't use messaging`
		`+ - Other`
		`+`
		`+ * Which Fedora communication channels do you follow? [M]`
		`+ - ask.fedoraproject.org`
		`+ - discussions.fedoraproject.org`
		`+ - Fedora Community Blog`
		`+ - Fedora Magazine`
		`+ - Fedora News on Telegram`
		`+ - Fedora Planet`
		`+ - Fedora on Facebook`
		`+ - Fedora/mattdm's Twitter accounts`
		`+ - Fedora-announce mailing list`
		`+ - r/fedora on Reddit`
		`+ - I don't follow Fedora news`
		`+ - Other`
		`+`
		`+ * How comfortable do you feel speaking up about your ideas/opinions/theories or asking questions in Fedora spaces?(chat platforms, pagure, discussion)`
		`+ - Completely comfortable`
		`+ - Neutral`
		`+ - Somewhat comfortable`
		`+ - Uncomfortable`
		`+ - Varies depending on space`
		`+ - Other`
		`+`
		`+ * Is English your first language? If not, do you find language as a barrier for participation in Fedora?`
		`+ - Yes`
		`+ - No + field for freeform response`
		`+`
		`+ ### Generic`
		`+`
		`+ * Which Fedora Editions do you use? [M]`
		`+ - CoreOS`
		`+ - IoT`
		`+ - Labs`
		`+ - Server`
		`+ - Silverblue`
		`+ - Spins`
		`+ - Workstation`
		`+ - Other`
		`+`
		`+ * Which architectures do you use? [M]`
		`+ - aarch64`
		`+ - arm`
		`+ - ppc64`
		`+ - s390x`
		`+ - x86_64`
		`+ - Don't know`
		`+`
		`+ * Do you use Fedora Modules? [S]`
		`+ - Yes`
		`+ - I tried, but then disabled them`
		`+ - I have never tried`
		`+ - Don't know`
		`+`
		`+ * Would you recommend Fedora Modules? Yes or no, and why?`
		`+ - Yes (comes with field)`
		`+ - No (comes with field)`
		`+`
		`+ * Have you tried to use Fedora Silverblue? [S]`
		`+ - Yes, and I still use it.`
		`+ - Yes, and I use it rarely.`
		`+ - I tried it, but then switched back to RPM-based system`
		`+ - I have never tried using it`
		`+`
		`+ * Do you develop on single board computers for Fedora? If yes, which ones?`
		`+ - Freeform field`
		`+`
		`+ ### Desktop`
		`+`
		`+ Opening question: Do you use Fedora as desktop. If not we skip the section.`
		`+`
		`+ * What is your preferred desktop environment? [S]`
		`+ - Cinnamon`
		`+ - Gnome`
		`+ - KDE`
		`+ - LXQT`
		`+ - Mate`
		`+ - XFCE`
		`+ - i3wm`
		`+ - Other`
		`+`
		`+ * Do you use Flatpaks? [S]`
		`+ - Yes, regularly`
		`+ - Occasionally`
		`+ - I tried, but then removed them`
		`+ - I have never tried`
		`+ - Don't know`
		`+`
		`+ * Would you recommend Flatpaks? Yes or no, and why?`
		`+ - Yes (comes with field)`
		`+ - No (comes with field)`
		`+`
		`+ * What is your preferred office suite? [S]`
		`+ - LibreOffice`
		`+ - Web-based`
		`+ - I don't use office tools`
		`+ - Other`
		`+`
		`+ * What is your preferred browser? [S]`
		`+ - Chrome`
		`+ - Chromium`
		`+ - Firefox`
		`+ - Gnome Web`
		`+ - I don't use browsers`
		`+ - Other`
		`+`
		`+ * What is your preferred e-mail client? [S]`
		`+ - Evolution`
		`+ - MailSpring`
		`+ - Thunderbird`
		`+ - emacs`
		`+ - mutt`
		`+ - web-based`
		`+ - I don't use e-mail clients`
		`+ - Other`
		`+`
		`+ * What is your preferred media player? [S]`
		`+ - Celluloid`
		`+ - Clementine`
		`+ - Lollypop`
		`+ - Rhythmbox`
		`+ - SMPlayer`
		`+ - Totem`
		`+ - VLC`
		`+ - mplayer`
		`+ - mpv`
		`+ - I don't use media players`
		`+ - Other`
		`+`
		`+ * What is your preferred image viewer? [S]`
		`+ - DigiKam`
		`+ - Eye of gnome`
		`+ - GThumb`
		`+ - Gwenview`
		`+ - Shotwell`
		`+ - I don't use image viewers`
		`+ - Other`
		`+`
		`+ * What is your preferred drawing tool? [S]`
		`+ - GIMP`
		`+ - Inkscape`
		`+ - Krita`
		`+ - MyPaint`
		`+ - I don't use drawing tools`
		`+ - Other`
		`+`
		`+ * How do you play Games? [M]`
		`+ - GOG`
		`+ - Lutris`
		`+ - Native`
		`+ - Steam`
		`+ - Wine`
		`+ - Dual-boot into Windows`
		`+ - I don't play games`
		`+ - Other`
		`+`
		`+ * How satisfied you are with Fedora on Desktop experience?`
		`+ * Rate from 1 to 5`
		`+`
		`+ ### Code`
		`+`
		`+ Opening question: do you use Fedora to write code?`
		`+`
		`+ * What programming languages do you use? [M]`
		`+ - C`
		`+ - C++`
		`+ - Go`
		`+ - Java`
		`+ - JavaScript`
		`+ - Lua`
		`+ - Perl`
		`+ - Python`
		`+ - Rust`
		`+ - Other`
		`+`
		`+ * What version control systems are you working with? [M]`
		`+ - Bazaar (bzr)`
		`+ - CVS`
		`+ - Git`
		`+ - Mercurial (hg)`
		`+ - Subversion (svn)`
		`+ - I don't use version control systems`
		`+ - Other`
		`+`
		`+ * What forge system are you interacting with? [M]`
		`+ - Bitbucket`
		`+ - Gerrit`
		`+ - GitHub`
		`+ - GitLab`
		`+ - Gitea`
		`+ - Pagure`
		`+ - Sourcehut`
		`+ - I don't use forge systems`
		`+ - Other`
		`+`
		`+ * Which text editor do you use (for random small edits)? [S]`
		`+ - Atom`
		`+ - Kate`
		`+ - SublimeText`
		`+ - VS Code`
		`+ - emacs`
		`+ - gedit`
		`+ - nano`
		`+ - vim`
		`+ - Other`
		`+`
		`+ * Which is your primary development environment? [M]`
		`+ - Any JetBrains product`
		`+ - Eclipse`
		`+ - NetBeans`
		`+ - Qt Creator`
		`+ - VS Code`
		`+ - emacs`
		`+ - vim`
		`+ - I don't have one`
		`+ - Other`
		`+`
		`+ * Which container tools do you use?`
		`+ - Docker`
		`+ - lxc`
		`+ - podman`
		`+ - systemd-nspawn`
		`+ - I don't use container tools`
		`+ - Other`
		`+`
		`+ * How satisfied you are with Fedora as a developer workstation?`
		`+ * Rate from 1(not satisfied) to 5 (completely satisfied)`
		`+`
		`+`
		`+ ### Community Outreach`
		`+`
		`+`
		`+ * What demographic(s) are you connected with locally?`
		`+ - Hobbiest`
		`+ - Open Source Communities`
		`+ - Professional`
		`+ - Tech Communities`
		`+ - University/College/Grade School`
		`+ - Other`
		`+`
		`+ * What kind of participation have you had in the Fedora's outreach in the past/currently?`
		`+ - Attendance/representation at events`
		`+ - Coordinating/organizing events`
		`+ - Demos/Workshops`
		`+ - Outreach at schools/universities`
		`+ - Outreach in professional networks`
		`+ - Other`
		`+`
		`+ * How familiar are you on how Fedora is organized as a project?`
		`+ * Rating 1-5`
		`+`
		`+ * How accessible do you find Fedora resources to be? (such as docs, wiki pages, pagure repo, IRC/chatroom)`
		`+ * Rating 1 (not accessible) - 5 (easily accessible)`
		`+`
		`+ * Who would you first try to contact if you wanted to run a Fedora event/needed swag?`
		`+ - FCAIC`
		`+ - Fedora Council`
		`+ - Local User Group`
		`+ - Mindshare Committee`
		`+ - Regional Fedora Ambassador group`
		`+ - Other`
		`+`
		`+ * Are you aware that Fedora provides concrete resources to further Fedora's vision and initiatives? (event sponsorships, travel assistance, swag for local projects/events)`
		`+ - Yes, and I have taken advantage of those resources`
		`+ - Yes, but the process did not go well for me`
		`+ - Yes, but I am not sure how to request resources`
		`+ - No, I was previously unaware`
		`+ - Other`
		`+`
		`+ * How satisfied are you with community outreach within and outside of the Fedora Project?`
		`+ * Rate from 1(not satisfied) to 5 (completely satisfied)`
		`+`
		`+ ### Close-up`
		`+`
		`+ * How satisfied are you with the Fedora Project overall?`
		`+ * Rate from 1(not satisfied) to 5 (completely satisfied)`
		`+`
		`+ * How likely are you to recommend contributing to Fedora to a friend?`
		`+ * Rate 1(unlikely) to 5 (very likely)`
		`+`
		`+ * Is there anything else you would like to share with the Fedora Project?`
		`+ * Open field`
		`+`
		`+ ### Thank you note`
		`+`
		`+ Link to the badge.`
		`\ No newline at end of file`

bookwar commented 2 years ago

Since the survey is the annual event, we should store the data which
helps us to run it next time.

This commit adds the first original version of the survey questions as
they were run in 2021. It will be updated later using the lessons
learned from parsing the first round of answers.

bcotton commented 2 years ago

As a minor note, I'd put this under the "Procedures" in the navigation instead of as its own category.

More substantially, when I saw "data", I assumed it would be a link to the results data, not the input. So we might want to make that clear (and add links to data for each year?)

I wonder if storing the LimeSurvey XML might be a better choice than a rendered AsciiDoc file that will have to be copy-pasted instead of importing and making small edits in the LimeSurvey UI. In either case, does this need to be in the rendered docs, or would checking a markdown file into a repo (that doesn't get published to docs) make more sense?

siddharthvipul1 commented 2 years ago

So there are 2 things here
1. Community members should be able to see existing questions (to request change/addition/deletion)
2. For limesurvey "wrangler" to upload those questions in the system

for 1, we definitely need a markdown/html/asciidoc - XML is not really easy to navigate
but we also don't want PRs to land just into readable formats! It will be very tedious to keep both of them sync if we are thinking of updating things at the end - we might miss some small change

I think having both is a better idea. When someone wants to propose a change or addition/removal, they can open a ticket, or post a discussion thread. Once agreed, we can open a PR with both markdown and LSS file change at the same time.

siddharthvipul1 commented 2 years ago

In either case, does this need to be in the rendered docs, or would checking a markdown file into a repo (that doesn't get published to docs) make more sense?

I am in favor of it NOT being in rendered doc (but a link in doc somewhere to the file)

bcotton commented 2 years ago

for 1, we definitely need a markdown/html/asciidoc - XML is not really easy to navigate
but we also don't want PRs to land just into readable formats! It will be very tedious to keep both of them sync if we are thinking of updating things at the end - we might miss some small change

I think having both is a better idea. When someone wants to propose a change or addition/removal, they can open a ticket, or post a discussion thread. Once agreed, we can open a PR with both markdown and LSS file change at the same time.

That sounds unpleasant. It requires the person making the PR to make the same change twice, including in a system they may not have used (the LimeSurvey UI was not easy to navigate when I created the XML for you to use in the Retrospective).

If we're going to keep the questions in a repo, somewhere (which I think is a reasonable thing to do), let's just go with a markdown/whatever version and not also keep the XML. Or say "if you want to suggest an edit, use your own LimeSurvey account to generate an updated XML file".
The latter choice is user-hostile, but I leave it in for completeness.

siddharthvipul1 commented 2 years ago

That sounds unpleasant. It requires the person making the PR to make the same change twice, including in a system they may not have used (the LimeSurvey UI was not easy to navigate when I created the XML for you to use in the Retrospective).

I was thinking of someone who knows and already uses limesurvey to make the PR (like you and me) but I understand it's a task taking upon ourselves..
Maybe have a change note somewhere that can be followed?
My thought process is coming from "if I have to create a new survey for next year": how easy for me is to check the delta. If it's going through the whole of markdown and comparing the not just questions but options, it would be a little awkward (in limesurvey you can just copy the survey to create a new one).
but it also doesn't feel right to say "you should have a limesurvey account where you can import questions to see, and then make changes, export and open a PR" - of course review would also be similarly complex.

In favor of welcoming more suggestions, I think we should go with markdown if we don't want both

rebased onto 39b53aa0b908d15a1495af65c8a0f46a5867ca23

2 years ago

rebased onto 58dc79e

2 years ago

bookwar commented 2 years ago

As we discusses with @riecatnor and @siddharthvipul1 the original sources of the LimeSurvey LSS are not suitable for direct editing.

Thus the optimal update process for Survey is:
collect changes in the markdown file over a year
before running teh survey upload the old version of the survey to LimeSurvey interface, update it according to the changes in the Markdown file, then save the updated file as a snapshot and keep for the next year.

Thus I updated the pull-request with markdown file which contains questiosn, and also added the content for two pages: overview and how-to with content added by @riecatnor

Those pages can be adjusted and polished further, but I'd rather merge the request now, and update it later, so that we have initial information in place.

Pull-Request has been merged by bookwar

2 years ago