Skip to content

Commit e4f2d55

Browse files
crowlKatscrowlKats
authored
docs: add governance information (#910)
1 parent 69b0a6a commit e4f2d55

File tree

3 files changed

+113
-18
lines changed

3 files changed

+113
-18
lines changed

‎frontend/docs/governance/charter.md

Lines changed: 75 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,75 @@
1+
---
2+
title: JSR Governance Charter
3+
description: JSR is a project built for the entire JavaScript ecosystem. This document outlines the charter document.
4+
---
5+
6+
## 1. Mission and purpose
7+
8+
The JSR board exists to improve the JavaScript and TypeScript ecosystem by
9+
providing a community service for sharing code through mechanisms such as
10+
hosting, moderation, and facilitating easy access to shared resources.
11+
12+
## 2. Board composition
13+
14+
The board will consist of 5 members. Members are selected based on their ability
15+
to represent large swaths of JavaScript users, including key stakeholders such
16+
as developers, framework authors, and platform maintainers.
17+
18+
## 3. Responsibilities
19+
20+
The board will be responsible for:
21+
22+
Setting policy and strategy for JSR. Overseeing operational matters, including
23+
securing a legal home for the organization. Ensuring alignment with the mission
24+
and acting as stewards of the community's trust.
25+
26+
## 4. Decision-making
27+
28+
Decisions will be made by majority vote. A quorum is required to hold a vote,
29+
defined as at least 3 members present.
30+
31+
## 5. Term limits and roles
32+
33+
Board members do not have term limits. No formal roles (e.g., chair, secretary)
34+
are defined at this time.
35+
36+
## 6. Legal organization
37+
38+
The board will function as an informal group initially. Members agree to abide
39+
by board decisions. One of the board's primary goals is to establish a legal
40+
home for JSR, either by joining an existing foundation (e.g., Linux Foundation,
41+
OpenJS) or forming its own 501(c)(3) or similar entity.
42+
43+
## 7. Transparency
44+
45+
Board decisions and meeting minutes will be posted publicly on an accessible
46+
platform, such as the organization's website or a public repository.
47+
48+
## 8. Dispute resolution
49+
50+
All disagreements among board members will be resolved through majority voting.
51+
52+
## 9. Funding
53+
54+
Funding will be provided by the Deno Company until a formal legal structure is
55+
established. In the event that Deno Company funding becomes unavailable, the
56+
board will explore alternative funding sources, including community
57+
contributions, sponsorships, or grants.
58+
59+
## 10. Charter amendments
60+
61+
The board will have the authority to revise this charter as necessary, following
62+
the same decision-making process (majority vote). Amendments will be
63+
communicated to the community through public postings, with an opportunity for
64+
review and feedback before finalization.
65+
66+
## 11. Conflict of interest policy
67+
68+
Board members must disclose any conflicts of interest that may arise and recuse
69+
themselves from decisions where such conflicts exist.
70+
71+
## 12. Onboarding and offboarding
72+
73+
New board members will be onboarded with a briefing on the charter and current
74+
initiatives. A member may resign by providing written notice. Removal of a
75+
member requires a majority vote of the remaining board.

‎frontend/docs/governance.md renamed to ‎frontend/docs/governance/overview.md

Lines changed: 22 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -18,11 +18,7 @@ community-first, modern platform for sharing JavaScript and TypeScript code.
1818
## Governance Board
1919

2020
The governance board is responsible for overseeing the project and ensuring that
21-
it remains true to its mission. The governance board has not yet been formed,
22-
but will consist of community members from various organizations relevant to the
23-
JavaScript ecosystem.
24-
25-
The governance board will be responsible for:
21+
it remains true to its mission. The governance board is responsible for:
2622

2723
- Overseeing JSR's move to a foundation
2824
- Setting the general direction of the project
@@ -33,10 +29,24 @@ The governance board will be responsible for:
3329
- Determining how to review open source contributions to the project, and how to
3430
add new reviewers to the project
3531

36-
The governance board will initially be formed out of trusted members of the
37-
community who have prior experience with open source projects and open
38-
governance. If you are interested, please email
39-
[[email protected]](mailto:[email protected]).
32+
### Members
33+
34+
The governance board consist of community members from various organizations
35+
relevant to the JavaScript ecosystem. Its current members are:
36+
37+
- Evan You (creator of Vue.js, founder of [VoidZero](https://voidzero.dev/))
38+
- Isaac Schlueter (creator of npm, [vlt](https://www.vlt.sh/))
39+
- James Snell ([Node.js](https://nodejs.org) TSC member,
40+
[Cloudflare](https://www.cloudflare.com))
41+
- Luca Casonato (core member of [Deno](https://deno.land))
42+
- Ryan Dahl (creator of [Node.js](https://nodejs.org) and
43+
[Deno](https://deno.land))
44+
45+
### Meetings
46+
47+
The governance board has meetings that are held privately, but releases notes
48+
from each meeting. You can find these notes on
49+
[GitHub](https://github.com/jsr-io/jsr/issues?q=label%3Ameeting%20is%3Aclosed%20Board).
4050

4151
## Moderation Group
4252

@@ -71,9 +81,9 @@ There is not currently a policy in place to determine how contributions to the
7181
JSR project are accepted. This will be determined by the governance board.
7282
Currently reviews are done by the Deno team.
7383

74-
## Open Working Group Meetings
84+
## Office Hours
7585

76-
JSR holds open working group meetings every two weeks on Fridays
86+
JSR holds office hour meetings every two weeks on Thursdays
7787
([view the public calendar](https://deno.co/jsr-meeting)).
7888

79-
[View video recordings of previous meetings here](https://drive.google.com/drive/folders/1nkV3s4SQP2-lQdy---0oHwHSVCjzhJlR).
89+
[View video recordings of previous meetings on YouTube](https://www.youtube.com/@jsr-io/videos).

‎frontend/docs/toc.ts

Lines changed: 16 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,12 @@ export interface TOCEntry {
55
group: typeof groupsNames[number];
66
}
77

8-
export const groupsNames = ["Guide", "Reference", "Use JSR with"] as const;
8+
export const groupsNames = [
9+
"Guide",
10+
"Reference",
11+
"Governance",
12+
"Use JSR with",
13+
] as const;
914

1015
export default [
1116
{
@@ -118,16 +123,21 @@ export default [
118123
id: "usage-policy",
119124
group: "Reference",
120125
},
121-
{
122-
title: "Governance",
123-
id: "governance",
124-
group: "Reference",
125-
},
126126
{
127127
title: "API",
128128
id: "api",
129129
group: "Reference",
130130
},
131+
{
132+
title: "Overview",
133+
id: "governance/overview",
134+
group: "Governance",
135+
},
136+
{
137+
title: "Charter Document",
138+
id: "governance/charter",
139+
group: "Governance",
140+
},
131141
{
132142
title: "Deno",
133143
id: "with/deno",

0 commit comments

Comments
 (0)