@@ -15,13 +15,17 @@ Team Membership is not time-limited. There is no fixed size of the Team.
15
15
16
16
There is no specific set of requirements or qualifications for Team Membership beyond these rules.
17
17
18
- Changes to Team membership should be proposed with an issue and labelled ` web-server-framework-agenda `
19
- to be included in the next [ team meeting] ( #team-meetings ) . Decisions are made via the
20
- [ Consensus Seeking Process] ( #consensus-seeking-process ) . If there are not objections in the
21
- issue new members may attend the meeting in which their membership is officially accepted.
18
+ Prospective members should request membership though a PR labelled ` membership-request ` which adds them to the
19
+ [ Team membership list] ( https://github.com/nodejs/web-server-frameworks/README.md#Web-Server-Frameworks-Team-Members ) .
20
+ The PR will be merged in accordance with the [ pull request consensus process] ( #Pull-Requests ) .
22
21
23
- If a Team member is unable to attend a meeting where a planned membership decision is being made,
24
- then their consent is assumed.
22
+ Team membership will be revisited every 6 months. A PR will be open moving members
23
+ without any activity in the past 6 months to a Past Collaborators list. Members
24
+ can comment on the PR to keep themselves in the members list.
25
+ The PR will be merged in 7 days in accordance with the [ pull request consensus process] ( #Pull-Requests ) .
26
+
27
+ Past collaborators may rejoin the Team using the same process specified
28
+ above for prospective members.
25
29
26
30
## Team Meetings
27
31
@@ -50,8 +54,9 @@ cannot veto or remove items.
50
54
The Team may invite persons or representatives from certain projects to
51
55
participate in a non-voting capacity.
52
56
53
- Decisions in meetings are made via the [ Consensus Seeking Process] ( #Consensus-Seeking-Process )
54
- and require a quorum of 50% of Members.
57
+ Decisions made in meetings must go through the [ pull request consensus process] ( #Pull-Requests ) .
58
+ One of the members present in the meeting will be responsible for opening the PR,
59
+ if one doesn't exist already.
55
60
56
61
The moderator is responsible for summarizing the discussion of each
57
62
agenda item and sends it as a pull request after the meeting.
@@ -74,18 +79,17 @@ Members participate in a vote.
74
79
75
80
## Pull Requests
76
81
77
- Pull requests that do not change the governance of the team can be merged into
78
- this repository provided the following conditions have been met:
82
+ Pull requests that do not change the governance of the team or remove members can
83
+ be merged into this repository provided the following conditions have been met:
79
84
80
85
* There are no outstanding objections
81
86
* There are two approvals by team members
82
87
* The PR has been open for at least 48 hours
83
88
84
- Pull requests that change governance of the team must meet the following conditions
89
+ Pull requests that change governance of the team or remove members must meet the following conditions
85
90
in addition to the ones listed for regular PRs.
86
91
87
- * The PR has been open for at least 7 days OR consensus is reached in a meeting
88
- with quorum of members.
92
+ * The PR has been open for at least 7 days.
89
93
90
94
If consensus cannot be reached, a pull request may still be landed after a vote
91
95
by the members to override outstanding objections.
0 commit comments