[METABUG] Process for triaging pybind11 issues
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 18k
- Forks
- 2.3k
- Avg merge
- 5d 17h
- Merged PRs (30d)
- 10
Description
Currently there is no process.
Opening this metabug to track discussions, starting with https://github.com/pybind/pybind11/pull/2831/files#r617672730.
Just speaking for myself:
- I'm trying to keep up at least looking at new PRs.
- I completely ignore the massive pile of open issues.
- I'm thinking we should formally adopt one of two models:
- A. Make it obvious that the pybind11 issue system is merely a public forum without oversight or support, where people can help each other.
- B. Or find some way to fund a small support staff.
(I don't think hoping for volunteer heros sacrificing their careers to provide pybind11 support is a healthy model.)
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 with the discussion linked from pull request #2831, then review the current open-issue and pull-request workflow. Done means the project has agreed on and documented a sustainable model for triaging pybind11 issues.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, python
- Domain
- developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100