delei opened a new issue, #681:
URL: https://github.com/apache/fesod/issues/681

   ## Background
   
   Our repository accumulates many issues that become stale over time due to 
lack of response from issue reporters or insufficient information. These stale 
issues create noise and make it difficult to focus on active, actionable items.
   
   
   ## Proposal
   Use GitHub Actions to check the created issues. Implement an automated 
system to manage inactive issues by labeling them and eventually closing them 
if they remain unresponsive for extended periods.
   
   
   ## Solution
   
   It is mainly divided into those steps to achieve it.
   
   ### Phase 1: Label Assignment
   
   I suggest that only the labels corresponding to the features should trigger 
the subsequent automatic processing procedures.
   
   - **Trigger**: Issues that have been waiting for feedback from the reporter 
for an extended period (e.g., after maintainer response but no follow-up)
   - **Action**: Apply the `waiting for feedback` label
   - **Criteria**: Issue has been inactive for a configurable period 
(suggested: **14 days** after last maintainer comment)
   
   
   ### Phase 2: Closure Warning
   
   - **Trigger**: **30 days** after the `waiting for feedback` label is applied
   - **Condition**: No new comments or activities during this period
   - **Action**: Bot posts a closure warning comment using the template below
   
   ```
   This issue has been automatically marked as stale because it has not had 
recent activity for 30 days. It will be closed in next 7 days if no further 
activity occurs.
   ``
   
   ### Stage 3: Auto-Closure
   
   - **Trigger**: 7 days after the closure warning is posted
   - **Condition**: No new responses or activities
   - **Action**: Automatically close the issue with a final comment
   
   ```
   This issue has been closed because it has not received response for too long 
time. You could reopen it if you encountered similar problems in the future.
   ```
   
   ## Benefits
   
   - **educed Noise**: Automatically removes stale issues that are unlikely to 
be resolved
   - **Better Resource Allocation**: Maintainers can focus on active, 
actionable issues
   - **Improved User Experience**: Clear communication about issue lifecycle 
and expectations
   - **Repository Health**: Maintains a cleaner issue tracker with relevant, 
current items


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to