From f4cf7e41901cdc54108a2f0e83c45b36c07a942e Mon Sep 17 00:00:00 2001 From: Josh Hawkins <32435876+hawkeye217@users.noreply.github.com> Date: Thu, 30 Apr 2026 12:47:58 -0500 Subject: [PATCH] change pinned to planned --- .github/pull_request_template.md | 2 +- .github/workflows/stale.yml | 4 ++-- CONTRIBUTING.md | 2 +- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md index 81d448f25..482f9939f 100644 --- a/.github/pull_request_template.md +++ b/.github/pull_request_template.md @@ -26,7 +26,7 @@ _Please read the [contributing guidelines](https://github.com/blakeblackshear/fr - This PR fixes or closes issue: fixes # - This PR is related to issue: -- Link to discussion with maintainers (**required** for large/pinned features): +- Link to discussion with maintainers (**required** for any large or "planned" features): ## For new features diff --git a/.github/workflows/stale.yml b/.github/workflows/stale.yml index 011f70afd..34bc2628b 100644 --- a/.github/workflows/stale.yml +++ b/.github/workflows/stale.yml @@ -19,8 +19,8 @@ jobs: days-before-stale: 30 days-before-close: 3 exempt-draft-pr: true - exempt-issue-labels: "pinned,security" - exempt-pr-labels: "pinned,security,dependencies" + exempt-issue-labels: "planned,security" + exempt-pr-labels: "planned,security,dependencies" operations-per-run: 120 - name: Print outputs env: diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 9cb575d37..74f59d011 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -12,7 +12,7 @@ If you've found a bug and want to fix it, go for it. Link to the relevant issue Every new feature adds scope that the maintainers must test, maintain, and support long-term. Before writing code for a new feature: -1. **Check for existing discussion.** Search [feature requests](https://github.com/blakeblackshear/frigate/issues) and [discussions](https://github.com/blakeblackshear/frigate/discussions) to see if it's been proposed or discussed. Pinned feature requests are on our radar — we plan to get to them, but we don't maintain a public roadmap or timeline. Check in with us first if you have interest in contributing to one. +1. **Check for existing discussion.** Search [feature requests](https://github.com/blakeblackshear/frigate/issues) and [discussions](https://github.com/blakeblackshear/frigate/discussions) to see if it's been proposed or discussed. Feature requests tagged with "planned" are on our radar — we plan to get to them, but we don't maintain a public roadmap or timeline. Check in with us first if you have interest in contributing to one. 2. **Start a discussion or feature request first.** This helps ensure your idea aligns with Frigate's direction before you invest time building it. Community interest in a feature request helps us gauge demand, though a great idea is a great idea even without a crowd behind it. 3. **Be open to "no".** We try to be thoughtful about what we take on, and sometimes that means saying no to good code if the feature isn't the right fit for the project. These calls are sometimes subjective, and we won't always get them right. We're happy to discuss and reconsider.