chore: adds meeting notes for 2018-11-27 bi-weekly sync #51
Conversation
ghost
assigned 
daviddias
changed the title
| - Lazy load of comments and replies (view more) | ||
| - In progress: | ||
| - versidag + ipfs-versidag modules | ||
| - https://github.com/ipfs/dynamic-data-and-capabilities/issues/50 |
There was a problem hiding this comment.
@satazor check out these threads:
- Versioning: Commit + Repo Datastructures ipfs/notes#23
- git on IPFS (ipld-git) ipfs/notes#45
- Rich Hickey's versioning thoughts ipfs/notes#195
They are full of insights that will be useful for you :)
| - Next: | ||
| - Integrate ipfs-versidag into discussify so that we have history | ||
| - This will require a small refactor since some of stuff currently in the CRDT is no longer necessary | ||
| - Either launch discussify in chrome/firefox store |
There was a problem hiding this comment.
Kickstarting the Identity/IDM will require me to do a technical top-down analysis to decompose it in smaller parts. Those parts can be made individually and even in parallel. There's a few people that want to contribute and those smaller parts can be assigned to whoever is interested in helping.
There's important stuff that needs to be done for Discussify to be launched in the stores:
- Make manifest.json compatible with Firefox: this will require to setup a manifest.json template and run it for Chrome and Firefox
- Pinner must be working; it would be bad if data is simply lost
- Add versioning to the data-model so that we can do breaking changes if necessary
- What we are thinking for now is simply suffixing the collaboration name with a version. It's assumed that whenever the version changes, all discussions are reset. Note that the data isn't actually lost, because you can always install the previous version to see the old comments.
- Later, we should think thoroughly on how we deal with migrations. This is a use-case of many DApps and I think that it's worth discussing it as a feature of peer-star-app.
- The history & new header can be later added via an update
I'm afraid that if I dedicate the time to do what I listed above, I will only be able to kickstart the identity in 1w+. I've talked with @pgte about adding Pedro Santos to help launching Discussify with these simpler tasks so that I can focus on Identity. He will follow up with you on that via email.
| - Implement new header (smaller and prettier) | ||
| - Publish on store: logo + copy + public key? | ||
| - ...or kickstart Identity/IDM | ||
| - Prepare talk about DApps + IPFS + peer-star-app for OPO.js |
There was a problem hiding this comment.
Will Discussify be released on the app store for OPO.js talk?
There was a problem hiding this comment.
I think it's possible, even if the history/new header aren't ready. We can launch those features later on via an update. @marcooliveira perhaps the launch plan should have this in mind
| - Decided to push off more sophisticated synchronization of version graphs for now | ||
| - IPLD also interested in this problem (may start talking in the https://github.com/ipld/replication repo) | ||
| - Starting sharing and version graph synchronization in https://github.com/aschmahmann/ipshare | ||
| - MultiWriter IPNS Draft Interface Specs (in the IPShare repo) |
There was a problem hiding this comment.
The MultiWriter IPNS should go into ipfs/specs
Might be good to check these threads:
- PubSub notes from the IPFS Workshop - recursion and corecursion, PubSub API and Self Certified Streams ipfs/notes#154
- IPNS Improvement Design Exploration ipfs/notes#260
- IPFS database: pubsub, consistency and persistence ipfs/notes#244
- Optimizing IPNS ipfs/notes#109
- IPNS's many uses for apps ipfs/notes#69
- IPNS+IPFS as a NoSQL database ipfs/notes#70
- desirable IPNS properties ipfs/notes#10
- Authenticated PubSub ipfs/notes#236
- pub/sub - publish / subscribe ipfs/notes#64
Notes for bi-weekly sync of #49