Proposal repos: not required?

[bathos]

When proposals don’t have repos, it’s not generally possible for people outside of TC39 to provide feedback or discuss in a way that will be visible and recorded for others. Right now there are four such proposals that are at stage 1. I’m surprised a public repo isn’t a requirement.

(Was hoping to provide feedback on / a suggestion for Map.prototype.updateOrInsert.)

[slikts]

You could use ES Discuss, but it's generally less usable or visible than a repo, so having a repo as a requirement would be preferable.

[ljharb]

A repo is generally a requirement after stage 1; there are few exceptions, and most predate ES6.

Certainly a repo would be required long prior to stage 2; i wouldn’t worry about not having an opportunity to provide feedback.

[bathos]

Cool, thanks — will close.

[mathiasbynens]

A repo is generally a requirement after stage 1

Out of curiosity, what makes you say that? The process document doesn't mention anything about it. Is this your personal opinion?

Mine is that I strongly agree with @bathos — having a repository should be a requirement, even for stage 1. I'd go even further and claim that every feature proposal that is presented to TC39 needs a repository of which the README addresses the requirements outlined in the process doc.

[rkirsling]

I agree with @mathiasbynens—I had (mistakenly or not) thought that the README effectively constituted the strawperson proposal to be presented.

It doesn't seem like a slide deck should be able to serve as a primary document in this way.

[ljharb]

That’s why i said “generally” - it’s not an explicit requirement, but i doubt any proposal could make a legitimate claim that it’d received and incorporated feedback without a repo, and the only proposal that has progressed beyond stage 1 without one is function.sent, which is still part of a larger repo and also predates the new process.

If someone thinks a repo should be a requirement, an issue or PR to the process document is appropriate, but not here :-)

[ljharb]

Got consensus on this today; #26 is merged.