02:23
<Domenic>
I'm just gonna merge https://github.com/whatwg/html-build/pull/291 . I was hoping to get more Rust reviewers but I think waiting is the wrong tradeoff.
13:03
<annevk>
I wonder if GitHub would benefit from having the equivalent of (Mozilla) Bugzilla's needinfo feature. There's quite a few threads where someone is asked a question and there's no answer. Presumably because the person asked got busy and has lost track of their notifications. And although needinfo can get problematic as well, it might improve a bunch of these cases?
13:33
<sideshowbarker>
I guess one imaginable way to hack around it in GitHub for now would be to add a label with the username of the needsinfo person. For some projects at least, the set of likely needsinfo people isn’t very large. and you could just create the labels as you need them.
13:37
<annevk>
sideshowbarker: I mean we can assign people and people can look up all the issues that have been assigned to them, but it's not quite the same.
13:39
<sideshowbarker>
hmm yeah I suppose the ability to assign people already kind of obviates the usefulness of using labels for it
13:42
<sideshowbarker>
I guess the reality is that for some people and some projects, they may be in an almost constant state of getting so many GH notifications that they have stopped being able to pay attention to them. And in those cases, you have to fall back to some other means of getting their attention when you really need it. Pinging on chat channels or DMing directly
14:39
<Dominic Farolino>
WHATWG working mode documentation has the definition of an "editor" (https://whatwg.org/working-mode#editor), but standards contain both "editors" and "authors": https://github.com/whatwg/sg/blob/main/db.json#L214-L235. My understanding is it is generally accepted that the four HTML "authors" are all seen as "editors" of HTML though, is that right?
14:40
<Dominic Farolino>
Is it the case that all "authors" really have editor powers over the standard, but one of them is deemed the official "editor", and is responsible for answering for the whole standard overall?
14:40
<Dominic Farolino>
If there is a definition of "author" that I'm missing, let me know.
14:52
<annevk>
Dominic Farolino: https://whatwg.org/workstream-policy Domenic is the Editor. Everyone else is a deputy editor, technically.
14:52
<annevk>
That's for the HTML Workstream, which includes the HTML and WebSockets Standards, iirc.
14:53
<annevk>
Although historically WHATWG editors were more like authors, today they are more like maintainers, maybe, although it varies a lot per standard and chapter within that standard.
14:54
<annevk>
(Clarifying all of this more might be worthwhile, but doing so in a consistent fashion would require studying a number of documents.)
15:02
<Dominic Farolino>
I see. I wonder if we could at least formalize the definition of "deputy editor" and its relationship with "author" in the db.json file, without too much extra study, since that's how things are behaving today already.
15:05
<Dominic Farolino>
At least I've heard a good bit of confusion internally about what "author" means in db.json, and questions around whether those people are editors or not. If authors in db.json are really deputy editors, that relationship could probably be cleared up relatively easily without too much archaeology. Do you agree Anne?
16:04
<annevk>
Dominic Farolino: that sounds reasonable. I guess I'd like to figure out why we went with "authors" there in the first place, but that should be straightforward.
22:08
<smaug>
keithamus: remind me - is there some magic to disable the behavior where github hides items/comments in issues?
23:04
<keithamus>
keithamus: remind me - is there some magic to disable the behavior where github hides items/comments in issues?
Sadly no. I think some people have built extensions to unfurl these but there’s no built in way.
23:27
<bkardell>
Eric Meyer made a bookmarklet
23:28
<bkardell>
https://meyerweb.com/eric/thoughts/2024/02/05/bookmarklet-load-all-github-comments/
23:28
<bkardell>
smaug: ^