From 2f39f87cc773230442970ce420b87dfb86fc01de Mon Sep 17 00:00:00 2001 From: alcapurrias <63966511+alcapurrias@users.noreply.github.com> Date: Tue, 26 Sep 2023 01:55:28 -0500 Subject: [PATCH] Payment Policy Document (#4035) Document copied from CryptPad as approved by the team in the 2023-09-25 meeting. --- doc/PaymentPolicy.md | 34 ++++++++++++++++++++++++++++++++++ 1 file changed, 34 insertions(+) create mode 100644 doc/PaymentPolicy.md diff --git a/doc/PaymentPolicy.md b/doc/PaymentPolicy.md new file mode 100644 index 000000000..ac5cfee87 --- /dev/null +++ b/doc/PaymentPolicy.md @@ -0,0 +1,34 @@ +

Payment Policy

+ +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. + + + +

Expense Submissions

+ +Payment requests should be submitted monthly for the previous month's work. A description of the work must be included. Some examples: + + + +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
+Open Source Collective
+440 N. Barranca Avenue #3717
+Covina, CA 91723, USA
+ +

Reimbursement Submissions

+Reimbursements must include receipts, whether a PDF copy or photo of a paper receipt. For more information on what constitutes a valid receipt, see Open Source Collective's documentation.