nodejs / nodejs/next-10

Prep for Deep Dive Project Advocacy and Promotion: Survey & Community Outreach

Open
#252 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
550
Forks
31
Avg merge
4h 27m
Merged PRs (30d)
1

Description

In preparation for our upcoming deep dive on project advocacy and promotion, we've decided to reach out to existing node community advocates, and collect some data from them through an open ended anonymous survey.

To do this, we will:

  • send out to a tweet asking the folks to tag and/or identify node community advocates
  • reach out to them individually and share out the survey
  • invite them to join us, and/or give input sync or async for the upcoming deep dive session

Below are some survey questions, I've put together, and I would like to iterate on this with the Next 10 team. Once we are happy with this list, I will create the Google Form Survey, and we can start sharing it out:

  • What initially drew you to become involved in advocating for the Node.js community?

  • Can you describe some typical activities you do as a Node.js community advocate?

  • Where are the communities you support and engage with primarily based?

  • What challenges do you face in your role as a community advocate for Node.js?

  • How do you currently engage with other members of the Node.js community?

  • Can you share any success stories or positive experiences you've had while advocating for Node.js?

  • What types of resources are most effective for your community when learning about Node.js?

  • What resources or support do you feel would enhance your effectiveness as a Node.js community advocate?

  • In what ways do you believe the Node.js community could improve its support for advocates like yourself?

  • Are there specific topics or areas within Node.js that you feel deserve more attention or focus from advocates?

  • How do you measure the impact or effectiveness of your advocacy efforts within the Node.js community?

  • What advice would you give to someone who is interested in becoming a Node.js community advocate?

  • What are some of the most misunderstood or confusing concepts for Node.js community members?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading the linked deep-dive issue #247 and reviewing the proposed survey questions here. Coordinate with the Next 10 team to finalize the questions, create the Google Form survey, identify Node.js community advocates, and complete the outreach and invitation steps described in the checklist.

Written by the indexing model from the issue text.

Assessment

Tech stack
node.js
Domain
content
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.