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

Would the MCB fix rule be high priority? #7230

Closed

Description

@ivysrono

For example:
#6941
#6956

Activity

  1. J0WI commented on Sep 30, 2016

    @J0WI
    Contributor

    Personally I don't think so. The Torbrowser is not affected by MCB issues and users can easily bypass them or disable the rule.

  2. jeremyn commented on Sep 30, 2016

    @jeremyn
    Contributor

    We have almost 400 open issues and very few people working on them so we have to be very conservative about what High Priority means.

    High Priority to me includes:

    • core functionality for mega-sites like Google or Facebook is completely broken
    • the add-on is entirely unusable for a large group of users, like all Chrome users, or all Mac users, or all Brazilian Portuguese users
    • there is a serious security problem like a ruleset that secretly redirects users to download virus-infected software
    • something is breaking all builds

    I can't think of anything else.

    If you think something should be high priority then ping us reviewers and explain why you think it's high priority, like "This is the most important social networking site in $COUNTRY and this problem is preventing anyone from logging in."

    Just my opinion, @fuglede @Hainish @J0WI what do you think?

  3. Hainish commented on Oct 11, 2016

    @Hainish
    Member

    I would add to this conflicts with other commonly used extensions. For instance, if HTTPS Everywhere disabled all other extensions from functioning, that would also be high priority.

  4. Hainish commented on Oct 11, 2016

    @Hainish
    Member

    Perhaps more generally "disrupts the functioning of other user-installed software" or something.

  5. jeremyn commented on Oct 11, 2016

    @jeremyn
    Contributor

    I would classify that under "entirely unusable for a large group of users".

  6. Hainish commented on Oct 12, 2016

    @Hainish
    Member

    The phrase "the add-on is entirely unusable for a large group of users" makes it sound like you are referring to HTTPS Everywhere being rendered unusable, not other addons becoming unusable due to HTTPS Everywhere.

  7. jeremyn commented on Oct 12, 2016

    @jeremyn
    Contributor

    That's a fair point.

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

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions