kiara/fedi-goals
1
0
Fork 1
Code Issues Pull requests 1 Projects Releases Packages Wiki Activity Actions

tweak proposal

Browse source
This commit is contained in:
Kiara Grouwstra 2025-06-05 12:24:44 +02:00
parent f826a9f64e
commit 3a786fda32
Signed by: kiara
SSH key fingerprint: SHA256:COspvLoLJ5WC5rFb9ZDe5urVCkK4LJZOsjfF4duRJFU
1 changed files with 28 additions and 35 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

63
fediversity.md
View file

@ -31,7 +31,6 @@ This way we make it easier to run public infrastructure.
## Open Source, Open Standards, Open Dependencies
All software used, produced or needed by our project and it's outcomes will be licensed under a valid Open Source Software license, will not be encumbered by patents unless covered under the Open Invention Network and will not use API's or services that are not reproducible in a fully free manner.
The only exception is for the UX design test-lab environment that will be used to ensure maximum interoperability with closed source but widely used systems and software (like operating systems and web-browsers).
No software specific for or usable by any single organisation will be created or produced under this grant.
@ -57,21 +56,19 @@ Concretely, we aim to achieve this using the following sub-goals:
1. Disseminate our results by engaging the open-source community to further expand on work in this direction;
1. Exploit our work by enabling reproducible deployments of an initial set of portable applications.
In addition, the team will have to find ways to ensure that all parts of our services use **open-source software**.
This will promote transparency and enable end-users to verify that their data is being handled ethically and in compliance with data privacy regulations.
Use of open-source software also gives users the freedom to use, modify, and distribute the software as they see fit, without restrictions or limitations.
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.
### Relevance
Overall, this proposal is highly relevant to the HORIZON EU Programme, specifically to the Human-centric Internet topic.
This proposal is highly relevant to the HORIZON EU Programme, specifically to the Human-centric Internet topic.
The objective of this topic is to support research and innovation in creating a more human-centric internet that prioritises user privacy, security, and control, while also promoting the ethical use of technology.
The proposed work aligns with this objective by show-casing a way to run digital services that prioritises user control and privacy, and by using open-source software and hardware to promote transparency and ethical use.
The proposed work aligns with this objective by show-casing a way to run digital services that prioritises user control and privacy, and by using open-source software to promote transparency and ethical use.
### Measurability
Measuring the success of this objective will depend on several metrics, such as the number of organisations and institutions that adopt our work directly or indirectly, and its impact within the open-source community.
Verifying the success of this objective will require user/developer feedback, engagement metrics, and independent audits to ensure that our services are meeting the highest standards of privacy and security.
The success of this objective will depend on several metrics, such as the number of organisations and institutions that adopt our work directly or indirectly, and its impact within the open-source community.
This will require user/developer feedback and engagement metrics to ensure that our services are meeting the highest standards of quality.
The proposed work is realistically achievable.
The use of open-source software, along with the focus on portability, will enable the proposed services to be easily adopted by our target audiences.
@ -85,7 +82,7 @@ This is a unique feature beyond what is currently available on the market.
## Identified applications
We have identified a number of applications as potentially relevant targets to offer as part of our project, emphasising the value to users' digital autonomy.
We have identified a number of applications as relevant targets to offer as part of our project, emphasising the value to users' digital autonomy.
To structure our efforts, we have categorized them into three waves, as follows:
- Low-hanging fruit (courtesy of SelfHostBlocks)
@ -105,16 +102,16 @@ Considerations taking into account in the selection of applications to be implem
As the initial application to be supported, we have selected [Forgejo](https://forgejo.org/), given it:
1. is supported in [SelfHostBlocks](https://github.com/ibizaman/selfhostblocks)
1. relevant features are merged upstream (c.f. Vaultwarden, where support for single sign-on is still outstanding)
1. uses a language featuring static typing, offering it a baseline level of robustness
1. is supported in [SelfHostBlocks](https://github.com/ibizaman/selfhostblocks), facilitating implementation
1. is part of our own infrastructure, allowing us to bootstrap
1. given the above, makes our development team self-sufficient for the purpose of its initial user feedback cycle
1. relevant features are merged upstream (c.f. Vaultwarden, where support for single sign-on is still outstanding)
1. uses a language featuring static typing, offering it a baseline level of robustness
Which other packages we will decide to support will depend further on the packages that will be adressed in the 'subgrant projects' that will be requested in the 'open calls'.
In finalising our initial selection, both with regard to quality-quantity trade-offs as well as relative priority among the identified applications, we will coordinate with relevant stakeholders as the project matures.
Our consideration to limit the initial list of supported applications is to keep focus on our core innovation, as properly adding support for applications involves at least:
Our consideration to limit the initial list of supported applications is to keep focus on our core innovation, as properly adding support for applications may involve:
- PoC:
- compartmentalising state for backups/portability/redundancy
@ -127,13 +124,13 @@ Our consideration to limit the initial list of supported applications is to keep
- hardening
- post-MVP:
- handling backward-incompatible setting interface changes
- coordinate with end-users to improve the user experience
- coordinating with end-users to improve the user experience
- if missing first-class Nix support:
- package for Nix
- create NixOS service module
- integrate with identified contracts (see SelfHostBlocks)
- maintain the above on version updates
- coordinate with upstream developers on immutable-friendly development
- packaging for Nix
- creating NixOS service module
- integrating with identified contracts (see SelfHostBlocks)
- maintaining the above on version updates
- coordinating with upstream developers on immutable-friendly development
The result of the work in the hosting vertical should be generic enough to support all NGI packages sufficiently documented and packaged in NixOS.
@ -142,11 +139,11 @@ The result of the work in the hosting vertical should be generic enough to suppo
One of the challenges we have identified is ensuring the security and privacy of our users' data, even if we will not collect this directly.
To overcome this challenge, we will use industry-standard open-source encryption methods and regularly update our software and hardware solutions to stay ahead of potential threats.
We will also need to work with experts in data privacy and cybersecurity to ensure that our software is secure and protect user data.
A periodic (monthly or bi-monthly) check if all security measures have been taken and if any updates are needed will be held.
Where and if possible we will automate these checks and integrate them in a 24/7 monitoring system.
Before having the software enter production, a periodic security check (monthly or bi-monthly) will be held to verify required security measures have been taken and to check if any updates are needed.
Where and if possible, we will automate these checks and integrate them in a 24/7 monitoring system.
Another challenge is that much of the software we aim to implement is still fairly new and as a result still changes frequently.
In order to deal with this, we will have to keep up with the change and at the same time provide a stable and predictable experience to our users.
Another challenge is that some of the software we aim to build upon is still somewhat new and as a result may still change more frequently.
In order to deal with this, we will have to keep up with potential changes and at the same time provide a stable and predictable experience to our users.
## Work package interdependencies
@ -170,31 +167,31 @@ This diagram graphically represents the relations:
Outcomes:
- Freedom of choice in the tools to use and (possibly) even alter to your own liking.
- The democratic process will be safeguarded.
- The democratic process may be safeguarded.
Target groups:
- Hosting companies looking to offer open-source applications.
- Developers looking to expand on the available applications respecting user autonomy.
General outcomes
General outcomes:
The outcomes and impacts of your project may:
- Give a better understanding of how to implement, maintain and run open-source managed applications respecting user autonomy.
- Give companies and organizations that specialize in web hosting a better starting point in offering such applications.
Technological outcomes
Technological outcomes:
- An increase in solutions around autonomous managed applications as well as in number of software packages supported by such solutions.
- Increased engagement with and innovation around open-source software, stemming from lowered barriers toward their adoption.
Economic outcomes
Economic outcomes:
- An uptake in the number of open-source managed applications offered by web hosts, as it becomes easier to offer these.
- Increased adoption of privacy-respecting software, as it becomes easier to consume these through the above-mentioned hosts.
Societal outcomes
Societal outcomes:
- The proposed platform could contribute to the creation of a more open and democratic digital landscape, where users have more control over their data and online interactions.
- The platform's focus on privacy and data portability could lead to greater trust in open-source digital platforms, which in turn could lead to increased participation and innovation.
@ -211,7 +208,7 @@ Some specific possible quantitative estimates include:
The focus on data portability could have significant benefits for users, allowing them to easily switch between online platforms and take their data with them.
1. Market disruption:
If our project is successful, it could have far-reaching impacts.
For example, if our platform gains a significant share of the market, it could lead to more competition among software services, potentially leading to improved user privacy and better options for data management.
For example, if our software gains a significant share of the market, it could lead to more competition among online software services, potentially leading to improved user privacy and better options for data management.
There are several requirements and potential barriers that may determine whether the desired outcomes and impacts of the project are achieved.
Some of them are:
@ -272,7 +269,7 @@ There are several communication strategies and measures that we will utilise dur
It will be used to share updates, news, publications, and other project-related information.
The website will be designed to be accessible and user-friendly.
1. Using social media:
We will reach out to Fediverse channels (e.g. Mastodon, Pixelfed, Peertube and Owncast) as well as commercial social media platforms such as X, LinkedIn, and Facebook to reach a wider audience and share project-related news and updates.
We will reach out to Fediverse channels (e.g. Mastodon, Pixelfed, Peertube and Owncast) as well as commercial social media platforms such as BlueSky, Threads, and LinkedIn to reach a wider audience and share project-related news and updates.
Social media are used to engage with stakeholders and respond to their queries and feedback.
While our values may be closer aligned with the open-source social media, we will also still have use for the commercial ones to spread our message initially.
1. Organising workshops and events:
@ -368,10 +365,6 @@ Table 3.1h: Purchase costs
| Description | Category | Cost (€) | Justification |
|-|-|-|-|
| Test hardware | Other goods, works and services | 200.000 | <p>For our UX research we need to acquire a reasonable diverse set of tablets, PC's and mobile phones so that we can support actually used devices. This is essential to deliver the kind of support people expect from software in general, but cloud services (like our products from the NGI technologies we choose). We want to create a test lab that is also accessible to the chosen technology developers at request. We will at least need to acquire the latest new models of popular phones and tablets other devices every 3 months (estimated total of 60 devices by the end of the project) and new models of laptops, chromebooks and the likes every 6 months (estimated total of 30 devices by the end of the project) and a few PC's with various form-factors and operating systems (estimated total of 24 devices by the end of the project). We expect to be using about 50.000 of the budget for this.</p><p>Another substantial part will be used for a test-setup 'at scale' for running the actual services: server-hardware, networking-hardware, storage-systems. Also we need to account for hosting and networking-costs in dual locations.</p><p>We will acquire about 80 server-systems, 12 storage-systems, and some networking equipment housed in two locations. All hardware will be second-hand as to keep cost low.</p><p>For this we expect to be using about 130.000 of the budget.</p><p>The remaining 20.000 euro we want to spend on two or four openhardware servers based on OpenPower to run a small pilot as part of the test/development setup to see where it makes sense to use OpenHardware in the setup for running Fediversity software.</p> |
| Remaining purchase costs | &nbsp; | 10.000 | Is for promotion and marketing material like stickers, banners, and other promotional material to hand out on each and every event we will visit. |
| Travel and subsistence | &nbsp; | 15.000 | Will be used for traveling between the Netherlands, the Nordics, France and the rest of Europe for attending conferences and other meetups. |
| Total | &nbsp; | 225.000 | &nbsp; |
Table 3.1.i: Other costs categories