Mastodon
/
Yuito-app-android
mirror of https://github.com/accelforce/Yuito
1
0
Fork 0
Code Issues Releases Wiki Activity

Payment Policy Document (#4035) 

Document copied from CryptPad as approved by the team in the 2023-09-25
meeting.
This commit is contained in:
alcapurrias 2023-09-26 01:55:28 -05:00 committed by GitHub
parent fbd99717c0
commit 2f39f87cc7
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 34 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

34
doc/PaymentPolicy.md Normal file
View File

@ -0,0 +1,34 @@
<h1>Payment Policy</h1>
We provide payment for work done on the Tusky project, including but not limited to, Coding, Code Review, Design, and User Support. We also reimburse all costs necessary to keep the project running, e.g. servers, hosting, domain renewals, and the occasional merchandise drop to promote the project.
We primarily use our budget to enable contributors who would otherwise not be able to contribute, and prioritize payments to such need-based contributors.
<ul>
<li>Payments for one-off contributions are welcome, but the scope of the work must be discussed and approved in our Matrix-based <a href="https://matrix.to/#/#Tusky-Code:matrix.org" target="_new">Tusky Code room</a> prior to the work commencing.</li>
<ul>
<li>Payment amounts for one-off contributions will be determined based on the scope of the work and amount of funds available, both of which will be discussed and agreed upon by the contributor and team up front. The payment amount will be considered approved with the sign-off of one of our <a href="https://opencollective.com/tusky#category-ABOUT" target="_new">OpenCollective Admins</a> after the discussion has occurred.</li>
</ul>
<li>Regular contributors can submit for payments based on a team-approved individual agreement.</li>
<li>Payment requests are approved by our <a href="https://opencollective.com/tusky#category-ABOUT" target="_new">OpenCollective Admins</a>. Admins <i>cannot</i> approve their own payment requests.</li>
<li>Payments have a soft cap of $500/month per contributor. Additional amounts may not be considered without a broad team consensus.</li>
</ul>
<h2>Expense Submissions</h2>
Payment requests should be submitted monthly for the previous month's work. A description of the work must be included. Some examples:
<ul>
<li>September 2023: [#] hours of development work on GitHub issues #1234, #5678, #9000.</li>
<li>September 2023: [#] hours of support work updating Tusky FAQs, answering email inquiries sent to the Tusky email address, and posting updates to the official Mastodon Tusky account.</li>
</ul>
You are not required to upload an invoice attachment (the data you submit in the expense form is sufficient) but if you would like to include an uploaded invoice, please make it out to:
Tusky<br>
Open Source Collective<br>
440 N. Barranca Avenue #3717<br>
Covina, CA 91723, USA<br>
<h2>Reimbursement Submissions</h2>
Reimbursements must include receipts, whether a PDF copy or photo of a paper receipt. For more information on what constitutes a valid receipt, see <a href="https://docs.oscollective.org/how-it-works/basics/invoice-and-reimbursement-examples#reimbursements" target="_new">Open Source Collective's documentation</a>.