I've noticed that much of the valuable discussion in gRFCs [1] these days is happening via GitHub's PR interface.
The proposal process currently says: > For at least a period of 10 business days (the minimum comment period), it > is expected that the OWNER will respond to the comments and make updates > to the RFC as new commits to the PR. Through the process, the discussion > needs to be kept to the designated thread in the mailing list in order to > avoid splintering conversations. The OWNER is encouraged to solicit as > much feedback on the proposal as possible during this period. PR comments > should belimited (sic, PR to fix [2]) to formatting and vocabulary. Note in particular: > the discussion needs to be kept to the designated thread in the mailing > list Practice and documentation have diverged. :-) Should we 1. update the documented process to reflect the what people are doing today, 2. as a community work to change our collective behavior and redirect comments on GitHub back to the mailing list thread (perhaps with help from automation), 3. figure out some sort of in between (e.g., reflect comments/message back and forth), 4. start a proposal to come up with a different process that doesn't invite such bifurcation, or 5. something else? I'm intentionally not linking to any examples, as I don't want to imply that anyone is doing anything wrong. I'm trying to bring this up as an observation that what we say we do and what we end up doing are different as a way to figure out how to bring them back in sync with each other so that new contributors know what to expect. [1]: https://github.com/grpc/proposal [2]: https://github.com/grpc/proposal/pull/176 -- Christopher Warrington Microsoft Corp. -- You received this message because you are subscribed to the Google Groups "grpc.io" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/DM5PR00MB03897E574A5DDE02370546899BDE0%40DM5PR00MB0389.namprd00.prod.outlook.com.
