Skip to content

Commit 85466da

Browse files
marco-ippolitomarco-ippolito
committed
chore: create initial documentation
1 parent 49aaf13 commit 85466da

File tree

4 files changed

+183
-2
lines changed

4 files changed

+183
-2
lines changed

‎CODE_OF_CONDUCT.md

+10
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
# Code of Conduct
2+
3+
The [Node.js Code of Conduct][] applies to this team.
4+
5+
# Moderation Policy
6+
7+
The [Node.js Moderation Policy][] applies to this team.
8+
9+
[Node.js Code of Conduct]: https://github.com/nodejs/admin/blob/master/CODE_OF_CONDUCT.md
10+
[Node.js Moderation Policy]: https://github.com/nodejs/admin/blob/master/Moderation-Policy.md

‎GOVERNANCE.md

+168
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,168 @@
1+
# TypeScript Team
2+
3+
## Members
4+
5+
The [nodejs/typescript](https://github.com/nodejs/typescript) GitHub
6+
repository is maintained by the Team and additional Members who are
7+
added on an ongoing basis.
8+
9+
There are two types of Members:
10+
11+
### Active Members
12+
13+
* Invited to all meetings
14+
* Can participate in [consensus seeking process](#consensus-seeking-process)
15+
* Counted towards quorum in [Team Meetings](#team-meetings)
16+
* Participates in voting
17+
18+
### Observers
19+
20+
* Invited to all meetings
21+
* Can participate in [consensus seeking process](#consensus-seeking-process)
22+
* Not counted towards quorum in [Team Meetings](#team-meetings)
23+
* Cannot participate in voting
24+
25+
## Team Membership
26+
27+
Team Membership is not time-limited. There is no fixed size of the Team.
28+
29+
There is no specific set of requirements or qualifications for Team Membership beyond these rules.
30+
31+
Changes to Team membership should be proposed with an issue and labelled `typescript-agenda`
32+
to be included in the next [team meeting](#team-meetings). Decisions are made via the
33+
[Consensus Seeking Process](#consensus-seeking-process). If there are not objections in the
34+
issue new members may attend the meeting in which their membership is officially accepted.
35+
36+
If a Team member is unable to attend a meeting where a planned membership decision is being made,
37+
then their consent is assumed.
38+
39+
New Members to the team are initially accepted as Observers.
40+
41+
Observers can request to be made Active Members following the above process.
42+
43+
Active Members requesting to be made Observers following the above process are automatically approved
44+
by the Team and do not require consensus.
45+
46+
Any Member requesting to be removed from the group following the above process are automatically approved
47+
by the Team and do not require consensus.
48+
49+
## Team Meetings
50+
51+
The Team meets bi-weekly on Zoom.us. A designated moderator
52+
approved by the Team runs the meeting. Each meeting should be
53+
published to YouTube.
54+
55+
Items are added to the Team agenda that are considered contentious or
56+
are modifications of governance, contribution policy, Team membership,
57+
or release process.
58+
59+
The intention of the agenda is not to approve or review all patches;
60+
that should happen continuously on GitHub and be handled by the larger
61+
group of Collaborators.
62+
63+
Any community member or contributor can ask that something be added to
64+
the next meeting's agenda by logging a GitHub Issue. Any Collaborator,
65+
Team member or the moderator can add the item to the agenda by adding
66+
the ***typescript-agenda*** tag to the issue.
67+
68+
Prior to each Team meeting the moderator will share the agenda with
69+
members of the Team. Team members can add any items they like to the
70+
agenda at the beginning of each meeting. The moderator and the Team
71+
cannot veto or remove items.
72+
73+
The Team may invite persons or representatives from certain projects to
74+
participate in a non-voting capacity.
75+
76+
Decisions in meetings are made via the [Consensus Seeking Process](#consensus-seeking-process)
77+
and require a quorum of 50% of Active Members.
78+
79+
The moderator is responsible for summarizing the discussion of each
80+
agenda item and sends it as a pull request after the meeting.
81+
82+
## Consensus Seeking Process
83+
84+
The Team follows a
85+
[Consensus Seeking](http://en.wikipedia.org/wiki/Consensus-seeking_decision-making)
86+
decision-making model.
87+
88+
When an agenda item has appeared to reach a consensus, the moderator
89+
will ask "Does anyone object?" as a final call for dissent from the
90+
consensus.
91+
92+
If an agenda item cannot reach a consensus, a Team member can call for
93+
the item to be decided by a vote or to table the issue to the next
94+
meeting. In both cases the decision must be seconded by a majority of the Team
95+
or else the discussion will continue. Simple majority wins. Only Active
96+
Members participate in a vote.
97+
98+
## Pull Requests
99+
100+
This section details expectations for team members involved in any pull
101+
requests that relate to the group's [scope][typescript-team-purpose].
102+
103+
The following expectations apply to all team members involved in a related pull
104+
requests in [this Repository][nodejs-typescript]. This section does
105+
not apply to [the Node.js core repository](https://github.com/nodejs/node).
106+
107+
These expectations are intended to ensure that all concurrent efforts align
108+
with the overall direction of the group for delivering a cohesive and predictable
109+
user experience for TypeScript support in Node.js.
110+
111+
Pull requests not included under the *special exemptions* section below must
112+
reach consensus in a meeting in order to be merged into this repository. A pull
113+
request that is is unable to reach consensus cannot be merged into this
114+
repository.
115+
116+
### Special Exemptions to the PR landing process
117+
118+
Special exception is made for pull requests seeking to make any of the following
119+
changes to this repository:
120+
121+
* Errata fixes.
122+
* Editorial changes.
123+
* Meeting minutes.
124+
* Updates to the team lists via the `ncu-sync` tool.
125+
* Doc Fixes
126+
* Tests
127+
* Fixing Conflicts with a rebase
128+
129+
These pull requests may be merged without being presented at a meeting if a
130+
reasonable time is given for review and there no dissent. The time period seen
131+
as reasonable for review varies on a case by case basis as determined by the
132+
author. A member may request a specific time period for review of such a pull
133+
request not to exceed the next meeting date. If a time for review is requested,
134+
members must wait for that time period to pass or review be completed prior to
135+
that time.
136+
137+
<a id="developers-certificate-of-origin"></a>
138+
139+
## Developer's Certificate of Origin 1.1
140+
141+
By making a contribution to this project, I certify that:
142+
143+
* (a) The contribution was created in whole or in part by me and I
144+
have the right to submit it under the open source license
145+
indicated in the file; or
146+
147+
* (b) The contribution is based upon previous work that, to the best
148+
of my knowledge, is covered under an appropriate open source
149+
license and I have the right under that license to submit that
150+
work with modifications, whether created in whole or in part
151+
by me, under the same open source license (unless I am
152+
permitted to submit under a different license), as indicated
153+
in the file; or
154+
155+
* (c) The contribution was provided directly to me by some other
156+
person who certified (a), (b) or (c) and I have not modified
157+
it.
158+
159+
* (d) I understand and agree that this project and the contribution
160+
are public and that a record of the contribution (including all
161+
personal information I submit with it, including my sign-off) is
162+
maintained indefinitely and may be redistributed consistent with
163+
this project or the open source license(s) involved.
164+
165+
<!-- Links -->
166+
167+
[nodejs-typescript]: https://github.com/nodejs/typescript
168+
[typescript-team-purpose]: ./README.md#purpose

‎LICENSE renamed to ‎LICENSE.md

File renamed without changes.

‎README.md

+5-2
Original file line numberDiff line numberDiff line change
@@ -1,2 +1,5 @@
1-
# typescript
2-
TypeScript support in Node.js core
1+
# TypeScript Team
2+
3+
## Purpose
4+
5+
The Node.js TypeScript Team maintains and actively develops the TypeScript support implementation in Node.js core.

0 commit comments

Comments
 (0)