Skip to content
This repository was archived by the owner on Apr 23, 2020. It is now read-only.
This repository was archived by the owner on Apr 23, 2020. It is now read-only.

Proper usage of labels #3

@luap42

Description

@luap42

Hello, I have created a system of labels. I will present it here so that every moderator can follow it and everyone else can understand it.

Proposing labels to my Issue/PR

Please prepend your Issue/PR title with the proposed labels:

[type: bug] Oh no it does not work :(

Category 1: Moderator-labels

Moderator-labels are prepended by an @. There are three at time of writing. Only one can be active per post:

  • @ANNOUNCEMENT for important announcements about ShitHub.
  • @CRITICAL for bug-reports that are critical and shall be fixed as soon as possible.
  • @IMPORTANT for everything else moderators think that is important.

Category 2: Document state (only for PR)

The document state is prepended by an is: . There are five document states. Only one can be active per post:

  • is: First Draft for plans and Ideas without any implementation
  • is: Implementation Candidate for drafts with a positive response and without an implementation but with a precise implementation plan
  • is: Request for Comments for an implemented version of a draft. Please comment to remove bugs and improve this solution (of course you can also commit to the PR)
  • is: Ready to merge for implementations ready to be merged to the main branch
  • is: Implemented for implementations merged to the main branch.

Category 3: Proposal state

The proposal state is prepended by a proposal-status: . There are three proposal states. A post can habe more than one of those:

  • proposal-status: Need more information if the proposal/document contains not enough information to give an appropriate answer.
  • proposal-status: Not reproducable if it is not possible to reproduce the problem
  • proposal-status: Reproducable if it is possible to reproduce the problem

Category 4: Concept state (only for Issue)

The concept state is prepended by a status: . There are six concept states. Only one can be active per post:

  • status: open: no action has been taken yet
  • status: duplicate: this is an exact duplicate of an other post (please sepcify the original post in a comment)
  • status: inwork: we are working at this post. please wait a bit and do not ask every hour/day ...
  • status: accepted: we accepted the proposal of this post but have not implemented it yet.
  • status: declined: we declined the proposal of this post. (please specify the reason for this in a comment)
  • status: completed: we accepted the proposal and implemented it.

Category 5: Post type

There are three post types. Only one can be set per post:

  • type: bug for bug reports
  • type: enhancement for ideas/enhancement proposals
  • type: information for informations about this system.

Please give me some feedback to this system.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions