As of March 2019, LegionBoard is officially declared end of life.
There won't be any further development and
schools should not consider start using it.

The _tools_ directory not only can, but should be renamed.

* Switch to legionboard.dorfbrunnen.eu

Fix subjects MySQL check and parameters

See merge request !17

LegionBoard checked whether to create the fields 'subject' if the field
'subjects' existed.

Additionally, the request parameter 'subjects' was used instead of
'subject'.

Sort and speed up tests

See merge request !16

Revise classes, files and namespaces

See merge request !15

* Renamed lib to LegionBoard
* All classes are now in the namespace \LegionBoard(\Resources, etc.)
* All filenames now follow their classnames
* Tests moved from LegionBoard to global namespace
* All classnames are now in StudlyCaps
* All method names are now in camelCase
* Properties in LegionBoard are now sorted alphabetically
* identification is renamed to id
* Static methods are marked as such
* processAPI() gets simplified to process()
* Some duplicate methods got removed
* legionboard.org is https-only

Due to this bug: https://stackoverflow.com/a/17498167

Use MySQL for unit tests

See merge request !14

Also fix an error introduced with namespaces.

Legionboard::testProcessAPINotExisting() is < PHP 7.2 because atoum seems to have problems with it.

Test with PHP 7.0 and 7.2-rc too

See merge request !13

Test PHP 5.6 too

See merge request !12

Enable Xdebug for test coverage

See merge request !11

It did not even work since new tables got introduced.

Format code to follow PSR-2 coding style

See merge request !10

Done with `vendor/bin/phpcbf`.

Related to !8.

Only one subject per resource

See merge request !9

Multiple subjects per resource should be done with #26.

Add very basic unit tests and check for coding style

See merge request !8

The GitLab CI job "phpcs" is allowed to fail because we do not follow the PSR2 coding style at the moment.
We can fix most of the problems reported there by running `vendor/bin/phpcbf`.
Because this changes all files and nearly all lines,
this should be done in a separate MR.

Related to #27.

It wants to check if a given shortcut already exists,
but the needed function wasn't in place.