forked from AcademySoftwareFoundation/openfx
-
Notifications
You must be signed in to change notification settings - Fork 36
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
standard-change: set git attribute to text
- Loading branch information
Showing
1 changed file
with
22 additions
and
22 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,23 +1,23 @@ | ||
| # Open Effects Proposal for Standard Change | ||
|
|
||
| Please read the contribution [guidelines](https://github.com/ofxa/openfx/wiki/Extending-OpenFX-Guidelines#submit-a-proposal-or-bug-report-to-review) first. | ||
|
|
||
| ## Standard Change Workflow | ||
| - [ ] Create proposal as issue (you're doing this now!) | ||
| - [ ] Tag this issue with `standard change` tag | ||
| - [ ] Identify subcommittee: at least one plug-in vendor, and at least one host | ||
| - [ ] Discuss the idea in this issue | ||
| - [ ] Write new or updated code | ||
| - [ ] Publish updates as a pull request on a `feature/PROPOSAL-NAME` branch | ||
| - [ ] Make sure that PR references this issue number to keep them in sync | ||
| - [ ] Discuss and review code in the PR | ||
| - [ ] When subcommittee signs off and other members don't have any further review comments, | ||
| maintainer merges PR to master which closes PR and issue | ||
|
|
||
| ## Problem | ||
|
|
||
| What problem does this proposed change solve? Be specific, concise, and clear. | ||
|
|
||
| ## Stakeholders | ||
|
|
||
| # Open Effects Proposal for Standard Change | ||
|
|
||
| Please read the contribution [guidelines](https://github.com/ofxa/openfx/wiki/Extending-OpenFX-Guidelines#submit-a-proposal-or-bug-report-to-review) first. | ||
|
|
||
| ## Standard Change Workflow | ||
| - [ ] Create proposal as issue (you're doing this now!) | ||
| - [ ] Tag this issue with `standard change` tag | ||
| - [ ] Identify subcommittee: at least one plug-in vendor, and at least one host | ||
| - [ ] Discuss the idea in this issue | ||
| - [ ] Write new or updated code | ||
| - [ ] Publish updates as a pull request on a `feature/PROPOSAL-NAME` branch | ||
| - [ ] Make sure that PR references this issue number to keep them in sync | ||
| - [ ] Discuss and review code in the PR | ||
| - [ ] When subcommittee signs off and other members don't have any further review comments, | ||
| maintainer merges PR to master which closes PR and issue | ||
|
|
||
| ## Problem | ||
|
|
||
| What problem does this proposed change solve? Be specific, concise, and clear. | ||
|
|
||
| ## Stakeholders | ||
|
|
||
| Who will benefit from this proposed change? Plug-ins, hosts, or both? Specific types of hosts? |