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

Create F2F agenda - 28-29 July 2016 #932

Closed
jakearchibald opened this Issue Jul 19, 2016 · 10 comments

Comments

Projects
None yet
5 participants
@jakearchibald
Copy link
Collaborator

jakearchibald commented Jul 19, 2016

https://github.com/w3c/WebPlatformWG/blob/gh-pages/meetings/16-07-28-29SW.md is the official place for the agenda, but I find it much easier to group-discuss these things in an issue.

Once things settle, I'll move the details into the official doc.

The structure last time seemed to work well, so I don't see any reason to change it.

Day 1

Day 2

These are just my suggestions, they aren't complete, and are totally up for debate.

@wanderview

This comment has been minimized.

Copy link
Member

wanderview commented Jul 22, 2016

Lets talk about whatwg/fetch#303.

@mkruisselbrink

This comment has been minimized.

Copy link
Collaborator

mkruisselbrink commented Jul 22, 2016

We should probably also go thru the issues without milestones to make sure they shouldn't be v1 issues. But maybe it makes more sense for somebody to do that before the meeting.

@RReverser

This comment has been minimized.

Copy link

RReverser commented Jul 22, 2016

@jakearchibald @wanderview whatwg/fetch#245 doesn't seem to be here? You mentioned on Twitter it will be likely discussed.

@inexorabletash

This comment has been minimized.

Copy link
Member

inexorabletash commented Jul 22, 2016

I won't be attending, but a plea for whatwg/storage#31 to get some attention.

@jakearchibald

This comment has been minimized.

Copy link
Collaborator

jakearchibald commented Jul 25, 2016

@jakearchibald

This comment has been minimized.

Copy link
Collaborator

jakearchibald commented Jul 27, 2016

To future-me: here's the script for getting issue data in the format above:

function getAllIssues(url) {
  const allIssues = [];

  return fetch(url).then(function processResponse(response) {
    const nextLink = response.headers.get('link').split(',').find(a => a.trim().endsWith('rel="next"'));
    const nextUrl = nextLink && nextLink.replace(/(^\s*<|>;.*$)/g, '');

    return response.json().then(data => {
      allIssues.push(...data);

      if (nextUrl) {
        return fetch(nextUrl).then(processResponse);
      }
      return allIssues;
    });
  });
}


getAllIssues('//api.github.com/repos/slightlyoff/ServiceWorker/issues?milestone=2').then(issues => {
  return issues.map(issue => {
    const decided = issue.labels.some(label => label.name == 'decided');

    return `  * [#${issue.number} ${issue.title}](${issue.html_url})${decided ? ' (decided)' : ''}`;
  }).join('\n');
});
@jakearchibald

This comment has been minimized.

Copy link
Collaborator

jakearchibald commented Jul 28, 2016

We should look at how many SWs are using global state. WebKit are interested in launching multiple instances of the SW in the fetch process.

F2F: Go ask developers about it. Would they like it to be opt-in?

@jakearchibald

This comment has been minimized.

Copy link
Collaborator

jakearchibald commented Jul 28, 2016

F2F: We need to gather the use-cases, and find out how we can solve them. We need to avoid getting locked into one worker instance.

@jakearchibald

This comment has been minimized.

Copy link
Collaborator

jakearchibald commented Jul 28, 2016

(deleted - posted on wrong issue)

@jakearchibald

This comment has been minimized.

Copy link
Collaborator

jakearchibald commented Jul 31, 2016

Thanks to everyone who attended, and especially @wanderview and Mozilla for hosting!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment