-
Notifications
You must be signed in to change notification settings - Fork 134
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
Comments
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. |
Which is in line with actual practice so +1 |
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. |
yeah let's update that |
+1 from me as well. |
@jasnell Maybe we should just insert the amount available into the document when something is allocated, that seems easiest |
Easiest yes, but I'm not certain if the allocated amount is public info. |
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. |
@jasnell That's public here: #250 (comment) |
seems to me this just needs a PR I'll try to get around to it soon(tm) |
Closing due to lack of any further activity |
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:
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.
The text was updated successfully, but these errors were encountered: