Create MEMBER_TRAVEL_FUND.MD

[hackygolucky]

As discussed in today's CommComm meeting, this creates the process about travel funds for the CommComm, since there is a separate scope of members than the TSC fund.

A separate issue will be filed about the specific request for the 2017 travel fund allocation.

ON HOLD
This PR is on hold for further coordination with the @nodejs/tsc for a joint travel fund.

[RichardLitt]

LGTM.

[ghost]

is this on the meeting agenda or can this be merged? /cc @nebrius

[nebrius]

@hackygolucky do we want to go ahead and merge this now, or wait until some of the meta-discussion around joint management is figured out first?

[hackygolucky]

@nebrius This needs to be coordinated with @jasnell @mhdawson and the TSC. The result of the last Board meeting was that they'd prefer a jointly coordinated single travel fund. So we may end up needing to scrap this PR and link to a new joint one, wherever it ends up contained.

[ghost]

now that the tsc travel fund has been made available for general members, isn't this PR obsolete?

[bnb]

@hackygolucky Is there any update on the status of this PR?

[jasnell]

Fyi... The travel fund is now jointly managed by the tsc and commcomm. There is already a tracking document in the tsc repo that can continue to be used

…

On Tue, Aug 29, 2017 at 10:49 AM Tierney Cyren ***@***.***> wrote: @hackygolucky <https://github.com/hackygolucky> Is there any update on the status of this PR? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#81 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAa2eVzMKRZV8UJozDEG8_KSM4DIsCO4ks5sdE8PgaJpZM4OC3e_> .

[bnb]

@hackygolucky can we close this issue, given the Travel Fund now lives in the nodejs/admin repo?

[hackygolucky]

We can def close this. See the nodejs/admin repo for filing for Travel Fund!