-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Comments
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. |
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. |
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). |
@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. |
I guess I'll close this then. |
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.
The text was updated successfully, but these errors were encountered: