Council meeting minutes from 2026-02-04

minutes of the students' representative council for study programs of computer science

Rental Contracts

As we discussed in an old meeting (13.11.2025) we want to update our rental contracts. The rental Taskforce will work out a new draft and propose it in a future meeting. We will then vote on whether we approve of it.

FutureMINT - Thinkathon 2026

Intro: We got an email asking us about whether we want to contribute to a project that is collecting issues that current MINT students are facing. The deadline for this is 06.02.2026.


Discussion: We could open a hedgedoc to collect ideas.

Immediate ideas:
- Usage of AI/LLMs (also the copyright concern of providing e.g. lecture notes to an AI/LLM)
- Lack of diversity in the CS department (e.g. gender representation)
- Integration of international students (UdS did a pretty good job here)
- Lack of practical experience (possibly more specific to UdS)
- Lack of integration into the job market
- Lack of confidence in your own abilities due to very high mental load/workload (e.g. having to learn a large number of programming languages) -> commonly leads to the misuse of AI/LLMs
- No dedicated courses about things like e.g. Git, Unix (possibly more specific to UdS)


Conclusion: We will set up a Hedgedoc to collect even more ideas and will then forward them to the project.

Nikofete Aftermath

Intro: After the Nikofete, some helpers felt like the event may not be sustainable in its current state. This is not necessarily due to some specific organisational problem but instead the result of a number of factors working together. Hence, it may be necessary to change the structure of the event in some way.
One thing that could also greatly help with this is some way for us to collect feedback (possibly also for events in general).
We are also very grateful for anyone who was able to help out during the Nikofete in some way, especially people who decided to help out very spontaneously.


Discussion:
Internal feedback: We could open a Hedgedoc to collect internal feedback and put the link in our internal Signal group (one Hedgedoc per event). Another option would be Github repositories.
Someone will have to work through the feedback and in the end it should all be made available in our Wiki, so that we can use it for future reference.

Public feedback: We could ask people for feedback during the events and later on add this information to our internal documents.

---------------------------------
One way of restructuring specifically the Nikofete would be to possibly scale it down to some extent. (e.g. providing either waffles or crêpes, not both). This could however leave a negative impression on students and may lead to new organisational issues (e.g. figuring out the amount of ingredients again).

Another important point would be to try and find more helpers and to also try to have more people allocated per shift.


There was also the proposal of maybe cooperating with the Math or Bachelor Plus MINT council in the future, if possible.


Conclusion: We will set up a hedgedoc to collect internal feedback for last year's Nikofete, which the respective Taskforce will eventually put into our Wiki. Based on the result, we will then think about how to proceed with other events as well.
And the Nikofete Taskforce will think about, what ways of restructuring might make sense for future iterations.

CS Students' Poll Website

Intro: There are a number of opportunities where it would be helpful to have something like a Poll Website for CS students. Someone would have to implement this, if we decide to go through with the idea.


Discussion: Using QUALIS for this is not an option as this is meant for lecture feedback and also not under our control. However, adding more ad more things to our infrastructure makes it harder to keep track of everything.

Another big problem is figuring out how to actually get people to participate.
It was suggested to do something similar to what we once did (a general vibe check with free coffee) or to just have council members walk around the buildings and directly talk to people. Another option could be to do polls in the Discord.

It makes sense to keep the questions (and the way of participating) as simple as possible (e.g. Yes/No) but this does limit, what things we can actually ask for and maybe the quality of the results.

It was also proposed to make very large and appealing posters, that allow students to participate.


Conclusion: We will try to make large posters whenever we want to have a poll among the students and we will try to keep the process as simple as possible.