Skip to content

Commit 133cfc5

Browse files
committed
merge
2 parents 7fa91d9 + 0ea007a commit 133cfc5

File tree

2 files changed

+37
-40
lines changed

2 files changed

+37
-40
lines changed

proposals/CHARTER.md

Lines changed: 12 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ The Haskell Foundation Technical Track (HFTT) is a task force of the Haskell Fou
66

77
## Purpose
88

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.
1010

1111

1212
## Responsibilities
@@ -28,13 +28,13 @@ The HFTT may make decisions regarding accepted technical projects. The CTO shall
2828

2929
## Term
3030

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.
3232

3333
## Membership
3434

3535
CTO:
3636

37-
- Emily Pillmore ([@emilypi](https://github.com/emilypi)), Haskell Foundation
37+
- Emily Pillmore ([@emilypi](https://github.com/emilypi))
3838

3939
Members:
4040

@@ -43,33 +43,33 @@ Members:
4343
- Andrew Lelechenko ([@Bodigrim](https://github.com/Bodigrim))
4444
- Davean Scies ([@davean](https://github.com/davean))
4545
- Edward Kmett ([@ekmett](https://github.com/ekmett))
46-
- Theophile Choutri ([@Kleidukos](https://github.com/Kleidukos))
46+
- Hécate ([@Kleidukos](https://github.com/Kleidukos))
4747
- Gil Mizrahi (@soupi)
4848

4949
## Membership Rules
5050

5151
- Reporting must be accurate, consistent, and in good faith
5252
- 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
5454
- No one may serve two terms consecutively, except for the CTO.
5555
- Elections *must* be held such that there is no period when the HFTT is not at full membership
5656

57-
## Election Procedure
57+
## Election Procedure
5858

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.
6060

6161
If not enough candidates apply for the number of seats expiring, the CTO may fill these seats as needed using their discretion.
6262

6363
## Becoming a member
6464

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.
6666

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.
6868

6969

7070
## Voting Procedure
7171

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:
7373

7474
### HFTP Statuses
7575

@@ -81,12 +81,12 @@ Ranked voting is used, with the following criteria required for each status:
8181

8282
### Membership changes
8383

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.
8585

8686

8787
## Reporting
8888

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.
9090

9191

9292
## Documents
@@ -102,6 +102,3 @@ Any change to this charter requires a 66% majority vote from the HFTT, with two
102102
* The HFTT may change its method of document storage at will.
103103
* The HFTT may make changes to its membership according to the rules set
104104
out in the *Membership Rules* section above.
105-
106-
107-

0 commit comments

Comments
 (0)