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
+14-12Lines changed: 14 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,42 +23,44 @@ HFTT Members are tasked with the following responsibilities:
23
23
24
24
None.
25
25
26
-
The HFTT may make decisions regarding accepted technical projects. The CTO shall arrange budgetary or resource requests as needed, based on the outcome of decisions made by the HFTT, with the budget committee and Executive Director of the HF.
26
+
The HFTT may make decisions regarding accepted technical projects. The CTO (or other delegated authority) shall arrange budgetary or resource requests as needed, based on the outcome of decisions made by the HFTT, with the budget committee and Executive Director of the HF.
27
27
28
28
29
29
## Term
30
30
31
-
CTO participation is required and indefinite. General HFTT members serve for 3 years.
31
+
The participation of least one person who is an HF Executive or delegated authority is required. General HFTT members serve for 3 years.
- Joachim Breitner ([@nomeata](https://github.com/nomeata/))
48
50
49
51
## Membership Rules
50
52
51
53
- Reporting must be accurate, consistent, and in good faith
52
54
- Changes to HFTT membership require simple majority approval
53
-
- 1 CTO and 8 general members shall be required for a functioning HFTT
54
-
- No one may serve two terms consecutively, except for the CTO.
55
+
- 1 Delegated authority and 8 general members shall be required for a functioning HFTT
56
+
- No one may serve two terms consecutively, except for the CTO/delegated authority.
55
57
- Elections *must* be held such that there is no period when the HFTT is not at full membership
56
58
57
59
## Election Procedure
58
60
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.
61
+
Elections shall be held in a public manner, using the forum designated by the HF bylaws for formal discussion. The CTO or other HF-delegated authority 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
62
61
-
If not enough candidates apply for the number of seats expiring, the CTO may fill these seats as needed using their discretion.
63
+
If not enough candidates apply for the number of seats expiring, the CTO or other HF-delegated authority may fill these seats as needed using their discretion.
0 commit comments