jcbrand, FWIW, when you come across a PR you can’t triage by yourself, dropping a note here would be great, especially if I seem unresponsive otherwise.
jonasw
triaging is something I can do when I have only little time, and it can help a lot when the triage ends up with "Needs Council"
jonasw
otherwise, you’re doing a great job there, thank you very much
jonasw
(going through the open PRs currently and merging them)
Tobihas joined
SamWhitedhas joined
flow
jonasw, may I suggest that we try to get council to leave a note/tirage once they handled a PR? There are a lot of old PRs with "Needs Council" that are in fact no longer in need for a council
jonasw
flow, there is daves spreadsheet of doom which is usually good
jonasw
and AFAICT there are no PRs which don’t actually need conucil currently open and marked needs council
jonasw
it’s just that they dropped off council agenda
jonasw
I’ll remind Dave soon
flow
jonasw, sure, but how does it help with PRs labeld "Needs Council"
jonasw
currently working on merges to clear the list a bit, then taking care of the rest
flow
jonasw, do you know why PR 650 is considered not desirable?
flow
(I've little background on this FWIW)
jonasw
I know it made sense to me back then
jonasw
flow, right, because omitting the type is perfectly legit and suggesting that it should always be there is wrong
flow
is list-multi like the default?
jonasw
no
jonasw
but omit is also not equivalent to the default
jonasw
it is tricky
jonasw
it depends on the form type:
form type "form": @type defaults to "text-single" (for omitted and unknown)
form type "submit": @type is OPTIONAL and needs to be inferred from context, no default
jonasw
flow, care to discuss https://github.com/xsf/xeps/pull/669 instead? ;-)