p4u1/docker-cli
0
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Improved wording of a maintainer's responsibilities

Browse Source 
Upstream-commit: dc1fa0745f779d8c9a513dea71021d263b89ca5f
Component: engine
This commit is contained in:
Solomon Hykes
2013-05-28 22:33:48 -06:00
parent 4ba126a045
commit 17eaf8b8af
1 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
components/engine/CONTRIBUTING.md
View File

@ -150,10 +150,10 @@ You don't have to be a maintainer to make a difference on the project!
It is every maintainer's responsibility to:
# Be aware of which pull requests they must review, and do so quickly
# Communicate clearly and transparently with other maintainers
# Be available to anyone with questions, bug reports, criticism etc. on their component. This includes irc, github requests and the mailing list.
# Make sure they respect the philosophy and design of the project
* 1) Expose a clear roadmap for improving their component.
* 2) Deliver prompt feedback and decisions on pull requests.
* 3) Be available to anyone with questions, bug reports, criticism etc. on their component. This includes irc, github requests and the mailing list.
* 4) Make sure their component respects the philosophy, design and roadmap of the project.
### How is this process changed?