Skip to content

Commit 23092be

Browse files
committed
Add a tip section about needs maintainer attention label
1 parent 386e70c commit 23092be

1 file changed

Lines changed: 13 additions & 5 deletions

File tree

‎CONTRIBUTING.md‎

Lines changed: 13 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ By participating you agree to follow our [Code of Conduct](CODE_OF_CONDUCT.md).
77
## Ways to contribute
88

99
> [!Important]
10-
> Please only submit pull requests if you have received approval from a maintainer.
10+
> Please only submit pull requests for an issue when you have received approval from a maintainer.
1111
> While we value good intentions, we require approvals for community code contributions to ensure we use everyone's time effectively.
1212
1313
- **Report bugs** — open an issue with steps to reproduce, expected vs actual behavior, and your environment.
@@ -18,16 +18,24 @@ For security vulnerabilities, do **not** open a public issue — see [SECURITY.m
1818

1919
### Why we require approvals for community code contributions
2020

21+
> [!Tip]
22+
> Every new issue by default is labelled with [needs-maintainer-attention](https://github.com/truefoundry/trueforge/issues?q=is%3Aissue%20state%3Aopen%20label%3Aneeds-maintainer-attention). A maintainer will review the issue and discuss the next steps. Please don't remove this label while creating the issue.
23+
2124
Effective changes to TrueForge require architectural context, an understanding of system-level constraints, and visibility into the project's roadmap. Community pull requests often focus on issues that are lower priority, affect a small number of users, or need substantial changes to fit the broader system. Reviewing and iterating on those changes can take more time than implementing a fix directly, diverting attention from higher-priority work.
2225

2326
Community expertise is most valuable when shared through detailed bug reports, reproduction steps, logs, root-cause analysis, and design discussions in issues. Understanding the problem, identifying the right solution, and prioritizing the work are typically the hard parts; implementation is comparatively straightforward with coding assistants.
2427

2528
For these reasons, we focus community contributions on issue reports, analysis, and feedback, over larger code changes.
2629

27-
| Label | Meaning |
28-
| -------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------- |
29-
| [`help-wanted`](https://github.com/truefoundry/trueforge/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22help%20wanted%22) | Well-scoped issue where community contributions are welcome. |
30-
| `needs-maintainer-approval` | Proposal is still awaiting maintainer review; contributors should not start implementation yet. |
30+
> [!Note]
31+
> If you would still like to contribute code, we keep a dedicated set of issues marked as [help-wanted](https://github.com/truefoundry/trueforge/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22help%20wanted%22) that are well scoped.
32+
33+
### Issue labels
34+
35+
| Label | Meaning |
36+
| ---------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------ |
37+
| [help-wanted](https://github.com/truefoundry/trueforge/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22help%20wanted%22) | Well-scoped issue where community contributions are welcome. |
38+
| [needs-maintainer-attention](https://github.com/truefoundry/trueforge/issues?q=is%3Aissue%20state%3Aopen%20label%3Aneeds-maintainer-attention) | Issue needs discussion with maintainers before implementation can start. |
3139

3240
### Reporting bugs
3341

0 commit comments

Comments
 (0)