This is not an abstract debate. I'm co-chairing the recently-chartered jsonpath WG and the co-editors said "we can use GitHub, right?"
We have to face the fact that this will inevitably create two separate channels where design discussions will occur; GitHub issues and the mailing list. On the other hand, I appreciate the commitment of co-editors and am very reluctant to tell them they shouldn't use the tools that make them productive.
[BTW, as we discuss this let's keep a clear discussion between the admittedly-arcane git semantics and the fairly-reasonable issue/diff management offered by GitHub.]
People who find all this worrying should start girding up their loins for the inevitable wave of people wanting to take it all to Slack… [/me ducks]
On Thu, Jan 7, 2021 at 10:35 AM Joel M. Halpern <jmh@xxxxxxxxxxxxxxx> wrote:
On whether I have watched git, I have seen the emails that git produces.
As other people have commented, they are extremely hard to use for a
discussion. That is why I keep talking about useful and udnerstandable
emails.
Yours,
Joel
On 1/7/2021 1:21 PM, Salz, Rich wrote:
>> Sorry, a once a week summary, no matter how good, does not let someone
> engage in the conversation. Also, responding to emails from such a
> summary in a fashion that is understandable is quite difficult.
>
> Your also comment brings to mind a question I asked earlier: did you ever subscribe to the RISKS or other digests? Ever reply to a posting there?
>
> Have you followed any GitHub repo's, and seen the email that comes when someone comments on an issue or pull request? Did you know you can click on "watch"? https://docs.github.com/en/free-pro-team@latest/github/managing-subscriptions-and-notifications-on-github/configuring-notifications
>
>> So no, I do not consider that a useful middle ground.
>
> Your turn to make a proposal.
>
>
