You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: proposals/CHARTER.md
+12-15Lines changed: 12 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ The Haskell Foundation Technical Track (HFTT) is a task force of the Haskell Fou
6
6
7
7
## Purpose
8
8
9
-
The HF Technical Track is an experienced group of people with knowledge of the Haskell ecosystem, responsible for the strategic technical direction on behalf of the Haskell Foundation. HFTT members should be either individuals responsible for a specific part of the Haskell ecosystem, or contributors and committers to parts of it.
9
+
The HF Technical Track is an experienced group of people with knowledge of the Haskell ecosystem, responsible for the strategic technical direction on behalf of the Haskell Foundation. HFTT members should be either individuals responsible for a specific part of the Haskell ecosystem, or contributors and committers to parts of it.
10
10
11
11
12
12
## Responsibilities
@@ -28,13 +28,13 @@ The HFTT may make decisions regarding accepted technical projects. The CTO shall
28
28
29
29
## Term
30
30
31
-
CTO participation is required and indefinite. General HFTT members serve for 3 years.
31
+
CTO participation is required and indefinite. General HFTT members serve for 3 years.
32
32
33
33
## Membership
34
34
35
35
CTO:
36
36
37
-
- Emily Pillmore ([@emilypi](https://github.com/emilypi)), Haskell Foundation
- Reporting must be accurate, consistent, and in good faith
52
52
- Changes to HFTT membership require simple majority approval
53
-
- 1 CTO and 8 general members shall be required for a functioning HFTT
53
+
- 1 CTO and 8 general members shall be required for a functioning HFTT
54
54
- No one may serve two terms consecutively, except for the CTO.
55
55
- Elections *must* be held such that there is no period when the HFTT is not at full membership
56
56
57
-
## Election Procedure
57
+
## Election Procedure
58
58
59
-
Elections shall be held in a public manner, using the forum designated by the HF bylaws for formal discussion. The CTO shall approve all language for the election publication. All additional publication on the part of the HFTT for the purpose of socializing the election should link to the formal discussion. Elections should be announced publicly exactly 60 days before member terms expire, and submissions should cease to be accepted 14 days before member terms expire, with all membership decisions finalized and publicized 7 days before member terms expire. During this 7-day lame duck period, no votes may be made on proposals.
59
+
Elections shall be held in a public manner, using the forum designated by the HF bylaws for formal discussion. The CTO shall approve all language for the election publication. All additional publication on the part of the HFTT for the purpose of socializing the election should link to the formal discussion. Elections should be announced publicly exactly 60 days before member terms expire, and submissions should cease to be accepted 14 days before member terms expire, with all membership decisions finalized and publicized 7 days before member terms expire. During this 7-day lame duck period, no votes may be made on proposals.
60
60
61
61
If not enough candidates apply for the number of seats expiring, the CTO may fill these seats as needed using their discretion.
62
62
63
63
## Becoming a member
64
64
65
-
It is not required to be a part of the HFTT in order to work on projects. In fact, it's quite the opposite: in order to find a list of projects on which to volunteer, one need only send a message (e.g. an email, slack DM, etc) to the leaders of individual projects. Likewise, individuals may freely contribute ideas and analysis of technical proposals by taking part in the HF Tech Proposal (HFTP) process commentary. However, the HFTT exists as the body empowered to ratify proposals and supervise projects to completion.
65
+
It is not required to be a part of the HFTT in order to work on projects. In fact, it's quite the opposite: in order to find a list of projects on which to volunteer, one need only send a message (e.g. an email, slack DM, etc) to the leaders of individual projects. Likewise, individuals may freely contribute ideas and analysis of technical proposals by taking part in the HF Tech Proposal (HFTP) process commentary. However, the HFTT exists as the body empowered to ratify proposals and supervise projects to completion.
66
66
67
-
In order to become a member, one must apply at election time, and be elected to the HFTT. With the exception of the first iteration of the HFTT, all members are elected by means of the election process.
67
+
In order to become a member, one must apply at election time, and be elected to the HFTT. With the exception of the first iteration of the HFTT, all members are elected by means of the election process.
68
68
69
69
70
70
## Voting Procedure
71
71
72
-
Ranked voting is used, with the following criteria required for each status:
72
+
Ranked voting is used, with the following criteria required for each status:
73
73
74
74
### HFTP Statuses
75
75
@@ -81,12 +81,12 @@ Ranked voting is used, with the following criteria required for each status:
81
81
82
82
### Membership changes
83
83
84
-
Requires 66% majority for approval. All initial membership seats shall be appointed by the CTO at their discretion.
84
+
Membership changes require 66% majority for approval. All initial membership seats shall be appointed by the CTO at their discretion.
85
85
86
86
87
87
## Reporting
88
88
89
-
HFTT members are expected to join monthly HFTP review meetings. If shepherding, project statuses should be reported at the bi-monthly HFTT standups.
89
+
HFTT members are expected to join monthly HFTP review meetings. If shepherding, project statuses should be reported at the bi-monthly HFTT standups.
90
90
91
91
92
92
## Documents
@@ -102,6 +102,3 @@ Any change to this charter requires a 66% majority vote from the HFTT, with two
102
102
* The HFTT may change its method of document storage at will.
103
103
* The HFTT may make changes to its membership according to the rules set
0 commit comments