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

Bugzilla issues elsewhere #196

Closed
2 tasks done
annevk opened this issue Sep 26, 2015 · 6 comments
Closed
2 tasks done

Bugzilla issues elsewhere #196

annevk opened this issue Sep 26, 2015 · 6 comments

Comments

@annevk
Copy link
Member

annevk commented Sep 26, 2015

The other "editor: Ian Hickson" are mostly empty (one contains an editorial issue that doesn't apply to non-forks) and even these are not too important.

I wonder if @AFBarstow has any ideas, since those components are clearly not maintained by Ian anymore.

@domenic
Copy link
Member

domenic commented Oct 1, 2015

I went through the first bullet point and found only two issues that were not related to editorial mishaps due to forking:

So checking that off as taken care of.

@domenic
Copy link
Member

domenic commented Oct 1, 2015

The second link only contains one open bug, where @annevk is recently involved. @annevk, maybe you could summarize its action item into a new GitHub issue, mark it as moved, and then we can close this meta-issue?

@annevk
Copy link
Member Author

annevk commented Oct 5, 2015

I created #226, but the main point behind this issue was if we could figure out a way to reduce the amount of channels for giving feedback. E.g., perhaps by closing those components.

@sideshowbarker @AFBarstow?

@AFBarstow
Copy link

The BugZ status of the 5 (so-called) "HTML(5) APIs" is: SSE (0), Messaging (0), Storage (0), Workers (1) and Sockets (4).

We (@sideshowbarker or some other staff) can and should now mark the first three above as "HISTORICAL" and disable write access. Is this what you want @annevk?

I would be reluctant to do the same to Workers and Sockets until they have ZarroBoogs (f.ex. the open bugs are copied to Github and then closed).

@annevk
Copy link
Member Author

annevk commented Oct 6, 2015

@AFBarstow yeah closing them would be great. It seems the remaining bugs are all nits about the issues with the fork being standalone, so those are not really actionable to the WHATWG.

@annevk
Copy link
Member Author

annevk commented Oct 6, 2015

I guess I'll close this then.

@annevk annevk closed this as completed Oct 6, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

3 participants