Re: [Tails-project] GitLab hosting: blocking and very import…
|This message is part of the following thread:|
|the complete thread tree sorted by date|
- self-hosting, because we have to admin everything
- immerda, because we are the admins of our own GitLab instance (which of course gives us an incomparable level of flexibility); immerda would manage the OS and GitLab installation so I expect it's mostly a spam management problem. This can be mitigated by choosing a different trade-off between "cost of admin" and "super smooth way towards a first contribution to Tails"; we can change our mind and adjust this trade-off as we want at any future time, so in the end I'm not concerned.
- Tor, because I can see it happen that to keep registration open enough for our taste on the long term, we have to get involved in moderation (fighting spam) at some point, and then labour cost can become similar to being hosted at immerda, except that instead of deciding ourselves what the trade-off should be and how much work we want to do, we have to negotiate this with a partner in the context of a power-imbalanced relationship.
|This message was posted to the following mailing lists:|
Mailing List Info | Nearby Messages
|[Tails-project] GitLab hosting: blocking and very important criteria?||Re: [Tails-project] #8948: Reconsider the terminology around "persistence"|
|lists.autistici.org administrated by postmaster||Lurker (version 2.3)|