Central FaRaFIN Calendar
Difficulty: easy- University software project
We are looking for students to deliver a central FaRaFIN calendar as part of their university software project, using an open-source solution or a self-hostable application. It should bring events together, support different groups and integrate with the existing infrastructure.
Responsibilities & profile
Calendar requirements
- SSO and SMTP: integrate sign-in through the existing identity provider and email delivery through a configurable SMTP server. Agree on supported protocols and infrastructure together.
- Group management and RBAC: manage dedicated calendars by group. Define administrator, editor and reader roles, and enforce access permissions on the server.
- Personal view: show or hide authorised calendars according to personal preferences and save the selection. Hiding a calendar in the interface does not replace access control.
- Calendar groups: provide separate, extensible areas for Events, Meetings, Veranstaltungen and Verteidigungen (thesis defences).
- Notifications: provide subscriptions to selected calendars with email notifications to subscribed mailboxes, for example for new events, changes, cancellations and reminders. Include unsubscribe options and notification preferences.
- Integration and compatibility: support .ics event downloads and calendar subscriptions via iCalendar feeds. An authorised read-only view should be embeddable in websites, for example using an iframe. Test display, updates and access controls with common calendar clients and browsers.
Quality and operation
- Modern interface: clear desktop operation with accessible navigation and forms. Smartphone support is an optional enhancement, not a requirement.
- Performance: fast calendar views and filters across multiple groups and larger event volumes. Agree on representative datasets and measurable response-time targets, and test them.
- Privacy and security: process only necessary personal data and separate public from internal events. Address role checks, protected calendar feeds, TLS, deletion and retention rules. Notifications and embedded views must not expose private events to unauthorised users.
Approach
Start by evaluating existing calendars and suitable open-source or self-hosting solutions. Compare functionality, licensing, integrations and maintenance effort. Justify the selected solution and implement missing integrations or extensions. Building everything from scratch is not a goal in itself.
Outcome & collaboration
Deliver a working demonstration, documented selection decisions, configuration and any source code, tests for permissions and integrations, and instructions for deployment, updates, backups and handover to FaRaFIN.
Project support
Experienced students offer experience, ideas and advice. They do not contribute code; implementation is the responsibility of your project team.
To agree together
Scope, team size, technologies, schedule, SSO and SMTP access, and responsibility for ongoing operation will be agreed together at the start. Academic supervision and recognition must be clarified with the responsible teaching staff. Agree with your supervisor whether and how LLMs may be used.
Preview description here
How to get in touch
Briefly introduce yourselves, what you study and whether you are applying individually or as a team. post@farafin.de
Get in touch ↗