Browse code

Improved wording of a maintainer's responsibilities

Solomon Hykes authored on 2013/05/29 13:33:48
Showing 1 changed files
... ...
@@ -150,10 +150,10 @@ You don't have to be a maintainer to make a difference on the project!
150 150
 
151 151
 It is every maintainer's responsibility to:
152 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
153
+* 1) Expose a clear roadmap for improving their component.
154
+* 2) Deliver prompt feedback and decisions on pull requests.
155
+* 3) Be available to anyone with questions, bug reports, criticism etc. on their component. This includes irc, github requests and the mailing list.
156
+* 4) Make sure their component respects the philosophy, design and roadmap of the project.
157 157
 
158 158
 ### How is this process changed?
159 159