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

Clarify Travel Fund status & process #377

Closed
eemeli opened this issue Oct 22, 2019 · 5 comments
Closed

Clarify Travel Fund status & process #377

eemeli opened this issue Oct 22, 2019 · 5 comments
Assignees

Comments

@eemeli
Copy link
Member

eemeli commented Oct 22, 2019

The travel fund proposal got advanced to Stage 3 in #312, and is therefore nominally "complete". However, its documents are only included under proposals/stage-3/TRAVEL_FUND, they contain a number of "TODO" mentions, and at least the 2019 record is missing some updates that have been made to the nodejs/admin version.

As an interested party to applying for the travel fund for the Montreal conference & summit, I actually have no idea about how I should proceed with my application. Should I apply here, or in the nodejs/admin repo? When is the process moving to this repo? How will any open requests be handled?

@Jonahss
Copy link
Member

Jonahss commented Oct 24, 2019

Open requests can be migrated. So apply through the old repo until #312 is fully completed.

The process itself (using expensify, email addresses) are all the same.

@Jonahss
Copy link
Member

Jonahss commented Oct 24, 2019

I plan on setting up the final PR for the proposal in the next 7 days. So if you want to wait for that, you can.

@christian-bromann
Copy link
Member

christian-bromann commented Jan 7, 2020

Given that we were short in time at the CPC meeting, let me phrase my question in here:

  • There is a section at the end on approved travel funds of previous year. Do we have already approval for travel fund this year? If so, by whom? Is it the OpenJS Foundation this time?

I created a draft for landing this here: #441

@christian-bromann
Copy link
Member

@eemeli please review final PR with suggested changes: #441. Cheers!

@mhdawson
Copy link
Member

Landed #441 so closing.

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

No branches or pull requests

6 participants