diff --git a/meeting-notes/20181127.md b/meeting-notes/20181127.md new file mode 100644 index 0000000..4bd206e --- /dev/null +++ b/meeting-notes/20181127.md @@ -0,0 +1,227 @@ +# Dynamic Data and Capabilities WG — November 27th, 2018 + +- **Lead:** @pgte +- **Notetaker:** @jimpick +- **Attendees:** + - @pgte + - @jimpick + - @andreforsousa + - @daviddahl + - @arkadiy + - @aschmahmann + - @marcooliveira + - @satazor + +- [**Zoom.us meeting URL**](https://protocol.zoom.us/j/586782711) +- [**Recording**](https://www.youtube.com/watch?v=CY_cVPEATc8&feature=youtu.be) + +## Agenda + +1. Start recording +1. Ask everyone to put their name into the list of attendees +1. Ask for a volunteer to take notes +1. Everyone can add items to this agenda for things they would like to discuss +1. Round of intros and updates + - Introduce yourself and your interest in this subject + - What have you accomplished since the last meeting? + - Were there any blockers? If so, which ones? Is it still blocked? Why? + - What is the next important thing you should focus on? +1. Demos + - peer-pad E2E load tests + - discussify replies +1. Questions + +### 2 Week Updates: + +(please copy this and add your update here :) + +#### @ + - Concluded: + - In progress: + - Blocked: + - Next: + +#### @satazor + - Concluded: + - Replies + - Lazy load of comments and replies (view more) + - In progress: + - versidag + ipfs-versidag modules + - https://github.com/ipfs/dynamic-data-and-capabilities/issues/50 + - Blocked: + - Add persistance of the data (pinner + sync UI language) + - Infrastructure + - Sync UI language being done for peerpad; will later borrow the same UI language + - 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 + - Prepare manifest.json for Firefox so that it's compatible + - Add versioning + TTL to the data model + - 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 + - Notes: + - + + +#### @aschmahmann + - Concluded: + - 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) + - In Progress: + - Version Graph Syncing specs + - Sharing specs + - Scaffolding for causal chat application (it will likely be Yjs + HTTP Go daemon). + - Blocked: + - Next: + - Start using ipshare repo to track tasks and next steps + - Finish writing and publishing above specs to the repos listed + - Continue MW-IPNS implementation + - Managing multiple simultaneous names (currently just does one) + - MW-IPNS basic pinner + - Notes: + - different use cases... + - thoughts on pubsub and topology + +#### @pgte + - Concluded: + - Started special-interest group Identity, lead by @satazor + - Created IRC channel #ipfs-identity + - Created IDM PM Github repo: https://github.com/ipfs-shipyard/pm-idm + - released delta-crdts v0.6.0 + - better collision-free UUID (was only happening in tests, but...) + - more and better RGA tests + - peer-star-app + - speed-up tests: https://github.com/ipfs-shipyard/peer-star-app/pull/120 + - released peer-star-app v0.10.0 + - many fixes and improvements in replication + - is backwards-incompatible + - In progress: + - Blocked: + - Next: + - Notes: + - + +#### @marcooliveira + +- In progress + - Sync with what the Design WG did while I was away + - Update design file structure based in discussions with Design WG + - Define where design assets will be stored and shared + - Define how DDC WG (and others) should interact and request from Design WG + - Create table of possible statuses, intervenients and message for each one + - Once we have a solution, will present to DDC to gather feedback, then it should become recommended UX for all peer-star apps (Peerpad, Discussify, IDM) + - Might require information on peer-star that is not yet available for dev + - Discuss how to launch "more public BETA" of Discussify + - Why? + - Not a real launch, we just want to make it easier to get beta testers on board, gather feedback and release updates + - Where + - Chrome Web Store + - Add-ons for Firefox + - To improve + - Extension banner will likely change: https://github.com/ipfs-shipyard/pm-discussify/issues/64 + - Peers/Pinning connectivity/consistency status; review with Sousa + +- Blocked + - Launch public BETA of Discussify + - Finish versidag and integrate it into discussify + - Pinner integration + - Versioning + TTL of data (to enable quick iterations) + - Need to ping Victor about this + - Who owns the key to publish? + - For Firefox Add-ons, need to generate slightly different manifest + +- Next + - Discussify: Copy & image for stores. Brand manual will be useful + - Find solutions for gathering feedback and metrics from BETA testers + - Find influencers & mediums where to announce effort and gather interest + - Discussify: Launch public BETA + +- Notes + +- Discuss with Pedro (open issue) + - All the pending issues/decisions to be done for launching Discussify + - Influencers we could use, who could write about us? + - GUI WG is discussing set of components that could be integrated into apps, might be interested in the UX for syncing status. + + +#### @jimpick + - Concluded: + - New maintainer of peer-pad repo on GitHub + - experimentation with e2e:load tests + - trip to Tokyo, talk at Tokyo Nodefest (currently in Sapporo!) + - suppress peer-star-app linter warnings (discuss) + - extended contract! + - In progress: + - investigating and cleaning up warnings in tests + - establish performance budgets for several test cases + - try to stabilize e2e:load even further + - investigate new persistence work from @pgte + - investigate connection speedups from @dirkmc + - simplify UI on production PeerPad (for internal use) + - production deploy of latest PeerPad / peer-star-app / pinner + - meet with Google in Tokyo - signed HTTP exchanges (lidel) + - write up Japan trip notes + - travel back to Canada + - Blocked: + - Next: + + +#### @arkadiy + - Concluded: + - surgery/thanksgiving! + - In progress: + - streamlining PeerPad for dogfooding (please see https://github.com/protocol/pm-peer-pad/issues/35) + - Notes: + - David Dias - do we make PM public? Arkadiy is ok with it + +#### @andreforsousa +- Concluded: + - Discussify: + - Open a new issue with Q&A for the UI level + - https://github.com/ipfs-shipyard/pm-discussify/issues/64 + - Left everything on the repo - Updated user journey and style guide + - PeerPad read-only mobile version is ready following the discussion on GH +In Progress: +- Discussify Brand Manual - kick off +- UX for Current Pinning status: + - Still Offline and connecting; + - Online and syncing; + - Online and synced; + - Online and failed; + - Synced and offline; + - Online and only me; +Next: +- Discuss all pinning status/persistency and advance with different UI approaches + - Provide a list with all scenarios (persistency) and the UI approaches by Nov 28th +- Upload updated PeerPad read-only mobile version on GH + + +Notes: + - + + + +#### @daviddahl +- Concluded: + - more tests added to ipfs-social-proof + - proper ascii-armoring of keys and signatures +- In Progress: + - adding actual W3C claims format for all 'proofs' + - updating tests validation and verification for new claims format +- Next: + - Examine apis for modularization for use in other systems + - Find out why Firefox is broken +- Notes: + - + + +------------- + +## Notes: + +