-
Notifications
You must be signed in to change notification settings - Fork 5
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
Status of this group #71
Comments
If no maintainers are aviailable, I propose retiring 'dat protocol' in favor of hypercore-protocol. This would entail moving many of these repositories to the datproject GitHub organization. Further enhancement proposals for the lower-level parts could happen in the hypercore-protocol github org, which @mafintosh plans to maintain. Please thumbs-up this issue to move forward, or otherwise express concerns here. |
I would volunteer as a maintainer Our project is looking for a home for technical documents/specification regarding standards (including protocols or extensions) that are shared among many dat projects in the ecosystemand how they are compatible. In my perception, hypercore-protocol is not going to be a place for standards that relate to e.g. It's shared and I propose tu use this organisation here to host those agreed upon specs that we can all reference :-) e.g. one of the first ones would be the regarding proper voting Good idea, but then we need time for proper proposals, because this is too important to just by the way thumbs up it.
...etc... |
@serapath we can move the DEPs repository to the datproject organization, and ongoing DEPs can still be talked about there. But I suspect related proposals could also happen in hypercore-protocol HYPs if there are any specific changes needed in the protocol |
Hey, @pfrazee @mafintosh @andrewosh, I wonder what the status of this group and repo is, and if we want to somehow figure out how to clean up the public presence here. This repository is linked from the main Dat docs which gets some hundreds or even thousands of readers per week so it's possible people are finding this and seeing it is potentially out of date/stale..
What should we do about it?
The text was updated successfully, but these errors were encountered: