diff --git a/.github/workflows/close_old_issues.yml b/.github/workflows/close_old_issues.yml index f93386d4f..88bc3b143 100644 --- a/.github/workflows/close_old_issues.yml +++ b/.github/workflows/close_old_issues.yml @@ -15,20 +15,20 @@ jobs: stale-issue-message: | We need some feedback on this issue. - Now we mark this as "stale" because there was no activity here for 14 days. + Now we mark this as "Abandoned" because there was no activity here for 14 days. - Remove the "stale" label or comment else this will be closed in 7 days. + Remove the "Stale" label or comment else this will be closed in 7 days. stale-pr-message: | We need some feedback on this pull request. - Now we mark this as "stale" because there was no activity here for 14 days. + Now we mark this as "Abandoned" because there was no activity here for 14 days. - Remove the "stale" label or comment else this will be closed in 7 days. + Remove the "Stale" label or comment else this will be closed in 7 days. close-issue-message: | As there was no activity here for a while we close this issue. But don't worry, the conversation is still here and you can get back to it at any time. - So feel free to comment if you have remarks or ideas on this topic. + Feel free to comment if you have remarks or ideas on this topic. days-before-stale: 14 days-before-close: 7 - exempt-issue-labels: 'pinned, next major, next minor, shaping, ready for development' - exempt-pr-labels: 'pinned, next major, next minor' + exempt-issue-labels: 'important' + exempt-pr-labels: 'important' diff --git a/docs/CONTRIBUTING.rst b/docs/CONTRIBUTING.rst index 092529f28..fcc4fb160 100644 --- a/docs/CONTRIBUTING.rst +++ b/docs/CONTRIBUTING.rst @@ -33,16 +33,13 @@ Mid and large scale issues are discussed in `Feature planning `__ : -We are using GitHub Labels to show the state of the issue: +- ``Simple``: Good choice to get started with LVGL contribution +- ``PR needed``: We investigated the issue but it still needs to be implemented +- ``Review needed``: A Pull request is opened and it needs review/testing -- ``planning``: Still discussing how to approach it. -- ``outlined``: We have come to a conclusion and the feature is ready to be developed. -- ``request-change()``: Each core member has a dedicated label, and when they request a change, they add their label. -- ``under development``: It's being developed by someone (can be developed only if no change is requested by the end of the cool-down phase). -- ``ready``: The pitch is developed and merged into master. -- ``stale``: Inactive, can be warmed up. -- ``rejected``: Not interested in this feature for some reason. .. _contributing_pull_request: