[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Publish minutes of 2022-01-20 meeting #149

Merged
merged 2 commits into from
Feb 2, 2022
Merged

Publish minutes of 2022-01-20 meeting #149

merged 2 commits into from
Feb 2, 2022

Conversation

Rob--W
Copy link
Member
@Rob--W Rob--W commented Jan 20, 2022

Generated from https://docs.google.com/document/d/1QkwhEMtMS67JBUkl_WVPZ4lRSKoWcQNlLJSf_GwSXg8/edit using the tool and process from #105.

During this meeting we discussed or mentioned #144, #145, #146, #120, #19, #115, #147, #72, #88, #134.

@Rob--W Rob--W requested review from dotproto and zombie January 20, 2022 18:44
Copy link
Member
@dotproto dotproto left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have a handful of clarifications. Most of them are for my own comments, but I tried to add a couple other points that stood out to me during the session.

_minutes/2022-01-20-wecg.md Outdated Show resolved Hide resolved
_minutes/2022-01-20-wecg.md Outdated Show resolved Hide resolved
_minutes/2022-01-20-wecg.md Outdated Show resolved Hide resolved
_minutes/2022-01-20-wecg.md Show resolved Hide resolved
* [carlos] Had previously raised this in the past. Created an issue because I believe this is something the group should do.
* [tomislav] The details are very implementation-specific, not sure if this is something that can be specified.
* [rob] Are we looking to clarify current behavior or attempt to standardize on a specific set of behaviors?
* [alexei] If everyone were to implement Mozilla's Limited Event page proposal ([issue 134](https://github.com/w3c/webextensions/issues/134)), then we would not have this inconsistency.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* [alexei] If everyone were to implement Mozilla's Limited Event page proposal ([issue 134](https://github.com/w3c/webextensions/issues/134)), then we would not have this inconsistency.
* [alexei] If everyone were to implement Mozilla's Limited Event page proposal ([issue 134](https://github.com/w3c/webextensions/issues/134)), then we would not have this inconsistency. Still have not heard a satisfactory reason why Google opposes this.

@ghostwords does this tweak look good to you?

Copy link
@ghostwords ghostwords Jan 25, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, thank you!

I think the closest to an actual explanation thus far has been that Google cares about low-end devices, which, given that SWs will probably use more not fewer system resources overall, does not make any sense.

_minutes/2022-01-20-wecg.md Outdated Show resolved Hide resolved
@Rob--W Rob--W force-pushed the meeting-2022-01-20 branch from 09a5b81 to 0c60556 Compare February 1, 2022 23:42
@Rob--W
Copy link
Member Author
Rob--W commented Feb 1, 2022

I have included all suggested edits in the source doc and updated the PR here. I also noticed that the year of the header was off, so I have prepended a commit to fix up the date in the previous meeting notes.

The diff is https://github.com/w3c/webextensions/compare/09a5b817b87e5154b6f9068a9238a9747ed8ca3d..0c60556493bba928b044ab022abf6d5633be6990

@Rob--W
Copy link
Member Author
Rob--W commented Feb 2, 2022

Since the meeting is tomorrow and the notes have been approved, with the review feedback included without changes, I'm going to merge this now.

@Rob--W Rob--W merged commit 97c90e9 into main Feb 2, 2022
github-actions bot added a commit that referenced this pull request Feb 2, 2022
SHA: 97c90e9
Reason: push, by @Rob--W

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants