Skip to content

Commit 34a7ec9

Browse files
Merge branch 'ep2025' into ep2025-overview
2 parents 54a4e0b + 82616b7 commit 34a7ec9

File tree

12 files changed

+412
-2
lines changed

12 files changed

+412
-2
lines changed

Dockerfile

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,7 @@
11
FROM node:20-slim
22

3+
RUN apt-get update && apt-get install -y make
4+
35
ENV PNPM_HOME="/pnpm"
46
ENV PATH="$PNPM_HOME:$PATH"
57

@@ -9,7 +11,7 @@ RUN pnpm config set store-dir /home/node/.local/share/pnpm/store
911

1012
WORKDIR /app
1113

12-
COPY package.json pnpm-lock.yaml ./
13-
RUN pnpm install
14+
COPY Makefile package.json pnpm-lock.yaml ./
15+
RUN make install
1416

1517
RUN mkdir -p /app/src
Lines changed: 67 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,67 @@
1+
---
2+
title: Beginners' Day Unconference
3+
url: /beginners-day-unconference
4+
subtitle:
5+
The Unconference is a part of this year's Beginners' Day.
6+
---
7+
# EuroPython & junior.guru Beginners' Day Unconference
8+
9+
As part of this year's Beginners' Day, on **Saturday 19th July** we'll be hosting the Unconference in cooperation with [junior.guru](https://junior.guru/). It's a full day of panel discussions, Q&A sessions, interactive sessions, and short talks focused on getting started and growing as a junior in a tech role.
10+
11+
<a href="https://junior.guru" class="block w-[350px] m-auto hover:scale-105 transition-transform " target="_blank">
12+
![junior.guru Logo](./images/junior-guru.png)
13+
</a>
14+
15+
## Program
16+
17+
### Panel discussion: How to Succeed In A Junior Role
18+
19+
Listen to a panel discussion with three junior developers as they share what life is really like after landing their first tech job. They’ll talk about working with colleagues, asking for help effectively, getting useful feedback, avoiding common pitfalls, overcoming early challenges, and the surprises they encountered along the way.
20+
21+
### Workshop: How To Succeed As A Junior
22+
23+
This interactive workshop puts you right in the center of the conversation. You’ll join a small group of fellow junior developers, each guided by an experienced mentor. Together, you’ll tackle real-world questions like: How do you identify transferable skills during a career change? What’s the best way to highlight your strengths in an interview? How do you stay motivated when the job gets tough?
24+
25+
Each group will explore these topics through open discussion, drawing on personal experiences and shared insights. At the end, we’ll come back together so each group can share one or two of their best takeaways with everyone. Bring your curiosity, your questions, and your voice—this is a session built for learning from each other.
26+
27+
![A group of people working and collaborating on computers during a workshop](./images/sprints1.jpg)
28+
29+
### Panel discussion: Landing A Great Job
30+
31+
What makes a candidate stand out? How do hiring managers really make decisions? In this panel, experienced recruiters and engineering leaders share what they’ve learned from hiring hundreds of people into tech roles. You’ll hear insider tips on what makes an application shine, how to navigate interviews, and what signals success once you're on the job.
32+
33+
Whether you're switching careers or just starting out, this is your chance to learn what the other side of the hiring table is really thinking—and how you can use that knowledge to land a role you’ll love.
34+
35+
### Discussion Circle: Junior vs. Senior
36+
37+
Join us for an engaging discussion where empathy takes center stage! What aspects of job interviews make no sense to juniors? Why do some leave for better opportunities after just a year? Why do beginners hesitate to ask for help when they get stuck?
38+
39+
On the other hand, what do seniors expect from juniors? What is it like to mentor less experienced colleagues, and how can it be done effectively? How can juniors ask questions without interrupting or slowing down their mentors? And how does one even become a senior in the first place? How did experienced developers learn throughout their careers, and how did they negotiate for better salaries?
40+
41+
Come share your perspective and help us explore those questions together!
42+
43+
![A group of people looking at a projector screen in a classroo](./images/sprints2.jpg)
44+
45+
### Q&A session: From Junior To Senior
46+
47+
You’ve landed your first job—now what? In this open Q&A session, we’ll explore the path from junior to senior developer, a journey that’s often less talked about but just as important. Bring your questions and hear honest, practical answers from experienced guests who’ve made the leap themselves or helped others do it.
48+
49+
We’ll cover topics like growing your skills, earning trust, taking on more responsibility, and navigating the messy middle of a tech career. Whether you’re curious about what “senior” really means or just want to know what to focus on next, this is your chance to ask.
50+
51+
### Lightning talks: My Journey To IT
52+
53+
Did you take an unexpected path into your first tech job? Faced challenges you didn’t anticipate? Got a piece of advice that made all the difference? Come share your story!
54+
55+
At the end of the day, we’re opening the stage for juniors to give short lightning talks about how they landed their first job in IT—what worked, what was hard, and what they learned along the way. This is a great opportunity to inspire others and reflect on your own journey.
56+
57+
Want to participate? Just add your name and topic to the sign-up flipchart at the venue during the day. Talks can go up to 10 minutes, but 5 minutes is perfect—let’s keep it snappy! No slides required—just your story and insights, but feel free to bring them if you’d like.
58+
59+
Whether you want to speak or just listen, this is a fantastic chance to learn, get inspired, and support fellow newcomers in the tech world!
60+
61+
## Sign up
62+
63+
EuroPython Beginners' Day Unconference is open to everyone, from high school students to late career changers. Entry is free for EuroPython ticket holders (any ticket type), and €5 otherwise.
64+
65+
<Button url="https://ep2025.europython.eu/beginners-day/#how-do-i-sign-up">Sign Up For The Unconference!</Button>
66+
67+
Applications are open until we run out of tickets. There are 48 spots available.

src/content/pages/guidelines.mdx

Lines changed: 229 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,229 @@
1+
---
2+
title: Speaker Guidelines
3+
subtitle: Are you presenting a session at EuroPython this year? We can’t wait to see it!
4+
---
5+
6+
# Speaker Guidelines
7+
8+
> Are you presenting a session at EuroPython this year? We can’t wait to see it!
9+
10+
Below we have a number of suggestions to help make your session a success. Of course, these are just
11+
guidelines - the most important thing is that your session reflects the story you want to tell in
12+
the most authentic way possible!
13+
14+
If you have any further questions, please feel free to reach out to [email protected].
15+
16+
## Making great slides
17+
18+
Remember that slides are there to back up the story you want to tell the audience, not to be the
19+
star of the show (that’s you!). As such, try to think about how you can keep the attention of your
20+
audience on what you’re saying, not what is on your slides. Some guidelines that can help with this
21+
are:
22+
23+
* Try to minimise the amount of text on your slide. Audiences will automatically start reading any
24+
text on a slide, and not listen to you while they’re doing so.
25+
* Use simple animations to display parts of the slide at a time, so that it is clear to the audience
26+
what you want them to pay attention to.
27+
* Try to “show, not tell” by using images or simple diagrams instead of text.
28+
* Don’t put anything on your slides that you don’t intend to explain.
29+
* Try not to cram too much on one slide. There are no hard and fast rules about how many slides to
30+
have in a talk, as long as the slides naturally flow with your spoken narrative and don’t overwhelm
31+
your audience with information.
32+
33+
This [wonderful blog
34+
post](https://distinct-browser-08c.notion.site/purplecon-tips-for-writing-a-good-conference-talk-cab51d9bfd474e26ae4b021a7a12f38b)
35+
goes into a lot more detail about how to really polish your slides.
36+
37+
If you’re in any room except for Forum Hall (the main room), please try not to present any important
38+
information in the lower third of the slides. Due to how the rooms are set up, this section may not
39+
be visible to people at the back of the room.
40+
41+
## Making sure everyone can hear you
42+
43+
We will be using the microphones in the podiums for talks and tutorials. For optimal audio quality
44+
and recording, adjust the microphone's height and angle to aim directly at your head (not your
45+
chest), especially if the previous speaker was significantly taller or shorter.
46+
47+
Maintain a consistent distance of 15-30 cm from the mic; this captures your voice clearly whilst
48+
minimising distracting plosives or breathing sounds. Crucially, stay in front of the microphone and
49+
near the podium throughout your talk, as moving away will mean the audience (and livestream) might
50+
not hear you properly.
51+
52+
If a question is asked from the audience without a microphone, please repeat it clearly into your
53+
microphone before answering. This ensures everyone in the room, as well as those on the livestream,
54+
can understand the context of your answer.
55+
56+
## Presenting code effectively
57+
58+
Please make sure that the code in your editor or IDE is big enough for the audience to read, and to
59+
be readable on the livestream and video recording. Use a font of at least **size 24**, or a zoom of
60+
at least **175%**. Please also use a light theme.
61+
62+
As with the slides, please do not show any code you’re explaining on the lower third of the screen
63+
(unless you are presenting in Forum Hall), as people sitting at the back of the room may not be able
64+
to see it.
65+
66+
Remember that this will be your audience’s first time seeing the code you’re sharing. Try not to
67+
show too much code at a time, and go through it bit-by-bit to make sure your audience is following
68+
what you’re trying to convey.
69+
70+
If you’re planning on doing live coding, we advise recording a video as a plan B. Nerves can get the
71+
best of all of us, and in the case you mistype your code may not work. We also advise having a local
72+
backup of anything you need rather than relying on the internet: while we do have dedicated ethernet
73+
cables on the podiums, Murphy has a special nose for materials needed during live sessions.
74+
75+
## Making your session accessible for everyone
76+
77+
We want everyone to feel welcome and comfortable at EuroPython. As such, it’s important that your
78+
session is accessible for all of your audience members.
79+
80+
In order to make accessible slides, you can check the following guidelines. In general, please
81+
consider the following:
82+
83+
* Use a simple, sans serif font with enough spacing between letters, with at least an 18-point font
84+
size. Examples include Calibri, Franklin Gothic Book, Lucida Sans and Segoe UI.
85+
* Use enough spacing between lines of text, and limit the amount of text per slide.
86+
* Use high-contrast colours, but please avoid red-green combinations. Try to use an off-white or
87+
cream background instead of bright white. This tool can help to select accessible colour
88+
combinations.
89+
* Avoid using images with text that might be hard to read.
90+
91+
Some people may be sensitive to loud noises, flashing lights or strobing effects. If you plan to use
92+
any of these, please give a warning beforehand.
93+
94+
Remember that many people in the audience are not native English speakers. Please try not to speak
95+
very quickly and speak as clearly as you can, in order to give everyone a chance to follow you.
96+
97+
## Managing your time
98+
99+
Talks include a 5 minute Q&A, meaning you will have 25 or 40 minutes to deliver your content. You
100+
may opt out of questions and use this entire time for your talk, but please let your session chair
101+
know that you want to do this before you start. You will be given a hard stop at the end of your
102+
session time in order to allow people to change rooms.
103+
104+
There is at least 10 minutes between each talk. Please arrive at the beginning of this 10 minute
105+
slot to set up for your talk and to make sure you have plenty of time to iron out any technical
106+
issues.
107+
108+
For tutorials, please arrive at least 20 minutes beforehand to make sure you have everything set up.
109+
Note that all tutorials include a 15 minute coffee break (check [the
110+
schedule](https://ep2025.europython.eu/schedule/tutorials/) for more details), so please plan
111+
accordingly.
112+
113+
## Setting up on the day
114+
115+
We do not provide computers for the presentation, so please bring your own device.
116+
117+
Each room will have the following connectors at the podium:
118+
119+
* A HDMI cable to connect to the projector. We will do our best to have USB-C to HDMI adapters for
120+
all of them, but we strongly encourage you to bring your own if you need one.
121+
* A wired ethernet cable. Please bring your own USB-C to RJ45 Ethernet adapter if your laptop
122+
requires one. You can of course use the Conference Wifi that all attendees use as well.
123+
* A power outlet to connect your charger with a [Type E plug](https://en.wikipedia.org/wiki/Schuko).
124+
Please note that Macbooks can enter power saving mode if they are not plugged in, even with a full
125+
|battery, leading to them having issues sending signals to the projector. As such, it’s safest to
126+
have your Macbook charger handy.
127+
128+
For all rooms except the Forum Hall, technicians usually arrive around an hour before the first
129+
sessions start. Please feel free to come by your room to test your setup. In the case that no one is
130+
there, they are likely to have just popped out, so don’t despair! Come back until you catch them.
131+
132+
**Meeting Room 241** will be available as a Speaker Ready Room. There will be a monitor with an HDMI
133+
cable if you want to check the set up for your presentation.
134+
135+
## Preparing for any technical difficulties
136+
137+
Even the best programmes can fail (we know this better than anyone!), and in a high pressure
138+
situation like a live talk or tutorial, it’s safest to prepare ahead.
139+
140+
We strongly recommend converting your final presentation slides to a universally viewable and
141+
WYSIWYG format such as PDF, and back this up both locally and in a place that can be easily
142+
retrieved from another device. This will not only give you a backup on your own device in case your
143+
presentation software or the connection to the cloud fails, but also allow you to quickly share it
144+
with a friend and use their device in case of complete failure.
145+
146+
In the case your session may require a special technical set up, such as playing audio or video, or
147+
needing extra devices such as a screen reader or an instrument, we ask that you please contact the
148+
Programme Committee ([email protected]) ahead of the conference. We can then set aside a
149+
specific time at the conference for you to test your setup before your session.
150+
151+
## Sharing your content
152+
153+
Please upload your slides directly to Pretalx before your session using the Resources section.
154+
155+
You can also optionally share your slides, and any other resources, during your session using a QR
156+
code.
157+
158+
Sharing your content allows attendees, especially those with vision impairments, to follow your
159+
content on their own devices. It also means they can easily follow up on anything interesting you
160+
shared as part of your talk!
161+
162+
## Knowing how many people to expect in your session
163+
164+
Each of the session rooms has a different capacity. You can find how many people your room will hold
165+
below. Please note that this is the maximum capacity: as there are many sessions running at the same
166+
time, your final number of attendees is likely to be smaller than this.
167+
168+
<div class="md_table">
169+
| Room | Maximum capacity |
170+
|------|------------------|
171+
| **Talks** |
172+
| Forum Hall | 700 |
173+
| North Hall | 210 |
174+
| South Hall 2A | 210 |
175+
| South Hall 2B | 210 |
176+
| Terrace 2A | 160 |
177+
| Terrace 2B | 120 |
178+
| **Tutorials** |
179+
| Club A | 100 |
180+
| Club B | 40 |
181+
| Club C | 40 |
182+
| Club D | 40 |
183+
| Club E | 100 |
184+
| Club H | 100 |
185+
| **Open spaces** |
186+
| South Room 221+222 | 30 |
187+
| South Room 223+224 | 30 |
188+
</div>
189+
190+
## Specific advice for tutorials
191+
192+
Please note that tutorials are intended to be a hands-on experience for the attendees, rather than a
193+
long talk. This means that a substantial component of the workshop should involve exercises that
194+
your participants can complete on their own machines at their own pace. In the case you intend to do
195+
live coding, this should be either done slowly enough that attendees can follow along, or be able to
196+
be replicated in a later exercise.
197+
198+
Please keep in mind that if attendees need to download materials for your tutorial, it is better to
199+
give them a heads up at least a couple of days prior. Bandwidth will be limited, and many public
200+
resources have some kind of rate limiting set up.
201+
202+
If you will need helpers for your session, please add them to your session in Pretalx or contact the
203+
Programme Committee ([email protected]) ahead of the conference, as we’ll need to create
204+
tutorial tickets for them.
205+
206+
To keep a more relaxed learning atmosphere there will be no video recording of your tutorial. Please
207+
note that this also means that participants cannot scroll back if they miss something, so if in
208+
doubt, go slow and be clear.
209+
210+
## Specific advice for posters
211+
212+
Posters need to be printed on size A0 paper with a portrait orientation. Please take care of the
213+
poster printing yourself ahead of the conference. We will provide a freestanding poster board you
214+
can stick your poster to. Please bring something to stick your poster to the board which will not
215+
damage it, such as Blu Tack. (We might have some at reception, but can not guarantee that.)
216+
217+
Poster sessions will take place in the hallway, close to the open space desks.
218+
219+
Please check the schedule for your assigned slot. This is the expected “minimum time” for you to be
220+
with your poster, but you are naturally welcome to stay for longer, or organise specific additional
221+
times for people to come and discuss your poster. As many things are happening at the conference at
222+
the same time, you might get a lower turn out during your actual poster session, but you can drum up
223+
interest in your poster throughout the whole conference - maybe even in a lightning talk!
224+
225+
It can feel a little awkward being in your poster session at first, but try to relax and have fun.
226+
As you see people walking around the session, or even looking at yours, start a conversation in a
227+
non-intrusive way (a friendly “Hey there!” is a great opener!). Ask a few questions about why
228+
they’re at the conference, and gently steer the conversation towards your poster. Before you know it
229+
you’ll be having a blast!
98 KB
Loading
7.99 KB
Loading
106 KB
Loading
163 KB
Loading
Lines changed: 1 addition & 0 deletions
Loading

0 commit comments

Comments
 (0)