55
66{% include nav.html active='Sponsors' %}
77
8-
98< div class ="container ">
109 < div class ="col-wide ">
1110 < h2 > Current sponsors</ h2 >
@@ -18,42 +17,46 @@ <h2>FAQ</h2>
1817 < dl class ="faqs ">
1918 < dt > What is this list?</ dt >
2019 < dd >
21- < p > These are the companies or individuals contributing a monthly amount to
22- help sustain Neovim development. See the
23- < a href ="https://salt.bountysource.com/teams/neovim "> bountysource
24- campaign</ a > for more details.</ p >
20+ < p >
21+ These are the companies or individuals contributing a monthly amount to
22+ help sustain Neovim's development. See the < a
23+ href ="https://salt.bountysource.com/teams/neovim "> Bountysource campaign</ a >
24+ for more details.
25+ </ p >
2526 </ dd >
2627
27- < dt >
28- < p > I'm a sponsor contributing $5/month but my URL is not listed,
29- which is what I expected from the bountysource reward description.
30- What is happening?</ p >
31- </ dt >
28+ < dt > I am a sponsor contributing $5/month, but my URL is not listed.</ dt >
3229 < dd >
33- < p > Bountysource does not yet provide a UI for sponsors to inform their
34- URL. Most URLs displayed in the list were obtained using the github API
35- and a heuristic to match the bountysource slug(a sort of sponsor
36- identifier) with the github username, but this method was error prone
37- and failed for many sponsors, including those that don't have a github
38- account.</ p >
39-
40- < p > If you are pledging $5/month or more and want to have your URL
41- listed, please send a PR to
42- < a href ="https://github.com/neovim/neovim.github.io/pulls ">
43- neovim.github.io</ a > with a new entry for your bountysource slug in the
44- < a href ="https://github.com/neovim/neovim.github.io/blob/master/js/sponsors-override.js ">
45- js/sponsors-override.js</ a > file. You can obtain your bountysource slug with the
46- following command:</ p >
47-
30+ < p >
31+ Bountysource does not yet have an UI for sponsors to provide their
32+ URL. Most URLs displayed in the list were obtained using the GitHub API
33+ and a heuristic to match the Bountysource slug (a sort of sponsor
34+ identifier) with the GitHub username, but this method was error prone
35+ and failed for many sponsors, including those that don't have a GitHub
36+ account.
37+ </ p >
38+ < p >
39+ If you are pledging $5/month or more and want to have your URL
40+ listed, please send a pull request to < a
41+ href ="https://github.com/neovim/neovim.github.io/pulls ">
42+ neovim.github.io</ a > with a new entry for your Bountysource slug in the < a
43+ href ="https://github.com/neovim/neovim.github.io/blob/master/js/sponsors-override.js ">
44+ js/sponsors-override.js</ a > file.
45+ If you don't have a GitHub account, you can write to the < a
46+ href ="https://groups.google.com/forum/#!forum/neovim "> Neovim mailing list</ a >
47+ instead.
48+ </ p >
49+ < p >
50+ You can obtain your Bountysource slug with the following command:
51+ </ p >
4852 < pre > < code > curl --header 'Accept: application/vnd.bountysource+json; version=2' 'https://api.bountysource.com/supporters?team_slug=neovim&per_page=10000&page=1' 2> /dev/null | python -m json.tool | grep -C5 $NAME | grep slug</ code > </ pre >
4953
50- < p > where $NAME should be replaced by your bountysource display name(as shown in the sponsor list).</ p >
54+ < p >
55+ Replace < code > $NAME</ code > by your Bountysource display name as shown in the sponsor list.
56+ </ p >
5157 </ dd >
5258
53- < dt >
54- Where are the original sponsors that used to be shown in the front page?
55- </ dt >
56-
59+ < dt > Where are the original sponsors that used to be shown on the front page?</ dt >
5760 < dd >
5861 < p >
5962 < div class ="first-level-sponsor ">
0 commit comments