Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Outline Hubot Evolution process #1

Merged
merged 13 commits into from
May 24, 2017
+95 −1
Merged

Outline Hubot Evolution process #1

Changes from 1 commit
Commits
Show all changes
13 commits
Select commit Hold shift + click to select a range
12f0371
Inherit process from Swift
bkeepers May 19, 2017
f6e7b39
Add template
bkeepers May 20, 2017
b2a3426
Change status name
bkeepers May 20, 2017
82ef75d
Author is responsible for implementation
bkeepers May 20, 2017
b73e0eb
File naming and when to merge
bkeepers May 20, 2017
94f8fb2
Consistent capitalization
bkeepers May 20, 2017
533f578
Add state config
bkeepers May 21, 2017
ae5bacc
Update state.yml
bkeepers May 21, 2017
f46f108
Add project, update states
bkeepers May 21, 2017
35881a6
Link to project board
bkeepers May 21, 2017
bb25c27
Update states
bkeepers May 21, 2017
51a8719
Update state in template
bkeepers May 21, 2017
dd13479
Link to project board
bkeepers May 21, 2017
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
File naming and when to merge
@bkeepers
bkeepers committed May 20, 2017

Unverified

The committer email address is not verified.
Learn about vigilant mode
commit b73e0eb5cd378f7e23fe7dfc58f2501b551e06d1
4 changes: 3 additions & 1 deletion CONTRIBUTING.md
View file
Original file line number Diff line number Diff line change
@@ -39,7 +39,9 @@ Reviews should usually be completed in a single week, but can run longer for par

After feedback from the community has been gathered, the maintainers will make a decision on whether to `accept` or `reject` the proposal.

Once a proposal has been accepted, it is usually up to the proposal author to implement it or discuss with the maintainers who will lead the implementation.
Once a proposal has been accepted, the file should be renamed to `proposals/###-feature-name.md`, where `###` is the Pull Request number. It is usually up to the proposal author to implement it or discuss with the maintainers who will lead the implementation.

Once a proposal has been implemented, the Pull Request will be merged.

## Proposal states