Skip to content
This repository was archived by the owner on Nov 18, 2021. It is now read-only.
This repository was archived by the owner on Nov 18, 2021. It is now read-only.

[Meta] create policy around locking of conversations #1594

Open

Description

@aspiers

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:

Activity

  1. aspiers commented on Jun 11, 2019

    @aspiers
    CollaboratorAuthor

    @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?

  2. cirosantilli commented on Jun 11, 2019

    @cirosantilli
    Collaborator

    I'd rather not interfere with people's commenting, it's gonna be hard.

    What we really need is: #601 and #1008 :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions