Create 2019-01-02--gui-and-in-web-browsers-weekly.md #821
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,117 @@ | ||
| # GUI & In Web Browsers Weekly Sync 2019-01-02 | ||
|
|
||
| - **Moderator & Notetaker:** _<none, it was a casual post-holiday call with surprisingly good attendance :)>_ | ||
| - **Attendees:** | ||
|
|
||
| - _@terichadbourne_ | ||
| - _@lidel_ | ||
| - _@jimpick_ | ||
| - _@olizilla_ | ||
| - _@hacdias_ | ||
| - _@alanshaw_ | ||
|
|
||
|
|
||
|
|
||
|
|
||
| **Moderator checklist** | ||
|
|
||
| - Ensure that there is a notetaker | ||
| - Start recording | ||
| - Call for additional agenda items | ||
|
|
||
|
|
||
|
|
||
|
|
||
| **Agenda** | ||
|
|
||
| _General discussions, decisions, etc._ | ||
|
|
||
| - Start with Team Updates and Demos | ||
|
|
||
|
|
||
|
|
||
|
|
||
| **Team Updates** | ||
|
|
||
| @lidel | ||
|
|
||
| - Done: | ||
| - Holidays :-) | ||
| - Discussions around accessing API of remote IPFS node - [in-web-browsers/issues/137](https://github.com/ipfs/in-web-browsers/issues/137) | ||
| - @Gozala shared some relevant ideas in | ||
| [Progressive peer-to-peer web applications (PPWA)](https://via.hypothes.is/https://gozala.hashbase.io/posts/Native%20talk.html) and tested initial assumptions in [in-web-browsers/issues/137#comment-450530548](https://github.com/ipfs/in-web-browsers/issues/137#issuecomment-450530548) | ||
| - Switched Companion to modern Clipboard API, PDF and SVG work again - [ipfs-companion/pull/649](https://github.com/ipfs-shipyard/ipfs-companion/pull/649) | ||
| - Added a warning about mixed-content when gateway URL is not a Secure Context - [ipfs-companion/pull/650](https://github.com/ipfs-shipyard/ipfs-companion/pull/650) | ||
| - Started discussion about the future of DNSLink cache - [ipfs-companion/pull/646](https://github.com/ipfs-shipyard/ipfs-companion/pull/646#issuecomment-450879014) + [go-ipfs/issues/5884](https://github.com/ipfs/go-ipfs/issues/5884) | ||
| - Next: | ||
| - Finalize OKRs | ||
| - tackle holiday backlog | ||
|
|
||
| - release Companion | ||
|
|
||
|
|
||
|
|
||
|
|
||
| @hacdias | ||
|
|
||
| - Done: | ||
| - Fixed issue where we were calling methods that only exist on macOS: <https://github.com/ipfs-shipyard/ipfs-desktop/pull/761> | ||
| - Fixed the links not opening in external windows: <https://github.com/ipfs-shipyard/ipfs-desktop/pull/769> | ||
| - Updated to Electron 4: <https://github.com/ipfs-shipyard/ipfs-desktop/pull/769> | ||
| - Fixed the black screenshot issue: <https://github.com/ipfs-shipyard/ipfs-desktop/pull/769> | ||
| - Improved the screenshots experience: there will be now a notification telling the user a screenshot was taken and if they click on it, Web UI will open on that screenshots. If the user has a multi-monitor setup, the screenshots will be in a directory. | ||
| - <https://github.com/ipfs-shipyard/ipfs-desktop/pull/759> | ||
| - <https://github.com/ipfs-shipyard/ipfs-desktop/pull/775> | ||
| - Blocked: | ||
| - Waiting for macOS guys on this PR: <https://github.com/ipfs-shipyard/ipfs-desktop/pull/770> | ||
| - Next: | ||
| - Go through Desktop’s issue list and see what can be closed and fixed. | ||
| - Prioritize native OS integrations: <https://github.com/ipfs-shipyard/ipfs-desktop/issues/679> | ||
| - Work on that ^^ | ||
| - 🧙♂️ | ||
|
|
||
| @alanshaw | ||
| - Done: | ||
| - JS IPFS 0.34 release dance 💃 | ||
| - Holidays | ||
| - Blocked: | ||
| - JS IPFS 0.34 release blocked on stack overflow issues with latest libp2p | ||
|
There was a problem hiding this comment. Are these issues documented? Could you link them here please? There was a problem hiding this comment. Will DHT be part of this release again? There was a problem hiding this comment. Just one issue: https://github.com/libp2p/js-libp2p-switch/issues/287 PRs resolving it:
This was discovered only when getting interop tests in good shape for the 0.34 release: ipfs/interop#51 As of right now, DHT is still not part of this release. Once we get the interop tests back in good shape we can evaluate how much work is remaining on the DHT endeavour. |
||
| - https://github.com/libp2p/js-libp2p-switch/issues/287 | ||
| - Next: | ||
| - Cool stuff coming to a JS IPFS near you: | ||
| - Way smaller bundle is coming <https://github.com/ipfs/js-ipfs/pull/1795> minified+gzip >50% smaller! | ||
|
|
||
| - DHT is coming! <https://github.com/ipfs/js-ipfs/pull/856> APPROVED - blocked on test failures | ||
| - Fast `ipfs.add` is coming <https://github.com/ipfs/js-ipfs-unixfs-importer/pull/10> | ||
| - > In real-world use, this changed the time it takes to \`jsipfs add\` a 260MB file to a fresh repo from 13.7s to 1.95s. By comparison\`go-ipfs\` takes 1.58s to add the same file to a fresh repo. | ||
|
There was a problem hiding this comment. @alanshaw @achingbrain how do the interop tests compare with this new change? It might have been that the previous 1/4 the speed to transfer a large file was largely bottlenecked by just adding the file itself. There was a problem hiding this comment. Wow yes good point, looking at the test code, the |
||
| - Work on benchmarks for <https://benchmarks.ipfs.team> | ||
|
|
||
| @terichadbourne | ||
|
|
||
| - Done: | ||
| - \[Live] Restructured ProtoSchool website to include community info <https://github.com/ProtoSchool/protoschool.github.io/pull/103> | ||
| - \[Merge pending review] Added a text-based tutorial on underlying concepts <https://github.com/ProtoSchool/protoschool.github.io/pull/59> | ||
| - Next: | ||
| - Seek volunteers to lead chapters so there’s more content at launch | ||
|
There was a problem hiding this comment. @terichadbourne suggestion: What about pinging the folks that already organize IPFS Meetups all over the place? There was a problem hiding this comment. @daviddias That's in my plans to tackle after launch. For now I'm focusing on PL folks who can serve as guinea pigs for my chapter setup process before I reach out more broadly. :) There was a problem hiding this comment. I see! Here is my attempt: Ping fabulous people of London @olizilla, @achingbrain @alanshaw and spetacular people of Porto @marcooliveira @satazor @vasco-santos @hugomrdias et al (you are really many), both purveyors of really awesome meetups, would you be so kind to respond to the ProtoSchool call? :D There was a problem hiding this comment. The London crew has already stepped up. 🎉 A Porto chapter would be awesome if the folks there have the time and interest! There was a problem hiding this comment. hey hey, let's chat! How can we get the conversation going? Maybe schedule a call? |
||
| - Get feedback internally and make most urgent tweaks before mid-month public launch | ||
|
|
||
| @olizilla | ||
|
|
||
| - Done: | ||
| - Holiday | ||
| - WIP Release plans for ipfs-gui <https://hackmd.io/FoaDLco6QSmaQ8RfiXE_fQ#> | ||
| - Requested Apple Developer Program enrollment | ||
| - Next: | ||
| - Fix ipfs-geoip for new ipfs object api (currently fixing tests, and reviewing api) | ||
| - Create project plan for ipfs-gui team for Q1 | ||
| - Create release issues for desktop, webui, share. | ||
| - Define Companion UI roadmap with lidel | ||
| - Pin down scope of ipfs http api exploration | ||
|
|
||
|
|
||
|
|
||
| **Discussion Highlights** | ||
|
|
||
| _Discussion highlights and additional notes._ | ||
|
|
||
| - Oli gave an overview of his GUI plans: <https://hackmd.io/FoaDLco6QSmaQ8RfiXE_fQ#> | ||
| - Jim gave an update about visiting Google Chrome Team in Tokyo and giving a demo: loading Signed HTTP Exchange from IPFS gateway using Service Worker -[in-web-browsers/issues/121](https://github.com/ipfs/in-web-browsers/issues/121#issuecomment-444769959) | ||
| - Teri is looking for feedback before revamped ProtoSchool goes live | ||
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.
Let me know if I can help :)
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.
@daviddias draft is in the 'wb' spreadsheet, if anything looks off would appreciate feedback as inline comments there or in #804 :)
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.
I just went through the KRs and posted a couple of comments. I believe there is room to enhance them with more real/current users interaction