Reappropriation of Davenverse projects
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 11
- Forks
- 4
- Avg merge
- 1h 49m
- Merged PRs (30d)
- 2
Description
Davenverse projects have long been idle, despite having a large place in our ecosystem.
I call for a TSC consensus on projects we want to promote to organization-level.
Available for TSC members: extraction of davenverse projects into a spreadsheet with a quick opinionated list of projects we should internalize to get the conversation going https://docs.google.com/spreadsheets/d/1oovi0UxS2H-Ynrc1lXuYFx_YyIyZ4eihslhE9mIh1hw/edit?gid=2071043758#gid=2071043758
Contributor 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.
Research direction
Start by reviewing the linked spreadsheet of Davenverse projects and the issue’s proposal for organization-level promotion. Bring the project list and opinions to the TSC for discussion; done means the TSC reaches consensus on which projects, if any, should be internalized.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100