docs: add maintainer notice #305
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
seeking active maintenance from S3 datastore users
gammazero
approved these changes
Oct 31, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Seeking active maintenance from actual S3 datastore users who have a financial incentive to keep this project alive AND optimized to minimize AWS billing.
Rationale
Setting expectations. Right now people assume this project is actively maintained.
Kubo does not use this backend, and our legacy collab cluster has no instance that is using S3 backend.
Lack of dogfooding means we are unable to properly triage issues / PRs in the long term, nor ensure performance / quality / cost-effectiveness.
cc @mishmosh @aschmahmann if you know companies / startups / projects that use S3 and could lend engineering time for this