Cleanup

Remove useless interfaces

Develop login screen

1. Email
2. Password
3. Login button

Develop Event editor (main page)

Develop console UI for editing events

1. Event name
2. Event description
3. Attached files list
4. Attached URLs list
5. Groups list
6. Tags list

Develop event history

Develop console UI for viewing and selecting event history

1. Sort by name / date
2. Select event for opening it in event editor

REST API for frontend part

1. Wrap input data to JSON files and provide REST API for sending them
2. Work collaboratively with backend developers who ar working on backend REST API schema

Configure database admins and roles

Add admins and roles

1. Developer (Full access)
2. Admin (Full access excluding database)
3. Table: id, email, password

Setup OAuth2 with SSO and Spring Security

1. Learn OAuth2 and SSO technologies
2. Learn the basics of Spring Security
3. Provide authorization of developers and admins
4. Include a basic login screen page without any design

Setup UI/UX design in Figma

1. Login page
2. Event editor
3. Event history list
4. App settings
5. Context menus

Setup REST API design in Postman

1. Getting event data

SLF4J

1. Add dependencies, prop file

Lombok

1. Add dependencies

Outlook forwarder

Introduce pushing events to Outlook with respect to the EventForwarder intrface

Create local LMS Moodle and design entry interface and parameters for getting API

Introduce more branches

1. main
2. backend-testing
3. frontend-testing

Create a skeleton of the code

1. Initialize an empty buildable project running on OpenJDK 18.0.1, Maven 4.0.0 and Springboot
2. Configure pom.xml: Add JUnit 5.8 and log4j2 dependencies, create an Application class with the main() method
3. Add .gitignore, README.md, and LICENSE files

Setup GitHub repository

1. Configure project deployment with Maven in GitHub Actions
2. Configure repository security features in GitHub Security

Setup WebServer and DataSource

1. Download, and install PostgreSQL 14.3 and the latest JDBC
2. Integrate empty data source into the project locally
3. Download Apache tomcat 10 and configure it

Groups and tags

Groups:

1. Bachelors (BS21...)
2. Masters (MS21...)
3. Ph. D / TA
4. Employee (DoE, 319...)

Admin tags:

1. Juridical
2. Extracurricular
3. Internship / Opportunity
4. Campus
5. Other

Note that admins must be able to add their tags and groups

Event data classes

Introduce event data classes (LMS event and Admin event)

Admin event:

1. Name, description
2. Attached files, URLs
3. Groups, tags lists
4. Importance: Obligatory/Optional (can be introduced using tags)

LMS event:

1. Name, description
2. Attached files, URLs
3. Groups, tags lists
4. Tag

Admins and developers mock table

1. id, email, password first name, last name
2. roles: admin, developer

Develop REST communication with Event history and database

1. Learn REST API and Spring Entities
2. Learn thymeleaf library
3. Develop communication with event history/editor and database

Configure Docker

1. Learn how to deploy an application and pack it into Docker image
2. Introduce deployment in Github Actions

REST controller

1. Combine REST API with DTO classes and write corresponding REST requests
2. Provide Unit testing of the controller

Core calendar get calendar events

1. Wrap Moodle API and get users' calendar data (core_calendar_get_calendar_events)
2. Try to take a data each 15 minutes
3. Write Unit tests

Too many useless wrapping

Remove Group and Location classes and use String instead.

Develop Outlook Calendar API wrapper

Develop Outlook Calendar API wrapper using Microsoft Graph API

1. Select members by their group / all members
2. Access to their private calendars

REST API schema

1. Provide diagrams describing what JSON data will be transferred according to our user stories
2. Learn what DTO is
3. Implement DTO classes

JDBC wrapper

Provide an implementation of the Model using PostgreSQL and JDBC

Update Maven settings

1. Make [package] configuration that allows to build a project to .jar file with included dependencies

Communication between mock model and console view

1. Develop a controller implementation working with a model and view
2. Introduce basic logic of event listening and forwarding to view

Learn and design MVC architecture

1. Introduce an updated use-case diagram
2. Introduce a UML diagram following MVC principles

Update project skeleton

1. Add corresponding packages and interfaces according to the UML diagram

Moodle server

1. Runs on VK Cloud
2. Add several testing users with testing data, allow API access
3. Add some courses, assignments and update their calendars

Groups and tags

Introduce groups and tags

Groups:

1. Bachelors (BS21...)
2. Masters (MS21...)
3. Ph.D. / TA
4. Employee (DoE, 319...)

Note that admins must be able to add their own tags and groups

Event data classes

Introduce event data classes (LMS event and Admin event)

Admin event:

1. Name, description
2. Attached files, URLs
3. Groups, tags lists
4. Importance: Obligatory/Optional (can be introduced using tags)

LMS event:

1. Name, description
2. Attached files, URLs
3. Groups, tags lists
4. Tag

Calendar page

1. We have already conducted a meeting related to calendar page and how it will look like. Ask @dmfrpro for details
2. Write necessary JS scripts for the calendar