57 lines
3 KiB
Markdown
57 lines
3 KiB
Markdown
Present:
|
||
Hans
|
||
Koen
|
||
Kevin
|
||
Ronny
|
||
Robert
|
||
Laurens
|
||
|
||
Absent:
|
||
Niols
|
||
|
||
NixCon:
|
||
Robert and Valentin will attend. Koen will not be there.
|
||
|
||
Koen:
|
||
- Went to PublicSpaces about the PeerTube project where we join as a technical supplier.
|
||
- The project will make 2 large PeerTube instances
|
||
- One for universities, one for smaller broadcasting orgs
|
||
- Goal is to explore the usability of PeerTube
|
||
- Spoke with Toon Toenenel en Pepijn Lemmens
|
||
- Hope to use some of PublicSpaces learnings for our Nordunet Project that also uses PeerTube
|
||
- Point of discussion was if not every organisation should have their own PeerTube server instead
|
||
- This could avoid the issues that the EDPS had with their Mastodon server
|
||
- No conclusions yet, still exploratory phase
|
||
|
||
Koen:
|
||
- Meeting with Eric Hermann from NLnet
|
||
- Writing down the technical specifications of Fediversity
|
||
- photo of drawings result in Matrix channel (will upload on git)
|
||
- Eric is a sysadmin who understands the pain of early choices that cannot be changed later once software is in production
|
||
- Looking for people who do large-scale Nix deployments
|
||
- Eric agrees that how Nix uses 'unstable' branch without having a clear 'stable' branch is a problem
|
||
- Nix is very much framed by the needs of programmers, less so of those of sysadmins
|
||
- Missing a 'Debian-Stable' style branch
|
||
- We've so far focused on low-level technical basis, but not a visible end-user product yet. Eric sees so no major blockers so far to get there
|
||
- Eric understands that these fundamental design decisions take time, and that we're on track with our current work.
|
||
- We need to formalise our design decisions more so they can be communicated to the rest of the community
|
||
- Service portability: on a high level this is clear how this work with S3. This should be tested early on in the process, as the migration process is the most difficult part of our design
|
||
|
||
Koen:
|
||
- Explaining document sketch ([https://git.fediversity.eu/Fediversity/meta/src/branch/main/architecture-docs/Fediversity%20architecture%20Koen%202024-10-21.jpg](https://git.fediversity.eu/Fediversity/meta/src/branch/main/architecture-docs/Fediversity%20architecture%20Koen%202024-10-21.jpg))
|
||
- Public orgs see Mastodon more as an experiment, and PeerTube as a more serious part of their communication suite
|
||
- Eric will formalise the document sketch
|
||
|
||
Koen:
|
||
- starting a video.procolix.eu to get more experience with PeerTube
|
||
- PeerTube devs use Debian as basis, not NixOS
|
||
- In order to get packages done properly, we first have to install them the way the dev makes them. For PeerTube and Pixelfed this is Debian
|
||
- This teaches how its done by the original dev, so we know better how and what to change to get it on Nix
|
||
- We'll continue this week with expanding our domain knowledge of our applications
|
||
|
||
Ronny:
|
||
- About Nix-stable: install Nix on top of Debian-stable
|
||
- Thinking about a way to get Nix-stable inside of Debian-stable
|
||
|
||
Ronny:
|
||
- MediaWiki document currently uses default values for storage, this should probably be changed |