Giter Club home page Giter Club logo

constitution's Introduction

CSH Constitution

The master branch's HEAD is the current legal constitution of CSH.

A compiled version of the document can be found here.

Modifying the Constitution

Do not make changes to master without their passing the proper house voting procedures. (At the very least, not text changes, anyways)

First, fork the consitution repo. Before making any changes, create a new git branch.
This helps us keep the constitution repo neat and is in general a good idea.

git checkout -b "branch_name"

A good branch name will briefly give an idea of what your changes have actually done.

Once you have made your changes, commit them with a proper commit message.
It is good practice to have an imperative clause in the subject line of your commit message.
Also, if your commit fixes any issues, put the issue number (with a # sign) in the commit body. ex: fixes #102

Also, be sure to rebase multiple commits into one before making a pull request.

Document Style

One sentence, one line. In general, follow the pattern of the existing document.

Software Requirements

Must have make, and pdflatex installed.

Installing dependencies on debian

sudo apt install texlive texlive-formats-extra make

Installing dependencies on fedora

sudo yum install texlive make

Compiling the Constitution

Once required software is installed, simply run make. Running make will build and link the articles properly. Review the PDF output to check for any errors before making a pull request. If additional commits are made, be sure to rebase down to one commit before submitting a pull request.

Submitting a Pull Request or Issue

To make contributing easier, there are templates for both issues and pull requests. Please fill out the appropriate options in the description as you make the pull request or issue so a maintainer can more easily help get your change committed. If you are making a pull request, be sure to make a pull request against origin/master from your own branch.

Step by Step Recap

  1. Fork this repo
  2. Make a new branch on your fork
  3. Modify the .tex files with your changes
  4. Commit, Push and make a Pull Request
  5. Announce the amendment at House Meeting.
  6. Wait for vote to pass then merge changes

constitution's People

Contributors

ajgajg1134 avatar bencentra avatar bmbowdish avatar clockfort avatar crigney3 avatar csssuf avatar devinmatte avatar galenguyer avatar gambogi avatar jabbate19 avatar jdrit avatar jeid64 avatar liam-middlebrook avatar mbillow avatar mco9734 avatar mfrancis95 avatar mstrodl avatar mxmeinhold avatar owencmiller avatar ramzallan avatar rossdylan avatar saucetray avatar sgreene570 avatar speakerbug avatar spencercreveling avatar stevenmirabito avatar talcohen avatar willdignazio avatar worr avatar zthart avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

constitution's Issues

Extra dependency needed on Ubuntu

On Ubuntu, I also needed texlive-formats-extra in order to build. Maybe this is the same on Debian. I'm not sure what the equivalent yum package is, if needed.

diff --git a/README.md b/README.md
index 730f79a..4fdffc7 100644
--- a/README.md
+++ b/README.md
@@ -31,7 +31,7 @@ Must have make, and pdflatex installed.
 
 Installing dependencies on debian
 
-`sudo apt install texlive make`
+`sudo apt install texlive texlive-formats-extra make`
 
 Installing depencdencies on fedora
 

PR Can't Have a Budget?

In the creation of the PR directorship budget in #219, 5% of the budget was allocated away from accum, but it also was not allocated away from accum it seems (attention to lines 503 and 508 509)

Accumulated & 5\% \\
\hline
\end{tabular}
\end{center}
The suggested total operational budget is \$8064.
This figure is based on yearly estimated on-floor member dues (\$160 x 72 members = \$11520) minus the 10\% reserved for Accumulated (Accum).

Define amount of freshmen rooms

Check one:

  • Semantic Issue: something about the meaning of the text is different
  • Non-semantic Issue: Spelling, grammar, or formatting changes.

Summary of issue:

Housing board/selections thing - How many freshmen rooms should be reserved for next year 33%.

Punctuation on bullet point lists is inconsistent

Check one:

  • Semantic Issue: something about the meaning of the text is different
  • Non-semantic Issue: Spelling, grammar, or formatting changes.

Summary of issue:
Some bullet lists have periods at the end of every list item, some do not. This is very minor, but could probably be scripted and fixed quickly.

Updating Constitution to match Current RIT Policy

Check one:

  • Semantic Issue: something about the meaning of the text is different
  • Non-semantic Issue: Spelling, grammar, or formatting changes.

Summary of issue:
As is the goal of the new constitution committee, we are moving to update our constitution to fall more in line with current RIT policy and co-opt sections that push us towards more modern expectations. Sections we should work to include start with but are not limited to:

  • Defined policy for practices often covered by Judicial's
  • Rights of members (from house and within house)
  • Clearly defined Anti-Hazing policy
  • Extension of RIT's policies where applicable

This list can expand and change, but this is the initial list based on recent discussions in house meeting as a starting point.

Grammar problem.

Check one:

  • Semantic Issue: something about the meaning of the text is different
  • Non-semantic Issue: Spelling, grammar, or formatting changes.

Summary of issue:
What are articles?
https://github.com/ComputerScienceHouse/Constitution/blob/master/bylaws.tex#L296
"If the member has previously passed an Membership Evaluation they will move to Alumni Membership status at the end of the Standard Operating Session (\ref{Alumni Membership Selection})."

Change an to a.

References to other parts of the Constitution and By-Laws don't specify which document they are referring to

Check one:

  • Semantic Issue: something about the meaning of the text is different
  • Non-semantic Issue: Spelling, grammar, or formatting changes.

Summary of issue:
Constitution 3.A.2 contains "the selection process as defined in 4.B." the 4.B is "linked" to Section 4.B "Closed Executive Board" which is clearly not the selection process. I assume that this 4.B is referring to By-Laws 4.B, which are about the selection process. I propose this "link" should be removed or changed to be a link to the By-Laws (if possible).

Similar problems are in the documents as a whole, with both documents using the same numbering system and not specifying which document is being referred to. I propose that there should be some means to differentiating which document is being referred to.

On-Floor Status Vote

Check one:

  • Semantic Issue: something about the meaning of the text is different
  • Non-semantic Issue: Spelling, grammar, or formatting changes.

Summary of issue:
During our Introductory Evaluations meeting we seem to automatically go for an On-Floor Status vote. The constitution does not mandate this, and I think we should talk about whether or not we should just stop doing it or an amendment needs to be added. I think house is generally in agreement that the On-Floor Status vote is a waste of time usually.

Is this how it has always been? Are there any Nth years that remember it being different?

Clarity for alumni in good standing

Check one:

  • Semantic Issue: something about the meaning of the text is different
  • Non-semantic Issue: Spelling, grammar, or formatting changes.

Summary of issue:
Section 3.B.7 and 3.C.2 are very vague about what happens when a member goes into alumni status.
specifically in 3.C.2

Active members who depart house without passing the current operating session’s Membership Evaluations are considered to be Alumni in bad standing. This may be appealed to the Executive Board in order to pursue a different outcome.

The current operating session's membership evaluation is a little unclear on when member can become an alumni in good standing. Can this only be done over the summer? I'm not sure if this is the way we've done it in the past, and we should probably rethink it and bring it up to date.

Vacated position

Line 394 is vague as to whether the inability to vote is true if the position is held by a stand-in member or the chairman

Advisory membership process appears to just be weird.

In the bylaws this section pops up.
d. Ballots will then be distributed for a secret ballot, fifty-percent House vote, as defined in 5.C.2. If more than two advisors are selected via this process, the Executive Board may call for a revote amongst the candidates selected in order to reduce the number of advisors to a workable level. If this decision is made, the candidates selected in the first ballot become the nominees for the second ballot and Step Three and Four are repeated. This recast process may not be repeated a second time.

This section is "numbered" by letter and references a three and four, which do not exist.

Also, it should probably be changed to say "as defined in the Constitution in 5.C.2" as that is talked about in the constitution not in the bylaws. Also, if you wanted to shorten that, you could define something like B.5.C.2 as bylaws section 5.C.2 and C.5.C.2 as constitution section 5.C.2. Just a thought.

Issue with References

Check one:

  • Semantic Issue: something about the meaning of the text is different
  • Non-semantic Issue: Spelling, grammar, or formatting changes.

Summary of issue:
There are currently 12 issues that aren't properly being displayed. The references need to be fixed. They currently display as ??

Line Reference Text
159 \ref{Selection Processes}
161 \ref{Expectations of an Introductory Member}
166 \ref{Introductory Evaluation}
184 \ref{Expectations of House Members}
199 \ref{Evaluations Processes}
244 \ref{Selection Process for Honorary Members}
262 \ref{Selection Process for Advisory Members}
339 \ref{Standard Operating Session}
343 \ref{Expectations of House Members}
344 \ref{Membership Evaluation}
347 \ref{Standard Operating Session}
460 \ref{Operations of the Operational Communications Directorship}

The issue lies within the Makefile, and that we need there to be existing .pdf files in order for the links to properly reference.

update hazing note

Check one:

  • Semantic Issue: something about the meaning of the text is different
  • Non-semantic Issue: Spelling, grammar, or formatting changes.

Summary of issue:

In section 4.B.1, at the bottom as an additional note, it reads

Additional Note:  No hazing shall occur at any time during the Selection Process in accordance with theNew York State Hazing Laws.

which should probably be expanded upon, and also default to RIT's hazing policy instead of New York state law. Maybe make a new subsection for what is and is not permitted.

Update number of on-floors + recalculate yearly budget

Check one:

  • Semantic Issue: something about the meaning of the text is different
  • Non-semantic Issue: Spelling, grammar, or formatting changes.

Summary of issue:

Since dropping Fish from on-floor housing, the max number of on-floor members has dropped from 72 to 55. This should be reflected in section 5.D.1.C "Breakdown of Dues for Directorship Budgets" where the new suggested total budget should be $8800.

We used this budget number for 2019/20, but the change was never reflected constitutionally.

Establish CI

Summary of issue:
We really really really should not track changes in the pdf blob.

Update Eboard's responsibility as mandatory reporters

Check one:

  • Semantic Issue: something about the meaning of the text is different
  • Non-semantic Issue: Spelling, grammar, or formatting changes.

Summary of issue:
In section 4.C.1.h, it says that it is Eboard's responsiblity to

To respect the privacy of House members confiding in the Executive Board, barring situations related to endangerment of oneself or others, sexual assault, or in the case of a Judicial Board

But this year Eboard does act as mandatory reporters, and it would be a good idea to rewrite this to reflect that change. Though it might just stay the same, I want to be very sure that that definition and RIT's definition of a mandatory reporter line up.

Articles reference non-production bylaws

Articles.tex:20

\externaldocument{articles}[https://github.com/bencentra/Constitution/blob/master/articles.pdf?raw=true]

Update the articles to point to production bylaws

Problems with terms of membership?

Check one:

  • Semantic Issue: something about the meaning of the text is different
  • Non-semantic Issue: Spelling, grammar, or formatting changes.

Summary of issue:
Reading over the terms of membership and eboard, seems there are two weird inconsistencies.
https://github.com/ComputerScienceHouse/Constitution/blob/master/articles.tex#L512

The term of an officer will be abbreviated due to resignation, impeachment, failure of the evaluation process, or change in membership status.

Does failing Spring Evals end the term of the officer? Current practice has been that they keep the position until the end of the year, regardless of Spring Evals.
Then there is a contradiction here, I think.
https://github.com/ComputerScienceHouse/Constitution/blob/master/articles.tex#L200

Active Membership shall last until the member: resigns, fails the Evaluation Process, or changes membership status.

Contradicts here:

https://github.com/ComputerScienceHouse/Constitution/blob/master/bylaws.tex#L296

If the member has previously passed an Membership Evaluation they will move to Alumni Membership status at the end of the Standard Operating Session (\ref{Alumni Membership Selection}).

Your active membership term ends if you "fail the Evaluation Process." But, you move to Alumni Membership at the end of the semester. So, do you still get to vote?

Remove Stale Branches

Check one:

  • Semantic Issue: something about the meaning of the text is different
  • Non-semantic Issue: Spelling, grammar, or formatting changes.

Summary of issue:
Someone should hit the delet this button on the two stale branches in this repo, unless we're keeping them around for some reason

Vague wording in Active Member section.

https://github.com/ComputerScienceHouse/Constitution/blob/master/articles.tex#L141

Receive priority over whom?
Also, are only active members on co-op allowed to come back on floor? Does that mean Harlan needs to pay dues to become an active member in order to be able to move on floor, meaning they pay dues for when they are not here?

Also, we don't define anywhere that an alum in good standing can just pay dues and become an active member again. We actually never define what an alum in good standing is. We only say how you become one.

Grammar error. https://github.com/ComputerScienceHouse/Constitution/blob/master/articles.tex#L168 Are not subject "to" any evaluations.

We need docs

The constitution is one of those documents that should be easy for a freshman walking in to CSH during the first week to make a PR to with very little git or unix experience. We should add instructions in the README or create a CONTRIBUTING.md that simply adds some info like that you need to modify the .tex files first, you must have pdflatex installed and then you must run make twice before committing and making a PR. Something like that would really lower the barrier for people to help with the constitution.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.