Skip to content

Commit 8b12cc6

Browse files
committed
Add Instructions for Rules of Procedure
1 parent 6c9ead4 commit 8b12cc6

File tree

1 file changed

+68
-0
lines changed

1 file changed

+68
-0
lines changed

rules-of-procedure/README.md

Lines changed: 68 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,68 @@
1+
# Rules of Procedure of the Student General Assembly
2+
3+
4+
You can find the current and all past versions of the Rules of Procedure of the Student General Assembly here.
5+
6+
This repository shall serve as the interface for discussions around future amendments to the Rules of Procedure. We will utilize Pull Requests for suggesting, discussing and potentially updating the Rules of Procedure.
7+
8+
Therefore, Amendments to the Rules of Procedure 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.
9+
10+
## Latest Version
11+
* **[v1.2 (Latest)](rules-of-procedure.md)**
12+
13+
14+
## Archive
15+
* [v1.1](archive/v1.1.md)
16+
* [v1.0 (Initial)](archive/v1.0.md)
17+
18+
# Contributing Guidelines
19+
20+
Amendments to the Rules of Procedure of the Student General Assembly can be suggested by all members of the student body ([§2 of the Statute](https://github.com/codeuniversity/student-council/blob/main/statute/statute.md#2---student-body)).
21+
22+
23+
## How to Propose Amendments
24+
25+
### Pro Track (on GitHub)
26+
Create a new branch. Make changes to the [latest version of the Rules of Procedure](rules-of-procedure.md) and push them.
27+
28+
Once you are happy with the suggested changes, open up a [Pull Request](/pulls).
29+
30+
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.
31+
32+
You can and are encouraged to discuss directly in your new Amendment Pull Request.
33+
34+
### Simple Track (Send us your Proposal)
35+
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:
36+
37+
1. [Copy the Rules of Procedure](https://raw.githubusercontent.com/codeuniversity/student-council/main/rules-of-procedure/rules-of-procedure.md?token=ACOWXF3Q6ILJ5PJSY2KD5NTBEZHI2) 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..."._
38+
2. Make your changes.
39+
3. Send it to [[email protected]](mailto:[email protected]) or to the council member of your choice via Slack.
40+
4. Describe the reasons for your proposed change. Make a strong pitch for your ideas.
41+
5. Done! We will facilitate the rest for you.
42+
43+
Need help with Markdown? Here is a great cheatsheet to get started: [Markdown Cheatsheet](https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet)
44+
45+
#### Stylistic Changes by Council Members
46+
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.
47+
48+
## Passing Your Amendment
49+
50+
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.
51+
52+
An amendment requires the approving majority vote of two thirds of the participating members of the Student Assembly ([§8 of the Statute](https://github.com/codeuniversity/student-council/blob/main/statute/statute.md#8---amendment-of-legal-provisions)).
53+
54+
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.
55+
56+
### Successful Vote
57+
58+
If an amendment has been passed by vote, it is ready to be merged. The current version will be [archived](archive). 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.
59+
60+
Council members need to make sure that the date of the version of the passed amendment matches the date of the day of voting.
61+
62+
The chairperson of the student council approves and merges the finalized Pull Request.
63+
64+
### Rejected Vote
65+
66+
If an amendment is rejected by vote, the branch and Pull Request will remain open.
67+
68+
Students have the right to make changes to the proposed amendment and request a new vote.

0 commit comments

Comments
 (0)