Community sentiment survey
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 15/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- content
Research direction
Start by reading the issue body and its brainstorming thread; no files, tests, or implementation entry point are identified. Before work can be considered done, the survey’s audience, questions, actionable outputs, and process would need to be defined.
Written by the indexing model from the issue text.
Description
Possible idea: should we do a survey of the TL community as a whole? It's easy for the Steering Committee to become an echo chamber, and it's worthwhile to make sure that we are in touch with the feelings and priorities of the whole organization.
This one is more an idea to ponder and maybe gradually evolve, not a call for action NowNowNow. Writing surveys is easy; writing good, actionable surveys that accurately represent sentiment and result in enough information to make better decisions is not. This one is unlikely to happen in the next month or two, but we can use this thread for brainstorming about it.
- Dominant language
- No language data
- Stars
- 0
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from typelevel/foundation
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
typelevel/foundation#8 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
typelevel/foundation#6 ·
All issues in typelevel/foundation
Similar issues
-
check:passed streams:add
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
curriculum documentation quality
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
githubnext/gh-aw-workshop#3897 ·
Maintainers usually reply within 2 days
-
correction metadata
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
acl-org/acl-anthology#10103 · 1 comment ·
Maintainers usually reply within 1 day
-
resources
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
railmapgen/rmg-palette#2445 ·
Maintainers usually reply within 1 day