Skip to content

Commit 9c7378d

Browse files
authored
Merge pull request #268 from Jonahss/travel-fund
proposal: OpenJS Travel fund
2 parents fc84337 + 80bf564 commit 9c7378d

File tree

1 file changed

+58
-0
lines changed

1 file changed

+58
-0
lines changed
Lines changed: 58 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,58 @@
1+
# OpenJS Travel Fund
2+
> Stage 0
3+
4+
Tracked by https://github.com/openjs-foundation/cross-project-council/issues/172
5+
6+
## Champion
7+
8+
Jonah Stiennon @jonahss
9+
10+
## Description
11+
12+
The Node.js organizations that existed prior to the formation of the OpenJS foundation oversaw a monetary fund for the purpose of member and affiliate travel to, and lodging at, events related to the foundation's mission. This proposal proposes moving the management responsibilities of this fund to the Cross Project Council (CPC), and making the funds available to all members of this broader organization. Since all projects have voting representation on the CPC, the beneficiaries of the fund will jointly manage it, and the previous owners of the fund will still vote on its use.
13+
14+
We shall review the process in this proposal, but the intent is to leave the mechanics of the fund unchanged, simply moving from the purview of the Node.js project into the domain of the OpenJS Foundation, overseen by the CPC. This operation can be viewed as a refactor which moves the travel fund up one level in the organizational tree.
15+
16+
The current fund is used mostly for attending collaborator summits, and we do not expect this to change.
17+
18+
## Difference from the current process
19+
20+
The existing process requires approval from two members of the [Node.js TSC](https://github.com/nodejs/TSC) and two members of the [Node.js Community Committee](https://github.com/nodejs/community-committee).
21+
The new process will require approval from four members of the CPC.
22+
23+
The role of fund "treasurer" will be removed, as it has been found to be redundant and is not currently filled (see https://github.com/openjs-foundation/cross-project-council/pull/268#issuecomment-513888283).
24+
25+
## Practical Specifics
26+
27+
- Move relevant files from nodejs/admin to openjs-foundation/cross-project-council such as:
28+
- https://github.com/nodejs/admin/blob/master/MEMBER_TRAVEL_FUND.md
29+
- https://github.com/nodejs/admin/tree/master/TravelFunds
30+
- https://github.com/nodejs/admin/blob/master/travel-visas.md
31+
- https://github.com/nodejs/admin/blob/master/expense-report-template.xls
32+
- https://github.com/nodejs/admin/blob/master/reimbursement_process.pdf
33+
- Modify these files to account for OpenJS rather than Node.js organizations
34+
- Remove mentions from nodejs/admin README, add links to CPC README
35+
- Remove the role of treasurer
36+
37+
## Required Resources
38+
39+
@brianwarner reports that everything can stay the same for the tools and accounts involved.
40+
No other resources required.
41+
42+
## How would success be measured?
43+
44+
Success will be achieved if Node.js and non-Node.js members use the travel fund to attend a Foundation-related event, and nobody notices the difference.
45+
46+
## Why this proposal is important
47+
48+
The Node.js project has demonstrated the value of providing a travel fund which allows project members to get together at collaborator summits and to represent/advocate for the project at other events. It is important to expand the travel fund (both resource and usage) so that other projects can benefit as well.
49+
50+
## Unresolved Questions
51+
52+
- Who is the current treasurer of the fund?
53+
54+
## What is necessary to complete this proposal
55+
56+
- Approval and buy-in from Node.js TSC and CommComm.
57+
- OpenJS board approval
58+
- Definition and wording of the travel fund mechanics, mostly moving files and updating references.

0 commit comments

Comments
 (0)