Skip to content

Suggestion: use labels sparingly #250

Description

@mouse07410

Look at other popular and widely-used projects on GitHub, such as https://github.com/openssl/OpenSSL.git and https://github.com/OpenSC/OpenSC.git

Both have tons of issues to process, but an issue would have maybe one, at most two labels. Here I see it rare for an issue to have less than four labels, usually five or six.

Please reconsider, and stop throwing every possibly-remotely-applicable label at an issue - it's both confusing and annoying to the viewer. Pick one that's the closest, and stay with it.

My $0.02.

Activity

  1. jordangov commented on Mar 14, 2019

    @jordangov
    Contributor

    @mouse07410 That's totally valid, and I would lean that way as well. However, the Code.gov website will scrape issues from our open source repositories and display them on their site - along with other Federal Government open source projects - in a single UI. In order for that page to have filtering capabilities it uses labels like the ones you see here. So, for the time being, we'll need to keep the labels as they are.

    (I'll leave this issue open for a bit just so others can comment/read if they wish.)

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

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions