From 075e3ac90d3de1cce9e6a47dbc1557726304a61b Mon Sep 17 00:00:00 2001 From: despiegk Date: Thu, 13 Mar 2025 09:30:13 +0100 Subject: [PATCH] specs --- process/process.md | 38 +++++++++++++++++++ .../farming_rewards_concepts.md | 1 + ...ult revenues) distributed to DAO voters.md | 0 .../ideas_not_ready}/internal_node_hosting.md | 0 4 files changed, 39 insertions(+) create mode 100644 specs/farming_rewards/farming_rewards_concepts.md rename {ideas_not_ready => specs/ideas_not_ready}/DAO revenues (staking vault revenues) distributed to DAO voters.md (100%) rename {ideas_not_ready => specs/ideas_not_ready}/internal_node_hosting.md (100%) diff --git a/process/process.md b/process/process.md index fb1f30f..dfeba2e 100644 --- a/process/process.md +++ b/process/process.md @@ -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. +## 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 Once issues are prioritized, they follow this general workflow: diff --git a/specs/farming_rewards/farming_rewards_concepts.md b/specs/farming_rewards/farming_rewards_concepts.md new file mode 100644 index 0000000..90a1d60 --- /dev/null +++ b/specs/farming_rewards/farming_rewards_concepts.md @@ -0,0 +1 @@ +... \ No newline at end of file diff --git a/ideas_not_ready/DAO revenues (staking vault revenues) distributed to DAO voters.md b/specs/ideas_not_ready/DAO revenues (staking vault revenues) distributed to DAO voters.md similarity index 100% rename from ideas_not_ready/DAO revenues (staking vault revenues) distributed to DAO voters.md rename to specs/ideas_not_ready/DAO revenues (staking vault revenues) distributed to DAO voters.md diff --git a/ideas_not_ready/internal_node_hosting.md b/specs/ideas_not_ready/internal_node_hosting.md similarity index 100% rename from ideas_not_ready/internal_node_hosting.md rename to specs/ideas_not_ready/internal_node_hosting.md