RTP Changes - Copyright Grant Hawerlander #256
Conversation
There was a problem hiding this comment.
I really like this amendment! The renewal process idea is very clever.
See attached proposals on wording.
My semantic questions are:
- Would we want this to be every semester as is currently written, or once per year?
- Why is extending an RTP a full selection process involving E-Board (considering the RTP will still be subject to renewal)?
- The current language seems to allow alumni to be voted in as RTPs for the first time. Is this the intent of the amendment?
| At the conclusion of each standard operating session, those intending to keep the rights and responsibilities of a current RTP must participate in a renewal process. | ||
| During the second to last E-Board Meeting of the semester, the OpComm Director shall present a formal statement summarizing the contributions and performance of each RTP. | ||
| After each statement, an E-Board Vote, as described in \ref{Executive Board Vote}, will be conducted to determine each candidate's continuation. | ||
| Failure to secure the required majority vote will result in the RTP being required to resign their position. |
There was a problem hiding this comment.
Proposal: "Any RTP who fails to receive the required majority vote must resign from their position and become a Prior RTP."
There was a problem hiding this comment.
Why is this a resigning? Why do they not simply become?
| The current RTPs may draft rules and regulations specifying the rights and privileges of Prior RTPs. | ||
|
|
||
| \asubsubsection{Renewal of a Root Type Person} | ||
| At the conclusion of each standard operating session, those intending to keep the rights and responsibilities of a current RTP must participate in a renewal process. |
There was a problem hiding this comment.
Proposal: "At the end of each Standard Operating Session, individuals wishing to retain their rights and responsibilities as a Root Type Person (RTP) must undergo a renewal process."
| The current RTPs may draft rules and regulations specifying the rights and privileges of Prior RTPs. | ||
|
|
||
| \asubsubsection{Renewal of a Root Type Person} | ||
| At the conclusion of each standard operating session, those intending to keep the rights and responsibilities of a current RTP must participate in a renewal process. | ||
| During the second to last E-Board Meeting of the semester, the OpComm Director shall present a formal statement summarizing the contributions and performance of each RTP. |
There was a problem hiding this comment.
Proposal: "During the second-to-last E-Board meeting of the Standard Operating Session, the OpComm Director will deliver a formal report on each RTP that outlines their contributions and overall performance."
There was a problem hiding this comment.
nit: what is a formal report? specifically, what makes it formal in this context?
| \asubsubsection{Renewal of a Root Type Person} | ||
| At the conclusion of each standard operating session, those intending to keep the rights and responsibilities of a current RTP must participate in a renewal process. | ||
| During the second to last E-Board Meeting of the semester, the OpComm Director shall present a formal statement summarizing the contributions and performance of each RTP. | ||
| After each statement, an E-Board Vote, as described in \ref{Executive Board Vote}, will be conducted to determine each candidate's continuation. |
There was a problem hiding this comment.
Proposal: "Following each report, the E-Board will conduct a vote as outlined in Section~\ref{Executive Board Vote} to determine whether the RTP will continue in their role."
| \renewcommand{\theenumi}{\arabic{enumi}} % For this section, we want items to use letters | ||
| \begin{enumerate} | ||
| \item Sign the Code of Conduct sheets pertaining to the responsible utilization of CSH and RIT facilities. | ||
| \item Obtain greater than or equal to 60\% of required signatures, excluding those of On-Floor Members who have not passed a Membership Eval, in the Intro Packet or successfully complete Intro Eval. | ||
| \item Obtain greater than or equal to 60\% of required signatures, excluding those of On-Floor Members who have not passed a Membership Eval, in the Intro Packet, or successfully complete Intro Eval. |
There was a problem hiding this comment.
Proposal: "\item Obtain greater than or equal to 60% of required signatures in the Intro Packet, excluding those of On-Floor Members who have not passed a Membership Eval, or successfully complete the Intro Eval."
| @@ -744,8 +744,11 @@ \subsection{Modifying the Constitution} | |||
| E-Board may choose to approve or reject the nomination by E-Board Vote with a quorum of seventy-five percent of the Eligible Votes. | |||
|
|
|||
| \asection{Root Type Persons} | |||
| The OpComm Directorship is responsible for overseeing the implementation of maintenance and upgrades to the CSH computer systems networks. | |||
| It is a self-governing committee making decisions by Immediate Relative Majority vote with two-thirds quorum of current RTPs. | |||
| Root Type Persons are the members that make up the OpComm Directorship. | |||
There was a problem hiding this comment.
Proposal: Root Type Persons are the members of the OpComm Directorship.
| The OpComm Directorship is responsible for overseeing the implementation of maintenance and upgrades to the CSH computer systems networks. | ||
| It is a self-governing committee making decisions by Immediate Relative Majority vote with two-thirds quorum of current RTPs. | ||
| Root Type Persons are the members that make up the OpComm Directorship. | ||
| They are responsible for overseeing the implementation of maintenance and upgrades to the CSH computer systems and networks. |
There was a problem hiding this comment.
Proposal: "They are responsible for maintaining and upgrading the CSH computer systems and networks."
| They are responsible for overseeing the implementation of maintenance and upgrades to the CSH computer systems and networks. | ||
|
|
||
| \asubsection{OpComm Directorship} | ||
| The OpComm Directorship is a committee making decisions by Immediate Relative Majority vote with two-thirds quorum of current RTPs. |
There was a problem hiding this comment.
Proposal: "The OpComm Directorship makes decision by Immediate Relative Majority votes requiring a two-thirds quorum of RTPs."
|
|
||
| \asubsubsection{Prior Root Type Persons} | ||
| Prior RTPs are those members who are no longer current Active Members and have not been granted an extension by the current RTPs. | ||
| Prior RTPs are not guaranteed access to the current root passwords and other authentication tokens. | ||
| Prior RTPs are any members who were previously an RTP and are not currently an Active Member or on an extension given by the RTPs. |
There was a problem hiding this comment.
Proposal: "Prior RTPs are former RTP members."
| An E-Board Vote, as described in \ref{Executive Board Vote}, is taken to determine whether the nominations of the RTP(s) are accepted. | ||
| \end{enumerate} | ||
| Giving an extension to a previous Active Member is the same as starting a selection process for a new RTP and should also follow this process. |
There was a problem hiding this comment.
Why is extending a prior Active Member a full separate selection process, as opposed to an RTP vote? (They'll still be subject to renewal so it seems cumbersome to do both.)
The language on this is also a bit unclear but I think resolving the semantic question will help with this.
| Prior RTPs are those members who are no longer current Active Members and have not been granted an extension by the current RTPs. | ||
| Prior RTPs are not guaranteed access to the current root passwords and other authentication tokens. | ||
| Prior RTPs are any members who were previously an RTP and are not currently an Active Member or on an extension given by the RTPs. | ||
| Prior RTPs are not guaranteed access to any elevated permissions to any systems or networks, including but not limited to the RTP LDAP role, Vault, or the root password. |
There was a problem hiding this comment.
why specify Vault? Authentication tokens and root passwords already covered this beyond any specific configuration or technology
(to quibble, we don't use hashicorp's vault, we have vaultwarden, and 5 years ago we had passbolt)
| At the conclusion of each standard operating session, those intending to keep the rights and responsibilities of a current RTP must participate in a renewal process. | ||
| During the second to last E-Board Meeting of the semester, the OpComm Director shall present a formal statement summarizing the contributions and performance of each RTP. | ||
| After each statement, an E-Board Vote, as described in \ref{Executive Board Vote}, will be conducted to determine each candidate's continuation. | ||
| Failure to secure the required majority vote will result in the RTP being required to resign their position. |
There was a problem hiding this comment.
Why is this a resigning? Why do they not simply become?
| The current RTPs may draft rules and regulations specifying the rights and privileges of Prior RTPs. | ||
|
|
||
| \asubsubsection{Renewal of a Root Type Person} | ||
| At the conclusion of each standard operating session, those intending to keep the rights and responsibilities of a current RTP must participate in a renewal process. | ||
| During the second to last E-Board Meeting of the semester, the OpComm Director shall present a formal statement summarizing the contributions and performance of each RTP. |
There was a problem hiding this comment.
nit: what is a formal report? specifically, what makes it formal in this context?
|
I still have concerns that this will just result in less RTPs, making it harder to ask an RTP for something, and also making it harder for an alum to help in the event something goes catastrophically wrong. The way this was described to me, it was just that an RTP would no longer be active and not count towards RTP votes, but that's not the case here. Good chance I'm wrong about this, but... I don't know. |
|
What's the motivation for this change? All I've heard regarding the 'why' has been word-of-mouth. |
Check one:
Summary of change(s):
RTPs are no longer RTP for life, RTPs will give notes to the OpComm Director and Opcomm will give the notes to Eboard and Eboard will vote on the RTP. The outcomes of this vote will be either the RTP will stay on for the next operating session or the RTP will no longer be an active RTP and perms will be removed by the end of the operating session.