-
-
Notifications
You must be signed in to change notification settings - Fork 449
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Looking for maintainers #1188
Comments
Dat is no longer being maintained? What happened? Edit: OK, just read the blog post: https://blog.datproject.org/2020/05/15/dat-protocol-renamed-hypercore-protocol/ |
The topmost layer, the content of this repository isn't. For an update see:
dat-ecosystem/comm-comm#149
…On Sun, May 17, 2020, 03:43 Aral Balkan ***@***.***> wrote:
Dat is no longer being maintained? What happened?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1188 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAG7FSTTLKUQ73R5WZVPXHDRR3NG3ANCNFSM4NCPCR7Q>
.
|
@martinheidegger I think a warning notice pointing here should be added to the project Readme. There are links out there pointing to this repo and this issue might go unnoticed. |
https://adoptoposs.org has been working on a channel for helping projects find new blood. Can't swear it'll work, but I suppose it won't hurt. :) |
If you're interested, I could join as a maintainer. I don't have the most JS experience, but enough to be able to understand the code and what's going on. More importantly, I have the time and skills to at least help the project move along. |
@nothead31 There are some effort revitalizing this going on, maybe join the discord? |
This repository is currently not maintained.
If you like this package, and have time, we welcome your contribution!
You can help with tested pull requests that address issues in this repository at any time but if you are interested in becoming a maintainer with write access, you can reach other members of the community for guidance in the gitter chat (#dat on freenode) and in community calls.
The text was updated successfully, but these errors were encountered: