tyler.durden
/
vim-airline
mirror of https://github.com/vim-airline/vim-airline.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Updated Becoming a Maintainer (markdown)

Bailey Ling 2016-01-14 22:03:12 -05:00
parent 972590a5c1
commit fde6c3235a
1 changed files with 16 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
Becoming-a-Maintainer.md

@ -7,6 +7,20 @@ We always welcome people who are interested in becoming a maintainer.
It's simple.
1. Show a history of contributions to the project.
2. Request to be a maintainer.
2. Request to be a maintainer by choosing your desired role(s).
The first point is self-explanatory. We like friendly faces over strangers. That and it gives you a taste of what's required to be a maintainer.
# Roles
## Code
If you're on GitHub, this is probably your natural element. Bugs need to get fixed, features need to get implemented. PRs need to be tested and merged, or rejected if it doesn't suite the project goals.
## Issue Triage
Issues need to be groomed and categorized into feature requests or bugs. For the latter, it may require that you create a virtual machine to replicate the exact environment of the user who sees an error to reproduce. It's not uncommon for bugs to be OS *and* desktop environment dependent.
## Documentation
One of the most commonly raised issues is how to configure Powerline fonts. What this illustrates is that the README and Wiki are still insufficient. Other times an issue may be raised based on a misinterpretation of a phrase. TLDR; English is hard, let's make it easier.