qsharp-community/roadmap

Q# Community Roadmap for 2021

roadmap's Issues

10 active members answering questions on forums

Summary
As a community, we want to have a more active presence/representation on other forums. This KR would have 10 active (posting/interacting at least once a month) members from Q# Community answering questions on other forums (reddit, SE, etc.)

Intended Outcome
We want to encourage folks who are working on Q# to help each other and see that there is a community they can rely on to help out when they are stuck. Having more engagement from our community outward can help make the community more visible and welcoming.

How will it work?

• Ask current members if they are answering questions on other forums, and if so which sites. Can try and setup some automation promoting regular posters answers.
• We can have a submission process for folks using issues on the main website repo and we can then promote them on social media.

10 new community blog posts

Summary
We want to have 10 new community blog posts to the site in 2021.

Intended Outcome
Authors can make a PR to the qsharp.community website and mods will do light review for topic and content accuracy.

How will it work?
Find those writing Q# content and enquire about mirroring or guest posting.

Create starter Q# content for each platform

Summary
We want to have the "get started" post and video for each operating system/development platform in common use.

Intended Outcome
This should help reduce the same starting questions on forums and accelerate onboarding of developers.

How will it work?
Have creator go through the docs and either record a video as they go through the process or write about their experiences after (with screen shots if possible).

Create Q# FAQ

Summary
Pull together answers to common Q# questions (possibly general QC questions as related to Q#) in one easy place to point to when teaching or learning Q#.

Intended Outcome
There should be a new page on the website (qsharp.community/faq or similar) that has a curated list of questions and answers with good external links.

How will it work?
It would be good to go through forum sites like stack exchange/overflow and reddit to see what folks are asking about Q#. Also reach out to folks who are teaching/writing about Q# to learn from their experiences to see what would be good to have on the list. Once the list is made, it would probably good to run it by some Q# dev folks for correctness :)

Host monthly community calls

Summary
Community calls are an important part of keeping a group informed and engaged on projects.

Intended Outcome
The goal would be to have these calls once a month, with a pre-published agenda and recordings available in post. Live sessions will rotate timezones to make it easier for folks to attend live.

How will it work?
We will need to first pick a platform like Jitsi/Twitch/Discord. A repo somewhere could hold the agenda that folks can add stuff to they want to discuss. A recording/post processing pipeline will be needed for the video recordings as well a YouTube channel setup. We can either have a regular host or have a rotating responsibility.

Collect learning resources and add to website

Summary
Make a definitive list (possibly with personal recs from devs) of resources for learning Q# or QC more generally.

Intended Outcome
The qsharp.community/learn page would be created and populated with content from around the web, prioritizing free/open source options first.

How will it work?
Go through and link awesome lists, social media posts for content. Can have blurbs about why folks recommend certain resources.

5 new active community repos

Summary
More active projects in the community will help show others how they can contribute or inspire what they might be interested in making themselves. This will help us grow the overall Q# community.

Intended Outcome
By the end of 2021, we will have 5 new active community projects in addition to our current projects.

How will it work?
We can solicit researchers or others actively contributing to main Q# repos. We can also develop some blog content that helps show people how to get started, which could also include repo templates.

300 Members

Summary
More folks using Q# means a better language and experience for all of us 💖

Intended Outcome
We want to have 300 folks in the Q# community by the end of 2021.

How will it work?
Currently membership is defined as joining the slack, as of the end of 2020 we have ~150 members.
Social media campaigns and other events like hackathons or participation with other open source quantum events can help us grow.

Create sponsored swag for contributions

Summary
Everyone like to represent the tech that they work on, we want to enable folks that work on Q# stuff to show it off!

Intended Outcome
We want to have a merch store that people can order from on-demand, as well as getting some sponsored stock of stickers and maybe socks that we can send out to contributors.

How will it work?
We will need to first design the stickers/swag and identify an appropriate storefront tech/site. Then soliciting some funding to pay for some amount of stock of stickers and socks as well as funds for mailing out the swag to contributors that meet certain criteria (maybe like writing a blog, or contributing a project or big feature of a project.)