02:48
<canadahonk>
how does it work with author vs champion?
02:49
<ljharb>
often they're the same people, but sometimes the author isn't a delegate and can't champion
02:49
<Chris de Almeida>
they are often the same, but authors author it and champions argue it
02:50
<ljharb>
and sometimes a new champion takes over an old proposal and the old champion is still the author
02:50
<canadahonk>
so if someone authored a proposal and I want to champion and potentially edit, I would be champion and me and the other would both be authors, right
02:50
<ljharb>
yep
02:51
<Chris de Almeida>
maybe, depends how much you add to it
02:51
<canadahonk>
sure, but generally
02:51
<Michael Ficarra>
very likely
02:51
<ljharb>
no hard rubric tho, just a judgement call
02:52
<Chris de Almeida>
champions must be on committee and authors needn't
02:56
<canadahonk>
also should only spec.emu be used today (not spec.html)?
02:57
<shu>
you can name it whatever you want
02:57
<shu>
i like html
02:57
<shu>
ain't nobody know what emu is
02:57
<Richard Gibson>
spec.sgml
02:58
<keith_miller>
Isn't it a bird?
02:58
<Andreu Botella (at TC39, 🕐 JST)>
spec.ostrich
02:58
<canadahonk>
spec.spec
03:01
<Meghan Denny>
emu comes from https://github.com/tc39/ecmarkup
03:02
<Meghan Denny>
i used to think it was a bikeshed fork but im not sure if thats true/when it happened if it did
03:03
<linusg>
file extensions are bloat: https://github.com/whatwg/html/blob/main/source
03:03
<ljharb>
name it whatever you want, but the template repo starts it out as spec.emu
04:07
<Domenic>
i used to think it was a bikeshed fork but im not sure if thats true/when it happened if it did
emu was from-scratch, built by Brian Terlson. IIRC, based on discussions between him and I at a Redmond TC39 shortly after ES6 publication. I had done Ecmarkdown, he did Ecmarkup.
04:08
<canadahonk>
random spec check: is "the extended mathematical value of" used in place of ℝ() only when the earlier steps do not handle +-Infinity?
04:57
<canadahonk>
intros in spec for proposals with only one clause, yay or nay
04:58
<bakkot>
I like to have a link to the github
04:58
<bakkot>
not everyone bothers
04:59
<canadahonk>
oh yeah that's nice
04:59
<canadahonk>
also is there an actual standard ;) / template for proposal's readme somewhere?
05:02
<bakkot>
nope
05:03
<Michael Ficarra>
@canadahonk I've developed this pattern over time: https://github.com/tc39/proposal-iterator-sequencing
05:03
<Michael Ficarra>
it changes a bit as the proposal goes through the stages
05:04
<Michael Ficarra>
earlier stages focus more on the open design space and later stages focus more on the design we ended up with
05:04
<canadahonk>
neat
05:11
<ljharb>
(fwiw the spec link will be on the right hand side, so it's arguably redundant to include it in the readme)
05:14
<bakkot>
the link on the RHS is not always to the spec; on proposals with a playground or docs it's usually those
05:14
<bakkot>
and the link on the RHS doesn't say what it is
05:15
<ljharb>
ah, that's fair. most proposals only have the spec link tho
05:15
<Richard Gibson>
what I really wish were more common is links to GitHub from the rendered spec, as in https://tc39.es/proposal-json-parse-with-source/
05:16
<ljharb>
yeah true, that'd be a good addition to ecmarkup actually
05:17
<Richard Gibson>

what, you don't like this?

shortname: &lt;a href="https://github.com/tc39/proposal-json-parse-with-source"&gt;proposal-json-parse-with-source&lt;/a&gt;
05:18
<ljharb>
oh interesting, that's workable i guess. i was thinking more of like the upper right dog-ear corner with a github logo
05:19
<Michael Ficarra>
the link on the RHS is not always to the spec; on proposals with a playground or docs it's usually those
yeah like https://github.com/tc39/proposal-joint-iteration#joint-iteration
05:20
<Michael Ficarra>
oh interesting, that's workable i guess. i was thinking more of like the upper right dog-ear corner with a github logo
yeah I have that on my demo pages https://tc39.es/proposal-joint-iteration/demo/
05:23
<ljharb>
i like https://github.com/tholman/github-corners a bit better
05:23
<Richard Gibson>

there's also the dead-simple approach taken by ecma262 itself

<div id="metadata-block">
  <h1>About this Specification</h1>
  …
  <ul>
    <li>GitHub Repository: <a href="https://github.com/tc39/ecma262">https://github.com/tc39/ecma262</a></li>
05:24
<ljharb>
not fancy enough :-p
05:30
<Richard Gibson>
https://i.giphy.com/media/v1.Y2lkPTc5MGI3NjExOG15N2NncXc5eWYzd2NhaGF4eXA5dm1pM2doZGk0aTJmYW5wNTFzNyZlcD12MV9pbnRlcm5hbF9naWZfYnlfaWQmY3Q9cw/WcYnTzdrjQphdu33xs/giphy.gif
05:31
<Michael Ficarra>
get github to update their official recommendations and I'll change it https://github.blog/news-insights/the-library/github-ribbons/
06:31
<Aapo Alasuutari>
spec.spec
spec.lgtm