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

rm methodology

Browse source
This commit is contained in:
Kiara Grouwstra 2025-05-21 16:05:17 +02:00
parent 389fb1c374
commit a901bac86e
Signed by: kiara
SSH key fingerprint: SHA256:COspvLoLJ5WC5rFb9ZDe5urVCkK4LJZOsjfF4duRJFU
1 changed files with 0 additions and 88 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

88
fediversity.md
View file

@ -86,94 +86,6 @@ The use of open-source software, along with the focus on portability, will enabl
The project plans to offer portability of services, allowing users to easily export their data from the platform and import it to another platform.
This is a unique feature beyond what is currently available on the market.
## Methodology
For the software development side of things, the project will use 'iterative development', which means the development process is a cycle, where we go back through the steps based on feedback and challenges that present themselves along the way.
1. **Planning:**
During the planning phase, the team will identify the key features and requirements of the service packages.
This will involve collaborating with stakeholders and users to understand their needs and expectations.
The team will then create a prioritised list of features and user stories, which will form the basis of the development plan.
1. **Designing:**
In the designing phase, the team will create the overall architecture and design of the software.
This will involve identifying strategically relevant service packages, including relevant settings, database schemas, and application programming interfaces (APIs).
The team will also identify any third-party libraries or tools that would be needed to implement the software.
1. **Coding:**
During the coding phase, the team will start implementing the software.
Once the software has reached its MVP stage, the development process will involve an initial user to facilitate working in short, user-feedback-driven iterations.
1. **Testing:**
The testing phase involves verifying that the software works as expected.
The team will develop a suite of automated tests that cover all the key features and scenarios of the software.
This will include unit tests, integration tests, and end-to-end tests.
The team will also perform manual testing to ensure that the user experience is smooth and error-free.
1. **Releasing:**
The final phase is the release to users.
The team will work on documenting usage of the software, and facilitate initial users to maintain a feedback loop.
The team will then use this feedback to inform further iterations of the software, and prioritise the next set of features and improvements.
In the context of building partnerships with hosting organisations, we will apply Design Thinking as a methodology.
Design Thinking is a user-centered, iterative methodology that is used to solve complex problems and create innovative solutions.
It involves a five-step process that includes empathy, definition, ideation, prototyping, and testing.
The following is an overview of how Design Thinking can be applied to build partnerships:
1. **Empathy:**
The first step in the Design Thinking process is to understand the needs, goals, and challenges of the target partners.
This can be done through research, interviews, surveys, and other forms of data collection.
By empathising with the target partners, we can gain a deeper understanding of their perspectives and identify opportunities for collaboration.
1. **Definition:**
Once we have a clear understanding of the target partners' needs, goals, and challenges, we can define the problem space and identify areas of mutual interest.
This involves synthesising the research data and creating a problem statement that is focused on meeting the target partners' needs.
1. **Ideation:**
The ideation phase involves generating a wide range of ideas for how we can address the problem statement and meet the target partners' needs.
This can be done through brainstorming sessions, workshops, and other forms of collaborative ideation.
The goal is to generate a diverse set of ideas that can be evaluated and refined in the next phase.
1. **Prototyping:**
In the prototyping phase, we create low-fidelity prototypes of the most promising ideas generated in the ideation phase.
These prototypes can take the form of mockups, wireframes, or other simple prototypes that can be tested and evaluated with the target partners.
1. **Testing:**
The final phase of the Design Thinking process involves testing the prototypes with the target partners and gathering feedback.
This feedback can be used to refine the prototypes and develop a more detailed plan for collaboration.
To apply Design Thinking to our project, we would start by conducting research and gathering data on the needs, goals, and challenges of end-users through our potential partners.
This can involve interviews with key stakeholders, surveys of potential partners, and analysis of existing data sources.
Using this research, we will then define the problem space and identify areas of mutual interest.
This will involve creating a problem statement that focuses on meeting the needs of users in the area of software services.
Next, we will generate a wide range of ideas for how we can address the problem statement and meet the needs of potential partners.
This will involve brainstorming sessions, workshops, and other forms of collaborative ideation with key stakeholders.
Using the ideas generated in the ideation phase, we will then prototype the most promising ideas.
Finally, we will test the prototypes (alphas, betas of our services) with potential partners and gather feedback.
This feedback will then be used to refine the prototypes and develop a more detailed plan for collaboration.
Through this process, we can build strong partnerships with hosting organisations based on mutual benefit and shared decision-making.
Our project is designed to comply with the 'do no significant harm' principle as per Article 17 of Regulation (EU) No 2020/852.
We are committed to ensuring that our methodology is environmentally-friendly and does not significantly harm any of the six environmental objectives of the EU Taxonomy Regulation.
Regarding the use of artificial intelligence (AI) based systems, we do not plan to use AI in our project.
However, if we were to use AI, we would ensure that our systems are technically robust, socially robust, reliable, and able to provide suitable explanations of their decision-making processes.
We would also follow industry-standard practices and regulations to minimise any unintended harm and safeguard the physical and mental integrity of humans.
To make sure we can achieve our project objectives, we have outlined a project management strategy:
- We will develop a clear and detailed project plan:
This will outline the tasks that need to be completed, who is responsible for each task, timelines, and dependencies.
- Establish effective communication:
Regular communication with all stakeholders is crucial for keeping everyone informed about progress, identifying and addressing issues, and ensuring that everyone is on the same page.
To this end we will also outline a communication plan to make sure all relevant stakeholders (European Commission, team members, both internal as external contractors) are well-informed throughout the process.
- Monitor progress:
Regular monitoring of project progress against the plan can help identify any potential delays or issues and allow for adjustments to be made to keep the project on track.
- Mitigate risks:
Identify potential risks and develop strategies for mitigating them.
This can help reduce the likelihood of delays or failures.
- Ensure proper resource allocation:
Make sure that resources, including staff, budget, and technology, are allocated appropriately to support the project objectives.
- Stay flexible:
We are prepared to adjust the project plan and approach as needed to ensure that objectives are met.
### Technologies used
#### [NixOS](https://nixos.org/)