This commit is contained in:
despiegk 2025-03-13 09:30:13 +01:00
parent fcd1ff24c6
commit 075e3ac90d
4 changed files with 39 additions and 0 deletions

View File

@ -53,6 +53,44 @@ We welcome community input on our priorities. If you have feedback on what shoul
Your input helps us ensure we're focusing on what matters most to the TFGrid3 community. Your input helps us ensure we're focusing on what matters most to the TFGrid3 community.
## Issue Labels
We use a set of labels to categorize issues and provide additional context about their nature and urgency. Understanding these labels helps contributors identify the type of issues they might want to work on or provide feedback for.
### Label Types
#### Defect
Used for bugs, errors, or functionality that isn't working as expected. Defects require fixing to restore proper functionality.
#### Feedback
Applied to issues that contain community feedback, suggestions, or general input about existing features or the project as a whole.
#### Question
Marks issues that ask for clarification, information, or guidance about the project, its features, or processes.
#### Roadmap
Indicates issues that represent significant features or milestones on our development roadmap. These often involve multiple tasks and align with strategic goals.
#### Story
Represents user stories or feature requests that describe functionality from an end-user perspective.
#### Task
Denotes specific, actionable work items that need to be completed. Tasks are often more granular than stories and may be part of implementing a larger story or roadmap item. Avoid putting many tasks, team should take responsibility to resolve stories.
#### Urgent
Highlights issues that require immediate attention due to their critical nature, such as security vulnerabilities or major functionality breakdowns.
### Using Labels
When creating or interacting with issues:
1. Consider which label(s) best describe the nature of the issue
2. Look for issues with labels that match your interests or expertise if you want to contribute
3. Respect the urgency indicated by labels, particularly for "Urgent" items
4. Understand that labels may change as issues evolve or are better understood
Labels work in conjunction with milestones to provide a comprehensive view of our project's status and priorities.
## Development Workflow ## Development Workflow
Once issues are prioritized, they follow this general workflow: Once issues are prioritized, they follow this general workflow:

View File

@ -0,0 +1 @@
...