Keynote: Software as a Public Service: Introducing the Sovereign Tech Fund
Felix RedaOct. 04
Nextcloud for hosting webinars
Keynote: The Digital Policy of the "Traffic Light" Government: Advancing Digitization while Shaping it Sustainably
Collabora Online: recent improvements
(Don't) Do It Yourself? - An Overview of Struggles and Set-Ups of Private and Organizational Nextcloud Users
Don't fall off the cloud: scale you MariaDB quickly and safely with MaxScale
DAVx⁵ – What's New and What's Next
Building a deGoogled and privacy-friendly and open source mobile ecosystem: the story behind /e/OS and Murena.
Panel session: How to contribute?
Moderator: Jan-Christoph BorchardtDone
Mostly Blizzz works on the backend bits, but can push some pixels if necessary. He knows a large part of the Nextcloud server and a good bunch of apps, having his hands dirty in LDAP, SAML, Flow, Comments, amongst many more. Blizzz is trying to keep Nextcloud's (as in company) services running. Occasionally he releases the server and also he likes to deal with different technologies. Blizzz identifies as night owl and knows how to exit vim.
In the ecosystem of Nextcloud we have, among others, apps and users. In any ecosystem each organism has a life cycle, and so have apps and users. And of course we have an interaction of both. Users may do set some options, generate data (or let the app do it), or the app might do some work in the background for the user.
Now, in the life cycle of a user there are various events that are dispatched that your app can or should listen to: whether it is user creation, changes of user attributes, disabling of users and also the deletion of users.
This lightning talk aims to give you an overview on these events.
*X will turn into a number once I get a clearer picture of it