Skip to content

Commit 8056ffc

Browse files
author
Tim Roberts
authored
Update information on using the 'Proposal' issue template
1 parent 0ac74eb commit 8056ffc

File tree

1 file changed

+4
-7
lines changed

1 file changed

+4
-7
lines changed

docs/contributing.md

Lines changed: 4 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -21,13 +21,10 @@ If possible, try and include an _isolated_ way in which the bug can be reproduce
2121
and actual behaviors. When creating your bug, please add the `'C-bug'` label to it.
2222

2323
## Have an idea for an improvement, or a new feature?
24-
We also accept _proposals_ for features or ideas as issues. When creating a _proposal_, please ensure to add the
25-
`'C-proposal'` label to it so that we can triage and track it on the
26-
[Proposal GitHub Project](https://github.com/orgs/p4lang/projects/1/views/1).
27-
28-
We use the [Proposal GitHub Project](https://github.com/orgs/p4lang/projects/1/views/1) to roadmap planned development
29-
effort, and as proposals are drafted and then elaborated upon, we anticipate discussion and questions appearing on your
30-
particular _proposal_ issue in order to help with that process.
24+
We also accept _proposals_ for features or ideas as issues. Use the 'Proposal' Issue template to ensure that your new
25+
issue has the `'C-proposal'` label applied to it. Internally, we use private GitHub Projects to roadmap planned
26+
development and as proposals are drafted, and then elaborated upon, we anticipate discussion and questions appearing
27+
on your particular _proposal_ issue in order to help with that process.
3128

3229
More information about how we process, manage and ultimately deliver proposals can be found in the
3330
[Issue Life-Cycle](./issue-lifecycle.md) under the _Proposal Issues_ section.

0 commit comments

Comments
 (0)