Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

Color code:SuggestedAcceptedIn ProgressDoneRejected



Microservice nameCodeResponsibleDiscussDescription
Core backendCOREFlaviuConfluenceResponsible for oAuth login with AP, user management etc
Should also be able to enable / disable other modules
Core frontendCOREFlaviuConfluenceResponsible 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
EventsEVENTSNico, SergeyConfluenceAll event-related stuff. Events, event applications, applicants acceptance, waiting lists, participants selection, etc.
Applications


Acts like a sub-service for events.
AlastairFOODNicoConfluence

Food planning module - A private project from Nico

TunnelTUNNELNicoJIRA
LDAP support

JIRA - Issue
Notifications

JIRA - IssueWould allow observers to register and push and receive notifications.
Notifications


  1. Emailer: Most likely will not write something ourselves, should use something existing. Flaviu mainly used sendgrid
  2. Push Notifications
Cron Module

JIRA - issueRegularily reoccuring tasks
Statutory microservice


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.
SU Mobile App


Same as SU-Webfrontend.
Events Mobile App


Derivative from SU app (or the other way around?)
  • No labels