nodejs / nodejs/next-10

Deep Dive: Advocacy and promotion for the project

Open
#247 13 comments 9 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

Issue to keep all information linked to the next Deep Dive and ideas to discuss before the event. Feel free to add others points that could make sense to discuss during the call, any questions or all topics that could be related

Topic: Advocacy and promotion for the project
Date: February 29th 11-1 ET (working date/time, subject to change if necessary)

Main points:

  • What do we want to advocate?

    • Events that are planned
    • Major discussion or core topics that would impact the community
    • Talks / Conferences / Online presentation ...
    • Some news about contributors
    • Specific topics linked to topics (new major release, security update...)
    • Topics / New that may be good to share with the community
  • To whom do we want to promote the project?

    • Other contributors
    • Users relying on the project
    • Companies that use (or want to use) the project
  • What are the principals points we want to advocate?

    • To whom
    • Which format to use
    • What's of interest
  • Outcomes

    • How do we want to advocate: content, format, who
    • What do we want to advocate: topics, subjects...

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 with the issue's listed advocacy topics, audiences, formats, and proposed outcomes. Done means the project has an agreed advocacy plan covering what to promote, whom to reach, and which content formats and responsibilities to use.

Written by the indexing model from the issue text.

Assessment

Domain
content
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.