Skip to content

Latest commit

 

History

History
105 lines (76 loc) · 4.04 KB

EXPENSE_POLICY.md

File metadata and controls

105 lines (76 loc) · 4.04 KB
Raw

Expense Policy

Fastify collaborators accept donations through the Open Collective platform and GitHub Sponsors to enhance the project and support the community.

This Collective is run by and for the benefit of the independent contributors to the Fastify open source software project. This Collective is not endorsed or administered by OpenJS Foundation, Inc. (the “OpenJS Foundation”). The OpenJS Foundation does not receive or have control over any funds contributed. The OpenJS Foundation does not direct or otherwise supervise the actions of any contributor to the Fastify project, and all donations made will be expended for the private benefit of or otherwise to reimburse individuals that do not have an employer/employee, contractor, or other agency relationship with the OpenJS Foundation. The Fastify marks used herein are used under license from the OpenJS Foundation for the benefit of the open source software community.

The admins of the Fastify Collective are the lead maintainers of the project.

This document outlines the process for requesting reimbursement or an invoice for expenses.

Reimbursement

Reimbursement is applicable for expenses already paid, such as:

  • Stickers
  • Gadgets
  • Hosting

Before making any purchases, initiate a new discussion in the fastify organization with the following information:

  • What is needed
  • Why it is needed
  • Cost
  • Deadline

Once the discussion is approved by a lead maintainer and with no unresolved objections, the purchase can proceed, and an expense can be submitted to the Open Collective. This process takes a minimum of 3 business days from the request to allow time for discussion approval.

The discussion helps prevent misunderstandings and ensures the expense is not rejected. As a project under the OpenJS Foundation, Fastify benefits from the Foundation's resources, including servers, domains, and travel funds.

Always seek approval first.

Invoice

Invoices are for services provided to the Fastify project, such as PR reviews, documentation, etc. A VAT number is not required to submit an invoice. Refer to the Open Collective documentation for details.

Adding a bounty to an issue

Issues become eligible for a bounty when the core team adds the bounty label, with the amount determined by the core team based on estimated hours * rate (suggested $50 per hour).

Example: If the estimated time to fix the issue is 2 hours, the bounty will be $100.

To add a bounty:

  • Apply the bounty label to the issue
  • Comment on the issue with the bounty amount
  • Edit the first comment of the issue using this template:
## 💰 Bounty

This issue has a bounty of [$AMOUNT](LINK TO THE BOUNTY COMMENT).
_Read more about [the bounty program](./EXPENSE_POLICY.md)_

For discussions on bounties or determining amounts, open a new discussion.

Outstanding contributions

The lead team can decide to add a bounty to an issue or PR not labeled as bounty if the contribution is outstanding.

Claiming a bounty

To claim a bounty:

  • Submit a PR that fixes the issue
  • If multiple submissions exist, a core member will choose the best solution
  • Once merged, the PR author can claim the bounty by:
    • Submitting an expense to the Open Collective with the PR link
    • Adding a comment on the PR with a link to their Open Collective expense to ensure the claimant is the issue resolver
  • The expense will be validated by a lead maintainer and then the payment will be processed by Open Collective

If the Open Collective budget is insufficient, the expense will be rejected.
Unclaimed bounties are available for other issues.