55
66< div class ="container golden-grid ">
77 < div >
8- < h2 > Sponsoring Neovim development</ h2 >
9- < dl class ="faqs ">
10- < dt > How can I sponsor Neovim?</ dt >
11- < dd >
12- < p >
13- You can sponsor Neovim via < a href ="https://github.com/sponsors/neovim "> GitHub Sponsors</ a >
14- or < a href ="https://opencollective.com/neovim "> Open Collective</ a > .
15- This makes it possible for core developers to work full-time for
16- a month or longer, accelerating projects like Lua stdlib, treesitter
17- parser engine, LSP framework, extended marks, embedded terminal, job
18- control, RPC API, and remote UIs.
8+ < h1 > Sponsor Neovim</ h1 >
199
20- Sponsorship is very rarely used to maintain (very minimal) infrastructure
21- costs for the Neovim project, such as hosting fees. 99.999% of the funding goes directly to funding
22- development work.
23- </ p >
24- </ dd >
25- < dt > How are funds dispersed?</ dt >
26- < dd >
27- < p >
28- Donations are managed via < a href ="https://opencollective.com/neovim "> Open Collective</ a > , which
29- provides public tracking for all
30- < a href ="https://opencollective.com/neovim/expenses "> expenses</ a > . Bitcoin transactions are visible
31- on the < a href ="https://www.blockchain.com/btc/address/1Evu6wPrzjsjrNPdCYbHy3HT6ry2EzXFyQ "> blockchain
32- explorer</ a > . The only donation options for neovim are via GitHub sponsors, Open Collective, and
33- Bitcoin. All prior funding sources have been transferred into Open Collective.
34- </ p >
35- </ dd >
36- < dt > What is expected of a contributor doing funded work?</ dt >
37- < dd >
38- < p >
39- Funded work is a way to support active contributors who have weeks of time to focus on the
40- project. This opportunity is available to contributors who have a developed a reputation for
41- reliable, high-quality contributions (code/documentation, GitHub review comments, and GitHub
42- technical discussions; < i > not</ i > IRC or other "ephemeral" places).
10+ < p style ="text-align: center; margin: 2em 0; ">
11+ < a href ="https://opencollective.com/neovim/donate " class ="btn "> Donate to Neovim</ a >
12+ </ p >
4313
44- It works like this: funded contributors are expected to focus < i > full-time</ i > for weeks or
45- even months, yielding tangible, high-quality contributions, with conspicuous, reliable,
46- regular activity on GitHub.
47- </ p >
48- </ dd >
14+ < h2 > 100% of funds go to development</ h2 >
15+ < p > We don't have an "administrative" staff. Funding goes directly to software development.</ p >
16+
17+ < h2 > Funds are managed by OpenCollective</ h2 >
18+ < p >
19+ 20+ < code > Open Source Collective 501(c)(6)</ code > < br >
21+ < code > EIN: 82-2037583</ code > < br >
22+ < code > 440 N Barranca Ave #3939 Covina, CA 91723 United States</ code > < br >
23+ < code > [email protected] </ code > < br > 24+ < a href ="https://opencollective.com/opensource#category-ABOUT "> Details</ a > < br >
25+ </ p >
26+
27+ < p >
28+ You can also donate via < a href ="https://github.com/sponsors/neovim "> GitHub Sponsors</ a > ,
29+ which will be routed to OpenCollective.
30+ </ p >
31+
32+ < h2 > How are funds used?</ h2 >
33+ < p >
34+ Funding makes it possible for core developers to work full-time for
35+ a month or longer, accelerating projects like Lua stdlib, treesitter
36+ parser engine, LSP framework, extended marks, embedded terminal, job
37+ control, RPC API, and remote UIs.
38+ </ p >
39+
40+ < p >
41+ We have < em > minimal</ em > infrastructure costs, which are funded from
42+ non-sponsor sources such as the < a href ="https://store.neovim.io "> Store</ a > .
43+ Those sources are routed to OpenCollective, so expenses will show up in OpenCollective.
44+ </ p >
45+
46+ < h2 > What is expected of a funded contributor?</ h2 >
47+ < p >
48+ Funded work is a way to support active contributors who have weeks of time to focus on the
49+ project. This opportunity is available to contributors who have a developed a reputation for
50+ reliable, high-quality contributions (code/documentation, GitHub review comments, and GitHub
51+ technical discussions; < i > not</ i > IRC or other "ephemeral" places).
52+ </ p >
53+
54+ < p >
55+ It works like this: funded contributors are expected to focus full-time for weeks or
56+ even months, yielding tangible, high-quality contributions, with conspicuous, reliable,
57+ regular activity on GitHub.
58+ </ p >
4959
50- </ dl >
5160 </ div >
5261
5362 < div style ="padding-left: 2em; ">
54- < h2 > Sponsors</ h2 >
63+ < h1 > Sponsors</ h1 >
5564 < div id ="sponsors2 " class ="first-level-sponsor ">
5665 < a href ="https://www.meta.com/ " style ="display: block; ">
5766 < picture title ="Meta " alt ="Meta logo ">
@@ -78,7 +87,7 @@ <h2>Sponsors</h2>
7887 </ div >
7988
8089 < dl >
81- < h3 style ="margin-top: 2em; "> Original fundraiser sponsors</ h3 >
90+ < h2 style ="margin-top: 2em; "> Original fundraiser sponsors</ h2 >
8291 < dd >
8392 < p >
8493 < div class ="first-level-sponsor ">
0 commit comments