|
| 1 | +======== |
| 2 | +Tidelift |
| 3 | +======== |
| 4 | + |
| 5 | +pluggy is a member of `Tidelift`_. This document describes how the core team manages |
| 6 | +Tidelift-related activities. |
| 7 | + |
| 8 | +What is it |
| 9 | +========== |
| 10 | + |
| 11 | +Tidelift aims to make Open Source sustainable by offering subscriptions to companies which rely |
| 12 | +on Open Source packages. This subscription allows it to pay maintainers of those Open Source |
| 13 | +packages to aid sustainability of the work. |
| 14 | + |
| 15 | +It is the perfect platform for companies that want to support Open Source packages and at the same |
| 16 | +time obtain assurances regarding maintenance, quality and security. |
| 17 | + |
| 18 | +Funds |
| 19 | +===== |
| 20 | + |
| 21 | +It was decided in the `mailing list`_ that the Tidelift contribution will be split evenly between |
| 22 | +members of the `contributors team`_ interested in receiving funding. |
| 23 | + |
| 24 | +The current list of contributors receiving funding are: |
| 25 | + |
| 26 | +* `@nicoddemus`_ |
| 27 | +* `@The-Compiler`_ |
| 28 | +* `@RonnyPfannschmidt`_ |
| 29 | + |
| 30 | +Contributors interested in receiving a part of the funds just need to submit a PR adding their |
| 31 | +name to the list. Contributors that want to stop receiving the funds should also submit a PR |
| 32 | +in the same way. |
| 33 | + |
| 34 | +The PR should mention `@pytest-dev/tidelift-admins`_ so appropriate changes |
| 35 | +can be made in the Tidelift platform. |
| 36 | + |
| 37 | +After the PR has been accepted and merged, the contributor should register in the `Tidelift`_ |
| 38 | +platform and follow the instructions there, including signing an `agreement`_. |
| 39 | + |
| 40 | +Admins |
| 41 | +====== |
| 42 | + |
| 43 | +A few people have admin access to the Tidelift dashboard to make changes. Those people |
| 44 | +are part of the `@pytest-dev/tidelift-admins`_ team. |
| 45 | + |
| 46 | +`Core contributors`_ interested in helping out with Tidelift maintenance are welcome! We don't |
| 47 | +expect much work here other than the occasional adding/removal of a contributor from receiving |
| 48 | +funds. Just drop a line to one of the `@pytest-dev/tidelift-admins`_ or use the mailing list. |
| 49 | + |
| 50 | + |
| 51 | +.. _`Tidelift`: https://tidelift.com |
| 52 | +.. _`mailing list`: https://mail.python.org/pipermail/pytest-dev/2019-May/004716.html |
| 53 | +.. _`contributors team`: https://github.com/orgs/pytest-dev/teams/contributors |
| 54 | +.. _`core contributors`: https://github.com/orgs/pytest-dev/teams/core/members |
| 55 | +.. _`@pytest-dev/tidelift-admins`: https://github.com/orgs/pytest-dev/teams/tidelift-admins/members |
| 56 | +.. _`agreement`: https://tidelift.com/docs/lifting/agreement |
| 57 | + |
| 58 | +.. _`@nicoddemus`: https://github.com/nicoddemus |
| 59 | +.. _`@The-Compiler`: https://github.com/The-Compiler |
| 60 | +.. _`@RonnyPfannschmidt`: https://github.com/RonnyPfannschmidt |
0 commit comments