Skip to content

Commit

Permalink
Update to travel fund policy (#1338)
Browse files Browse the repository at this point in the history
- Adds a confidentiality clause
- Addresses the following points of and closes #1258
  - Mention speakers are covered through a separate fund, add link to fund
  - State that the cadence of CPC review might be > monthly
  - Clarify whether the fund covers attendance to event (no collab summit) where requester isn't speaking
  - Mention flexibility around deadlines
  - Mention expense reports should be sent asap
- Removes the section on completing a trip report which was confusing

---------
Signed-off-by: Tobie Langel <tobie@unlockopen.com>
Co-authored-by: Timmy Willison <timmywil@users.noreply.github.com>
  • Loading branch information
tobie authored Jul 22, 2024
1 parent 76116dd commit ff0cd0c
Showing 1 changed file with 21 additions and 19 deletions.
40 changes: 21 additions & 19 deletions community-fund/COMMUNITY_FUND_POLICY.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,13 +6,19 @@ The OpenJS Foundation’s community fund supports travel and attendance at event

* Collaborators
* Standards body participants
* Speakers

The fund can cover the costs, in whole or in part, of a participant's hotel, transportation, and some event registrations.
> [!Note]
> If you're _speaking_ at an event, you should apply through the [OpenJS Foundation's Speakers Bureau](https://openjsf.org/events#:~:text=Speakers%20Bureau) instead.
The fund can cover the costs, in whole or in part, of a participant's hotel, transportation, and event registration for approved events.
Applicants should explore employer-sponsored funding options as their first source of financial support.
Additionally, 25% of the community fund is allocated specifically to support underrepresented groups.
Funding decisions are determined by a combination of need and potential impact.

## Confidentiality

All travel fund requests are treated confidentially: only CPC members and OpenJS Foundation staff have access to the requests. Expense reports are managed according to the Foundation's [Privacy Policy](https://privacy-policy.openjsf.org/).

## Transparency

In **2023**, 26 funding requests were made by 22 contributors for a total requested sum of $47,500 with a maximum of 2 requests per contributor.
Expand All @@ -22,7 +28,7 @@ All requests were granted.

For 2024, $60,000 was allocated to the fund.

_All ammounts are in United States dollar._
_All ammounts are in United States dollars._

## Community Fund Rules

Expand All @@ -41,49 +47,45 @@ Funding is not transferable to another person, or any other event.

### Submit Travel Fund Request

Submit your travel fund request to the Cross Project Council by completing [this application](https://forms.gle/QDt3iqoXXB5Ycovz8).
Submit your travel fund request to the Cross Project Council (CPC) by completing [this application](https://forms.gle/QDt3iqoXXB5Ycovz8).
Please see [Deadlines and Timelines](#deadlines-and-timelines) for information about cut-off dates.

### Wait For Approval

The Cross Project Council reviews requests once per month. If your request is approved, you will be notified via email. Only
approved requests are eligible for reimbursement.
The CPC will review requests as soon as possible, usually in the next CPC private session (every 2 weeks).
You will be notified by email if your request is approved or denied. Only approved requests are eligible for reimbursement.

## Getting Reimbursed

### Submitting Expenses

After the event, kindly submit your expenses within 30 days:
After the event, kindly submit your expenses within 30 days.

> [!Note]
> The faster expenses are submitted, the faster any leftover funds can be reallocated to allow additional people to travel. So **please submit your expenses as quickly as possible**. Thank you!
* Fill out these [two forms](https://drive.google.com/drive/folders/1E-dTuqnIWpZN2NP-1ioAWzK_W2zSwa_P?usp=share_link)
* Submit the forms along with **all** receipts [here](https://form.asana.com/?k=S6lGzAjHv2uv7M8llnhO_w&d=9283783873717)

Please note that expenses without receipts can not be paid.

### Submitting A Trip Report

The process for submitting a trip report is TBD.
<!-- Provide a trip report by filling out the following form. Preferably, also provide pictures and video of the
event for use on social media. -->

### Receiving Payment

Payments are processed within 30 days.

## Deadlines and Timelines
## Deadlines and Timelines

The default deadline for submitting a community fund request is 8 weeks prior to the travel date to allow for all requests for an event to be reviewed at the same time.
The default deadline for submitting a community fund request is 8 weeks prior to the travel date to allow for all requests for an event to be reviewed at the same time. If you've missed a deadline, or if a deadline was impossible to meet, please submit your request anyway, explaining why you weren't able to meet the deadline if possible.

Some events might have a fixed deadline for applications. Those deadlines will be posted to this repository.
Some events might have a fixed deadline for applications. Those deadlines will be posted below.

## CPC Review Schedule & Process
## CPC Review Process

- CPC will review requests as soon as possible, usually in the next CPC private session (every 2 weeks)
- Pending requests will be sent to the private CPC mailing list prior to the review meeting.
In the context of the lazy consensus process, the pending request list is a proposal to accept
all of the requests. CPC members may raise any objections before the scheduled meeting,
otherwise a final decision to approve a request can be confirmed in the meeting.
- The CPC will use a scoring rubric to help with decision making
- The CPC will use a [scoring rubric](#scoring-rubric) to help with decision making.
- If any requests are rejected, an email with the rejected requests will be sent to the private
CPC mailing list and CPC members will have 2 days to object before the decision is confirmed.
Approved requests will be confirmed right away.
Expand Down

0 comments on commit ff0cd0c

Please sign in to comment.