Progress report October 2017

October was a busy month for us, since almost everyone of us was busy. Nevertheless, we've managed to do some stuff!

• An automated testing was implemented for oms-events, meaning that the oms-events tests on Travis would use the actual core implementation and not the stubs. Also, an integration of new oms-core version and oms-serviceregistry was started, and Sergey Peshkov has managed to get some of the API endpoints working. That means that we'll most likely see the working API for oms-events in a few weeks!
• Alastair has gotten a couple of bugfixes, as Nico was implementing test coverage and got disappointed, implemented more tests and found bugs. Alastair is usable already, and when oms-events is up even event-permissions can be implemented to make Alastair ready for its first beta-release. Unfortunately the working service found no resonance in the network so far, Nico would be happy about any kind of feedback or testers!
• A new microservice joined the cloud: oms-central-frontend will take over the job of rendering the combined frontend from all microservice. This is at first logically cleaner and nicer for future frontend development, it slims down the core and also makes the site rendering more efficient. In the future this will be the place for automated frontend testing. The PR of it is not really up yet because Nico is in the jungle and doesn't have a lot of time to do so, hopefully someone can jump in. In general the central frontend is solely a technical change and the appearance of the site does not change (except for it using opensans now), so including it into the development workflow is simply a convenience issue and does not necessarily need to happen soon.

Resolved Issues:

Merged Pull Requests:

New Issues: