8000 clarifying intended label usage (#101) · onware/document-api-python@d55f126 · GitHub
[go: up one dir, main page]

Skip to content

Commit d55f126

Browse files
author
Russell Hay
authored
clarifying intended label usage (tableau#101)
1 parent 9e1d875 commit d55f126

File tree

1 file changed

+22
-0
lines changed

1 file changed

+22
-0
lines changed

contributing.md

Lines changed: 22 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -23,6 +23,28 @@ files to assist in the repro. **Be sure to scrub the files of any potentially s
2323
For a feature request, please try to describe the scenario you are trying to accomplish that requires the feature. This will help us understand
2424
the limitations that you are running into, and provide us with a use case to know if we've satisfied your request.
2525

26+
### Label usage on Issues
27+
28+
The core team is responsible for assigning most labels to the issue. Labels
29+
are used for prioritizing the core team's work, and use the following
30+
definitions for labels.
31+
32+
The following labels are only to be set or changed by the core team:
33+
34+
* **bug** - A bug is an unintended behavior for existing functionality. It only relates to existing functionality and the behavior that is expected with that functionality. We do not use **bug** to indicate priority.
35+
* **enhancement** - An enhancement is a new piece of functionality and is related to the fact that new code will need to be written in order to close this issue. We do not use **enhancement** to indicate priority.
36+
* **CLARequired** - This label is used to indicate that the contribution will require that the CLA is signed before we can accept a PR. This label should not be used on Issues
37+
* **CLANotRequired** - This label is used to indicate that the contribution does not require a CLA to be signed. This is used for minor fixes and usually around doc fixes or correcting strings.
38+
* **help wanted** - This label on an issue indicates it's a good choice for external contributors to take on. It usually means it's an issue that can be tackled by first time contributors.
39+
40+
The following labels can be used by the issue creator or anyone in the
41+
community to help us prioritize enhancement and bug fixes that are
42+
causing pain from our users. The short of it is, purple tags are ones that
43+
anyone can add to an issue:
44+
45+
* **Critical** - This means that you won't be able to use the library until the issues have been resolved. If an issue is already labeled as critical, but you want to show your support for it, add a +1 comment to the issue. This helps us know what issues are really impacting our users.
46+
* **Nice To Have** - This means that the issue doesn't block your usage of the library, but would make your life easier. Like with critical, if the issue is already tagged with this, but you want to show your support, add a +1 comment to the issue.
47+
2648
## Fixes, Implementations, and Documentation
2749

2850
For all other things, please submit a PR that includes the fix, documentation, or new code that you are trying to contribute. More information on

0 commit comments

Comments
 (0)
0