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

General update to the Member Travel Fund doc #181

Closed
wants to merge 2 commits into from

Conversation

addaleax
Copy link
Member

We talked about travel funding at the last TSC meeting with the result that the document on it should be updated and we would want to keep track of all approved requests (and, in particular, their amounts) in a table.

@nodejs/tsc Please take a look and let me know what you think!

@williamkapke
Copy link
Contributor

This was discussed in the 2016-12-15 TSC meeting here:
https://www.youtube.com/watch?v=r1chJO9nbRQ&t=2090s

@williamkapke
Copy link
Contributor

This should fix #145

- Widen the scope of the travel fund to include general support for
  Node.js Foundation projects. This matches the actual usage it
  has seen in the past more appropriately.
- Add a table at the bottom of the file listing the receivers of
  travel funds.

Fixes: nodejs#145
@addaleax
Copy link
Member Author

addaleax commented Jan 3, 2017

This should fix #145

Added a Fixes: tag to the commit message, thanks for pointing that out!

Copy link
Member

@mhdawson mhdawson left a comment

Choose a reason for hiding this comment

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

LGTM

Copy link
Contributor

@nebrius nebrius left a comment

Choose a reason for hiding this comment

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

LGTM too

@mikeal
Copy link
Contributor

mikeal commented Jan 12, 2017

I don't know if this needs to be in the doc but in the case where we don't provide a stipend but instead do a re-imbursement or book the travel ourselves we should update the doc with the real cost.

@addaleax
Copy link
Member Author

@mikeal Sorry for the late reply – I guess that depends on who’s doing the update. I assume you wouldn’t want to take that work on for yourself, but otoh I think in the cases where travel is directly booked by the NF the person in question doesn’t even know the total amount? (I don’t know how much my flight to Austin was, for example.)

@addaleax
Copy link
Member Author

I probably won’t be able to be at tomorrow’s TSC meeting, so just to let everyone know:

  • I haven’t merged this PR yet because I’d kinda prefer if a TSC member merged this
  • I don’t think this is urgent, so feel free to wait on @mikeal’s response to my last comment

@Fishrock123
Copy link
Contributor

@addaleax so @mikeal on call today said we can just get that info from the foundation (such as from @mikeal).

Could you update the doc with info stating that one travel is done we should open a PR against the repo to adjust it to the actual cost (including any costs we may need to get from the NF)?

@Fishrock123
Copy link
Contributor

@nodejs/tsc Will be merging this once @addaleax updates it if there are no outstanding concerns.

@addaleax
Copy link
Member Author

@Fishrock123 done, added a short note on that. if you prefer some other wording let me know, or just edit this PR :)

Fishrock123 pushed a commit that referenced this pull request Feb 1, 2017
- Widen the scope of the travel fund to include general support for
  Node.js Foundation projects. This matches the actual usage it
  has seen in the past more appropriately.
- Add a table at the bottom of the file listing the receivers of
  travel funds.

Fixes: #145
PR-URL: #181
@Fishrock123
Copy link
Contributor

TSC has been consistently positive about this, landing as we all appear to have consensus about this.

Landed in 6ea0b67, thanks again @addaleax!

@Fishrock123 Fishrock123 closed this Feb 1, 2017
@addaleax addaleax deleted the tf-update branch February 1, 2017 19:08
@Trott Trott removed the tsc-agenda label Sep 2, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants