You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 18, 2021. It is now read-only.
As pointed out in #1472 (comment), it would be helpful for the maintainers of this repository to have a documented policy for when (if ever) it's suitable to lock conversations. Such a policy would ensure consistent and fair use of the locking feature. This issue tracks the task of creating that policy.
Example use cases
In order to improve our understanding of when and how locking would help us, let's gather evidence and collecting examples of conversations in this repo which could potentially benefit from locking, by updating this list:
@TPS@clarkbw@cirosantilli Maybe we should lock #283 at least temporarily as per #283 (comment), as an experiment to see whether locking can help or causes more problems than it solves?
As pointed out in #1472 (comment), it would be helpful for the maintainers of this repository to have a documented policy for when (if ever) it's suitable to lock conversations. Such a policy would ensure consistent and fair use of the locking feature. This issue tracks the task of creating that policy.
Example use cases
In order to improve our understanding of when and how locking would help us, let's gather evidence and collecting examples of conversations in this repo which could potentially benefit from locking, by updating this list:
The text was updated successfully, but these errors were encountered: