New Maintainers?
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 566
- Forks
- 163
- Avg merge
- 4h 51m
- Merged PRs (30d)
- 2
Description
I do not personally have time to maintain this crate any more and I suspect the other maintainers are also quite short on time nowadays. I think it's time to put out an "official" call for "this crate is in maintenance mode now". The way I personally view this crate:
- For
ssh2I think anyone who's interested can pick it up. I'm not going to merge any changes tossh2as a crate from now on most likely. - For
libssh2-systhis is depended on bylibgit2-syswhich is used by Cargo, so it is a pretty important dependency. I will try to merge bug/security fixes myself but other than that I don't have the time to help improve this.
If you'd like to help maintain this leave a comment here. I'm happy to transfer ssh2 ownership and such without much ado, but for libssh2-sys you'll need to be a relatively trusted member of the Rust community since Cargo depends on it.
Contributor guide
No contributing guide indexed for this repository
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 in issue #228, focusing on the stated maintenance status of ssh2 and the bug/security-fix expectations for libssh2-sys. Done would be an agreed maintenance or ownership plan recorded by maintainers; no code files or tests are identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- developer-experience
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100