Group Jobs¶
Every group job has a definition of done: a concrete, checkable state we can confirm at the monthly group day.
If a job is not declared "done" at the monthly group day, and there was no prior notification that it could not be done, we subtract 5 cake points (= 1 cake) in the GroupOS. Prior notification means you flagged ahead of time — to the people who depend on the job — that you would not get it done and why (see Responsibility and crunch periods).
"Done" does not always mean a visible change. For maintenance-type jobs, if there was nothing to do, a confirmed check — you looked, and everything is in order — counts as done. The point is that you actively verified it and can say so at the group day, not that you produced something every month.
For jobs shared by more than one person, everyone listed is responsible. If the job is not done, the penalty applies to each of them — you cannot assume the other person covered it.
| Job Title | Description | Definition of Done | Person |
|---|---|---|---|
| Socializer | Organizes social events, ensures team bonding, and maintains a positive group atmosphere. | One social event held this month, or a dated event for next month announced with logistics shared. | Mara, Sadra |
| Social Media Manager | Handles the group's social media presence, shares updates, and engages with the community online. | At least one post published this month and all incoming mentions/replies answered. | Sreekanth, Adithya |
| Outputs Manager | Curates and maintains the group output database; ensures papers, code, talk slides, poster PDFs, and other outputs are logged and tracked. | Output database up to date for the past month, with all new outputs — including slides for talks and poster PDFs — entered. | Meiling |
| Website Manager | Manages the group's website, focused on curating news and papers based on the output database and newsletter. | News/papers section refreshed in the past month from the output database and newsletter; site reflects current activities and group. | Rostislav |
| Group Seminar Manager | Organizes and schedules group seminars, manages logistics, and is responsible for the room. Also schedules maintenance time. | Seminar slots for at least three months in advance filled and shared, with speakers confirmed and room booked. | Adrian |
| Group Newsletter Coordinator | Editor-in-chief of the group newsletter. | This period's newsletter sent, or scheduled with content locked. | Gordan |
| Pods Manager | Coordinates the pods — rotations, monthly pod sessions, and that each pod runs its weekly responsibility (see the weekly cycle). | Current pod assignments posted; this month's pod sessions scheduled or held; quarterly rotation done on time. | Viktor |
| Calendar Manager | Maintains the group calendar and ensures all important group meetings are up to date in it, so everyone is aware of important dates. | Confirmed check: every important group meeting/event is in the calendar with correct time; nothing missing or stale. | Adrian |
| Standup lead | Organizes standup sessions. | Every standup this period ran or was explicitly cancelled (e.g., maintenance week). | Viktor |
| IT Infrastructure Manager | Manages group IT. | Every IT issue raised this period is resolved or triaged with a status — or a confirmed check that systems run with no open issues. | Martiño |
| Templates & Visualization Manager | Maintains the group package template, paper templates, and other shared templates, and manages visualization tools and resources, including the plotting styles; assists with their use. | Issues reported this period fixed — or a confirmed check that templates and plotting styles still build and are current. | Martiño |
| Coffee Kitchen Manager | Takes care of the coffee kitchen, including maintaining a list to charge people. | Charge list reconciled for the period — or a confirmed check that supplies are stocked and nothing is owed. | Sadra |
| Zulip Manager | Oversees the Zulip chat platform, ensures channels are organized, and manages user access. | Access and channel requests this period actioned — or a confirmed check that channels and access are in order. | Kevin |
| GitHub Manager | Manages the group's GitHub repositories, including archiving old repos and updating READMEs. | Inactive repos archived and stale READMEs updated this period — or a confirmed check that repos and access are in order. | Kevin |
| Group Handbook Manager | Maintains and updates the group handbook, ensuring it reflects current practices and policies. | Pending changes merged — or a confirmed check that the handbook reflects current practice. | Kevin |
| Group OS Manager | Ensures the GroupOS works, fixes bugs, develops roadmap for new features | Kevin |
Paused
Coding Club Lead is paused for now.
Responsibility and crunch periods¶
Group jobs are everyone's responsibility. If you have a paper deadline or a genuine crunch period, you can deprioritize your group job for that week — but you communicate it to the person who depends on it, you do it in advance, and you either catch up or arrange coverage. This is a standing rule for everyone.