GAFAM Dependency Sundown Committee/Roadmap

Proposed agenda item Make a participatory process or assembly to start the process of GAFAM Dependency Sundown

Background

• A proposal was raised here: https://meta.decidim.org/processes/bug-report/f/210/proposals/17852

• Discussions have been had on our element channel

• A debate with the general assembly took place during the first day of Decidim Fest 2025 regarding if this was possible and if so, how to approach it

In general, the community agrees it is a desirable path to sundown GAFAM dependencies. But we have also acknowledged there are relevant tradeoffs to be had, such as time spent maintaining infrastructure will mean less time developing Decidim. Or simply saving money from things such as CI/CD. Email servers are also non-trivial to replace. But the community is technopolitically aligned with the importance of self-hosting and the values are aligned with out Social Contract.

Intended outcome(s)
GAFAM Dependency Sundown is not a process that can be made quickly or even completely. This request is only for the committee to discuss how to start such a process. On the Decidim Fest discussion it was suggested we start by mapping the dependencies we have and discuss as a community sun-downing strategies for each. The community can also be enlisted to help achieve these replacements.