Hello! Intel has graciously supported SyncEvolution for a long time, even after it became a spare time project again. But now I really should consider how to continue with the project without relying on infrastructure provided by Intel. This includes: - syncevolution.org domain - web hosting (syncevolution.org, downloads.syncevolution.org) - mailing list (syncevolution(a)syncevolution.org) - mailing list archive (https://lists.syncevolution.org/hyperkitty/list/syncevolution@syncevoluti...) - build server Outside of Intel we already have: - git repo + issue tracker (https://gitlab.freedesktop.org/SyncEvolution) For the mailing list, https://lists.freedesktop.org may be a viable alternative. I have a full copy of old emails that could be imported. This may be more relevant for hosting a public archive of those emails than it is for actual, on-going discussions, though ;-) Will users on this list re-subscribe on another mailing list or should I to try to add current subscribers automatically? Would a Google Groups be better? It looks like I can do most of the setup there myself instead of having to rely on freedesktop.org admins, including sending out invitations to current subscribers. The current content on https://syncevolution.org has aged badly. Not only is some of it stale, rendering also suffered from multiple Drupal updates. Moving it elsewhere is an opportunity to clean this up. I would try to keep links valid as much as possible or at least have redirects. However, I only intend to copy page content, not comments. My plan is to export the original content (usually plain text with some Markdown and HTML), clean it up and then run a static page generator to recreate the HTML site. I have some experience with Sphinx, but not a whole lot. In fact, this would be a perfect opportunity for someone with spare time to help out. Any volunteers? The source code for the web site could be in a new "web" repo. I don't think freedesktop.org supports hosting of static pages, so perhaps GitHub would be a better place for such a "web" repo? Then the rendering can be done by a GitHub action and the result be exposed as a GitHub page. This is a pragmatic compromise between free software purism (GitHub is only a free service, but not free software!) and ease of use. It could also be that it encourages drive-by contributions because the barrier for contributions would be lower, although that doesn't seem that likely. The downloads.syncevolution.org content is something that I would maintain and host myself somewhere. I would also run the builds on my own machine. I'm leaning towards moving the domain to CloudFlare and then configure syncevolution.org so that it becomes a frontend for the web pages and downloads. -- Best Regards Patrick Ohly