Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify payments eligibility #168

Merged
merged 8 commits into from
Oct 7, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
50 changes: 44 additions & 6 deletions src/pages/about.astro
chadwhitacre marked this conversation as resolved.
Show resolved Hide resolved
Original file line number Diff line number Diff line change
Expand Up @@ -103,12 +103,50 @@ const members = filterInactiveMembers(await getMembers());
<section>
<h2>What payments are eligible?</h2>

<p
>Companies directly pay maintainers of Open Source projects they depend on, with no strings attached. Paying
developers to do specific work does not count towards the Pledge. Feel free to participate in <a
href="https://github.com/opensourcepledge/osspledge.com/issues/112">our ongoing discussion</a> on what counts
and what doesn't.</p
>
<p>The primary intent with the Pledge is <b>no-strings-attached payments
to Open Source maintainers</b>. Start there.</p>

<ol>

<li>Open Source projects that your company controls are out of scope.
If you own the trademark, it doesn't count.</li>

<li>Open Source projects that exclusively benefit your company's
own ecosystem are out of scope.</li>

<li>Directly employing maintainers is laudable, yet outside the core
scope of the Pledge, because of the complexity and subtle conflicts
of interest that come along with that.</li>

<li>It's okay if you get non-exclusive logo placement or other
acknowledgement for your payments, or an hour or two of consulting
time along with a large sponsorship, but anything beyond such minimal
benefits puts the payment out of scope.</li>

<li>Payments to <a
href="https://fossfoundation.info/">foundations</a> are generally
in scope, even though most foundations today are not set up to pay
maintainers (they focus more on conferences, trademarks, etc.). We
hope that the Pledge will enable foundations to shift towards
paying maintainers in the future.</li>

<li>It's great if your company also actively participates in the
projects you fund, via code contributions, membership on an
advisory council or board, and the like.</li>
chadwhitacre marked this conversation as resolved.
Show resolved Hide resolved

<li>Platforms such as <a href="https://thanks.dev/home">thanks.dev</a>,
<a href="https://opencollective.com/">Open Collective</a>, and
<a href="https://github.com/sponsors">GitHub Sponsors</a> are a
common way to pay maintainers, though some can also
be used to make payments that are out-of-scope for the Pledge. Only
payments that fit our criteria are in scope, regardless of payment
platform.</li>

</ol>

<p>When in doubt, use your best judgement and be transparent in your
annual report.</p>

</section>

<section>
Expand Down