Fediversity/Fediversity
12
1
Fork 3
Code Issues 22 Pull requests 2 Actions Projects 1 Activity

Add report on 24.11 ZHF hackathon #40

Merged
fricklerhandwerk merged 3 commits from fricklerhandwerk/Fediversity:zhf-report into main 2024-11-28 17:01:42 +01:00
Conversation 0 Commits 3 Files changed 7 +74 -12
fricklerhandwerk commented 2024-11-27 15:53:57 +01:00
Owner
Copy link

depends on #38

depends on https://git.fediversity.eu/Fediversity/Fediversity/pulls/38
fricklerhandwerk added 2 commits 2024-11-27 15:53:59 +01:00
add report on 24.11 ZHF hackathon
All checks were successful
/ check-pre-commit (pull_request) Successful in 23s
Details
5390d869c5
Niols reviewed 2024-11-27 17:23:05 +01:00
website/content/events/2024-11-zurich-zhf.nix Outdated
@ -0,0 +2,4 @@
{
collections.events.entry = { link, ... }: {
title = "NixOS 24.11 ZHF hackathon";
name = lib.mkForce "zhf-24-11";
Niols commented 2024-11-27 17:18:08 +01:00
Owner
Copy link

Why is this mkForce necessary?

Why is this `mkForce` necessary?
fricklerhandwerk commented 2024-11-28 09:38:01 +01:00
Author
Owner
Copy link

There's a default value that makes make a slug from the title, but right, that one should probably mkDefault so here we don't need mkForce.

There's a default value that makes make a slug from the title, but right, that one should probably `mkDefault` so here we don't need `mkForce`.
👍 1
Niols commented 2024-11-28 09:39:27 +01:00
Owner
Copy link

Thanks; no worth an issue imo. I'll mark this as resolved.

Thanks; no worth an issue imo. I'll mark this as resolved.
Niols marked this conversation as resolved
website/content/events/2024-11-zurich-zhf.nix Outdated
@ -0,0 +7,4 @@
start-date = "2024-11-23";
end-date = "2024-11-24";
start-time = "10:00";
end-time = "17:00";
Niols commented 2024-11-27 17:17:59 +01:00
Owner
Copy link

Looks like datetime would be better here? They could also include the timezone of the event, but I guess it's implicitly conveyed in the description already.

Looks like datetime would be better here? They could also include the timezone of the event, but I guess it's implicitly conveyed in the description already.
fricklerhandwerk commented 2024-11-28 09:39:10 +01:00
Author
Owner
Copy link

Separating time and date allows avoiding parsing, since we may have events that have a date but no time; so yes, simplicity. For now we assume local time, and generally we're lacking a time handling library for the Nix language.

Separating time and date allows avoiding parsing, since we may have events that have a date but no time; so yes, simplicity. For now we assume local time, and generally we're lacking a time handling library for the Nix language.
👍 1
fricklerhandwerk marked this conversation as resolved
website/content/events/2024-11-zurich-zhf.nix Outdated
@ -0,0 +12,4 @@
body = ''
The biannual [Zürich NixOS ZHF hackathon](https://zurich.nix.ug/) has become somewhat of an institution for maintaining the tradition of preparing the upcoming NixOS release.
The main goal of the two-day gathering is to bring down the number of build failures on the [continuous integration system Hydra](https://status.nixos.org/) before the release: Zero Hydra Failures.
Niols commented 2024-11-27 17:19:38 +01:00
Owner
Copy link

It's not that obvious what's the logical link of the : here. But maybe we consider that it is for our target? Otherwise I'd maybe go for something like:

The main goal of the two-day gathering is to bring down the number of build failures on the continuous integration system Hydra before the release: ZHF stands for Zero Hydra Failures.

It's not that obvious what's the logical link of the `:` here. But maybe we consider that it is for our target? Otherwise I'd maybe go for something like: > The main goal of the two-day gathering is to bring down the number of build failures on the continuous integration system Hydra before the release: ZHF stands for _Zero Hydra Failures_.
👍 1
fricklerhandwerk marked this conversation as resolved
website/content/news/24-11-zurich-zhf.nix Outdated
@ -0,0 +1,22 @@
{ config, lib, ... }:
Niols commented 2024-11-27 17:22:26 +01:00
Owner
Copy link

The name of the event file is 2024-11-* while this one is 24-11-*. I'd go for YYYY-MM for both, but I don't care as much about this particular choice as I care about consistency!

The name of the event file is `2024-11-*` while this one is `24-11-*`. I'd go for `YYYY-MM` for both, but I don't care as much about this particular choice as I care about consistency!
👍 1
fricklerhandwerk marked this conversation as resolved
fricklerhandwerk force-pushed zhf-report from 5390d869c5 to 2ba91fef6e 2024-11-28 09:43:28 +01:00 Compare
Niols approved these changes 2024-11-28 09:47:01 +01:00
fricklerhandwerk force-pushed zhf-report from 2ba91fef6e to 8899b82e51 2024-11-28 11:07:16 +01:00 Compare
fricklerhandwerk merged commit 8fa6c2f6f4 into main 2024-11-28 17:01:42 +01:00
fricklerhandwerk deleted branch zhf-report 2024-11-28 17:01:43 +01:00
Sign in to join this conversation.
Reviewers
No reviewers
Niols
Labels
Clear labels   
blocked

   
project-management

Project management related tasks

  
question
No labels
blocked
project-management
question
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
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/Fediversity#40
No description provided.
Delete branch "fricklerhandwerk/Fediversity:zhf-report"

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?