RustPython / RustPython/RustPython
Recruiting maintainers
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 22.4k
- Forks
- 1.5k
- Avg merge
- 16h 33m
- Merged PRs (30d)
- 165
Description
The project is losing maintainers. I am still doing some jobs but not as much as before.
I also don't have enough time to finish time consuming jobs like #5299
Yes, any project lose momentum at some point. But it doesn't necessarily means dying.
If anyone is interested in the project, but not diving in it because the project looks less being maintained, it is an opportunity for you.
Please contact me anyone who is interested in this project. I will try my best to support to do it.
I joined this project to get better at Rust. And had awesome years thanks to many great developers.
cc @coolreader18 @qingshi163 @windelbouwman @shinglyu @cthulahoops @DimitrisJim @palaviv @BenLewis-Seequent @mireille-raad @fanninpm
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
The issue names no files, tests, or implementation entry points and asks for maintainer recruitment rather than a code change. Start by clarifying a specific ownership area and acceptance criteria with project maintainers; completion cannot be determined from this issue alone.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100