Skip to content
Jim Fuller edited this page Apr 26, 2025 · 42 revisions

curl-up

curl up 2025

This is the annual curl meetup. Developers, users, fans, enthusiasts. People who want to talk about curl and listened to presentations about curl over a whole weekend.

Insights from the project. Stories from users. Planning for the future. Learning from the past. Related technologies. Coming protocol developments - and everything that can be considered related or adjacent to this. There is no better place to learn about curl and curl internals than curl up.

We are an open and inclusive set of friendly people. Past curl ups have typically consisted of 20-30 persons.

When

May 3-4, 2025

Where

Prague, Czechia
Vlkova 36
Praha 3 – Žižkov, 130 00

The venue is called Pracovna. Find it on Google maps / Mapy.cz

Register

Go here. Registration is mandatory to attend.

Fee

The event is entirely free of charge, thanks to our generous project sponsors.

Agenda

Friday May 2

Dinner event for those who said yes before April 27.

Saturday May 3

start topic who what
08:30 setup Daniel/Jim get the camera, mike and live-stream ready
09:00 welcome - state of curl Daniel walk-through of the curl project right now, and what's happening 2025.
09:30 coffee
10:00 state of curl (continued) Daniel
11:00 Evolutions Stefan Eissing things we worked on during last year
11:30 curl container update James Fuller
12:00 curl testing statistics Dan Fandrich
12:45 The quest for a mascot Daniel
13:00 Lunch - provided
14:00 wcurl Samuel Henrique one year later - Remote presentation
14:30 curl CTX James Fuller team tabletop simulation of major security event against curl project
15:30 Break
16:00 curl CTX James Fuller team tabletop simulation of major security event against curl project
17:00 end of day

Social event: Dinner at a restaurant. TBD

Sunday May 4

start topic who what
09:00 welcome - curl security Daniel Past year, where we are, what to do, how to do better. Security is important.
09:30 coffee
10:00 Security data and tooling X curl James Fuller
10:30 Time for a Curl Agent Stefan Eissing
11:00 Genetic Algorithm fuzzing with curl part Deux James Fuller
11:30 curlx_ as an internal library Daniel?
12:00 HTTP news and how to curl them Daniel
13:00 Lunch - provided
14:00 100-year-curl Daniel
14:30 Discussion: performance, load & benchmark testing Team
15:00 -
15:30 break
16:00 -
17:00 end of curl up 2025 see you in 2026

Proposed sessions

Tell us what you want to speak up about.

Tell us what you want to listen to.

The state of curl (Daniel Stenberg)

60 - 90 minutes walk-through of the curl project right now, and what's happening 2025.

100-year-curl (Daniel Stenberg)

A short presentation about the current setup for contingency and an open discussion about the future, recruiting new maintainers, getting younger people involved in the project, financing and how to make curl survive another hundred years.

curl security (Daniel Stenberg)

Past year, where we are, what to do, how to do better. Security is important.

CTX curl (James Fuller)

With participants adopting the roles of 'The Curl team', 'Others' and 'Note takers' - I will facilitate running a series of plausible security scenarios against curl with the goal of identifying better approaches to secure development, identify how we might respond to emerging security issues as well as have a bit of fun. The session would be between 1-2 hours, interactive and establish ground rules of engagement as well as being mindful that running in a public forum naturally constrains.

Curl container update (James Fuller)

Genetic Algorithm fuzzing with curl part Deux (James Fuller)

The quest for a mascot (Daniel Stenberg)

Evolutions (Stefan Eissing, Saturday?)

A look at some things we worked on during last year

  • Abstractions help: blocking connect code squeeze
  • Controlled connection shutdowns (and why they are good)
  • TLSv1.3 Early Data, SSL session caching and Im-/Export

Time for a Curl Agent? (Stefan Eissing, Sunday?)

I have an idea. It's not really new. But maybe its time has come?

A curl-agent and a curl-add, very similar to what OpenSSH has, that acts as a key=value store. Starting a curl command line would contact the agent over a unix domain socket and lookup variable values there when needed.

A session for some light Sunday morning brainstorming...

See also https://github.com/curl/curl/wiki/curl-tool-master-client

Curl office hours/workshop

It might be nice (maybe at the beginning of first or 2nd day) to have a general 'meetup with curl' open for general public ... its something we can try to attract interested people ... enticements such as stickers and tshirts might go down well, we might even consider this for a general event at the pub. The idea being that we would have small workshop for people to ask questions, give feedback and engage.

Security data and tooling and curl C (James Fuller, Sunday ?)

A short presentation on how curl interoperates with common security data formats and tooling - does it matter for an open source project like Curl ?

curlx_ as an internal library (team)

The curlx_ "system" could be turned into a proper internal (static) library that can be used by libcurl, curl and test servers. Could reduce build times and simplify things?

HTTP news and how to curl them

  • cookie update
  • QUERY method
  • resumable uploads
  • ...

Issue/PR Triage

We can spend some time going through Issue / PR.

Discussion on using perltidy/perlcritic

Which formatting options, if we should do this at all ?

Discussion on load, scale & benchmark tests

Lets have a discussion about the many kinds of performance testsuites that we might consider for curl/libcurl

wcurl, one year later (Samuel Henrique "samueloph") - Remote presentation

If live, has to be on the 3rd between and 12:00 and 15:00 (CET) - Best between 13:30 and 14:30. This session doesn't need the full hour, 30m would be fine.

curl testing statistics (Dan Fandrich)

What can we glean from the curl regression test data analyzed by Test Clutch?

Video recording

We intend to record all presentations on video and make them available after the event.

If the infrastructure permits, we will try to live-stream them as well.