docker/cli
1
0
Fork 0
mirror of https://github.com/docker/cli.git synced 2026-01-15 07:40:57 +03:00
Code Activity

use a numbered list for maintainers responsibility

Browse Source 
At the moment maintainers responsibility are spelled out with a hybrid
list. I.e. an unordered list with an associated number.

In this commit I the number list proper is used.

Docker-DCO-1.1-Signed-off-by: Daan van Berkel <daan.v.berkel.1980@email.com> (github: dvberkel)
Upstream-commit: cc96d312526dac5eff3e0521b921e08301715ce5
Component: engine
This commit is contained in:
Daan van Berkel
2014-06-13 06:51:54 +02:00
parent 219f245ad1
commit 14681fef9b
1 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
components/engine/hack/MAINTAINERS.md
View File

@@ -24,12 +24,12 @@ speak up!
It is every maintainer's responsibility to:
* 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.
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
4. Make sure their component respects the philosophy, design and
roadmap of the project.
## How are decisions made?