Merge pull request OWASP#1050 from za/issue-1016-90-days

Added github actions to un-assigned issues after 90 days of inactivity

.github/workflows/project-management.yml

@@ -0,0 +1,20 @@
+name: Project Management
+
+on:
+  schedule:
+    - cron: '0 2 * * *'
+
+jobs:
+  # Best used in combination with actions/stale to assign a Stale label
+  unassign-issues-labeled-waiting-for-contributor-after-90-days-of-inactivity:
+    name: Unassign issues labeled "Stale" after 90 days of inactivity.
+    if: github.event_name == 'schedule'
+    runs-on: ubuntu-latest
+    steps:
+      - uses: boundfoxstudios/action-unassign-contributor-after-days-of-inactivity@main
+        with:
+          last-activity: 90 # After how many days the issue should get unassigned
+          labels: 'stale,help wanted' # Only search for issues containing this labels (comma-separated)
+          exempt-assignees: 'Octo,Cat,bendehaan,commjoen' # Exempt some assignees from being unassigned
+          # labels-to-remove: 'Stale' # Labels to remove after unassigning an issue
+          message: 'Automatically unassigned after 90 days of inactivity.'

CONTRIBUTING.md

@@ -34,6 +34,8 @@ The minimum requirements for code contributions are:
 3. New and changed lessons _must_ have a corresponding integration test.
 4. [Status checks](https://docs.github.com/en/github/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks) should pass for your last commit.
 
+And please note that this project has *three months* implementation windows. So once you've been assigned to a task/issue, try to make your PR accepted within this period.
+
 Additionally, the following guidelines can help:
 
 ### Keep your pull requests limited to a single issue