This repository has been archived by the owner on Apr 16, 2020. It is now read-only.
chore: adds meeting notes for 2019-01-08 meeting #62
Conversation
This file contains 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
ghost
assigned 
daviddias
reviewed
Jan 9, 2019
| - Pedro mentioned we must rename peer-base because the owner of the peerbase name declined to give it to us. He will make a pool with a few suggestions so that we can decide on the new name. | ||
| - Pedro showed a PR about the WG roadmap in which we all participated in response to Dirk. | ||
| - Arkady tried to reach a 3rd party to adopt our tech but it's too soon. We need to make the stack more stable and reliable first. | ||
| - Adin and Pedro mentioned that we should learn from what textile and bring that knowledge to peer-base. Later on, and if textile agrees, they can replace parts that they built with parts from peer-base. |
There was a problem hiding this comment.
Or the other way around :)
There was a problem hiding this comment.
I don't necessarily agree that they're going to use parts of peer-base. They're more advanced than peer-base in many aspects. Right now we're focusing on a) learning what they did and b) their difficulties and how we can help.
daviddias
reviewed
Jan 9, 2019
|
|
||
| ## Notes: | ||
| - Jim demoed a peer-base RGA CRDT working in a terminal using nodejs. XState was used as state machine to change between starting, sending, saved, receiving, etc.. | ||
| - Pedro mentioned we must rename peer-base because the owner of the peerbase name declined to give it to us. He will make a pool with a few suggestions so that we can decide on the new name. |
There was a problem hiding this comment.
I do not understand why does the responsibility fall on top of a non collaborator to pick the right name.
There was a problem hiding this comment.
“He” still refers to Pedro Teixeira, perhaps we should make that clear.
There was a problem hiding this comment.
Meanwhile, you could continue using the name peer-star which precedes peer-base
There was a problem hiding this comment.
Other ideas that come to mind:
- peer-platform
- peer-radix
daviddias
reviewed
Jan 9, 2019
| - Pedro showed a PR about the WG roadmap in which we all participated in response to Dirk. | ||
| - Arkady tried to reach a 3rd party to adopt our tech but it's too soon. We need to make the stack more stable and reliable first. | ||
| - Adin and Pedro mentioned that we should learn from what textile and bring that knowledge to peer-base. Later on, and if textile agrees, they can replace parts that they built with parts from peer-base. | ||
|
|
There was a problem hiding this comment.
A few questions:
- Shouldn't all the peer-* apps and building blocks move to the peer-base org? Namely:
- https://github.com/ipfs-shipyard/peer-pad
- https://github.com/ipfs-shipyard/workshop-todo-dapp
- https://github.com/ipfs-shipyard/js-delta-crdts
- https://github.com/ipfs-shipyard/discussify-styleguide
- https://github.com/ipfs-shipyard/discussify-browser-extension
- https://github.com/ipfs-shipyard/js-ipfs-versidag
- https://github.com/ipfs-shipyard/discussify-styleguide
- https://github.com/ipfs-shipyard/js-versidag
- https://github.com/ipfs-shipyard/pm-discussify
- https://github.com/ipfs-shipyard/peer-star-infra
- https://github.com/ipfs-shipyard/pm-peer-pad
- https://github.com/ipfs-shipyard/pm-idm
- https://github.com/ipfs-shipyard/peer-star
- https://github.com/ipfs-shipyard/peer-star-react
- https://github.com/ipfs-shipyard/peer-star-network-vis-react
- https://github.com/ipfs-shipyard/peer-star-network-vis
- https://github.com/ipfs-shipyard/peer-star-peer-color
- https://github.com/ipfs-shipyard/peer-flipchart
- https://github.com/ipfs-shipyard/demo-ipfs-todo
- https://github.com/ipfs-shipyard/peerpad-peer-crdt
- https://github.com/ipfs-shipyard/dapp-identity-api
- https://github.com/ipfs-shipyard/dapp-identity-api
- https://github.com/ipfs-shipyard/peer-pad-core
- https://github.com/ipfs-shipyard/y-ipfs-connector
- https://github.com/ipfs-shipyard/peer-crdt-textarea-binding
- https://github.com/ipfs-shipyard/kipster
- https://github.com/ipfs-shipyard/peer-identity-demo
- https://github.com/ipfs-shipyard/peer-identity
- https://github.com/ipfs-shipyard/peer-crdt
- https://github.com/ipfs-shipyard/peer-crdt-ipfs
- https://github.com/ipfs-shipyard/peer-blog
- https://github.com/ipfs-shipyard/peer-cacl
- https://github.com/ipfs-shipyard/peer-crdt-example
- https://github.com/ipfs-shipyard/peer-crdt-bind-codemirror
- https://github.com/ipfs-shipyard/peer-crdt-platform
- https://github.com/ipfs-shipyard/ipfs-pubsub-peer-monitor
- https://github.com/ipfs-shipyard/ipfs-live-db
- https://github.com/ipfs-shipyard/ipfs-iiif-db
- https://github.com/ipfs-shipyard/tevere
- Any work planned to rebase the current apps on top of peer-base??
There was a problem hiding this comment.
Btw, looking at all this repos. If feels it is time to clean up, deprecate and create an onboarding story for all this work. I mean, if I were to build a DApp using IPFS, CRDTs and CACLs, where do I start?
There was a problem hiding this comment.
Good call, scheduling that in: #64
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
No description provided.