This repository has been archived by the owner on Feb 8, 2023. It is now read-only.
Create 2018-11-21--gui-and-in-web-browsers-weekly.md #771
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,127 @@ | ||
| # GUI & In Web Browsers Weekly Sync 2018-11-21 | ||
|
|
||
| - **Lead:** @olizilla | ||
| - **Notetaker:** @lidel | ||
| - **Attendees:** | ||
| - @terichadbourne | ||
| - @olizilla | ||
| - @lidel | ||
| - @alanshaw | ||
| - @hacdias | ||
| - @fsdiogo | ||
|
|
||
| ## Before the Sync | ||
|
|
||
| - Write down your updates | ||
| - What have you accomplished since the last Weekly? | ||
| - Were there any blockers? If so, which ones? Is it still blocked? Why? | ||
| - What is the next important thing you should focus on? | ||
| - Read updates of others | ||
| - Any questions, requests to communicate? | ||
| - Ask everyone to put their name into the list of attendees and add any last minute agenda items | ||
| - Go over everyone's updates and ask if there are any questions or things to discuss | ||
| - Everyone can demo something! | ||
|
|
||
| ## Agenda | ||
|
|
||
| - PSA: Upate IPFS Working Group Capacity Planner (link in Action Items at the end) | ||
| - Q4 mid quarter scoring - should we skip the mid quarter self assesment this time? | ||
| - IPFS KPIs | ||
| - metrics to track how the project is doing. | ||
| - A lightweight tool to let different teams set their own prorities, but still pull in the same direction. | ||
|
|
||
| ## Notes | ||
|
|
||
| ### Team Updates | ||
|
|
||
| - @lidel | ||
| - Done: | ||
| - Moved meeting notes to [team-mgmt](https://github.com/ipfs/team-mgmt/pull/760) and added Zoom Call URL to [IPFS Calendar (UTC)](https://calendar.google.com/calendar/embed?src=ipfs.io_eal36ugu5e75s207gfjcu0ae84@group.calendar.google.com&ctz=UTC) with Oli as co-host. | ||
| - Issue updates related to foreign fetch being removed from ServiceWorker | ||
| - Summary: [in-web-browsers/issues/55](https://github.com/ipfs/in-web-browsers/issues/55#issuecomment-439255498) | Details: [arewedistributedyet/issues/32](https://github.com/arewedistributedyet/arewedistributedyet/issues/32) | ||
| - Fixed up basic Service Worker demo to work with latest js-ipfs - [ipfs-service-worker/pull/16](https://github.com/ipfs-shipyard/ipfs-service-worker/pull/16) | ||
| - Started looking into js-ipfs in service worker shared over iframe - [service-worker-gateway/issues/30](https://github.com/ipfs-shipyard/service-worker-gateway/issues/30) | ||
| - Removed suggestion to set `Access-Control-Allow-Credentials` from GUIs, docs and scripts as a part of [HTTP Headers Cleanup](https://github.com/ipfs/in-web-browsers/issues/132) | ||
| - `window.ipfs.enable()` is now used by `window.ipfs-fallback` if available ([#2](https://github.com/ipfs-shipyard/window.ipfs-fallback/pull/2)) | ||
| - Next: | ||
| - publish API drafts as PR for comments | ||
| - finish sw+iframe demo/poc to test feasibility of [service-worker-gateway/issues/30](https://github.com/ipfs-shipyard/service-worker-gateway/issues/30#issue-381410578) | ||
| - @alanshaw | ||
| - Done: | ||
| - Files API refactor (MERGED NOT YET RELEASED) | ||
| * `ipfs.files.add` => `ipfs.add` | ||
| * `ipfs.files.addPullStream` => `ipfs.addPullStream` | ||
| * `ipfs.files.addReadableStream` => `ipfs.addReadableStream` | ||
| * `ipfs.files.cat` => `ipfs.cat` | ||
| * `ipfs.files.catPullStream` => `ipfs.catPullStream` | ||
| * `ipfs.files.catReadableStream` => `ipfs.catReadableStream` | ||
| * `ipfs.files.get` => `ipfs.get` | ||
| * `ipfs.files.getPullStream` => `ipfs.getPullStream` | ||
| * `ipfs.files.getReadableStream` => `ipfs.getReadableStream` | ||
| * --- New core files API methods (js-ipfs) / moved from `ipfs.util` (js-ipfs-api): | ||
| * `ipfs.addFromStream` | ||
| * `ipfs.addFromUrl` | ||
| * `ipfs.addFromFs` | ||
| * See https://github.com/ipfs/js-ipfs/pull/1720 | ||
| - `ipld-dag-pb` refactor (MERGED NOT RELEASED) TLDR; no `multihash` or `cid` properties | ||
| - [`--cid-base`/`?cid-base` PR](https://github.com/ipfs/js-ipfs/pull/1552) is ready for review! | ||
| - `window.ipfs.enable()` is now used by `window.ipfs-fallback` if available ([#2](https://github.com/ipfs-shipyard/window.ipfs-fallback/pull/2)) thanks @lidel! | ||
| - Pair programming with [@pkafei](https://github.com/pkafei) | ||
| - [0.34](https://github.com/ipfs/js-ipfs/issues/1721) is coming end of Nov/beginning of Dec | ||
| - Blocked: | ||
| - [Object API breaking change to return CIDs](https://github.com/ipfs/interface-ipfs-core/pull/388#issuecomment-437866965) "soft blocks" a release of js-ipfs-api. | ||
| - Next: | ||
| - Implement `addFrom*` methods in js-ipfs | ||
| - Write interop tests for CIDv0/1 put and get | ||
| - @fsdiogo | ||
| - Done: | ||
| - Share Files working without public gateways | ||
|
There was a problem hiding this comment. Could it use the Service Worker Gateway? There was a problem hiding this comment. It could. Right now it's using ipfs-redux-bundle that chooses the best available connection and fires up a There was a problem hiding this comment. woa! I didn't know about that! Can someone do a video tutorial pleaaase? There was a problem hiding this comment. ipfs-redux-bundle is React-specific lib we use internally for R&D in WebUI/Companion/Desktop, API is not stable yet :) |
||
| - https://github.com/ipfs-shipyard/ipfs-share-files/pull/44 | ||
|
There was a problem hiding this comment. Just gave share.ipfs.io a spin. Was intrigued by
There was a problem hiding this comment. Btw, this is kind of the same as https://filenation.io. What is different in this app that justifies creating and maintaining another codebase? There was a problem hiding this comment. I'm not sure I follow the question in the image. This is not supposed to mimic a gateway, the visible url and # is for the app internal routing. It's similar in the way that is an app to share files, yes.
There was a problem hiding this comment. To compliment Diogo's points, there is a relevant background discussion in ipfs/ipfs-gui#34 (Design: Share files via IPFS). IIRC historical reasoning for ipfs-share-files was along these lines:
|
||
| - Enable dir listing and downloading folder structures | ||
| - https://github.com/ipfs-shipyard/ipfs-share-files/pull/47 | ||
|
There was a problem hiding this comment. It would be cool to have channels just like the exchange files example has There was a problem hiding this comment. Yes, that is something that is being discussed (ipfs/ipfs-gui#52, ipfs/ipfs-gui#36) but probably will fall under the Web UI. There was a problem hiding this comment. There is also ipfs/ipfs-gui#57 ("hackpad for file sharing" ) which is exactly about taking the "exchange files example", refining the UX and integrating it with ipfs-webui (directly or via ipfs-share-files). The wow factor of doing this right could be massive. This will happen for sure, but we want to get MVP with basic sharing out of the door, and iterate from there. |
||
| - Next: | ||
| - Integrate Share Files in Web UI and Companion | ||
| - IPFS UI Component Library ✨ | ||
| - @olizilla | ||
| - Done: | ||
| - Design Systems London Conf | ||
| - Error modal design | ||
| - share files planning | ||
| - Next | ||
| - Define what's todo in Desktop | ||
| - Fix resource utilization in webui | ||
| - cut webui release | ||
| - @hacdias | ||
| - Done: | ||
| - Merge 'The PR' of IPFS Desktop | ||
| - https://github.com/ipfs-shipyard/ipfs-desktop/pull/662 | ||
| - Still working on: | ||
| - IPFS Desktop settings on Web UI | ||
| - https://github.com/ipfs-shipyard/ipfs-webui/pull/883 | ||
| - Error handling on Desktop: | ||
| - https://github.com/ipfs-shipyard/ipfs-desktop/pull/697 | ||
|
|
||
| ### Discussion Highlights ✨ | ||
|
|
||
| - Some js-ipfs in Service Worker updates: [in-web-browsers/issues/55](https://github.com/ipfs/in-web-browsers/issues/55#issuecomment-439255498) | ||
| - js-ipfs 0.34 coming at the end of Nov/beginning of Dec with [nice API cleanup/refactoring](https://github.com/ipfs/js-ipfs/pull/1720) | ||
| - IPFS Desktop: improving UX for [error handling, built-in issue reporting](https://github.com/ipfs-shipyard/ipfs-desktop/pull/697) | ||
| - IPFS Share App: wip on improvements for users without ipfs-companion (embedded js-ipfs + gateway) | ||
| - Proto School: wip on saving state to local storage between learning sessions | ||
| - Open discussion: working hours / open-door-policy to provide support for people with questions about GUI/websites? | ||
| - PSA: Working Group Capacity Planner (@all: see Action Item below) | ||
| - We did Milestone Evaluation Exercise ([notes](https://hackmd.io/haC8c6tPQYiBHJp09KzbMQ)) | ||
| - Review of [IPFS Project KPI Draft](https://docs.google.com/document/d/1r2Ng8Ura9yg63Aq8sXpJQ-PKFhDzJADoHRxZUESUugg/edit#) (will be made public in following weeks) | ||
| - Everyone grabbed one Milestone and picked one Awesome and one Meh milestone and we discussed what makes them that way. | ||
| - Brief discussion about the need for explaining basic concepts "just in time", so users are not overwhelmed. Both [docs.ipfs.io](https://docs.ipfs.io/guides/concepts/) and [proto.school](https://github.com/ipfs-shipyard/proto.school/pull/59) try to address this. | ||
| - Creating websites with IPFS is a good opportunity to onboard users with IPFS concepts. | ||
|
|
||
| ### By The Way! ✨ | ||
|
|
||
| - @Gozala (Research Engineer at Mozilla) joined us last week during [All Hands Call](https://github.com/ipfs/team-mgmt/issues/756) and gave a talk about [mozilla/libdweb](https://github.com/mozilla/libdweb). [Recording](https://www.youtube.com/watch?v=0fT9HC2Crqw) and [Meeting Notes](https://github.com/ipfs/team-mgmt/blob/master/meeting-notes/2018/2018-11-12--all-hands.md#main-presentation) are available. | ||
|
|
||
|
|
||
| ### Action Items | ||
|
|
||
| - @all: Fill your estimated availability for 2019 in J column of [IPFS Working Group Capacity Planner - 2019 Roadmapping](https://docs.google.com/spreadsheets/d/1M7vSGfQyHZFQ0D-WpBcbjLCZrNT0x-qiRcR_7qzgyJo/#gid=2055723494). If you don't have write access, just message @lidel or @olizilla. | ||
| - @all: Read [IPFS Project KPI Draft](https://docs.google.com/document/d/1r2Ng8Ura9yg63Aq8sXpJQ-PKFhDzJADoHRxZUESUugg/edit#) and provide comments | ||
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thaank you ❤️