elast0ny / elast0ny/shared_memory

Maintenance status check: are PRs being reviewed?

Open
#119 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Rust
Stars
444
Forks
63
PR merge metrics
No merged PRs in 30d

Description

## Question

Is `shared_memory` still being actively maintained?

I noticed:
- Last commit on `master`: ~Jan 2023 (`fda4134`)
- Last push: ~Sep 2023
- ~15 open issues, several PRs sitting unmerged

I just filed [#118](https://github.com/elast0ny/shared_memory/pull/118) to bump `nix` from 0.23 → 0.30, which is required to build `shared_memory` under the OpenHarmony Tier-2 Rust targets (`*-unknown-linux-ohos`). The patch itself is small and mechanical, but I'd love to know:

1. Are PRs being reviewed at all right now? Should I expect a response, or is the project effectively in caretaker mode?
2. Is there interest in adding a co-maintainer? This crate is depended on by some fairly large downstreams (e.g. it's pulled in transitively by the [`vite+`](https://github.com/voidzero-dev/vite-plus) toolchain via [`vite-task`](https://github.com/voidzero-dev/vite-task)), and a small backlog of dependency bumps + cross-platform fixes is accumulating.
3. If neither of the above, would you consider transferring or blessing a fork?

Not trying to be pushy — totally understand life happens and OSS maintenance is hard. Just trying to figure out the right path forward so downstream users (myself included) know whether to wait, fork, or help.

Thanks for the crate, it's been useful! 🙏

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.