We process expenses twice a week after an admin of the Collective has approved them. We make payments via PayPal and Bank Transfer (using Wise) and can only make payouts to countries served by these payment processors. You are not required to upload an invoice document (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:
Collective Name, Open Source Collective, 440 N. Barranca Avenue #3939, Covina, CA 91723, USA

INFORMATION REQUIRED ON EXPENSES:
Please refer to the documentation here for payment processing requirements on reimbursements and invoices.

REFUNDS:
If you would like a refund, please email [email protected] with the transaction #, the collective you donated to, the date, and the amount of the transaction.

Intro

The team behind exist-db consists of volunteers, who are always looking for new contributors. Our Bounty program is an opportunity to solve issues that could be neglected otherwise. Contributors who fix these issues will be rewarded financially. Principles No compromise on quality

We're not able to accept pull requests that aren't completed to a high standard in a reasonable timeframe. Please only pick up bounties that you are confident you can complete at your current knowledge and skill level. We will not accept pull requests or pay bounties for code that's not up to the standard we need to maintain exist-db moving forward. Our dev team is happy to answer questions and provide some limited support. For general guidelines about what's expected in the code, check our code review guide. How it works

Our Bounty model is simple: Issue submitters or core contributors attach bounties to an open issue. We want to attract quality contributions. The issue will only be considered complete and approved for payment if the Pull Request is approved and merged by an exist-db core contributor.

Workflow for Bounty Hunters

Search for issues with attached bounties: link coming soon
Express interest by commenting on the issue and ask to be assigned
You'll be assigned and given an expected timeframe to deliver (if you aren't able to meet the deadline, the issue may be assigned to someone else)
Create your solution
Open a Pull Request to get your code reviewed
Incorporate any feedback from Core Contributors
PR is reviewed, approved, and merged by a Core Contributor
Submit your invoice as an expense to eXist-db*
Get paid!

FAQ

How do I get paid from a Collective?

Submit an expense and provide your payment information.

How are expenses approved?

Collective admins are notified when an expense is submitted, and they can approve or reject it.

Is my private data made public?

No. Only the expense amount and description are public. Attachments, payment info, emails and addresses are only visible to you and the admins.

When will I get paid?

Payments are processed by the Collective's Fiscal Host, the organization that hold funds on their behalf. Many Fiscal Hosts pay expenses weekly, but each one is different.

Why do you need my legal name?

The display name is public and the legal name is private, appearing on receipts, invoices, and other official documentation used for tax and accounting purposes.

More info →

Collective balance

$43.06 USD

Fiscal Host:

Open Source Collective