At the Amsterdam meeting we also identified 3 central aspects of where we see the role of this network (or federation). Citing from memory, these were more or less:
- provide visibility of librehosters to the general public/end users
- provide a space for exchange of information and good practices (e.g. what is the best way to deploy and maintain discourse; exchanging on deploym
- engage in collaboration to address common technical challenges
For 1. we have the example of @pierreozoux of where can get a Nextcloud hosted, as well as providing proper user documentation for its usage. Another example is to have the list of librehosters (as discussed here), what they are and information from the processed librehosters JSON, which helps end users to opt for one or another.
For 2. we have this discourse forum or the riot channels as platforms for exchange, apart from IRL meetings. We can here discuss not only how to deploy specific software and collaborate on building packages e.g. for discourse, but also overall exchange on best practices, models and architectures for librehosters: do we use docker-compose or ansible for deployments? Do we build a kubernetes cluster, what effort does it mean? What are ways to deal with identity and SSO in our applications? How are we doing backups? etc.
For 3. we have the larger collaboration projects, where several individuals and organisaitons of similar interest can onboard. @pierreozoux already mentioned the examples of the souk and of libre.sh.