Merge branch 'main' of git.fediversity.eu:Fediversity/meta

This commit is contained in:
BjornW 2025-03-31 14:23:29 +02:00
commit 6b965debaf
3 changed files with 111 additions and 0 deletions

View file

@ -0,0 +1,31 @@
**Demo rehearsel:** 2025-03-31 @10:00
**Present:** Kiara, Koen, Ronny, Kevin, Gheorghe, Robert, Bjorn, Valentin, Nicolas, Hans
**Absent:** Eric (known)
__Agenda__
* Koen starts with presenting
* Kevin will present the demo
__Presentation & Demo notes__
* Financed by EC, not "being" from EC.
* I suggest to say Prototype and not Product for now.
* I thought we were going to use the coloured EU flag(@Ronnynote: Koen is using an older version of the pdf.../ auch, okay)
* We need a bit more 'what is the mvp about'/'what is the demo about'
* s/Hello world/Welcome
* First show that the apps are not deployed yet. Let people visit the urls themselves
* Can we make the split screen in demo wide, instead of long? (@kevinnote: yes but this was only normal sized monitor i have at the moment)
* Because of the elementary graphical interface, maybe a lower resolution of display will make the command text greater.
* When speak about the interface would be nice to have it visible on the screen.
* The argument for having ops done by professionals needs some polish => we are targeted at organisations (if you can run your own hardware, go!)
* Why skip slides? Will not skip.
* benefits providers: these are the benefits FOR providers
* Maybe don't switch between the presentation & demo. It's a bit distracting. (hans: I think that's a good thing, it breaks it up in different bits that makes it a bit more lively)
* I would suggest to add in the benefits and the other images also the Services offered to the Users to give the whole image of the prototype.
* The architecture diagram is an old one. The NixPanel is no more there.
* Nix is not an operating system ;..)
* roberth: One term keeps it simple and is good enough
* Nix is a system for building software more reproducibly
* The old NixPanel in the architecture is not mapped by the Django(Python) description.
* People can't write comments on Forgejo without an account, and there's no way to register
* Why not Develop & contribute Django (Python) in How to participate?
* Incantation -> Incarnation

View file

@ -0,0 +1,33 @@
**Standup:** 2025-03-31 @09:30
**Present:** Kiara, Koen, Ronny, Kevin, Gheorghe, Robert, Bjorn, Valentin, Nicolas
**Absent:** Hans (known), Eric (known)
* Kiara
* Past day(s): continue on deploy button online
* Today: investigate SSH strategy for above and to deal with password-protected SSH keys
* Koen
* now have some experience with pixelfed
* want to upgrade the pixelfed cluster this afternoon and bring it live this evening so we can announce it tomorrow before the conference
* Kevin
* Worked on the panel friday, it shows now if the deploy was a succes and which services have been deployed
* today can work more on the panel but dont know what yet will discuss with kiara
* Bjorn
* Friday: Partnermeeting
* Today: demo & prep for Fediforum
* Valentin
* Wrote up design discussion on configuration data model versioning and format conversion
* Internal meetings
* Nicolas
* Last week disabling the machine
* Working on reproducing the NixOps4 upstream deployment test
* Got stuck with providing DNS within the sandbox
* Robert: there's some code I can give you for that
* Gheorghe
* No blockers
* Friday: Internal PM activities
* Today: Internal PM activities
* Ronny
* Good partnermeeting on Friday
* Robert
* Finishing up flake input override support (needed for ad hoc testing, generally useful)
* Next: stateful resources

View file

@ -0,0 +1,47 @@
# Visual design meeting 2025-03-31
Present: {thijs,timon}@slik, {koen,kevin,kiara}@procolix
- thijs: updated the designs as per the last meeting, supporting workspaces, dark/light themes, (implied) usage graphs, future fediverse services, updated theme
- koen: maybe categorize services using tags, e.g. fediverse, productivity, chat, video, microblogging
- thijs: so allow filtering by this too?
- koen: yes
- kiara: i like the new design
- koen: KDE's designs looks pretty, maybe also look at that
- timon: *clicks mastodon install, leading to detail page*
- koen: maybe allow batch selecting to install, as in current barebones technical implementation
- koen: please add icons for more applications
- timon: *showing preview page for mastodon*
- koen: again, minimize needed clicks, e.g. using basic vs advanced install rather than 'install' vs 'manage', then allow users to maybe tweak after
- thijs: then just do 'install' vs 'manage' as you probably don't want non-basic installs, so people can tweak after
- koen: you should be able to just use them when installed, afterwards change 'install' button to like 'go to your instance'
- koen: i like the detail page's log view, may end up long tho, so maybe add a 'show more' ellsion
- timon: fleshed out the settings view, as well as a users list
- thijs: the users list is more an example of a CRUD page, as you mentioned wanting to do SSO/LDAP before
- koen: again, distinguish stuff everyone should see vs advanced settings we by default should not bother busy non-technical users with
- thijs: you have not configured a domain yet, so cannot deploy mastodon yet - we should probably nag people on mandatory settings they have yet to set, also show progress bar for this
- koen: start simple, then show everything when desired
- thijs: different ways to not scare people off, not sure scaring people with advanced settings is the way, you could instead just show optional settings
- koen: still sounds scary
- thijs: otherwise may not notice what you can do with it
- thijs: you may not know a user's role up-front
- koen: start as basic user
- thijs: sysadmins will feel confused tho
- koen: maybe ask in the onboarding / sign-up what role you want
- thijs: onboarding, what else?
- thijs: we made sure to use only open-source fonts and icons
- koen: i see some details we will not use: e.g. pricing plans ending in 99, pricing plans worded to sell rather than offer transparency (wording shown in design: 'perfect' without elaboration as to why), pricing that needs explaining so people can understand why they should not feel ripped off
- kiara: isn't usage much more fungible?
- koen: we should show those from the panel, but there are different ways to approach this as per an operator's business model
- thijs: maybe hosts should get to choose how to approach this
- koen: agree, companies will have limited resources and may prefer to not make things too granular, tho in larger set-ups one may need to be able to better justify how pricing scales
- thijs: do we always want granular pricing?
- koen: by default yes, if you don't want that, it's open-source so you can fork if you like
- thijs: thanks - what else should we change for tomorrow?
- koen: maybe add graphs over time on disk space and number of applications deployed
- kiara: actually whether the background looks grey or white-ish for me depends on which monitor i view it on
- thijs: ok let's make it a bit lighter still
- koen: maybe also add user settings like advanced/novice, allow scrolling thru the app list, add an icon as per fediversity.eu (NGI - fediversity)
- koen: from pic 'many branches of the fediverse' use: lemmy, bookwyrm, funkwhale, friendica, castopod, writefreely, matrix, owncast, peertube, forgejo, passbolt
- kiara: this image already shows potential tags too
- thijs: we'll try and add the configurable color themes too