Fork

[hardliner66]

I stumbled across this crate because I wanted to use 9p for a project of mine. Seeing that the last updates were years ago, I forked the project and put it up under a github org. I updated all the dependency versions and fixed everything that broke because of the updated dependencies, modernized a few things in the code, removed the unsafe code, updated the readme, replaced the travis build with github actions and updated the example so it properly cleans up after itself.

I also renamed the project to rs9p and published it to cargo, so that others can use it from there.

If you want to be the main maintainer of this, I can transfer ownership of the crate and the organization to you.

The fork can be found here: https://github.com/rs9p/rs9p

[donno]

A downside of the fork is the fact issue tracking isn't enabled and can't be as per https://github.com/orgs/community/discussions/161368. As that discussion mentioned, the work around would be to use discussions. That would enable using discussion to talk about the direction of the fork as well as able to discuss issues on this project within the context of the fork (i.e. reference to issues here), without polluting this project's issue tracker as much.

[hardliner66]

If there are no plans to update the original, I can leave the fork network, which would allow the use of issues. I just wanted to give the author a heads up in case they want to continue maintaining the crate.

I will also enable discussions later, when I'm on PC.

Edit:
I just enabled discussions, but I also saw that its possible to enable issue tracking, so I guess the info might be outdated or wasn't completely correct in the first place.