Cheers to former maintainers 🙌

* Removing inactive maintainers * Being explicit about how we check for activity * Swapping my @name given I [changed my name](https://medium.com/@mbbroberg/i-have-a-maiden-name-58207e099e78)
intelsdi-x · Jun 16, 2017 · 20d886f · 20d886f
1 parent bf49679
commit 20d886f
Show file tree

Hide file tree

Showing 2 changed files with 20 additions and 23 deletions.
diff --git a/docs/AUTHORS.md b/docs/AUTHORS.md
@@ -12,7 +12,7 @@
 [@lmroz](https://github.com/lmroz)  
 [@lynxbat](https://github.com/lynxbat)  
 [@marcin-krolik](https://github.com/marcin-krolik)  
-[@mjbrender](https://github.com/mjbrender)  
+[@mbbroberg](https://github.com/mbbroberg)  
 [@nqn](https://github.com/nqn)  
 [@PatrykMatyjasek](https://github.com/PatrykMatyjasek)  
 [@ppalucki](https://github.com/ppalucki)  

diff --git a/docs/MAINTAINERS.md b/docs/MAINTAINERS.md
@@ -14,41 +14,38 @@ While our maintainers guide Snap, the plugins, and the community forward in a po
 ## Snap Maintainers
 Below is the list of Snap Maintainers, they are largely responsible for approving pull requests and thus have the final say on coding style and implementation. 
 
-| Name              | Tag                |
-|:------------------|:-------------------|
-| Andrzej Kuriata   | @andrzej-k         |  
-| Cody Roseborough  | @IRCody            |  
-| Emily Gu          | @candysmurf        |  
-| Izabella Raulin   | @IzabellaRaulin    |  
-| Joel Cooklin      | @jcooklin          |  
-| Katarzyna Kujawa  | @katarzyna-z       |  
-| Kelly Lyon        | @kjlyon            |  
-| Lukasz Mroz       | @lmroz             |  
-| Marcin Krolik     | @marcin-krolik     |  
-| Marcin Olszewski  | @marcintao         |  
-| Marcin Spoczynski | @sandlbn           |  
-| Maria Rolbiecka   | @mkuculyma         |  
-| Mateusz Kleina    | @mkleina           |  
-| Matt Brender      | @mjbrender         |  
-| Nicholas Weaver   | @lynxbat           |  
-| Olivier Cano      | @kindermoumoute    |  
-| Patryk Matyjasek  | @PatrykMatyjasek   |
-| Rashmi Gottipati  | @rashmigottipati   |  
+| Name              | Tag              |
+|:------------------|:-----------------|
+| Andrzej Kuriata   | @andrzej-k       |
+| Emily Gu          | @candysmurf      |
+| Izabella Raulin   | @IzabellaRaulin  |
+| Joel Cooklin      | @jcooklin        |
+| Katarzyna Kujawa  | @katarzyna-z     |
+| Kelly Lyon        | @kjlyon          |
+| Lukasz Mroz       | @lmroz           |
+| Marcin Krolik     | @marcin-krolik   |
+| Marcin Olszewski  | @marcintao       |
+| Marcin Spoczynski | @sandlbn         |
+| Maria Rolbiecka   | @mkuculyma       |
+| Mateusz Kleina    | @mkleina         |
+| Matt Broberg      | @mbbroberg       |
+| Patryk Matyjasek  | @PatrykMatyjasek |
+| Rashmi Gottipati  | @rashmigottipati |
 
 ### Responsibilities of Snap Maintainers
 Maintainers are expected to contribute regularly in at least one of the following capacities:
 * Direction/Design: Meaningfully contributing to RFC or design comments
 * Code Contributions: Submitting pull requests for either bug fixes or features
 * Support: Active participation in a support role in some form (code reviews, addressing questions, triaging issues)
 
-If a maintainer is consistently unable to perform the above actions they will be asked to withdraw from the maintainer group. This does not preclude them from becoming a maintainer at a later date.
+Maintainer participation is measured by activity visible on their GitHub overview page ([example](https://github.com/mbbroberg#overview)) and in our [public Slack](http://slack.snap-telemetry.io). If a maintainer is consistently unable to perform the above actions they will be asked to withdraw from the maintainer group. This does not preclude them from becoming a maintainer at a later date.
 
 ## Initial Authors
 All contributors are equally important to us, but we would like to thank the [initial authors](AUTHORS.md#initial-authors) for helping make open sourcing Snap possible.
 
 ## Contact Us
 Contacting us is easy! Use these simple tips for the most effective communication with us.
-* **For a quick question:** reach out to us on [Slack](https://intelsdi-x.herokuapp.com/). You can search by GitHub handles and ping individual users, start a group conversation, and post to the Snap community. Maintainers check this regularly and will be the fastest way of contacting us.
+* **For a quick question:** reach out to us on [Slack](https://slack.snap-telemetry.io). You can search by GitHub handles and ping individual users, start a group conversation, and post to the Snap community. Maintainers check this regularly and will be the fastest way of contacting us.
 * **If you find a bug in the code or have a question about some code:** go ahead and [open up a GitHub issue](https://github.com/intelsdi-x/snap/issues). This will start a dialog. If you don't know how to solve the issue we will pick it up and help fix the bug. 
 * **To get a specific person's attention:** @mention them in an issue and they will get back to you.
 * **For plugin related issues:** contact the plugin's author or reach out to a maintainer.