search

dat-ecosystem / consortium

Process Information for the Dat Protocol Working Group (Notes, Agenda, Members)
39 stars 5 forks source link

Status of this group #71

Open okdistribute opened 4 years ago

okdistribute commented 4 years ago

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?

okdistribute commented 4 years ago

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.

serapath commented 4 years ago

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. cabal:// or cobox or any other project specifics, but it's also nothing that really belongs to us.

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 related-feeds "DEP", a later one might include a process for dat project DEPs and a later one might include a browser URI standard which supports all the projects in the dat ecosystem.

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.

  1. proper information about who can vote and what are the proposals
  2. rules of voting including notifying people and giving them time
  3. also whether we have some privacy about the votes (github makes it public)

...etc...

okdistribute commented 4 years ago

@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