llvm / llvm/Community.o

consider hiring a community manager

Open
#9 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
1
Forks
1
PR merge metrics
No merged PRs in 30d

Description

From our community.o workshop discussion:

I think the reason that most community.o issues don't get a lot of active contribution, despite good will from the llvm community in general, is that most contributors are either students or paid employees. As such, they have to "dance with the ones that brought them," and so community contribution would need to take up mostly personal time. It isn't fair to ask folks to work on community stuff with their personal time.

Some video games rely on strong community interaction, and the games industry has developed a skillset for community managers. These folks are critical for the success of online games, and are paid employees who keep busy managing their online communities. I'm not certain if there's a similar set of paid professionals with experience in open source, but I think the Foundation would have the most success on advancing community issues by having a person who is accountable for advancing the work.

Contributor guide

No contributing guide indexed for this repository

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

The issue contains a community workshop discussion proposing a paid community manager, but it names no files, tests, or implementation entry point. Start by reviewing the proposal and clarifying whether the Foundation wants to pursue the role; there is no code-defined completion condition yet.

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.