constitution.tex 17.9 KB
Newer Older
1
2
3
4
5
6
\documentclass{article}

\usepackage[top=1in,bottom=1in,left=1in,right=1in]{geometry}

\title{\bfseries Constitution of Student-Run Computing and Technology at 
George Mason University}
7
\date{Date drafted: \today}
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
\author{\texttt{srct@gmu.edu}}

\setcounter{secnumdepth}{0}

\usepackage{hyperref}

\usepackage{color}

\pagenumbering{gobble}

\begin{document}
  
  \maketitle
  
  %%%%%%%%%%%%%
  %%% SECTION 1: Name of Organization
  %%%%%%%%%%%%%
  \section{Article I --- Name of Organization}
  This student organization shall be named Student-Run Computing and 
  Technology (SRCT). The website for SRCT shall be located at 
  \url{srct.gmu.edu}.
  
  %%%%%%%%%%%%%
  %%% SECTION 2: Purpose of Organization
  %%%%%%%%%%%%%
  \section{Article II --- Purpose of Organization}
  Student-Run Computing and Technology (SRCT) will seek to enhance 
  student computing at Mason. SRCT will focus on establishing and 
  maintaining systems which would provide specific services to the 
  general Mason community.
  
Chris Reffett's avatar
Chris Reffett committed
39
40
41
42
43
44
45
  \subsection{Open Source}
  SRCT is strongly committed to the principles of Free and Open Source
  Software, and it is recommended that software used by or created by SRCT be
  Free and Open Source. However, we do acknowledge that there are times when
  proprietary software is more practical or more appropriate, and so our
  committment to open source shall not be considered an absolute requirement.
  
46
47
48
49
50
  %%%%%%%%%%%%%
  %%% SECTION 3: Membership
  %%%%%%%%%%%%%
  \section{Article III --- Membership}
  Membership in this organization will not be restricted on the basis of 
51
52
53
  race, color, religion, ethnicity, national origin, physical or mental 
  disability, sexual orientation, veteran status, gender identity, gender 
  expression, sex, or age. 
54
55
56
  \\ \\
  Membership is open to all currently enrolled GMU students in good 
  academic standing with the university with a minimum cumulative GPA of 
57
  at least 2.0 who support the advancement of the organization's 
58
59
60
  principles.
  \\ \\
  SRCT members will be classified as either \textbf{contributors} or 
61
  \textbf{developers}. In this document, the term ``general membership''
62
  shall refer to the combined body of contributors and developers.
63
64
65
66
67
68
69
70
  
  \subsection{Contributors}
  Contributors are individuals interested in joining the SRCT community. 
  All new members of SRCT are initially considered contributors. These 
  members may not participate in official votes, nor will they have 
  access to SRCT project management positions. They may contribute to 
  SRCT projects under the guidance and supervision of a project 
  manager.
Michael Bailey's avatar
Michael Bailey committed
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
  
  \subsection{Project Manager Positions}
  Project Managers are the lead figures in individual SRCT projects. 
  Project managers have the final determination of what elements or 
  decisions enter the production phase of a project, with the exception of the
  Systems Administrator having veto authority if the change presents a clear and 
  present security risk or management inconvenience, or a veto by simple majority by the 
  executive board if it impacts the larger perception of SRCT or the university. In the event
  a project manager for a project does not exist and there is no distinct interest in 
  someone taking on the position, the systems administrator will approve production
  changes at his/her own discretion.
  
  Project Managers will be elected at the discretion of the President, Vice President, and 
  Systems Administrator in a simple majority. To remove a project manager is also done
  at the discretion of the President, Vice President and Systems Administrator in a simple
  majority.
  Physical attendance should not be mandatory for participation in this vote.
  
Chris Reffett's avatar
Chris Reffett committed
89
90
91
  \subsection{Becoming a Developer}
  To attain developer status, a contributor must demonstrate leadership skills,
  commitment to SRCT principles, and technical ability. To become a developer,
92
  a contributor (hereafter referred to as ``prospective developer'') should
Chris Reffett's avatar
Chris Reffett committed
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
  notify the Executive Board of their desire to become a developer and present
  a justification for gaining developer status. This justification should
  include a brief history of the prospective developer's contributions to the
  organization. Alternatively, a developer may nominate a contributor to the
  Board and provide a similar rationale. The Board will review the rationale
  and vote on whether to admit the prospective developer. If the Board votes
  against admitting the developer, then the developer body (including the
  members of the Executive Board) shall be provided with the prospective
  developer's rationale and will have their own chance to vote, conducted
  according to the rules of an official vote. If the developers vote to
  admit the prospective developer, they shall be admitted without prejudice.
  If the developers vote to not admit the prospective developer, then the
  prospective developer shall not be given developer status, but may re-apply
  in the future. No prospective developer may be voted on more than twice in
  one semester.
108
109
110
111
112
113
114
115
116
117
118

  \paragraph{Developer Selection Criteria}
  To be accepted as a developer, an individual must meet two of the
  following three criteria, with emphasis on the first two.

  \begin{itemize}
    \item Active contributions to SRCT software projects.
    \item Active leadership participation in SRCT community events.
    \item Active social participation in the SRCT community, including
    meeting or event attendance.
  \end{itemize}
119
120
121
122
123
124
125
126
127
128
129
130
131
132
  
  \subsection{Developers}
  Developers are individuals invested in the SRCT community. These 
  members have full voting rights and may request project management 
  positions. A project management position entails access to SRCT 
  infrastructure as required by their project, and as overseen by the
  System Administrator. Additionally, project management entails the
  responsibility to maintain project documentation and oversee project
  development. Developers may also contribute to SRCT projects under 
  the guidance and supervision of the project manager. To attain 
  developer status, a contributor must demonstrate leadership skills, 
  commitment to SRCT principles, and technical ability. Prospective 
  developers will be selected based on these qualifications by official 
  vote. Any prospective developer will not be voted on more than twice 
133
134
135
136
137
138
139
140
  per semester.
  Any developer who leaves the university, whether by graduating or otherwise,
  loses their developer status. Developers who graduate automatically become
  alumni members. Developers who leave the university without graduating
  do not automatically gain alumni status, but may request alumni status
  from the Executive Board, who will decide the matter by a majority vote.
  Developers who are expelled lose their developer status and may not request
  alumni status.
Chris Reffett's avatar
Chris Reffett committed
141
142
143
144
145
  \\ \\
  The following categories, \textbf{alumni members} and
  \textbf{honorary members}, are special categories of membership. The
  purpose of these categories is to allow non-GMU people to contribute to
  SRCT. Members of these categories shall be listed as members, but will
146
  not be counted in membership totals, and will not count as ``Members'' when
Chris Reffett's avatar
Chris Reffett committed
147
148
149
150
151
152
  this document refers to such.

  \subsection{Alumni Members}
  Alumni members are former developers or contributors who graduated
  from George Mason in good standing with SRCT. They may contribute to
  projects and offer advice, but they may not vote, hold leadership
153
  positions, or control SRCT resources.
Chris Reffett's avatar
Chris Reffett committed
154
155
156
157
158
159
160
161

  \subsection{Honorary Members}
  Honorary members are people who have been recognized for providing
  significant service, expertise, or other contributions to SRCT. They
  may be nominated by any contributor or developer and must be approved
  by a majority vote of the Executive Board. They may contribute to projects
  and offer advice, but may not vote, hold leadership positions, or control
  SRCT resources.
162

163
164
  \subsection{Revocation of Membership}
  In extraordinary circumstances, if a motion is brought and seconded at 
165
166
167
168
169
170
171
  a meeting for revocation of a developer's status, the SRCT general membership
  will be notified by email of the motion not less than five days before the
  following meeting. If a quorum of developers is present, an official vote 
  will be held by secret ballot, requiring a $\frac{3}{4}$ supermajority of 
  present developers. Although an official vote, all present contributors will
  be allowed to present arguments for or against revocation of developer
  status prior to the vote. 
172
  \\ \\
173
174
  Developer status will be automatically removed if suspended or expelled by 
  the university.
175
176
177
178
179
  
  %%%%%%%%%%%%%
  %%% SECTION 4: Officers
  %%%%%%%%%%%%%
  \section{Article IV --- Officers}
180
  Officers' terms are for two semesters; there are no term limits. All 
181
182
183
184
185
186
  officers will attend any training required by OSI. The 
  \textbf{Executive Board} is defined as the collection of all five
  officer positions.
  
  \subsection{President}
  The President of SRCT presides over all meetings; serves as 
187
  spokesperson for SRCT; acts as its main liaison to the Advisor, 
188
  and OSI; oversees the transition to next semester's officers, and 
Manuel Gauto's avatar
Manuel Gauto committed
189
190
  ensures SRCT fulfills its constitutional obligations. Upon election,
  the president assumes a position on the Infrastructure Management Team.
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
  
  \subsection{Vice President}
  The Vice President assists the President of SRCT to the extent the 
  President requests, and assumes the responsibilities of the President 
  in the President's absence, resignation, or removal. The Vice 
  President oversees all voting.
  
  \subsection{Treasurer}
  The Treasurer keeps accurate records of any expenditures and 
  accounting as outlined by the Office of Student Involvement's 
  ``Fiscal Management Policies and Forms.''
  
  \subsection{Secretary}
  The Secretary takes minutes at each meeting and publishes them to 
  SRCT's website, keeps record of the membership status of SRCT members, 
  and maintains all other necessary records and files.
  
  \subsection{System Administrator}
Manuel Gauto's avatar
Manuel Gauto committed
209
210
211
212
  The System Administrator is technical representative for the membership body,  
  fields all questions related to technical issues from project managers, and 
  directly supervises all project managers. Upon election, the System Administrator
  assumes a position on the Infrastructure Management Team.
213
214

  \subsection{Removal of Officers}
215
216
217
218
219
  Two SRCT developers may present a motion to remove an officer. The general
  membership will be notified by email, and developers will have no fewer
  than five days to review the motion. If a quorum is present at the next
  SRCT meeting, the motion may be approved by a $\frac{3}{4}$ vote by secret 
  ballot of all present developers. This is considered an official vote.
220
221
  
  \subsection{Advisor}
222
  The primary Advisor shall be a full time member of the faculty or staff at 
223
224
225
226
227
  George Mason University. The Advisor shall be selected by agreement of 
  the officers, and it is the responsibility of the officers to find a
  replacement should the Advisor no longer be suited for the position.
  The Advisor may offer guidance and support for SRCT, but may not 
  participate in any votes.
Manuel Gauto's avatar
Manuel Gauto committed
228
229
230
231
232
233
234
235
 
  \subsection{Infrastructure Management Team}
  The Infrastructure Management Team is the body is placed in charge of all
  SRCT hardware and software. This board does not fill a seat of the 
  executive board and has no powers vested to that team. The President and
  System Administrator will have a seat on the board unless impeached or 
  removed by vote of Infrastructure Management Team. The other two members 
  are elected by the Infrastructure Management Team and remain members 
236
237
238
  until resignation or loss of affiliation with George Mason University.
  Lastly, the operation of the Infrastructure Management Team is governed 
  by the Infrastructure Management Guidelines.
Manuel Gauto's avatar
Manuel Gauto committed
239

240
241
242
243
244
  %%%%%%%%%%%%%
  %%% SECTION 5: Elections
  %%%%%%%%%%%%%
  \section{Article V --- Elections}
  \subsection{Standard Elections}
245
246
  Elections will be held during the first meeting of March, with the
  results to come into effect at the start of the following semester.
247
248
  \\ \\
  Voting shall be handled in a secret ballot to be counted by the 
249
250
251
  highest ranking executive not in contest for any officer position, or if
  all positions are in contention, then by a quorum of all developers
  not directly involved in elections.
252
253
254
255
256
257
258
259
  \\ \\
  In the event of a tie, a second round of voting will be held between 
  the top two candidates following the same procedures of the first 
  round.
  \\ \\
  In the event of a further tie, the Advisor will determine the winner.
  
  \subsection{Special Elections}
260
261
262
263
  In event of the resignation of an officer, removal of an officer, or 
  any other situation in which there is a vacant executive position,
  an election will be held to fill that position for the remainder of 
  the term following the procedures above.
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294

  %%%%%%%%%%%%%
  %%% SECTION 6: Impeachment or Resignation
  %%%%%%%%%%%%%

  \section{Article VI --- Impeachment or Resignation}
  While an officer is in an elected position, they must fulfill the 
  responsibilities of that position. If an elected officer fails to 
  perform their responsibilities or abuses the privileges of their 
  position, they will be subjected to impeachment and a subsequent 
  removal of office.
  
  \subsection{Removal of Officers}
  Two SRCT developers may present a motion to remove an officer. The general
  membership will be notified by email, and developers will have no fewer
  than five days to review the motion. If a quorum is present at the next
  SRCT meeting, the motion may be approved by a $\frac{3}{4}$ vote by secret 
  ballot of all present developers. This is considered an official vote.

  \subsection{Officer Resignation}
  In the event that an elected officer no longer wishes to hold their 
  position, they shall announce their decision at the next SRCT Organizational 
  meeting. If they are not able to attend the meeting, then they are 
  responsible for finding another method to communicate this decision to 
  the other officers.

  \subsection{Vacant Positions}
  If an elected position becomes vacant due to an impeachment or 
  resignation, a special election will be held to fill that vacant 
  position as described in Article V.II.

295
296
  
  %%%%%%%%%%%%%
297
  %%% SECTION 7: Meetings
298
  %%%%%%%%%%%%%
299
  \section{Article VII --- Meetings}
300
301
302
303
304
  SRCT shall meet on a weekly basis. Meetings should be scheduled to 
  accommodate the greatest number of members. All members of the Mason
  community are welcome to attend meetings. Attendance by SRCT 
  contributors and developers is not mandatory, but highly recommended. 
  Consistent absence may be viewed as grounds for revocation of 
305
  developer status.
306
307
308
309
310
  \\ \\
  The Executive Board has the right to call its own private meetings at
  its discretion.
  \\ \\
  A quorum shall be defined to include at least two officers, and either 
311
312
313
  a simple majority of developers or seven total developers including at
  least two officers, whichever is less. On official votes, in the event
  of a tie, the deciding vote shall be cast by the presiding officer.
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
  \\ \\
  The President shall preside over all meetings. In the event of the 
  President's absence, the meeting shall be presided over by the highest
  ranking available officer.
  \\ \\
  The most recent edition of Robert's Rules of Order will guide meeting 
  procedure.
  \\ \\
  Meetings will consist of at least one of two possible discrete 
  sections, an \textbf{organizational} section and a 
  \textbf{development} section. What type of meeting is scheduled for a
  particular week will be made clear at the time of the meeting's 
  announcement.
  
  \subsection{Organizational Meeting}
  Organizational meetings are to present motions, discuss status of SRCT 
  initiatives and other matters of interest or concern to SRCT, vote on 
  germane resolutions, and other matters permitted by SRCT's officers. 
  All members of the Mason community are welcome to present topics of 
  discussion at meetings. Developers and contributors may vote on 
  non-official resolutions.
  
  \subsection{Development Meeting}
  Development meetings are not subject to the rigorous standards 
  outlined above. They are entirely optional meetings. Development 
  meetings will be used to provide developers and contributors with an 
  opportunity to meet in person and work together on projects in a 
  relaxed atmosphere. There are no time or attendance limits, 
  requirements, or expectations placed on development meetings.
  
  %%%%%%%%%%%%%
345
  %%% SECTION 8.1: Finance
346
  %%%%%%%%%%%%%
347
  \section{Article VIII.I --- Finance}
348
349
350
351
352
353
  No dues shall ever be required as part of SRCT membership.
  \\ \\
  This clause shall not be construed to restrict other fundraising 
  mechanisms.
  
  %%%%%%%%%%%%%
354
  %%% SECTION 8.2: Amendments
355
  %%%%%%%%%%%%%
356
  \section{Article VIII.II --- Amendments}
Chris Reffett's avatar
Chris Reffett committed
357
  Two developers may jointly propose an explicitly defined 
358
359
360
  constitutional amendment at a meeting. The general membership will be 
  emailed a copy of the language of the amendment and have no fewer than
  five days to review the proposed amendment. At the next SRCT meeting, if a
361
  quorum is present, the amendment may be approved by a $\frac{3}{4}$ 
362
  vote by secret ballot of all present developers. This is considered an 
363
364
365
366
367
368
369
  official vote.
  \\ \\
  The Office of Student Involvement must review all amendments in the 
  same matter as a completely new constitution.
  \\ \\
  Changes which do not affect the meaning of the text, such as updated 
  formatting and links, may be made at the discretion of the board.
370
371
372
373
  \\ \\
  While contributors may not directly propose amendments, they may convince
  developers to sponsor an amendment on their behalf. Developers should only
  sponsor an amendment if they agree with the changes to be made.
374
375
376
377
378
379
  
  %%%%%%%%%%%%%
  %%% SECTION 9: Ratification
  %%%%%%%%%%%%%
  \section{Article IX --- Ratification}
  This constitution shall become effective upon approval by a 
380
381
  $\frac{3}{4}$ vote of the developers, and a Student Involvement staff 
  member. This is considered an official vote.
382
  \\ \\
383
  Constitution Ratified on: March 28, 2017
Manuel Gauto's avatar
Manuel Gauto committed
384

385
\end{document}