[Git][reproducible-builds/reproducible-website][master] 4 commits: rbs2026: fix title and sort order for the notes
Mattia Rizzolo (@mattia)
gitlab at salsa.debian.org
Sat Sep 26 09:19:46 UTC 2026
Mattia Rizzolo pushed to branch master at Reproducible Builds / reproducible-website
Commits:
411d3e8e by Mattia Rizzolo at 2026-09-26T11:15:22+02:00
rbs2026: fix title and sort order for the notes
Signed-off-by: Mattia Rizzolo <mattia at debian.org>
- - - - -
75146298 by Mattia Rizzolo at 2026-09-26T11:15:54+02:00
rbs2026: add the main agenda index page (wip)
Signed-off-by: Mattia Rizzolo <mattia at debian.org>
- - - - -
ea564cf5 by Mattia Rizzolo at 2026-09-26T11:19:03+02:00
rb2026: fix the permalinks
Signed-off-by: Mattia Rizzolo <mattia at debian.org>
- - - - -
57c81cb9 by Mattia Rizzolo at 2026-09-26T11:19:13+02:00
rb2026: add session note picture
Signed-off-by: Mattia Rizzolo <mattia at debian.org>
- - - - -
19 changed files:
- _events/gothenburg2026/agenda/d1-atproto.md
- _events/gothenburg2026/agenda/d1-badbuild.md
- _events/gothenburg2026/agenda/d1-imagebuilds.md
- _events/gothenburg2026/agenda/d1-longtail.md
- _events/gothenburg2026/agenda/d2-buildinfrastructure.md
- _events/gothenburg2026/agenda/d2-cross-distro.md
- _events/gothenburg2026/agenda/d2-nonreproducible.md
- _events/gothenburg2026/agenda/d2-rb-enforcement.md
- _events/gothenburg2026/agenda/d2-rb-security.md
- _events/gothenburg2026/agenda/d2-rb-social.md
- _events/gothenburg2026/agenda/d2-transparency-logging.md
- _events/gothenburg2026/agenda/d3-files.md
- _events/gothenburg2026/agenda/d3-rb-ai.md
- _events/gothenburg2026/agenda/d3-rb-enforcement2.md
- _events/gothenburg2026/agenda/d3-rebuilderd.md
- _events/gothenburg2026/agenda/d3-sourcedateepoch.md
- _events/gothenburg2026/agenda/d3-trusting-trust.md
- + _events/gothenburg2026/agenda/index.md
- _events/gothenburg2026/index.html
Changes:
=====================================
_events/gothenburg2026/agenda/d1-atproto.md
=====================================
@@ -1,8 +1,8 @@
---
layout: event_detail
-Gothenburg 2026 - Day 1 - Distributing metadata
+title: Gothenburg 2026 - Day 1 - Distributing metadata
order: 10
-permalink: /events/gothenburg2026/agenda/d1-atproto.md
+permalink: /events/gothenburg2026/agenda/d1-atproto/
---
- Headline: **Distributing metadata**.
- (transparency logs might be a topic related to this.)
=====================================
_events/gothenburg2026/agenda/d1-badbuild.md
=====================================
@@ -1,8 +1,8 @@
---
layout: event_detail
Gothenburg 2026 - Day 1 - Bad builds
-order: 10
-permalink: /events/gothenburg2026/agenda/d1-badbuild.md
+order: 20
+permalink: /events/gothenburg2026/agenda/d1-badbuild/
---
Greg's work: uses stabilizer (these stabilizers guarantee removing non-malicious differences)
=====================================
_events/gothenburg2026/agenda/d1-imagebuilds.md
=====================================
@@ -1,8 +1,8 @@
---
layout: event_detail
-Gothenburg 2026 - Day 1 - Image builds
-order: 10
-permalink: /events/gothenburg2026/agenda/d1-imagebuilds.md
+title: Gothenburg 2026 - Day 1 - Image builds
+order: 30
+permalink: /events/gothenburg2026/agenda/d1-imagebuilds/
---
## What was necessary for making Arch images reproducible:
=====================================
_events/gothenburg2026/agenda/d1-longtail.md
=====================================
@@ -1,8 +1,8 @@
---
layout: event_detail
-Gothenburg 2026 - Day 1 - the long tail
-order: 10
-permalink: /events/gothenburg2026/agenda/d1-longtail.md
+title: Gothenburg 2026 - Day 1 - the long tail
+order: 40
+permalink: /events/gothenburg2026/agenda/d1-longtail/
---
## Problem
The Pareto principle applies to fixing r-b issues. 80% of the benefit need 20% of the work and what non-determinism remains becomes increasingly harder to make deterministic.
=====================================
_events/gothenburg2026/agenda/d2-buildinfrastructure.md
=====================================
@@ -1,8 +1,8 @@
---
layout: event_detail
-Gothenburg 2026 - Day 2 - Build infrastructure
-order: 10
-permalink: /events/gothenburg2026/agenda/d2-buildinfrastructure.md
+title: Gothenburg 2026 - Day 2 - Build infrastructure
+order: 50
+permalink: /events/gothenburg2026/agenda/d2-buildinfrastructure/
---
Improve serving and format of buildinfo files
=====================================
_events/gothenburg2026/agenda/d2-cross-distro.md
=====================================
@@ -1,8 +1,8 @@
---
layout: event_detail
-Gothenburg 2026 - Day 2 - Cross-distro reproducibility
-order: 10
-permalink: /events/gothenburg2026/agenda/d2-cross-distro.md
+title: Gothenburg 2026 - Day 2 - Cross-distro reproducibility
+order: 60
+permalink: /events/gothenburg2026/agenda/d2-cross-distro/
---
## Cross-distro reproducibility
=====================================
_events/gothenburg2026/agenda/d2-nonreproducible.md
=====================================
@@ -1,8 +1,8 @@
---
layout: event_detail
-Gothenburg 2026 - Day 2 - the remaining 1%
+title: Gothenburg 2026 - Day 2 - the remaining 1%
order: 10
-permalink: /events/gothenburg2026/agenda/d2-nonreproducible.md
+permalink: /events/gothenburg2026/agenda/d2-nonreproducible/
---
## The remaining 1%
@@ -30,3 +30,6 @@ Thought: make the profile a different package, similar to the signing solution i
Idea: use a fuzzer to find an input that makes a test undeterministic. Fuzzer that make a profile for the code. Fuzzer that "understands" the language, find inputs that are constant but non-deterministic output.
Idea: Upstream instructions on how to perform a profiling run. Example: profile.sh which runs the program and outputs instrument binaries, providing profiling information and is determinstic.
+
+
+
=====================================
_events/gothenburg2026/agenda/d2-rb-enforcement.md
=====================================
@@ -1,8 +1,8 @@
---
layout: event_detail
-Gothenburg 2026 - Day 2 - Enforcement
-order: 10
-permalink: /events/gothenburg2026/agenda/d2-rb-enforcement.md
+title: Gothenburg 2026 - Day 2 - Enforcement
+order: 70
+permalink: /events/gothenburg2026/agenda/d2-rb-enforcement/
---
## Enforcement
=====================================
_events/gothenburg2026/agenda/d2-rb-security.md
=====================================
@@ -1,8 +1,8 @@
---
layout: event_detail
-Gothenburg 2026 - Day 2 - Security and Reproducible Builds
-order: 10
-permalink: /events/gothenburg2026/agenda/d2-rb-security.md
+title: Gothenburg 2026 - Day 2 - Security and Reproducible Builds
+order: 80
+permalink: /events/gothenburg2026/agenda/d2-rb-security/
---
# Security and RB
=====================================
_events/gothenburg2026/agenda/d2-rb-social.md
=====================================
@@ -1,8 +1,8 @@
---
layout: event_detail
-Gothenburg 2026 - Day 2 - Social aspects of Reproducible Builds
-order: 10
-permalink: /events/gothenburg2026/agenda/d2-rb-social.md
+title: Gothenburg 2026 - Day 2 - Social aspects of Reproducible Builds
+order: 90
+permalink: /events/gothenburg2026/agenda/d2-rb-social/
---
## social
=====================================
_events/gothenburg2026/agenda/d2-transparency-logging.md
=====================================
@@ -1,8 +1,8 @@
---
layout: event_detail
-Gothenburg 2026 - Day 2 - Transparency logging
-order: 10
-permalink: /events/gothenburg2026/agenda/d2-transparency-logging.md
+title: Gothenburg 2026 - Day 2 - Transparency logging
+order: 100
+permalink: /events/gothenburg2026/agenda/d2-transparency-logging/
---
## transparency-logging
=====================================
_events/gothenburg2026/agenda/d3-files.md
=====================================
@@ -1,7 +1,7 @@
---
layout: event_detail
title: Gothenburg 2026 - Day 3 - Files what are they even good for?
-order: 10
+order: 110
permalink: /events/gothenburg2026/agenda/d3-files/
---
=====================================
_events/gothenburg2026/agenda/d3-rb-ai.md
=====================================
@@ -1,8 +1,8 @@
---
layout: event_detail
-Gothenburg 2026 - Day 3 - RB and AI
-order: 10
-permalink: /events/gothenburg2026/agenda/d3-rb-ai.md
+title: Gothenburg 2026 - Day 3 - RB and AI
+order: 120
+permalink: /events/gothenburg2026/agenda/d3-rb-ai/
---
## Observed Benefits
* Extracts builds structures when vague
=====================================
_events/gothenburg2026/agenda/d3-rb-enforcement2.md
=====================================
@@ -1,8 +1,8 @@
---
layout: event_detail
-Gothenburg 2026 - Day 3 - Enforcement, part 2
-order: 10
-permalink: /events/gothenburg2026/agenda/d3-rb-enforcement2.md
+title: Gothenburg 2026 - Day 3 - Enforcement, part 2
+order: 130
+permalink: /events/gothenburg2026/agenda/d3-rb-enforcement2/
---
Follow-up of a [session on day 2](d2-rb-enforcement.md)
=====================================
_events/gothenburg2026/agenda/d3-rebuilderd.md
=====================================
@@ -1,8 +1,8 @@
---
layout: event_detail
-Gothenburg 2026 - Day 3 - rebuilderd
-order: 10
-permalink: /events/gothenburg2026/agenda/d3-rebuilderd.md
+title: Gothenburg 2026 - Day 3 - rebuilderd
+order: 140
+permalink: /events/gothenburg2026/agenda/d3-rebuilderd/
---
## rebuilderd
=====================================
_events/gothenburg2026/agenda/d3-sourcedateepoch.md
=====================================
@@ -1,8 +1,8 @@
---
layout: event_detail
-Gothenburg 2026 - Day 3 - SOURCE_DATE_EPOCH
-order: 10
-permalink: /events/gothenburg2026/agenda/d3-sourcedateepoch.md
+title: Gothenburg 2026 - Day 3 - SOURCE_DATE_EPOCH
+order: 150
+permalink: /events/gothenburg2026/agenda/d3-sourcedateepoch/
---
- Bernhard proposed changes to the S_D_E spec on the rb-general list, which we discussed and found largely uncontroversial, so we went on to prepare actual MRs and propose them on the list:
- https://salsa.debian.org/reproducible-builds/specs/source-date-epoch-spec/-/merge_requests/8 links to all the others:
=====================================
_events/gothenburg2026/agenda/d3-trusting-trust.md
=====================================
@@ -1,8 +1,8 @@
---
layout: event_detail
-Gothenburg 2026 - Day 3 - Trusting trust
-order: 10
-permalink: /events/gothenburg2026/agenda/d3-trusting-trust.md
+title: Gothenburg 2026 - Day 3 - Trusting trust
+order: 160
+permalink: /events/gothenburg2026/agenda/d3-trusting-trust/
---
- Well-known trusting trust problem:
- Fully recursive reproducible builds
=====================================
_events/gothenburg2026/agenda/index.md
=====================================
@@ -0,0 +1,176 @@
+---
+layout: event_detail
+title: Gothenburg 2026 - Agenda
+order: 1
+permalink: /events/gothenburg2026/agenda/
+---
+
+
+# WIP
+## this needs to be converted to proper markdown and link to the proper actual pages
+
+
+Day 1 - Tuesday, 22 September 2026
+
+8.30 Morning beverages available
+
+9.00 Opening Circle
+
+The 2025 Reproducible Builds Summit will be called to order with a fast-paced kickoff that includes words of welcome from the organizers, brief participant introductions, along with overviews of the agenda, participation guidelines and meeting logistics.
+
+9.45 Project Updates I
+
+* Mapping who is in the room
+** NOTES: https://pad.riseup.net/p/rbsummmit2025-d1-mappingprojects-keep
+
+Arch Linux - LINK(s)
+F-Droid - Client 2.0 is ready, repo is 35% RB, academia verified 19k packages (83% built, 94% of them repro)
+open SUSE - LINK(s) https://lists.opensuse.org/archives/list/factory@lists.opensuse.org/thread/C7BCS4OC2XPR5ZNOEXCJGP6NXL2W5BNT/
+OSS Rebuild - LINK(s) https://oss-rebuild.dev/
+rebuilderd - LINK(s) https://github.com/kpcyrd/rebuilderd
+Debian - https://reproduce.debian.net/ gates packages in the next Debian release (blocking regressions and new not reproducible packages)
+
+10.45 Break
+
+Please note that all break times are approximate :)
+
+11.15 Project Updates II
+
+Build tools/registries OCI/ORAS - LINK(s)
+Transparency logs - LINK(s) https://www.sigsum.org/
+Debian - LINK(s) https://reproduce.debian.net/
+repro-threshold - LINK(s) https://github.com/kpcyrd/repro-threshold
+Archiving + integrity/transpareancy of non-software stuff - https://archive.rip
+DETTRACE - LINK(s) https://github.com/bmwiedemann/dettrace https://build.opensuse.org/package/show/devel:tools/dettrace
+
+We'll continue the program with short question-driven updates from a range of participants on a range of projects from across the Reproducible Builds ecosystem.
+
+12.30 Lunch
+
+Participants are encouraged to sit with those who they have not yet met or engaged.
+
+13.30 Collaborative Working Sessions
+
+* AT Protocl
+** ✅NOTES: https://pad.riseup.net/p/rbsummmit2026-atproto
+* Bad and malicious builds
+** ✅NOTES: https://pad.riseup.net/p/rbsummmit2026-badbuilds
+* Reproducible image builds
+** ✅NOTES: https://pad.riseup.net/p/rbsummmit2026-imagebuilds
+* Chasing the long tail of reproducibility
+** ✅NOTES: https://pad.riseup.net/p/rbsummmit2026-longtail
+
+15.15 Closing Circle
+
+The closing session will invite participants to weigh in on what has been most useful during the course of Day 1, and refine their goals and priorities for the agenda of Day 2.
+
+16.00 Adjourn to Hack Time
+
+19.00 Dinner -
+
+Day 2 - Wednesday 23 September 2026
+
+8.30 Morning beverages available
+
+9.00 Opening Circle
+
+The day will start with a summary of Day 1 outcomes and a Day 2 Agenda Overview.
+
+9.15 Collaborative Working Sessions
+
+*Source Date Epoch
+** ✅NOTES: https://pad.riseup.net/p/rbsummmit2026-sourcedateepoch
+* RB Enforcement
+** ✅NOTES: https://pad.riseup.net/p/rbsummmit2026-rb-enforcement
+* Social Engagement of Developers
+** ✅NOTES: https://pad.riseup.net/p/rbsummmit2026-social
+* Buildinfo Infrastructure
+** ✅NOTES: https://pad.riseup.net/p/rbsummmit2026-buildinfoinfrastructure
+
+10.45 Break
+
+Please note that all break times are approximate :)
+
+11.00 Peer skill and knowledge share
+
+Participants will be invited and encouraged to request or share any skill they consider relevant to the meeting scope. The session will be structured so as to minimize group size and maximize 1-on-1 sharing opportunities.
+
+12.30 Lunch
+
+Participants are encouraged to sit with those who they have not yet met or engaged.
+
+13.30 Collaborative Working Sessions
+
+* High-priority non-reproducible packages ("last 1%")
+** ✅NOTES: https://pad.riseup.net/p/rbsummmit2026-nonreproducible
+* RB & Security
+** ✅NOTES: https://pad.riseup.net/p/rbsummmit2026-rb-security
+* Transparency logging
+** ✅NOTES: https://pad.riseup.net/p/rbsummmit2026-transparency-logging
+* Android file formats for reproducibility
+** ❌NOTES: https://pad.riseup.net/p/rbsummmit2026-android
+* Cross-distro reproducibility
+** ✅NOTES: https://pad.riseup.net/p/rbsummmit2026-cross-distro
+
+15.15 Closing Circle
+
+The closing session will invite participants to weigh in on what has been most useful during the course of Day 2, and refine their goals and priorities for the agenda of Day 3.
+
+16.00 Adjourn to Hack Time
+
+19.00 Dinner
+
+Day 3 - Thursday 24 September 2026
+
+8.30 Morning beverages available
+
+9.00 Opening Circle
+
+The day will start with a summary of Day 2 outcomes and a Day 3 Agenda Overview.
+
+9.15 Collaborative Working Sessions
+
+* Source Date Epoch Round III
+** ✅NOTES:https://pad.riseup.net/p/rbsummmit2026-sourcedateepoch
+* AI and RB
+** ✅NOTES: https://pad.riseup.net/p/rbsummmit2026-rb-ai
+* rebuilder
+** ✅NOTES: https://pad.riseup.net/p/rbsummmit2026-rebuilderd
+* Enforcement II
+** ✅NOTES:https://pad.riseup.net/p/rbsummmit2026-rb-enforcement-ii
+
+10.45 Break
+
+Please note that all break times are approximate :)
+
+11.00 Collaborative Working Sessions
+
+12.30 Lunch
+
+Participants are encouraged to sit with those who they have not yet met or engaged.
+
+13.30 Mapping next conversations and next steps
+
+The group will pause before the final session to take stock of the progress made to this point in the week and to inventory action items, next steps and other bridges to post-event collaboration.
+
+* Trusting Trust
+** ✅NOTES: https://pad.riseup.net/p/rbsummmit2026-trusting-trust
+* Source Date Epoch Round III
+** ✅NOTES: https://pad.riseup.net/p/rbsummmit2026-sourcedateepoch
+* Files
+** ✅NOTES: https://pad.riseup.net/p/rbsummmit2026-files
+* Package groupings
+** ❌NOTES: https://pad.riseup.net/p/rbsummmit2026-package-groupings
+
+
+
+
+15.00 Closing Circle
+
+Participants will summarize key outcomes from the event, and discuss next steps for continuing collaboration after the meeting.
+
+16.00 Adjourn to Hack Time
+
+19.00 Dinner
+
+
=====================================
_events/gothenburg2026/index.html
=====================================
@@ -94,8 +94,7 @@ It was followed by two extra days of pure, unmoderated hacking time, September 2
<h2>Agenda</h2>
<p>The agenda as usual was shaped by the interest of our attendees.</p>
-<!--
-<p>The topics discussed and the notes from the relevant sessions are available from <a href="{{ "/events/vienna2025/agenda" | relative_url }}">this page</a>.</p>
+<p>The topics discussed and the notes from the relevant sessions are available from <a href="agenda">this page</a>.</p>
<h2>Event Documentation</h2>
@@ -105,18 +104,19 @@ There was a huge variety of topics discussed. To give a few examples:
</p>
<ul>
<li>project status updates</li>
- <li>how to talk to stakeholders and policymakers </li>
- <li>new getting started guide</li>
- <li>all things rebuilder</li>
+ <li>…</li>
+ <li>…</li>
+ <li>all things rebuilderd</li>
<li>and many many more.</li>
</ul>
To get more details you can check out the following links:
<ul>
<li>
- the <a href="{{ "/events/hamburg2024/agenda" | relative_url }}">Agenda</a> with links to many session notes
+ the <a href="agenda">Agenda</a> with links to many session notes
</li>
- <li>
+</ul>
+<!-- <li>
some <a href="{{ "/events/hamburg2024/outcomes" | relative_url }}">results and outcomes</a> from the hacking sessions
</li>
<li>
View it on GitLab: https://salsa.debian.org/reproducible-builds/reproducible-website/-/compare/b02b2de50f8bf6922b6dcfc4eebb1cf1af6be407...57c81cb9d065c35cd0aec9d0d4638fbed48fd8a7
--
View it on GitLab: https://salsa.debian.org/reproducible-builds/reproducible-website/-/compare/b02b2de50f8bf6922b6dcfc4eebb1cf1af6be407...57c81cb9d065c35cd0aec9d0d4638fbed48fd8a7
You're receiving this email because of your account on salsa.debian.org. Manage all notifications: https://salsa.debian.org/-/profile/notifications | Help: https://salsa.debian.org/help
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.reproducible-builds.org/pipermail/rb-commits/attachments/20260926/0ff87a39/attachment.htm>
More information about the rb-commits
mailing list