* [TODO] decide next steps regarding the notes migration
* [TODO] migrate remaining internal services under our direct control (Redmine, LDAP, OTRS)
* [TODO] we did not receive any feedback regarding the notes migration altogether. We assume this means that everything is fine and decided to go on with the migration
## Twitter Access
* [INFO] we had access to the @TYPO3Server Twitter handle through Tweetdeck
* [INFO] the account itself was running under the address of a former team member and we did not had the password
* [INFO] password was aquired and added to the password database
## TYPO3.CMS Mirror in GitLab
* [INFO] we set up a mirror of the TYPO3.CMS repository in Gitlab
* [TODO] goal is to move git.typo3.org to GitLab and get rid of Git Daemon/GitWeb altogether. We are in contact with the core team to plan the required steps.
## Status Page
*[INFO] our [status page](status.typo3.org) gets its services and their status out of Zabbix
* [INFO] as we move away from Zabbix, we need a new solution
* [TODO] either keep current code but switch backend to new monitoring, or switch to another solution
* [TODO] define requirements
* define services and get their status automatically out of our monitoring (Icinga 2)
* ability to add articles to inform about downtimes/maintenance windows
* integration into our @TYPO3server Twitter account (push maintenance & downtime infos to Twitter)
* [TODO] possible software
* https://cachethq.io/ (in use at Andris company already)
* http://staytus.co/ (dont know it but looks promising)
* [TODO] we decided to test with Cachet. Andri will prepare a demo for the next meeting
## Various
* ...
## Next Meeting
* The next meeting will take place on Tuesday, April 21, 2020 08:30 CEST