diff --git a/Pictures/10000001000003F4000004EF79A4F3605EBA79FB.png b/Pictures/10000001000003F4000004EF79A4F3605EBA79FB.png new file mode 100644 index 0000000..1705aeb Binary files /dev/null and b/Pictures/10000001000003F4000004EF79A4F3605EBA79FB.png differ diff --git a/Pictures/100048410000111F000013C76C98E745D4C15CD9.svg b/Pictures/100048410000111F000013C76C98E745D4C15CD9.svg new file mode 100644 index 0000000..35fb76a --- /dev/null +++ b/Pictures/100048410000111F000013C76C98E745D4C15CD9.svg @@ -0,0 +1,283 @@ + + + + diff --git a/Pictures/1000542F0000111F000013C771F768BC3ED83C54.svg b/Pictures/1000542F0000111F000013C771F768BC3ED83C54.svg new file mode 100644 index 0000000..f1a3962 --- /dev/null +++ b/Pictures/1000542F0000111F000013C771F768BC3ED83C54.svg @@ -0,0 +1,278 @@ + + + + diff --git a/Pictures/1000832F00001126000013CFFE7D3120C542E28D.svg b/Pictures/1000832F00001126000013CFFE7D3120C542E28D.svg new file mode 100644 index 0000000..3918444 --- /dev/null +++ b/Pictures/1000832F00001126000013CFFE7D3120C542E28D.svg @@ -0,0 +1,616 @@ + + diff --git a/Pictures/100086E70000111F000013C7258F044CA4EE0031.svg b/Pictures/100086E70000111F000013C7258F044CA4EE0031.svg new file mode 100644 index 0000000..cbedba4 --- /dev/null +++ b/Pictures/100086E70000111F000013C7258F044CA4EE0031.svg @@ -0,0 +1,609 @@ + + + + diff --git a/fediversity.md b/fediversity.md index 15bf576..25d181b 100644 --- a/fediversity.md +++ b/fediversity.md @@ -4,7 +4,8 @@ # History of changes --------------|-----------|-------------------------------------------------------------------- +| Date | Pages | Description | +|-|-|-| | 2023-10-10 | Page 1-41 | Changed the name of the acronym of the project to Fediversity | | 2023-10-10 | Page 5 | added a paragraph on the use of open hardware | | 2023-10-10 | Page 11 | added two paragraphs on the selection of different NGI technologies | @@ -15,7 +16,6 @@ | 2023-10-12 | Page 41 | Updated Gant Chart | | 2023-10-12 | Page 3 | Added Open Source, Open Standards, Open Dependencies | | 2023-10-12 | Page 15 | Added work package interdependencies and added a new page | --------------|-----------|-------------------------------------------------------------------- # Preamble @@ -412,168 +412,22 @@ This powerful preemptive disclosure prevents malicious parties from obtaining a ## Summary -+----------------------+----------------------+----------------------+ -| Specific needs | Expected results | Communication and | -| | | dissemination | -| What are the | What does | measures | -| specific needs that | Fediversity expect | | -| triggered this | to generate by the | What dissemination, | -| project? | end of the project? | exploitation and | -| | | communication | -| | | measures will | -| | | Fediversity apply to | -| | | the results? | -+----------------------+----------------------+----------------------+ -| Availability of | Easier and | Outreach towards | -| content in the | predictable use of | main stream | -| Fediverse: | NGI-supported open | consumers: | -| | source software: | | -| Even though the | | Press and guerrilla | -| fediverse is now | We aim to provide | marketing, tech | -| used by a lot of | hosting providers | talks and webinars, | -| 'normal users' most | and public | decentralised social | -| public organizations | organizations with a | media, project | -| are lacking from | cookbook/script that | speaker bureau. | -| providing content to | will allow them to | | -| the Fediverse. | implement, and | | -| | maintain | | -| | NGI-supported open | | -| | source software in | | -| | such a way that it | | -| | feels comfortable | | -| | for IT staff to do. | | -+----------------------+----------------------+----------------------+ -| Use of open source | Better and more | Engage with | -| software is hard: | content in the | technical, | -| | Fediverse: | operational | -| The general | | | -| misconception is | by getting better | community and | -| that the use of open | support of IT staff | decision makers: | -| source software is | in running | | -| hard and it is | NGI-supported | Webinars for | -| difficult for large | fediverse platforms | 'families' of | -| organizations (both | we expect NRENs and | projects to showcase | -| public and private) | other public | progress to internet | -| to run, and maintain | organizations to | service providers, | -| open source | move to an 'open | research networks, | -| software. | first' approach for | operator groups, | -| | sharing their | hosters, CERTs, etc. | -| | content, moving away | | -| | from Big Tech. A | | -| | secondary effect of | | -| | this could be that | | -| | due to the | | -| | availability of that | | -| | content more people | | -| | would start using | | -| | the Fediverse giving | | -| | meaning to the term | | -| | 'network effect'. | | -+----------------------+----------------------+----------------------+ -| Service portability | Basic level of | Make project results | -| is lacking: | service portability: | discoverable: | -| | | | -| Even though there | We expect to get | One stop shop portal | -| are now regulations | several projects to | to browse through | -| that state that you | create a way to | different categories | -| can get all your | actually export both | of projects and | -| personal data from | data and settings so | discover new | -| service providers. | you can not only | technologies of | -| It is still quite | move to another | interest. | -| hard to move from | service provider, | | -| one platform to | but also do so | | -| another. With the | transparantly. | | -| event of federated | | | -| networks you can | | | -| export your data | | | -| from one instance | | | -| and move to another. | | | -| This is not easy and | | | -| requires quite some | | | -| work. | | | -+----------------------+----------------------+----------------------+ -| | | Engage European SMEs | -| | | and investors: | -| | | | -| | | Create a competitive | -| | | alternative economy | -| | | based on open source | -| | | with convenience and | -| | | value-add services. | -+----------------------+----------------------+----------------------+ +| **Specific needs**: What are the specific needs that triggered this project? | **Expected results**: What does Fediversity expect to generate by the end of the project? | **Communication and dissemination measures**: What dissemination, exploitation and communication measures will Fediversity apply to the results? | +|-|-|-| +| **Availability of content in the Fediverse**: Even though the fediverse is now used by a lot of ‘normal users’ most public organizations are lacking from providing content to the Fediverse. | **Easier and predictable use of NGI-supported open source software**: We aim to provide hosting providers and public organizations with a cookbook/script that will allow them to implement, and maintain NGI-supported open source software in such a way that it feels comfortable for IT staff to do. | **Outreach towards main stream consumers**: Press and guerrilla marketing, tech talks and webinars, decentralised social media, project speaker bureau. | +| **Use of open source software is hard**: The general misconception is that the use of open source software is hard and it is difficult for large organizations (both public and private) to run, and maintain open source software. | **Better and more content in the Fediverse**: by getting better support of IT staff in running NGI-supported fediverse platforms we expect NRENs and other public organizations to move to an ‘open first’ approach for sharing their content, moving away from Big Tech. A secondary effect of this could be that due to the availability of that content more people would start using the Fediverse giving meaning to the term ‘network effect’. | **Engage with technical, operational +community and decision makers**: Webinars for ‘families’ of projects to showcase progress to internet service providers, research networks, operator groups, hosters, CERTs, etc. | +| **Service portability is lacking**: Even though there are now regulations that state that you can get all your personal data from service providers. It is still quite hard to move from one platform to another. With the event of federated networks you can export your data from one instance and move to another. This is not easy and requires quite some work. | +| **Basic level of service portability**: We expect to get several projects to create a way to actually export both data and settings so you can not only move to another service provider, but also do so transparantly. | **Make project results discoverable**: One stop shop portal to browse through different categories of projects and discover new technologies of interest. | +| | | **Engage European SMEs and investors**: Create a competitive alternative economy based on open source with convenience and value-add services. | -+----------------------+----------------------+----------------------+ -| **Target groups**: Who will use or further up-take the results of the project? Who will benefit from the results of the project? | **Outcomes**: What change does Fediversity expect to see after successful dissemination and exploitation of project results to the target groups? | **Impacts** | -| | | | -| Who will use or | What change does | What are the | -| further up-take the | Fediversity expect | expected wider | -| results of the | to see after | scientific, economic | -| project? Who will | successful | and societal effects | -| benefit from the | dissemination and | of the projects | -| results of the | exploitation of | contributing to the | -| project? | project results to | expected impacts | -| | the target groups? | outlined in the | -| | | respective | -| | | destination in the | -| | | work programme? | -+----------------------+----------------------+----------------------+ -| **Software and | **Significant uptake | **Societal: | -| hardware companies | by interested users: | | -| and in-house | | Sustainable | -| developers: | Projects improve the | ecosystem around | -| | state of the art and | open source and open | -| Developers (also | can be customised, | hardware projects | -| in-house) from | offering distinct | which creates a | -| public and private | advantages over | virtuous cycle of | -| sector that benefit | existing | collaboration, | -| from quality | (proprietary or | growth and | -| reusable components | legacy) tools. | innovation. | -| and turnkey best | | | -| practices. | | | -+----------------------+----------------------+----------------------+ -| **Regular end users: | **Adoption by service | **Societal: | -| | providers, network | | -| Many technologies | operators and | Privacy and security | -| within NGI Zero | platforms: | improvements help | -| directly benefit | | users avoid risks, | -| those that want to | Efforts within the | especially important | -| increase their | infrastructure and | for vulnerable | -| online privacy, | hosting layer, and | groups like | -| independence and | at the level of | minorities, | -| security. | platforms and | whistle-blowers, | -| | distributions will | activists, refugees | -| | 'automatically' | and journalists. | -| | benefit users. | | -+----------------------+----------------------+----------------------+ -| **Enterprises and | **Integration of | **Economic:** | -| public sector: | project output into | | -| | major open source | ISPs, hosters, | -| Organisations can | solutions: | network operators, | -| replace proprietary, | | companies and civil | -| possibly unethical | Superior solutions | society (re)use | -| business software | tend to gradually | project output to | -| with open source, | replace legacy | deliver services | -| user-respecting | technologies and | that grant users | -| solutions. | improving standards | more autonomy and | -| | has a strong effect | privacy. | -| | on the overall | | -| | marketplace. | | -+----------------------+----------------------+----------------------+ -| **Academia and | **Usage and (paid) | **Economic:** | -| research: | services for | | -| | enterprises and | We expect a new | -| Unlike proprietary | organisations:** | economy will start | -| ("black box") tools | | to evolve based on | -| and services, open | On top of state of | value added support | -| source solutions are | the art FOSS | and services for | -| well-suited for | solutions everyone | e.g. end-to-end | -| academics and | can build | communication, | -| private and public | competitive business | private data | -| sector research as a | and services. | storage, federated | -| subject and to | | and decentralised | -| experiment with new | | identity management. | -| ideas. | | | -+----------------------+----------------------+----------------------+ +| **Target groups**: Who will use or further up-take the results of the project? Who will benefit from the results of the project? | **Outcomes**: What change does Fediversity expect to see after successful dissemination and exploitation of project results to the target groups? | **Impacts**: What are the expected wider scientific, economic and societal effects of the projects contributing to the expected impacts outlined in the respective destination in the work programme? | +|-|-|-| +| **Software and hardware companies and in-house developers**: Developers (also in-house) from public and private sector that benefit from quality reusable components and turnkey best practices. | **Significant uptake by interested users**: Projects improve the state of the art and can be customised, offering distinct advantages over existing (proprietary or legacy) tools. | **Societal**: Sustainable ecosystem around open source and open hardware projects which creates a virtuous cycle of collaboration, growth and innovation. | +| **Regular end users**: Many technologies within NGI Zero directly benefit those that want to increase their online privacy, independence and security. | **Adoption by service providers, network operators and platforms**: Efforts within the infrastructure and hosting layer, and at the level of platforms and distributions will ‘automatically’ benefit users. | **Societal**: Privacy and security improvements help users avoid risks, especially important for vulnerable groups like minorities, whistle-blowers, activists, refugees and journalists. | +| **Enterprises and public sector**: Organisations can replace proprietary, possibly unethical business software with open source, user-respecting solutions. | **Integration of project output into major open source solutions**: Superior solutions tend to gradually replace legacy technologies and improving standards has a strong effect on the overall marketplace. | **Economic**: +ISPs, hosters, network operators, companies and civil society (re)use project output to deliver services that grant users more autonomy and privacy. | +| **Academia and research**: Unlike proprietary (“black box”) tools and services, open source solutions are well-suited for academics and private and public sector research as a subject and to experiment with new ideas. | **Usage and (paid) services for enterprises and organisations**: On top of state of the art FOSS solutions everyone can build competitive business and services. | **Economic**: We expect a new economy will start to evolve based on value added support and services for e.g. end-to-end communication, private data storage, federated and decentralised identity management. | # Quality and efficiency of the implementation @@ -585,17 +439,12 @@ Not applicable. Table 3.1h: Purchase costs -+------------------+------------------+----------+------------------+ -| Description | Category | Cost (€) | Justification | -+------------------+------------------+----------+------------------+ -| Test hardware | Other goods, works and services | 200.000 |
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 social networking 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.
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.
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.
For this we expect to be using about 130.000 of the budget.
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 Fediverse software.
| -+------------------+------------------+----------+------------------+ -| Remaining purchase costs | | 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 | | 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 | | 225.000 | | -+------------------+------------------+----------+------------------+ +| Description | Category | Cost (€) | Justification | +|-|-|-|-| +| Test hardware | Other goods, works and services | 200.000 |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 social networking 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.
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.
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.
For this we expect to be using about 130.000 of the budget.
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 Fediverse software.
| +| Remaining purchase costs | | 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 | | 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 | | 225.000 | | Table 3.1.i: Other costs categories @@ -750,12 +599,11 @@ All projects that fail on any of these knock-out criteria, will not be further r Projects receive an initial rating on three criteria: -|---------|--------------------------------------| | Weight | Criterion | +|---------|--------------------------------------| | 30% | Technical excellence/feasibility | | 40% | Relevance/Impact/Strategic potential | | 30% | Cost effectiveness/Value for money | -|---------|--------------------------------------| The total weighted score of projects has to be above 5 (out of 7) to pass to the next stage.