Compare commits

...
Sign in to create a new pull request.

15 commits

Author SHA1 Message Date
Kiara Grouwstra
9f25fd986d
add minutes from design meeting 2025-03-12 13:55:26 +01:00
029c55e743 Add meeting-notes/2025-03-12 standup notes.md
Stand up notes
2025-03-12 09:37:17 +01:00
c53a8d46ee Add meeting-notes/2025-03-11 standup notes.md
Standup notes
2025-03-11 09:40:32 +01:00
5a16f56c2e Add meeting-notes/2025-03-10 standup notes.md
Standup notes
2025-03-11 09:28:57 +01:00
e12f8224a6 Add meeting-notes/2025-03-07 standup notes.md
Standup notes
2025-03-07 10:56:46 +01:00
cbe290628e Add meeting-notes/2025-03-06 standup notes.md
Catching up with standup notes
2025-03-07 10:43:08 +01:00
d4fae12375 Add meeting-notes/2025-03-05 standup notes.md
Catching up with standup notes
2025-03-07 10:41:06 +01:00
Gheorghe Aurel Pacurar
167b2df825 Merge remote-tracking branch 'origin/main' 2025-03-05 16:53:09 +02:00
Gheorghe Aurel Pacurar
c7431ed63d Merge remote-tracking branch 'origin/main' 2025-03-05 16:47:11 +02:00
9d829c5d3f Merge pull request 'add note on nixops priorities' (#26) from progress-indicator-note into main
Reviewed-on: #26
Reviewed-by: Valentin Gagarin <valentin.gagarin@tweag.io>
2025-03-05 15:44:20 +01:00
Gheorghe Aurel Pacurar
5263958f0e Merge remote-tracking branch 'origin/main' 2025-03-05 11:24:36 +02:00
Gheorghe Aurel Pacurar
393119cc7d Merge remote-tracking branch 'origin/main' 2025-03-05 11:23:13 +02:00
Gheorghe Aurel Pacurar
32675afc4a Adding the documents in the D2.1 and D2.2 deliverables folder. 2025-03-05 11:20:52 +02:00
d4e7b959a7 Add meeting-notes/2025-03-04 standup notes.md
Standup notes
2025-03-04 12:46:24 +01:00
Kiara Grouwstra
68178405a8
restructure the meeting notes to consistently start with the ISO date format, as it facilitates using computer sorestructure meeting notes to consistently start with ISO date format
facilitates using computer sorting to obtain a chronological order,
which makes it easier to find things.

note i also deleted a minutes file for a date that we had two copies for
in the repo.
2025-03-04 10:23:19 +01:00
27 changed files with 269 additions and 28 deletions

View file

@ -1,28 +0,0 @@
Attendees: Gheorghe, Richard, Valentin, Ronny, Nicolas, Björn
Not attending: Koen & Robert (travelling), Kevin (day off)
* Bjorn set up some data structures in the internal Wiki
* Valentin:
* Met Eli from Thymis & Johannes from Clan. Discussed the three system architectures with them.
* NixOps took some time for them to make it click. Now I know a bit better what we can learn from them, and if and on what we can collaborate. Overlap might be rather small with those projects.
* We need to think about how to convey the power of NixOps in such a way that people understand this properly -- it's at a very high level of abstraction (essentially an IO monad for the Nix language), while people typically think in terms of their concrete use cases.
* That gap requires some storytelling and didactic techniques to bridge.
* Will work on a report & publish it on the website to communicate
* Valentin & Bjorn will have a chat tomorrow after standup
* Gheorghe:
* Shared the UML info last Friday
* Will work on the financials & get the numbers
* Diagram code wants to add a PR
* Update the numbers
* Nicolas:
* Wiki e-mail: we need to have a secrets management solution.
* No test for PeerTube yet. So I started working on it. Probably finished today
* Ronny:
* Will have a look at Gheorghe's PR.
* Richard:
* Will ask Kevin about his work & check if I can help out
* Looking for stuff to work on
* Nicholas opened up the wiki registration so each team member can create their own account today.
* Nicholas: Make Forgejo send out notifications (Nicholas will do this).

View file

Before

Width:  |  Height:  |  Size: 3.7 MiB

After

Width:  |  Height:  |  Size: 3.7 MiB

View file

@ -0,0 +1,76 @@
# fediversity design meeting 2025-03-12
present: slik (thijs, tiemon) + procolix (lois, kevin, kiara)
- thijs: what is the project called and who does what?
- thijs: how do you see front-end dev for this?
- kiara: we don't need you to do an implementation using some front-end framework - just the design will do.
- thijs: what will be the concrete deliverable then for the demo?
- kiara: if for fediforum we do not have the design implemented yet that is acceptable.
- thijs: maybe we will make it in time.
- tiemon: sounds ambitious.
- thijs: should we deliver code or would an interactive design do?
- kiara: an interactive design will do.
- kiara: could this handle animations too?
- tiemon: yes.
- thijs: could you explain some terminology here like fediverse, protagio, providers, panel?
- kevin: *explains*
- thijs: which applications will you do, and how do these get added?
- kiara: mastodon, pixelfed and peertube at least.
- kevin: *explains about fediversity sub-grants*
- thijs: who will select what applications get added then?
- kiara: formally the Open Internet Discourse Foundation.
- thijs: are there set criteria for this? are these political decisions?
- kiara: fediversity is open-source, tho as maintainers we will eventually need to make decisions take into account our capacity given the maintenance work involved.
- thijs: how might hosts, users, workspaces and accounts relate?
- kiara: we will offer SSO across applications.
- thijs: what if people say use this from both professional as well as other roles? can they then have workspaces representing their accounts at different hosts?
- kiara: i envision the web client as agnostic to orchestration capabilities, so a client application logged in to accounts at different hosts thru e.g. workspaces could technically be possible, tho i would not see this as significantly affecting our design currently.
- thijs: how about a host admin panel to e.g. restrict offered applications? or for hosts' accountants?
- kiara: hosts consist of sysadmins, so a config file may currently suffice for them as a user interface.
- kevin: hosts also already have their own client-facing front-ends.
- thijs: cli for now, so for the design focus on the operator panel? ok.
- thijs: *asking about terminology*
- *kevin + kiara explain*
- thijs: do you want to offer a federated UX?
- kevin: the deployed applications federate already.
- thijs: applications tend to offer support buttons. who is in charge of offering this support, operators, hosts or you?
- kiara: the operator, afaik.
- kevin: we might direct users to the application manuals.
- thijs: will fedipanel come with a knowledge base aimed at the operators?
- kiara: we could link to a static one deployed from our end.
- kevin: probably better to include this in the panel deployment.
- thijs: sure, let me know.
- thijs: we can show what we had so far in design program figma.
- tiemon: you can navigate and interact with the designs, and they can generate html as well.
- thijs: we like to work with job stories, so not just user stories like 'as a ...' but also including 'so that ...'.
- kiara: great, so do we.
- thijs: we can show some UIs we like for reference.
- thijs: you won't offer file management from the panel, right?
- kevin: correct.
- kiara: fyi our deployment is somewhat big-bang still, rather than say configure mastodon -> deploy -> configure pixelfed -> deploy - we can not yet enqueue such syncs.
- thijs: where can we find your application?
- kevin: the code is at <https://git.fediversity.eu>, but we also have a recent demo video.
- tiemon: we saw that one, yeah.
- thijs: here is a wireframe so we can align on the chrome (= UI parts that are always there).
- kiara: we do not yet have workspaces, but multiple deployments per user could become an option.
- thijs: how about an admin interface to manage users?
- kiara: we will have to go thru hosts' SSO because of billing.
- kevin: yes this will go thru LDAP.
- thijs: how about showing stats about e.g. numbers of mastodon users?
- kiara: applications should already handle stuff specific to them, so we don't plan to do this.
- thijs: how about application settings (generic vs application-specific)?
- kiara: generic ones will apply to say configure VM resources or sub-domains, tho otherwise most should be application-specific.
- thijs: no auto-scaling?
- kiara: not for now.
- thijs: how about a billing interface?
- kevin: hosts would use their existing ones.
- tiemon: how is pricing determined then?
- kiara: hosts may set this based on the usage info we will provide.
- thijs:
- font: manrope?
- kiara: looks pretty.
- icon sets, selected by open-source / pretty / ...:
- [iconoir](https://iconoir.com/)?
- [phosphor](https://phosphoricons.com/)?
- kevin+lois+kiara: this one looks prettier.

View file

Before

Width:  |  Height:  |  Size: 276 KiB

After

Width:  |  Height:  |  Size: 276 KiB

View file

Before

Width:  |  Height:  |  Size: 258 KiB

After

Width:  |  Height:  |  Size: 258 KiB

View file

@ -0,0 +1,35 @@
**Standup:** 2025-03-04 @09:30
**Present:** Bjorn, George, Ronny, Kevin, Lois, Valentin, Kiara, Robert
**Absent:** Nicholas (known), Hans (known), Koen (known)
* Bjorn
* Yesterday: no Fediversity.
* Today: Catch up
* Ronny
* Yesterday no Fediversity
* no blockers no updates
* Gheorghe
* No blockers
* Yesterday: Internal specific PM activities
* Today: Internal specific PM activities
* Eric
* No blockers
* No updates
* Kiara
* Yesterday: Form PR. Unblock front & backend so triggering with NixOps will work.
* Today: continue with this
* Loïs
* No blockers
* No updates
* will continue work with Kevin and Kiara on the django
* Kevin
* No updates
* will continue work with lois and kiara on the django
* Valentin
* Clarified things we need from NixOps4 for the MVP and mid/long term with Robert and Kiara
* Summary: a bit of JSON logging for now, but eventually we'll serve OpenTelemetry in the Panel for capturing fine-grained progress indication
* Hacked out a sketch for managing versioned configuration schemas
* Code reviews
* Robert
* Worked on OpenTelemetry logging
* No blockers

View file

@ -0,0 +1,29 @@
**Standup:** 2025-03-05 @09:30
**Present:** Bjorn, Eric, Gheorghe, Koen, Lois, Valentin, Kevin
**Absent:** Nicholas (known), Hans (known), Ronny (known), Kiara (Nix gathering)
* Bjorn
* Yesterday: other obligations :(
* Today:
* Q: How is the work on deliverable 3 going? Demo on Monday 10th...
* Eric
* No blockers, no updates
* Gheorghe
* No blockers
* Testerday: Internal PM activities
* Today: Internal PM activities
* Loïs
* Looked at Kiara's feedback for fedipanel
* No blockers
* Koen
* Spoke with Thijs and Timo and Kiara
* I would like a general 'how to check an application' before sending it to NixPkgs discussion (not now).
* Remy (EU thing)
* Valentin
* Pingponged code with Kiara yesterday, should merge basic handling versioned configurations today
* Available for consultation and code review
* Kevin
* worked on the django yesterday resolving some comments from valentin in our pr
* schedule for today is pretty full so probaly wont get much done for fediverse
* Robert
* No updates

View file

@ -0,0 +1,37 @@
**Standup:** 2025-03-06 @09:30
**Present:** Bjorn, Eric, Gheorghe, Koen, Lois, Ronny, Valentin
**Absent:** Nicholas (known), Hans (known), Kiara (known)
* Gheorghe
* No blockers
* Yesterday: Internal PM activities + starting the central document for the Tweag back-end Nix creation.
* Today: Internal PM activities + continuing the central document for the Tweag back-end Nix creation.
* Koen
* no blockers
* no updates
* Valentin
* Discussed steps for demo preparation with Bjorn, Kevin, Lois
* Continued tying up the data models in the backend
* Reviewed the deliverables document Gheorghe prepared
* Reviewed Robert's "modular services" PR
* https://github.com/NixOS/nixpkgs/pull/372170/
* Bjorn
* Yesterday: spoke with Ronny, Valentin & with Kevin & Lois about the demo
* Today: will speak with Koen.
* TODO: will remove the old board
* Loïs
* Blockers: Needing a review on pr 141
* Worked on MVP 2 preperation
* Worked with Valentin and Kevin on versioned configurations
* Today: Prepare further for demo 2
* Eric
* no blockers
* available
* Kevin
* blocked on needing a review on the pr 141
* Yesterday, met with loïs and Valentin to look at versioned configurations
* also had a meeting with loïs, valentin and Bjorn for the mvp 2 next tuesday
* This morning had a discusion with Loïs to prepare for the next demo
* Ronny
* Had a chat with Bjorn about structure
* Preparing the partnermeeting on Friday

View file

@ -0,0 +1,15 @@
**Standup:** 2025-03-07 @09:30
**Present:** Bjorn, Gheorghe
* Gheorghe
* No blockers.
* Yesterday: Internal project meetings and actions. Meet Erik and discussed more details about the documentation.
* Today: Internal project meetings and actions.
* Bjorn
* Yesterday:
* chat with Koen
* cleanup Meta repo
* Today:
* partner status meetup
* add daily standup notes to repo

View file

@ -0,0 +1,26 @@
**Standup:** 2025-03-10 @09:30
**Present:** Björn, Hans, Gheorghe, Ronny, Robert
**Absent:** Koen (known), Kevin (known) Lois (known), Valetin (known), Nicolas (known)
* Björn
* Friday:
* Partners meeting
* Standup (no more on Friday)
* Today
* Chat with Kiara?
* Mail partners
* Gheorghe
* No blockers
* Friday: Internal PM activities
* Today: Internal PM activities
* Hans (welcome back!)
* planning to work on other projects than Fediversity
* Robert
* Did some prep work for improving flakes integration
* Will not attend most standups until 27th (see wiki)
* Will be available at Matrix for questions
* Ronny
* No blockers
* No updates
* Need to reschedule partnermeeting
* Looking forward to demo tomorrow

View file

@ -0,0 +1,32 @@
**Standup:** 2025-03-11 @09:30
**Present:** Bjorn, Kevin, Koen, Kiara, Gheorghe, Lois, Eric, Ronny
**Absent:** Hans (known), Valentin(known), Nicolas(known)
* Bjorn
* Yesterday: partners mail
* Today:
* Demo
* Going through planning
* Chat with Kiara
* Koen
* fighting windmills (nix and debian). Start with learning the app on the OS it supports, than look at things like Nix.
* Kevin
* no updates:
* today: doing the demo with lois en kiara
* Kiara
* Past days: Planet Nix
* Today: continue triggering orchestration from panel, get back up to speed, maybe discuss roadmap
* Gheorghe
* No blockers
* Yesterday: Internal PM activities
* Today: Internal PM activities
* Loïs
* Today: Demo 2, discuss whats next
* Past days: prepared for demo 2
* Eric
* No blockers, available
* Ronny
* No blockers
* Looking forward to demo
* Robert
* no updates and now traveling listening in but noisy environment

View file

@ -0,0 +1,19 @@
Standup: 2025-03-12 @09:30
Present: Björn, Kiara, Eric, Kevin, Lois
Absent: Koen (known), Gheorghe(known), Nicolas(known), Robert(known), Valentin(known), Ronny(known)
Updates:
* Kiara:
* Yesterday: paired on nixops from django with Lois
* Today: ^
* Bjorn
* Yesterday: Demo & meetings
* Today: going through work packages / deliverables & other obligations
* Eric
* available
* Loïs
* Yesterday: Demo 2, made a connection between panel and Nixops
* Continue working on the panel today
* Kevin
* Yesterday: Demo 2 & after discussion
* small talk a with koen about my availability