Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

doc: add travel fund allocation for 2021 #725

Merged
merged 3 commits into from
May 25, 2021
Merged

Conversation

mhdawson
Copy link
Member

@mhdawson mhdawson commented Mar 4, 2021

Add amount approved by board for 2021

Add amount approved by board for 2021
Copy link
Member

@joesepi joesepi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the update.

I will also have some travel fund housekeeping updates that I started today. Simply moving 2020 to archived and adding a new 2021 file and updating links and adding a very simple readme to the travel fun directory pointing to the documentation in the project-resources file.

@brianwarner
Copy link
Contributor

This time around I would also recommend using the LFX crowdfunding tool to handle actual reimbursement. It can be set up specifically for travel funds, and can also receive donations from organizations other than the Foundation.

To my knowledge it can't replace the actual decision process (e.g., CPC still needs a way to track and approve applications, and avoid overspending the budget) but it does provided a streamlined process to actually get paid, and provides a transparent ledger.

Copy link
Contributor

@tobie tobie left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The Member Travel Fund allocation process focusses on helping underserved communities in particular. If there is a year in which underserved communities are suffering it is this year.

In this context, cutting down this fund without reassigning the savings into a program that does the same kind of work sends the wrong signal and isn't aligned with the values we are trying to defend, notably in #699.

While we don't necessarily have a program setup just yet, we should request from the Board a formal commitment to earmark the saved funds for DEI-related work and have it mentioned in this PR.

@mhdawson
Copy link
Member Author

mhdawson commented May 5, 2021

@tobie this was discussed in latest Board finance committee meeting, and the a recommendation was made to the board. Based on that recommendation the board approved changing the total back to $60k, changing the budget line item to community fund with the expectation the the CPC will propose additional review/approval processes for spending the money beyond just travel.

I think next steps after this lands is for CPC to work on proposals for other ways the fund may be used.

Copy link
Contributor

@tobie tobie left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a great outcome! Thank you for your advocacy and the Board members for their understanding.

@tobie
Copy link
Contributor

tobie commented May 6, 2021

I think next steps after this lands is for CPC to work on proposals for other ways the fund may be used.

Tracking this in #756.

@mhdawson
Copy link
Member Author

mhdawson commented May 6, 2021

I'll leave this until next CPC meeting so we can give an update to the full team before landing.

@tobie
Copy link
Contributor

tobie commented May 25, 2021

Update was given to the CPC. Tracking the proposal that the CPC has to make in #756. This can be merged.

@mhdawson mhdawson merged commit 7b05569 into main May 25, 2021
@mhdawson mhdawson deleted the mhdawson-2021-allocation branch May 25, 2021 18:04
tobie pushed a commit that referenced this pull request Sep 1, 2023
* doc: add travel fund allocation for 2021

Add amount approved by board for 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants