Quick summary:

1. Callable syntax: Support for shorthand syntax remains unanimous. There was a pretty heated debate about the last remaining question: should the PEP have shorthand only or extended syntax as well? I've added details in the doc. 

   Takeaway: We’ve been discussing this topic for months now and there are *no* prospects of a firm consensus on extended syntax. Given that the 3.11 deadline is early May 2022 and we will probably need to iterate on the PEP based on SC feedback, the current plan is for us to go ahead and draft the PEP with shorthand syntax. Hopefully, we can implement it, submit it to the Steering Council, and get it approved (can take ~2 months) before the deadline for 3.11.

2. Precise types for **kwargs: People said this is a valuable feature. The main remaining question is about bikeshedding: **kwargs: Unpack[Movie] vs Expand[Movie] vs **Movie.

3. Better discussion forum than typing-sig: Email threads here lack code markup and syntax highlighting, don't have a convenient "like" button that people actually use, and can be hard to follow after a while. We settled on trying out GitHub Discussions for about a month to see if there are major drawbacks compared to typing-sig. I've mentioned the pros and cons in the doc. 

  Sebastian Rittau volunteered to clean up the python/typing GitHub repo so that we can use it. Sebastian: Could you let us know when we can start moving discussions there? (If python/typing isn't feasible due to noisy help-related questions and we can't filter it easily, we might need a separate repo for typing-sig.)