So my suggestion is discussion should happen on the list, and
NEP
updates should be merged promptly, or just self-merged. Sound
good?
Agreed that overall (1) is better than (2), rejected NEPs
should be visible. However there's no need for super-quick
self-merge, and I think it would be counter-productive.
Instead, just send a PR, leave it open for some discussion, and
update for detailed comments (as well as long in-depth
discussions that only a couple of people care about) in the
Github UI and major ones on the list. Once it's stabilized a
bit, then merge with status "Draft" and update once in a while.
I think this is also much more in like with what python-dev
does, I have seen substantial discussion on Github and have not
seen quick self-merges.
Ralf
Agreed. Perhaps we could have some kind of guideline to prevent
flooding the mailing list.