Second Outcobra Meetup 28. April 2017

2nd Outcobra Meetup / Planning meeting

Date: 28. April 2017

You can find the original notes for this wiki entry here

[TOC]

Agenda items

• Code licensing
• Sprint planning
• Caching
• Materialize CSS
• Colorpicker behaviour
• Release cycle
• Closed beta
• Various issues

Code licensing

We chose to go the open source way and move away from our current commercial licensing.

One of the GPL licenses will be chosen by @jmesserli

Task: Choose GPL license

Spring planning

Sprint 10 (In-between sprint):

• Finished on the 2017-04-30

Sprint 11 (QA sprint):

• Finished on the 2017-05-07
• Frontend unit tests
• Move old mockups to Adobe XD
• Create mockups for mark ui
• Server backups
  • To dropbox or some other free storage place
  • Add backup & restore tests to QA sprint checklist

Sprint 12 (Technical debt sprint):

• Finished on the 2017-05-14
• Materialize CSS
• Finishing touches for QA sprint
• Refactoring
• Create userstory issues for mark ui sprint

Sprint 13 (Mark UI feature sprint):

• Finished on the 2017-05-28
• Implement mark UI

Caching

We are implementing the caching in either sprint 12 or sprint 13.

For now, it will only be used for the RepositoryLocator and DtoLocator classes

Materialize CSS

Will be replaced by angular/flex-layout or a css grid. The first try will be with angular/flex-layout.

Colorpicker

For UX reasons, we are adopting a new "magic" button that chooses a random color. The existing buttons will behave like this:

• Cancel: Does nothing, the form will be invalid without a selected color
• OK: Selects the selected color

The selected color should be displayed in a better way according to @M4R1KU

Release cycle

The next release must happen before sprint 13 (marks) and will have the version number 1.1.0.

After that, every feature sprint will increment the MINOR version number by one, e.g. 1.2.0.

We will discuss the release numbers again when we go into the beta stage.

Closed beta

The closed beta must at least contain the following features:

1. Marks
2. Exams
3. Basic dashboard

Before we can go into the beta stage, we might need:

• New product name
• Matching domain

What we do need:

• A new server for the production environment
  • Backups & restore testing
• A way to deploy to this environment

Various issues

Frontend refactoring will happen in the "in-between sprint".

If we don't get an official angular/material datepicker until the beta stage, we will have to deploy a hotfix to fix the date parsing issue.