replace copypaste of issue tracker with actual key results

This commit is contained in:
Valentin Gagarin 2025-06-11 18:04:58 +02:00
parent 41a7ac66ef
commit 9e6c39eb88

View file

@ -152,22 +152,20 @@ Whereas the core abstraction in Fediversity is a NixOS configuration module, a m
![](https://git.fediversity.eu/Fediversity/meta/raw/branch/main/architecture-docs/host-architecture.png) ![](https://git.fediversity.eu/Fediversity/meta/raw/branch/main/architecture-docs/host-architecture.png)
## Break-down of project milestones ## Breakdown of project milestones and key results
Whereas details of the implementation may need to be decided as the technical challenges involved become clear, we can already give a higher-level planning of relevant milestones and some of their salient features: Whereas details of the implementation may need to be decided as the technical challenges involved become clear, we can already give a higher-level planning of relevant milestones and some of their salient features:
1. [implement a way to run online services emphasising user autonomy and data portability](https://git.fediversity.eu/Fediversity/Fediversity/issues/347) - Implement a way to run online services emphasizing user autonomy and data portability
1. [Finalize architecture doc](https://git.fediversity.eu/Fediversity/Fediversity/issues/39) - Integration tests pass for
1. [code-based migration data model](https://git.fediversity.eu/Fediversity/Fediversity/issues/103) - Setting up a fediversity hosting environment from a declarative configuration
1. [migrating application data between hosting providers](https://git.fediversity.eu/Fediversity/Fediversity/issues/100) - Configuring, deploying, and migrating a set of dummy applications
1. [application offering generalised](https://git.fediversity.eu/Fediversity/Fediversity/issues/369) - Code passes data protection audit
1. [NixOS configuration as the core abstraction](https://git.fediversity.eu/Fediversity/Fediversity/issues/339) - Disseminate our results by engaging the open-source community to further expand on work in this direction
1. [disseminate our results by engaging the open-source community to further expand on work in this direction](https://git.fediversity.eu/Fediversity/Fediversity/issues/348) - Present results on at least 3 conferences
1. [automated dev-ops workflows](https://git.fediversity.eu/Fediversity/Fediversity/issues/224) - At least 5 applications compatible with Fediversity thanks to external contributions by 2027-03
1. [external developers empowered to contribute](https://git.fediversity.eu/Fediversity/Fediversity/issues/288) - Exploit our work by enabling reproducible deployments of an initial set of portable applications
1. [exploit our work by enabling reproducible deployments of an initial set of portable applications](https://git.fediversity.eu/Fediversity/Fediversity/issues/349) - There are 3 fediverse applications available out of the box:
1. [applications deployed on command](https://git.fediversity.eu/Fediversity/Fediversity/issues/99) - Mastodon
1. [kick-started initial feedback cycle](https://git.fediversity.eu/Fediversity/Fediversity/issues/225) - PeerTube
1. [brought into production](https://git.fediversity.eu/Fediversity/Fediversity/issues/228) - Pixelfed
1. [nix-less bootstrap](https://git.fediversity.eu/Fediversity/Fediversity/issues/332)
1. [key features improving user experience supported](https://git.fediversity.eu/Fediversity/Fediversity/issues/289)