Open Collective
Open Collective

Invoice Summary to Bazel Rules Authors SIG

Bzlmod, BCR, rules_js updates

Invoice #122420

Submitted by Jenny Magolan on February 7, 2023

Invoice items
Derek Cormier: 12 hours in December & January public-to-bcr: - fix bug preventing rules_erlang release from publishing - fix bug where yanked versions would be overwritten on bcr Publish to BCR: - better error messaging around missing fork installations - notify maintainers when users encounter a bug - avoid downloading full repository contents rules_js: add bzlmod test matrix on ci - debug publish-to-bcr issues for bazel-contrib/rules_cuda - rules_js: automatically update pnpm lockfile under bzlmod rules_js: support npm auth, bins, and importing npm and yarn lockfiles under bzlmod rules_js: bzlmod test coverage for e2e rules_js: auto lock update solution (run no-op sync target rather than bazel sync) Alex Eagle: 2.5 hours in December & January rules_python runfiles to pypi bzlmod BCR-UI: link to release notes, remove experimental
Date: February 7, 2023

$3,190.00 USD

Total amount $3,190.00

payout method

Bank account

Paid from Fiscal Host

Open Source Collective

440 N Barranca Ave #3717 Covina, CA 91723

By Jenny Magolanon

Expense created

By Jenny Magolanon

Expense updated

By keithon

Expense approved

By Benjamin Nickollson

Expense processing

By Benjamin Nickollson

Expense paid

Collective balance
$28,313.90 USD

Fiscal Host
Open Source Collective

Expense policies

We process payouts twice a week after they have been approved by the admin of the Collective. 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 #3717, Covina, CA 91723, USA
Here are examples of what a Reimbursement or Invoice needs to contain in order for us to process it for payment. 
If you would like a refund, email [email protected] with the # of the transaction, the collective you made the donation to, the date and the amount of the transaction.


Typical rate for documentation work is $130USD/hr.

Engineering work can be billed at up to $220/hr, which is the same rate Chrome is paying.

For example, for $33k in June (assuming 150hr/mo) works out to $220/hr.


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.

Collective balance