From 24acf512f5216619487eb2ed7480c81732c94b34 Mon Sep 17 00:00:00 2001 From: Josh Cummings <3627351+jzheaux@users.noreply.github.com> Date: Tue, 18 Feb 2025 14:49:17 -0700 Subject: [PATCH] Updated Community Duty Tasks (markdown) --- Community-Duty-Tasks.md | 16 ++++++++++------ 1 file changed, 10 insertions(+), 6 deletions(-) diff --git a/Community-Duty-Tasks.md b/Community-Duty-Tasks.md index b7e39fe..07559e4 100644 --- a/Community-Duty-Tasks.md +++ b/Community-Duty-Tasks.md @@ -21,10 +21,14 @@ Otherwise, do the following: If it's a `type: bug`, also do the following: -1. Consider the urgency of the issue. Does it affect many users? :arrow_up: Has it been around for a long time and we are just hearing about it now? :arrow_down: Is it part of a new feature? :arrow_up: Is there an easy workaround? :arrow_down: +1. Consider the urgency of the issue: + * Does it affect many users? :arrow_up: + * Has it been around for a long time and we are just hearing about it now? :arrow_down: + * Is it part of a new feature? :arrow_up: + * Is there an easy workaround? :arrow_down: 2. Reproduce it. If you don't have enough information, ask and label with `status: waiting-for-feedback`. 3. If not a bug, label with `status: declined`. -4. If a high-urgency bug, assign to the next patch release of the earliest supported version +4. If a high-urgency bug, assign to the next patch release of the earliest supported version. 5. If a low-urgency bug, assign to the earliest supported `.x` milestone. 6. Develop a workaround and post it as a comment. 7. If an ideal-for-contribution bug, label it as `status: ideal-for-contribution` and invite the poster to contribute @@ -36,7 +40,7 @@ If it's a `type: enhancement`, do the following: 1. Evaluate it. If you don't have enough information, ask and label with `status: waiting-for-feedback`. 2. If you disagree, mark the ticket as `status: declined`. 3. If you agree, assign the appropriate milestone; either "General Backlog" or the next `.x` generation where it will fit. You might remind the contributor that tickets with votes usually happen before tickets that don't. -4. For an ideal-for-contribution feature, label it as `status: ideal-for-contribution` and invite the poster to contribute +4. For an ideal-for-contribution feature, label it as `status: ideal-for-contribution` and invite the poster to contribute. 5. Add any additional needed explanation in a comment. 6. If at this point the feature is addressed, close it. @@ -57,7 +61,7 @@ For each [contributed PR](https://github.com/spring-projects/spring-security/iss 1. Follow the same rules as **Triage Issues**. 2. If ready to merge, merge the PR. These are usually unassigned PRs where any requested changes have been approved and the issue has a concrete milestone and not just a `.x` milestone. -3. If there is an issue linked to the PR, close the issue, mark it as `status: duplicate`, and include some comment like `Superceded by {the PR number}` +3. If there is an issue linked to the PR, close the issue, mark it as `status: duplicate`, and include some comment like `Superceded by {the PR number}`. 4. If it is a simple PR, like a typo, an obvious fix, a formatting or naming convention improvement or the like, ready it for merging. #### **Answer Questions on StackOverflow** @@ -71,8 +75,8 @@ For each PR, do the same as **Triage Dependabot PRs**. #### **Check the `spring-security` Chat Channels** -1. Check the internal channel and either answer questions or ping the right person -2. Check the [gitter channel](https://gitter.im/spring-projects/spring-security) and either answer questions or ping the right person +1. Check the internal channel and either answer questions or ping the right person. +2. Check the [gitter channel](https://gitter.im/spring-projects/spring-security) and either answer questions or ping the right person. ### Schedule :calendar: