Compare commits
2 commits
5ce5233063
...
d2cf5ce601
| Author | SHA1 | Date | |
|---|---|---|---|
| d2cf5ce601 | |||
| 2c47d644d8 |
1 changed files with 5 additions and 8 deletions
|
|
@ -49,6 +49,7 @@ This objective aligns with the work programme topic by advancing the development
|
|||
|
||||
The key technical aspect of Fediversity is to provide the framework for applications to easily switch between different hosting providers, or to their own infrastructure, without losing their data.
|
||||
This objective is important as it promotes user control and choice, without being locked into a particular platform or service.
|
||||
It would be a unique feature beyond what is currently available on the market.
|
||||
|
||||
Concretely, we aim to achieve this using the following sub-goals:
|
||||
|
||||
|
|
@ -57,7 +58,7 @@ Concretely, we aim to achieve this using the following sub-goals:
|
|||
1. Exploit our work by enabling reproducible deployments of an initial set of portable applications.
|
||||
|
||||
In addition, the team will ensure that all parts of our services use **open-source software**.
|
||||
This will promote transparency and gives users the freedom to use, modify, and distribute the software as they see fit, without restrictions or limitations.
|
||||
This will promote transparency and gives users the freedom to use, modify, and distribute the software as they see fit, without artificial restrictions or limitations.
|
||||
|
||||
### Relevance
|
||||
|
||||
|
|
@ -75,10 +76,6 @@ The use of open-source software, along with the focus on portability, will enabl
|
|||
|
||||
## Ambition
|
||||
|
||||
### Service portability
|
||||
|
||||
The project plans to offer service portability: allowing users to easily export their data and application state from one hosting provider's environment and import it to another.
|
||||
This is a unique feature beyond what is currently available on the market.
|
||||
|
||||
## Identified applications
|
||||
|
||||
|
|
@ -150,11 +147,11 @@ In order to deal with this, we will have to keep up with potential changes and a
|
|||
To give a clear view of what interdepencies we expect:
|
||||
|
||||
1. Project Management: will keep an overview of all other Work Packages.
|
||||
1. Implementation: will make for the core software needed for further Work Packages.
|
||||
1. Vertical Hosting: will offer a 'feedback loop' and feed to WP5
|
||||
1. Enhancement & Usability: will feed back to the verticals and feed to WP5
|
||||
1. Dissemination & Outreach
|
||||
1. Vertical Public Organisations: (dropped)
|
||||
1. Open calls and grant management: will feed back to the vertical and feed to WP5
|
||||
1. Enhancement & Usability: will feed back to the verticals and feed to WP5
|
||||
1. Outreach & Dissemination
|
||||
|
||||
This diagram graphically represents the relations:
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue