Reviewing pull request guidelines favor Slack and calls over written comments #5027
Labels
area/docs
kind/documentation
Issue is a documentation task
lifecycle/rotten
priority/important-soon
Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
The Reviewing pull request guidelines at various points suggest to use Slack or calls over using comments on issues and pull request.
IMO this is the wrong default for an OSS project. Discussions should for transparency reasons occur as much as possible on issues and pull request.
I also think that contrary to what the docs suggest written discussions are less heated than Slack conversations or calls.
Having conversations on Slack or on calls makes it much harder for other (community) members to participate.
The text was updated successfully, but these errors were encountered: