NixOS / NixOS/foundation

[Funding]: Saltsprint 2026-06-22 – 2026-06-27

Open
#243 2 comments 0 reactions 1 assignee View on GitHub

@Lassulus is already working on this.

Since Mar 11, 2026.

event-funding-request Spending/Approved
Dominant language
No language data
Stars
141
Forks
17
PR merge metrics
No merged PRs in 30d

Description

Event Name

Saltsprint 2026

Event Website

https://saltsprint.org

Event Purpose

Our goal is to get contributors together in one place to leverage the high bandwidth, low latency exchanges that are possible in person: working on hard problems, taking time to discuss things in depth, experimenting with and showing off fresh ideas - and last but not least welcoming new contributors and strengthening community bonds.

Event Visitors

30

Event Organizer

Flying Circus / Christian Theune

Budget amount

1000

Budget description

The SaltSprint has a generally low entry level budget of around 2000€ of which the Flying Circus will sponsor 1000€ and the time for organizing. The intention is to demonstrate that sprints can be organized on a budget.

Within the baseline budget we:

  • book a sufficiently large event location with workspaces for all participants
  • proper internet connection
  • breakfast and snacks, fruits and drinks for all participants

We will also invite other sponsors to increase stretch goals where so we can potentially increase the amount of catering provided by us and maybe provide some merchandising, like a T-Shirt. (On the baseline budget we expect people to cover their own lunch and dinner choices.)

We'll also provide a budget retrospective and publicize the budget (showing the decision points and various options we implemented depending on the available funding and participants) to help other people make decisions about hosting sprints in the future.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.