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

Define Travel Fund approval requirements #254

Closed
williamkapke opened this issue Apr 20, 2017 · 12 comments
Closed

Define Travel Fund approval requirements #254

williamkapke opened this issue Apr 20, 2017 · 12 comments
Assignees

Comments

@williamkapke
Copy link
Contributor

The Travel Fund process seems to be working well so far:
https://github.com/nodejs/TSC/blob/master/Member-Travel-Fund.md

The approval (voting?) requirements are not defined however. I think the TSC has been working on a "majority" approval required.. but that is not included in the document.

It does say:

The TSC will consider each proposal in its next regular meeting.

I don't think this is happening. It seems that it is currently just working off getting a majority TSC PR approvals..? Maybe my memory is off on this.

Please document what it takes to achieve the official approval.

@mikeal
Copy link
Contributor

mikeal commented Apr 20, 2017

The TSC will consider each proposal in its next regular meeting.

Good catch, this should probably be changed so that approvals can be completed via issue votes and only bubble up to the meeting if untended or controversial.

@jasnell
Copy link
Member

jasnell commented Apr 20, 2017

this should probably be changed so that approvals can be completed via issue votes...

Which is in line with actual practice so +1

@bnoordhuis
Copy link
Member

The current online process works well so +1 to updating the document. I can file a pull request if no one is already working on it.

@jasnell
Copy link
Member

jasnell commented Apr 20, 2017

The one thing that we definitely need, however, is greater visibility into exactly how much money is left in the fund. It would be good if we can have a periodic review on that from either @mikeal or @rvagg

@Fishrock123
Copy link
Contributor

yeah let's update that

@mhdawson
Copy link
Member

mhdawson commented Apr 21, 2017

+1 from me as well.

@addaleax
Copy link
Member

@jasnell Maybe we should just insert the amount available into the document when something is allocated, that seems easiest

@jasnell
Copy link
Member

jasnell commented Apr 21, 2017

Easiest yes, but I'm not certain if the allocated amount is public info.

@mikeal
Copy link
Contributor

mikeal commented Apr 22, 2017

The board has assumed that it would be public being that the TSC would have to manage it. In future allocations that can be made more explicit.

@ChALkeR
Copy link
Member

ChALkeR commented May 8, 2017

@jasnell That's public here: #250 (comment)

@Fishrock123
Copy link
Contributor

seems to me this just needs a PR

I'll try to get around to it soon(tm)

@Fishrock123 Fishrock123 self-assigned this Aug 17, 2017
@jasnell
Copy link
Member

jasnell commented Sep 16, 2017

Closing due to lack of any further activity

@jasnell jasnell closed this as completed Sep 16, 2017
@Trott Trott removed the tsc-review label Nov 8, 2017
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

9 participants