XSF Editor Team - 2018-07-05

Welcome editors!

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.

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"

otherwise, you’re doing a great job there, thank you very much

(going through the open PRs currently and merging them)

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

flow, there is daves spreadsheet of doom which is usually good

and AFAICT there are no PRs which don’t actually need conucil currently open and marked needs council

it’s just that they dropped off council agenda

I’ll remind Dave soon

jonasw, sure, but how does it help with PRs labeld "Needs Council"

currently working on merges to clear the list a bit, then taking care of the rest

jonasw, do you know why PR 650 is considered not desirable?

(I've little background on this FWIW)

I know it made sense to me back then

flow, right, because omitting the type is perfectly legit and suggesting that it should always be there is wrong

is list-multi like the default?

no

but omit is also not equivalent to the default

it is tricky

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

flow, care to discuss https://github.com/xsf/xeps/pull/669 instead? ;-)

jonasw, will do :)

jonasw: thanks for the encouragement, will do :)