...
|
...
|
@@ -139,9 +139,9 @@ Solomon.
|
139
|
139
|
|
140
|
140
|
### How can I become a maintainer?
|
141
|
141
|
|
142
|
|
-Step 1: learn the component inside out
|
143
|
|
-Step 2: make yourself useful by contributing code, bugfixes, support etc.
|
144
|
|
-Step 3: volunteer on the irc channel (#docker@freenode)
|
|
142
|
+* Step 1: learn the component inside out
|
|
143
|
+* Step 2: make yourself useful by contributing code, bugfixes, support etc.
|
|
144
|
+* Step 3: volunteer on the irc channel (#docker@freenode)
|
145
|
145
|
|
146
|
146
|
Don't forget: being a maintainer is a time investment. Make sure you will have time to make yourself available.
|
147
|
147
|
You don't have to be a maintainer to make a difference on the project!
|
...
|
...
|
@@ -149,10 +149,11 @@ You don't have to be a maintainer to make a difference on the project!
|
149
|
149
|
### What are a maintainer's responsibility?
|
150
|
150
|
|
151
|
151
|
It is every maintainer's responsibility to:
|
152
|
|
- a) be aware of which pull requests they must review, and do so quickly
|
153
|
|
- b) communicate clearly and transparently with other maintainers
|
154
|
|
- c) be available to anyone with questions, bug reports, criticism etc. on their component. This includes irc, github requests and the mailing list.
|
155
|
|
- d) make sure they respect the philosophy and design of the project
|
|
152
|
+
|
|
153
|
+# Be aware of which pull requests they must review, and do so quickly
|
|
154
|
+# Communicate clearly and transparently with other maintainers
|
|
155
|
+# Be available to anyone with questions, bug reports, criticism etc. on their component. This includes irc, github requests and the mailing list.
|
|
156
|
+# Make sure they respect the philosophy and design of the project
|
156
|
157
|
|
157
|
158
|
### How is this process changed?
|
158
|
159
|
|