Council meeting minutes from 2025-07-21
minutes of the students' representative council for study programs of computer science
Begin: | 16:24 |
End: | 18:45 |
Present: | Daniel Butz, Jan-Philipp Fonfara, Lizzie Schmitz (from: 16:54), Abigail Pereira, Qianhao Zhang (till: 17:07), Yağmur Akarsu, Alexander Rogovskyy, Lukas Abelt, Clemens Beining, Simon Döring, Kevin Müller |
Moderator: | Jan-Philipp Fonfara |
Minute taker: | Daniel Butz |
Quorate: | no |
Agenda
Quality of Meeting Protocols
---- INTRO ------
We had some complaints about the quality of the recent protocols, we went over them and tried to find improvements.
---- DISCUSSION ------
From the notes:
The protocol don't seem sometimes very informative, for example they don't need to include every single thing that happened in the meeting, like "looking for slides".
Putting in the notes from the pre-meeting doc verbatim is not good, since the notes are sometimes not in the same format (or subjective or more internal).
In the meeting:
Protocols should catch the essence of the discussion, while not repeating itself.
StuPa style of protocol is bad, meaning going into much detail like "x said", "y said", ...
Structuring it with "intro" , "discussion" and "conclusion" would make them easier to read.
One opinion was that putting in names in the public section of the protocol like "[name]: something said" is unnecessary and too much politics for what the council does/is. Putting names in the internal version is fine, so members know who to address for the topic. This was agreed on by the present members.
The minute taker should read more over the text to check if it is good to publish.
A second minute taker will also read over the minutes for error checking.
Where to put the notes from the doc in the protocol should also be thought over whats best.
Currently it was in the beginning, it will be in the "DISCUSSION" intro now.
There were questions, what the purpose of the meeting pre doc was:
The document for the meetings is used to propose topics for the next meeting and already give information pre-meeting.
It was stated, that the comments in the doc are sometimes long and go back and forth which makes it hard or much to read before the meeting. Also the discussion should happen in the meeting and not in the doc. We therefore decided, that if a person can not attend the meeting, they can comment on the topics in the doc otherwise they should hold their comment back for during the meeting.
We could completely separate discussion and topics, but this would lead to two separate docs, which would be hard to maintain and would lead to info being out of sync. Therefore we decided to not do this.
We also discussed what to do with non urgent topics or soon™:
There will be now a bar that separates them in the same doc in the bottom section. A second doc for this was vibed out.
---- CONCLUSION ------
- Protocols will be better proofread (by two minute takers)
- there will be a section format (INTRO, DISCUSSION, CONCLUSION)
- The pre-meeting doc will have a benched topic sections
- Protocols will use a nameless format and only contain relevant things. (No "xyz picked nose")
- Doc notes will be put into the meeting but cleaned up better.
Update on Fachschaftsbefragung
---- INTRO ------
We got contacted by the student quality bureau for an interview where we are supposed to share with them how students of CS feel about studying.
---- DISCUSSION ------
Working in the council elected and volunteering we heard a lot of opinions and problems but we wanted to reach out more and get more direct feedback.
Therefore we held an event last Friday, asking you (students) how you feel about studying here. The good, the bad, the ugly. It was well visited and we will do one again this Tuesday (22.07). There will be free tee and coffee while we chat about uni.
If you have any tea to spill, things you like, things you hate, things you want to see changed, come visit us :)
Anything you share will be put forward anonymously but unfiltered to the uni quality bureau.
---- CONCLUSION ------
There will be another event tomorrow Tuesday (22.07) starting in the morning until the evening in E1.3.
The quality bureau interview is on Thursday, the results will be shared in the Friday meeting.
There will be more actions from the council regarding the problems your shared with us, more in the next meeting. Feel free to also join our meetings, every student is welcome :) (next meeting: Friday 25.07 13:15, E1.3 RindPhi door by the blue banner)
New Projector, Status
---- INTRO ------
We are still in the process of choosing a new projector, some where presented.
For the last discussion of this topic, see protocols from 27.06 (https://cs.fs.uni-saarland.de/uber-uns/protokolle/?prot_id=20250627).
---- DISCUSSION ------
The one we currently have has 3000 lumen. It is getting old (like some of our members) and not working so great during the day where there is sun (also like some of our members).
There were several options presented during the meeting and we discussed about the different specs of the presented projectors.
The image is not so visible during the day. (It also produces random noise on high frames).
---- CONCLUSION ------
There will be a smaller list next meeting (this Friday) and we will vote on the one we think is best.
Math Prep Course requests funding
---- SKIPPED ------
To: Next meeting this Friday.
Reason: We did not have quorum to vote on this.
Deans Lunch WS2025 — Begin of Organisation
---- SKIPPED ------
To: Potentially next meeting this Friday.
Reason: The attendance poll was a bit late for this meeting, there was no cross check with who will attend (topic authors) before the topics were locked in.