Open Collective
Open Collective
Loading

Expenses

Newest First
All expenses
All methods
All
All

Migration from Gradle Groovy to Kotlin DSL - Issue #2699

Category
Maintenance and Development
from Kaushal Kumar Singh to MapLibre
$250.00 USD
Paid
Invoice #223914
bounty

Heatmap Fix for 3D Terrain (issue 1081)

Category
Maintenance and Development
from Samarth Otiya to MapLibre
$500.00 USD
Paid
Invoice #217718
bounty

#2436 Replace usage of android.os.AsyncTask with Kotlin Coroutines

Category
Maintenance and Development
from Eric Smith to MapLibre
$100.00 USD
Paid
Invoice #217034
bounty

2xM bounties (April/May)

Category
Maintenance and Development
from Andrew Olsen to MapLibre
$500.00 USD
Paid
Invoice #214605
bounty

Bounty Claim

Category
Maintenance and Development
from Christian Neumann to MapLibre
$1,000.00 USD
Paid
Invoice #214267
bounty

Fixing Android deprecation warnings (issue 1607)

Category
Maintenance and Development
from Eric Smith to MapLibre
$100.00 USD
Paid
Invoice #213553
bounty

Issue #2526 (bounty)

Category
Maintenance and Development
from Dilshodbek Jumabaev to MapLibre
$100.00 USD
Paid
Invoice #213230
bounty

MapLibre Native Support

Category
Maintenance and Development
from Clever Software Solutions Inc to MapLibre
$6,785.73 USD
Paid
Invoice #196009
bounty

March/April 2024 bounty payout

Category
Maintenance and Development
from fynngodau to MapLibre
$350.00 USD
Paid
Invoice #193947
bounty

Issue #2094 (bounty S)

Category
Maintenance and Development
from Andrew Olsen to MapLibre
$100.00 USD
Paid
Invoice #193319
bounty
Page Total:$9,785.73 USD

Payment processor fees may apply.

Page of 5
Collective balance
$592,379.68 USD

Current Fiscal Host
Open Source Collective

Expense policies

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.


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.