Skip to content
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

2020.04.29-2020.07.30 | dat consortium call #37

Closed
2 tasks done
Tracked by #7
serapath opened this issue Feb 26, 2020 · 5 comments
Closed
2 tasks done
Tracked by #7

2020.04.29-2020.07.30 | dat consortium call #37

serapath opened this issue Feb 26, 2020 · 5 comments

Comments

@serapath
Copy link
Member

serapath commented Feb 26, 2020

@serapath serapath changed the title 2020.03.04 | dat consortium call 2020.03.?? | dat consortium call Mar 23, 2020
@serapath serapath changed the title 2020.03.?? | dat consortium call 2020.05.?? | dat consortium call Apr 29, 2020
@cblgh
Copy link

cblgh commented May 2, 2020

@serapath yo! i think the hypercore standard you've been interviewing people about would be very good to bring up in one of the may meetings of the dat consortium, it's something we're talking a lot about in cabal atm :)

@serapath
Copy link
Member Author

serapath commented May 4, 2020

thanks a lot :-) I really appreciate the support and didn't expect it.
I answered on the comm-comm issue that we have significant time reserved for pushing this further as soon as we finally finish our first milestone, which keeps us very busy right now

@serapath serapath changed the title 2020.05.?? | dat consortium call 2020.Q3.?? | dat consortium call Jun 13, 2020
@serapath
Copy link
Member Author

@cblgh any news? what's the status in cabal? :-)

@cblgh
Copy link

cblgh commented Jun 15, 2020

@serapath this particular issue/feature is put on the backburner for now in cabal, i think datdot will have to be the one to champion something ^_^

@serapath serapath mentioned this issue Feb 17, 2021
24 tasks
@serapath serapath changed the title 2020.Q3.?? | dat consortium call 2020.04.29 | dat consortium call Feb 17, 2021
@serapath
Copy link
Member Author

serapath commented Feb 17, 2021

thx for the feedback.
will close this issue for now and we will start championing it and tackle it once we get datdot running, which might still need some considerable time, but we'll definitely come back to it at some point :-)

it's all in this issue now:

@serapath serapath changed the title 2020.04.29 | dat consortium call 2020.04.29-2020.07.30 | dat consortium call Feb 17, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants