Skip to content

Latest commit

 

History

History

statute

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
 
 
 
 
 
 

Statute of the Student Body

§ 1 - Scope of application These statutes regulate in particular the education, composition, responsibility, procedures and terms of office of the student body of the CODE University of Applied Sciences.

You can find the current and all past versions of the Statute of the Student Body here.

This repository shall serve as the interface for discussions around future amendments to the Statute. We will utilize Pull Requests for suggesting, discussing and potentially updating the Statute.

Therefore, Amendments to the Statute can be directly suggested via this platform. Follow the Contributing Guidelines further below to start partcipating here or learn about alternative ways to suggest changes.

Latest Version

Archive

Contributing Guidelines

Amendments to the Statute of the Student Body can be suggested by all members of the student body (§2 of the Statute).

How to Propose Amendments

Pro Track (on GitHub)

Create a new branch. Make changes to the latest version of the Statute and push them.

Once you are happy with the suggested changes, open up a Pull Request.

Describe the reasons for your proposed change. Make a strong pitch for your ideas for everyone reading it. Invite others to participate in our proposed amendment and start discussions around it.

You can and are encouraged to discuss directly in your new Amendment Pull Request.

Simple Track (Send us your Proposal)

You may not feel familiar with the whole GitHub Process. That's fine! Here's how you can propose an amendment in the same fashion as described before:

  1. Copy the Statute in it's Markdown form into a new text document on your local computer. You can alternatively download the page with a right-click and selecting "Save as...".
  2. Make your changes.
  3. Send it to [email protected] or to the council member of your choice via Slack.
  4. Describe the reasons for your proposed change. Make a strong pitch for your ideas.
  5. Done! We will facilitate the rest for you.

Need help with Markdown? Here is a great cheatsheet to get started: Markdown Cheatsheet

Stylistic Changes by Council Members

All members of the student council are allowed to make changes to proposed amendments regarding the formatting and stylistic nature of the document. This may affect headlines, use of italics, bold or similar. Direct changes to the content from council members are prohibited and need to be suggested by separate pull request.

Passing Your Amendment

Once a suggested amendment has been discussed and is in it's final version, a vote can be held to pass it in a Student General Assembly. The student council invites to these meetings. The students council informs all students about the proposed amendment prior to the assembly.

An amendment requires the approving majority vote of two thirds of the participating members of the Student Assembly (§8 of the Statute).

After a vote, the associated Pull Request of the proposed amendment will be flagged with Passed or Rejected by one of the student council members respective to the vote results. Additional details on the vote will be appended to the Pull Request as a comment.

Successful Vote

If an amendment has been passed by vote, it is ready to be merged. The current version will be archived. This archived version will be appended as a commit to the amendment's Pull Request. This can be done by any of the council members.

Council members need to make sure that the date of the version of the passed amendment matches the date of the day of voting.

The chairperson of the student council approves and merges the finalized Pull Request.

Rejected Vote

If an amendment is rejected by vote, the branch and Pull Request will remain open.

Students have the right to make changes to the proposed amendment and request a new vote.