Due: month 6 of the project.
During the continuous effort to build a working environment for easy setup and deployment we will create a technical architecture document that explains how the different parts work together and which design choices have been made. This document will also be made available on the project website.
Due: month 6 of the project.
Release a report on the estimated collective current investment on fediverse technology.
Look at qualifiers like:
- Used system resources (CPU, storage, networking)
- Amount of software developers actively working on Fediverse software products
- Amount of system administration engineers actively working on Fediverse software products
- Amount of moderation and governance people
Due: month 3 of the project.
After the first 3 months a global plan will be ready and delivered. This plan will take care of how any research data will be registered and presented. If any research data will be generated during this project depends on the outcome of the projects done with NORDUnet or if any Subgrants will generate any research data.
Due: month 12 of the project.
The release of a set of instructions, documentation and reproducible Nix-packages that together build a test environment for hosting multiple Fediverse programs (at least, but not limited to Mastodon, Peertube and Pixelfed) and possible supporting software (like dns-servers, mailservers and authentication mechanisms).
Due: month 12 of the project.
For releasing and building the software we will use a continuous integration and continuous deployment setup. This will help us track bugs and user-feedback specifically for the created hosting setup. This setup will also be described in the technical architecture document of deliverable D2.5
Stuff that needs to be done for the Xmas holidays 2024 and is not covered by a workpackage deliverable.
Due: month 12 of the project. (new due date: end of May, begin June 2025-06-01)
Based on the requirement documents stated in deliverable D3.1 NORDUnet will propose a number of 3 to 5 pilot programs to be executed at different institutions in different countries. These pilot programs will be presented at a conference to be held somewhere in the Nordics end of 2024.
Due: month 6 of the project.
As part of the communication a set of documents, imagery and other presentation formats will be created. So that if anyone want to further communicate the project they have a ready to use set.
Due: month 2 of the project.
To be effective in all efforts to reach our audiences and get our message across we need a good strategy. This strategy will be documented and publicly made available.
Due: month 9 of the project.
A test lab will be setup that houses a range of recently often used devices that can be used to test UX design in real-world environments. The testlab will consist of a mix of phones, tables, laptops and other general use computers.
TBD: new due date
Due: month 9 of the project. (new due date end of Q1 2025, 2025-04-01)
A document that states the results of the research of the needs and wishes of the member public organisations of NORDUnet. This document will be used as input for deliverable D3.2
Due: month 18 of the project.
During the process we will develop a number of Nix packages and NixOS services, possibly in the form of Nix Flakes, that can serve as a starting point for other Hosting organizations to run the select NGI software in such a way that provides end-users with a 'one click' interface to use the software.
We will aim to start the collaboration process with the Nix community in as early stage as possible.
Original title: Technical architecture document pilot programs
Due: month 18 of the project.
Based on the chosen pilot programs from deliverable D3.2 OID, together with Tweag will implement the setup needed to run the pilot program. These will be described in a technical architecture document that can be used to reproduce the built setup later.
Orginal title: Nix service flakes, packages and NixOS services for pilot programs
Due: month 18 of the project.
The implementation of the pilot programs will result in a set of reproducible Nix service flakes, Nix packages and NixOS services, these willl be made publicly available.
Original title: CI/CD setup for pilot programs
Due: month 18 of the project.
For releasing and building the software we will use a continuous integration and continuous deployment setup. This will help us track bugs and user-feedback specifically for the created hosting setup. This setup will also be described in the technical architecture document pilot programs of deliverable D3.3
Due: month 18 of the project.
Based on the experiences of communication with all external parties we will be in touch with during the first half of the 3 year period we will create a list of UX design enhancements on the projects we use. We will create a report of recommended UX design requirements with a priority ranking based on our findings.
Due: month 18 of the project.
Every 18 months we will publish an overview of what we have done in terms of communication and media-attention. This overview itself will also be a publication and thus public.
Due: month 24 of the project.
The release of a set of instructions, documentation and reproducible Nix-packages that together build a beta test production environment for hosting multiple Fediverse programs (at least, but not limited to Mastodon, Peertube and Pixelfed) and possible supporting software (like dns-servers, mailservers and authentication mechanisms). Iteration based on deliverable D2.1
Due: month 24 of the project.
Based on the requirements listed in deliverable D5.1 we will chose a few top-priority issues that we will create a new UX design for.This design will be made publicly available and will be discussed with the various projects to involve them in our project.
Due: month 30 of the project.
Together with the creators/maintainers of the various projects we will implement a few of the top UX design changes as suggested in deliverable D5.2 We will create one or more webinars or sessions (perhaps on larger in-person events like hacker-campings or other conferences) on the subject to try to get the different projects to implement similar ux designs to get a more consistent Fediverse experience. We will also share this with the NORDUnet pilots.