-
Notifications
You must be signed in to change notification settings - Fork 102
/
sponsors.html
97 lines (90 loc) · 3.74 KB
/
sponsors.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
---
layout: default
title: Sponsors
---
{% include nav.html active='Sponsors' %}
<div class="container golden-grid">
<div>
<h2>Sponsoring Neovim development</h2>
<dl class="faqs">
<dt>How can I sponsor Neovim?</dt>
<dd>
<p>
Neovim operates a <a href="https://github.com/sponsors/neovim">campaign</a>
to fund ongoing development. This makes it possible for core
developers to work full-time for a month or longer, accelerating
projects like Lua stdlib, treesitter parser engine, LSP framework,
extended marks, embedded terminal, job control, RPC API, and remote UIs.
Sponsorship is also used to maintain (very minimal) infrastructure
costs for the Neovim project, such as hosting fees.
</p>
</dd>
<dt>How are funds dispersed?</dt>
<dd>
<p>
Donations are managed via <a href="https://opencollective.com/neovim">open collective</a>, which
provides public tracking for all
<a href="https://opencollective.com/neovim/expenses">expenses</a>. Bitcoin transactions are visible
on the <a
href="https://www.blockchain.com/btc/address/1Evu6wPrzjsjrNPdCYbHy3HT6ry2EzXFyQ">blockchain
explorer</a>. The only donation options for neovim are via GitHub sponsors, open collective, and
Bitcoin. All prior funding sources have been transferred into open collective.
</p>
</dd>
<dt>What is expected of a contributor doing funded work?</dt>
<dd>
<p>
Funded work is a way to support active contributors who have weeks of time to focus on the
project. This opportunity is available to contributors who have a developed a reputation for
reliable, high-quality contributions (code/documentation, GitHub review comments, and GitHub
technical discussions; <i>not</i> IRC or other "ephemeral" places).
It works like this: funded contributors are expected to focus <i>full-time</i> for weeks or
even months, yielding tangible, high-quality contributions, with conspicuous, reliable,
regular activity on GitHub.
</p>
</dd>
</dl>
</div>
<div>
<h2>Sponsors</h2>
<div id="sponsors3" class="first-level-sponsor">
<a href="https://rizin.re/">
<img width="297" height="100" src="/images/sponsors/rizin.svg" alt="Rizin"/>
</a>
</div>
<div id="sponsors4" class="first-level-sponsor">
<a href="https://route4me.com/">
<img width="300" height="76" src="/images/sponsors/route4me-logo.png" alt="Route4Me Route Planner" />
</a>
</div>
<dl>
<h2>Thanks to the original fundraiser sponsors:</h2>
<dd>
<p>
<div class="first-level-sponsor">
<a href="http://digitalocean.com"><img src="/images/sponsors/[email protected]"
alt="Digital Ocean logo" width="311" height="50"></a>
</div>
<table class="second-level-sponsors">
<tr>
<td>
<a href="http://bountysource.com"><img src="/images/sponsors/[email protected]"
alt="Bountysource logo" width="144" height="53"></a>
</td>
<td>
<a href="http://superjer.com"><img src="/images/sponsors/[email protected]"
alt="SuperJer logo" width="119" height="115"></a>
</td>
</tr>
<tr>
<td>
<img src="/images/sponsors/[email protected]" alt="Ryan Durk logo" width="125" height="45">
</td>
<td> </td>
</tr>
</table>
</p>
</dd>
</dl>
</div>
</div>