Fediversity/meta
13
3
Fork 4
Code Issues Pull requests Projects Releases Packages Wiki Activity

sketch roadmap to an MVP demo #24

Merged
fricklerhandwerk merged 2 commits from fricklerhandwerk/meta:mvp-demo-roadmap into main 2025-01-27 10:13:43 +01:00
Conversation 3 Commits 2 Files changed 1 +110
fricklerhandwerk commented 2025-01-22 11:45:19 +01:00
Owner
Copy link
  • goal as set by @bjornw on 2024-01-20
  • proposal with input from @koen on 2025-01-22
- goal as set by @bjornw on 2024-01-20 - proposal with input from @koen on 2025-01-22
fricklerhandwerk added this to the WP2: D2.2 – Software release beta environment milestone 2025-01-22 11:45:30 +01:00
fricklerhandwerk added this to the Project board project 2025-01-22 11:45:33 +01:00
fricklerhandwerk reviewed 2025-01-23 10:14:45 +01:00
2024-01-mvp-demo-roadmap.md Outdated
@ -0,0 +9,4 @@
- What components are needed?
- Which Fediverse services are we going to offer?
- There are ~47 (~9weeks) workdays between 27-01-2025 and 01-04-2025. How will we divide the work among the team?
fricklerhandwerk commented 2025-01-23 10:14:45 +01:00
Author
Owner
Copy link

Assumptions

  • Users will use the Fediversity infrastructure
    • We won't be able to make it portable yet. But this is still the ultimate goal for the project
    • Eventually we'll also need to describe the infrastructure one needs to run it
  • Services ready to run on top of Garage: PeerTube, Mastodon, Pixelfed
  • The point of the demo is communicating:
    • That the project extists, what it is about, how it's special, and that it's progressing towards its goals
    • That this is the infrastructure you can use to provide a micro-cloud to end users
    • The ultimate goal is infrastructure portability (can only mention, not demonstrate it)
    • That we care about technological and economic sustainability
    • That organisations that want to participate in the Fediverse, we may be a good partner
  • Target audiences:
    • Peers, potential clients, policymakers
    • Hosting providers, organisations with sysadmins
# Assumptions - Users will use the Fediversity infrastructure - We won't be able to make it portable yet. But this is still the ultimate goal for the project - Eventually we'll also need to describe the infrastructure one needs to run it - Services ready to run on top of Garage: PeerTube, Mastodon, Pixelfed - The point of the demo is communicating: - That the project extists, what it is about, how it's special, and that it's progressing towards its goals - That this is the infrastructure you can use to provide a micro-cloud to end users - The ultimate goal is infrastructure portability (can only mention, not demonstrate it) - That we care about technological and economic sustainability - That organisations that want to participate in the Fediverse, we may be a good partner - Target audiences: - Peers, potential clients, policymakers - Hosting providers, organisations with sysadmins
fricklerhandwerk marked this conversation as resolved
fricklerhandwerk commented 2025-01-24 11:01:10 +01:00
Author
Owner
Copy link

Updated the summary after syncing with @Niols to make sure we both understand it. @Fediversity/OID @Fediversity/nlnet please review

Updated the summary after syncing with @Niols to make sure we both understand it. @Fediversity/OID @Fediversity/nlnet please review
fricklerhandwerk force-pushed mvp-demo-roadmap from e850e99e3d to 5bee8171bb 2025-01-24 11:02:11 +01:00 Compare
hans commented 2025-01-24 13:07:06 +01:00
Owner
Copy link

The link to an older discussion is invalid:

Start preparing a Django service (as discussed 2024-11-06) that will eventually replace the manually processed form

Otherwise it looks fine to me.

The link to an older discussion is invalid: Start preparing a Django service (as discussed 2024-11-06) that will eventually replace the manually processed form Otherwise it looks fine to me.
fricklerhandwerk commented 2025-01-27 10:12:43 +01:00
Author
Owner
Copy link

Yes, to my surprise those meeting notes went to the private repo...

Yes, to my surprise those meeting notes went to the private repo...
fricklerhandwerk force-pushed mvp-demo-roadmap from 82ac18de69 to 5362af9df3 2025-01-27 10:13:14 +01:00 Compare
fricklerhandwerk merged commit cfdfbf59b0 into main 2025-01-27 10:13:43 +01:00
fricklerhandwerk deleted branch mvp-demo-roadmap 2025-01-27 10:13:43 +01:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
WP2

work related with WP2 (from grant agreement)

  
WP3

work related with WP3 (from grant agreement)

No labels
WP2
WP3
Projects
Clear projects
No items
No project
Project board
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Fediversity/meta#24
No description provided.
Delete branch "fricklerhandwerk/meta:mvp-demo-roadmap"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?