...
| Microservice name | Code | Responsible | Discuss | Description |
|---|---|---|---|---|
| Micro service example | EXAMPLE | Confluence - Development | Responsibilities:
Functionalities:
| |
| Core backend | CORE | Flaviu | Confluence | Responsible for oAuth login with AP, user management etc Should also be able to enable / disable other modules |
| Core frontend | CORE | Flaviu | Confluence | Responsible for ALL frontend related stuff (should be tied with CB aka should be rendered by CB for security purposes and easier management). Other modules' frontend will be rendered by this one using templates and cross site requests |
| Events | EVENTS | Nico, Sergey | Confluence | All event-related stuff. Creating, modifying, displaying and deleting events, approving events, managing events' organizers |
| Applications | Everything related to the events' applications for the generic events (not statutory and not SU). Applying for the events, managing applications, approving participants. | |||
| Alastair | FOOD | Nico | Confluence | Food planning module - A private project from Nico |
| Tunnel | TUNNEL | Nico | JIRA | |
| LDAP support | JIRA - Issue | |||
| Notifications - pipe | N-PIPE | JIRA - Issue | Would allow observers to register and push and receive notifications. | |
| Notifications - email | N-EMAIL | Emailer: Most likely will not write something ourselves, should use something existing. Flaviu mainly used sendgrid | ||
| Notifications - push | N-PUSH | Push Notifications | ||
| Cron Module | JIRA - issue | Regularily reoccuring tasks | ||
| Statutory microservice | Application procedure for the statutory events and stuff that happens during statutory events (agorae, epms): Agenda, Proposals and voting on proposals, members, etc. - Not parts of events module | |||
| Voting | Candidatures, Evaluation (like impact measurement for events), also Recursion (-; | |||
| Antenna Microservice | Local management tools for antennae like members-list, working groups, local comitees, etc. Might just be another frontend to the core, low priority | |||
| Reporting | Generate anonymous reports with user and member statistics. | |||
| Finance | Fee management. Event budgeting. Parts of this are inside the core module at the moment, will be moved out of oms-core for this. | |||
| Storage | A possibility to backup data to external systems easily. | |||
| Travel | for example: AEGEE-couchsurfing | |||
| Gamification | E.g. create badges like "Visited 5 events" or "Attended 3 Agorae in a row" | |||
| Comments | Make commenting everything possible. Reuse of disqus might be the way to do it. | |||
| SU Webfrontend | Summer University Website: Will be a little different from the usual events frontend, maintained and developed by SUCT. |
...