You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description = "Propose a talk for DevOpsDays Geneva 2025"
5
+
+++
6
+
<styletype="text/css">
7
+
div.sponsor-rowimg.img-fluid{
8
+
max-height: 70px;
9
+
}
10
+
a.jssocials-share-link, a.event-cta-button {
11
+
background-color: #8e44b3;
12
+
}
13
+
</style>
14
+
<br>
15
+
<br>
16
+
17
+
DevOpsDays Geneva 2025 call for papers is open for the 6th edition!
18
+
19
+
We are pleased to announce the opening of the CFP submission for the DevOpsDays 2025 conference.
20
+
21
+
{{< cfp_dates >}}
22
+
<br>
23
+
24
+
We cordially remind you that CFP's should not have any commercial aspect.
25
+
26
+
27
+
As actors of the IT evolution you are part of the central pillar of the organisation of our society. This year we would like to highlight talks that make the link between tech and the colossal societal impact: human, ecological, financial and technological.
28
+
29
+
We welcome your experiences and feedback particularly on GreenOps optimisation ideas, impact, ways to monitor advances and synergy of actions.
30
+
31
+
32
+
<strong>We’re looking for quality over quantity!</strong>
33
+
34
+
We are open to all talks but having a societal dimension will be a plus.
35
+
36
+
We will review CFPs as they come in, but please do not expect a reply before the closing date.
37
+
38
+
We strive to create a program that balances the cultural and technical aspects of DevOps.
39
+
40
+
We will not reject submissions solely based on the fact they come from a vendor, but we will not accept vendor pitches.
41
+
42
+
While you can submit more than one proposal, please limit yourself. We want to hear the talk you are most passionate about.
43
+
44
+
<strong>So when ready fill the CFP <ahref='https://i14b.com/u/dodge25cfp'target='_blank'>Here</a></strong>
45
+
46
+
<br>
47
+
For any questions do not hesitate to contact us {{< email_organizers subject="Talk proposal - DevOpsDays Geneva 2025 - Questions">}}
Copy file name to clipboardExpand all lines: content/page/organizing.md
+57Lines changed: 57 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -98,6 +98,8 @@ The code of conduct must include the following:
98
98
- Why: Marketing is tricky, especially as a new event in a world where social media is quickly changing. Be sure to check out the [Visibility](#visibility) section for some tips and tricks.
99
99
***T-6.5 Months to Event:** Ensure registration opens
100
100
- Why: The more time the registration is open, the more potential visibility it gets. Be sure to checkout the [Setting Up Registration](#setting-up-registration) section for more information.
101
+
***T-5 months before Event:** Contribute "sustainability donation"
102
+
- Why: Once you have started selling tickets, you should have the liquidity to make this donation, to [help devopsdays itself continue to operate](#sustainability-donation).
101
103
***T-4.5 months before Event:** Initiate voting of submissions with the organizers
102
104
- Why: Certain speakers submit to multiple events, require notice to their employers and/or require (international) travel. Getting voting done, on time, and in advance, allows those individuals to arrange the needful. Visit [Setting Your Program](#setting-your-program) for more information.
103
105
***T-3.5 months before Event:** Launch the program
@@ -118,6 +120,7 @@ Part of organizing the event is handling of the local event's money. This will b
118
120
-**Sponsorship**: Invoicing sponsors and processing their payments.
119
121
-**Registrations**: Collecting payments from attendees and, if required, issuing official invoices.
120
122
-**Expenses**: Paying for services such as venue booking, catering, merchandise, and more.
123
+
-**Sustainability Donation**: The donation back to devopsdays to help pay for community infrastructure, and more.
121
124
122
125
You cannot announce a date until you know you have a way to handle money. Realizing too late that you cannot process money has led to rescheduled or canceled events in the past.
123
126
@@ -180,6 +183,7 @@ Categories to consider:
180
183
-**Signage**: Directional and informational signs for the event.
181
184
-**Speaker Expenses**: Hosting a speakers' dinner and small appreciation gifts.
182
185
-**Administrative Costs**: Insurance, taxes, and payment for accounting services.
186
+
-**Sustainability Donation**: Cost of a full price ticket.
183
187
184
188
**Important Reminder:** As you've seen in the [rules](#essential-rules-for-organizing) above, these events are not intended for individual or corporate profit. This includes unnecessary high personal expenditures for the benefit of organizers. We can't give precise numbers as to what qualifies as large amounts, since that would vary widely. Consider typical appropriate pricing for your region, and determine if you would find it to be unusually expensive.
185
189
@@ -207,6 +211,59 @@ First, a recommendation: Have a tiered budget for a Good, Better, Best. A Good v
207
211
208
212
However you set up that tiered system for your event, have some go/no-go dates in mind for deciding when you can do each one. A Good vs Better event call might come in the month leading up to your event when you evaluate how much sponsorship money you have gotten in. This is why we say 80%+ of your event budget should come from sponsorship funds! If you set yourself up this way, you know you can put on a good event for the community regardless of how many people actually come, avoiding the need to cancel. Some cities might not have the luxury of having a Good version that is doable because all of the event venues are huge and require food and beverage contracts, for example, but if you can do it, do so.
209
213
214
+
### Sustainability Donation
215
+
216
+
🆕 New in 2025
217
+
218
+
The management and operations of the DevOpsDays infrastructure has always been, and will continue to be, run on a volunteer basis. The services that provide this infrastructure, however, are not free. While we have benefitted from punctual donations and free tiers of services over the years, the reality is that this model is not sustainable. In order to promote a sustainable funding model, and to ensure the continuity of the DevOpsDays global community, as of 1 January 2025, we are introducing a modest event fee: each time you run an event (generally once per year), you donate the equivalent of at least **one full price attendee ticket to your event** to the global DevOpsDays organisation (though you may choose to donate more, if you want).
219
+
220
+
We expect that this donation will be made **on or around when you announce your ticket prices, as then you will know the amount**. This may also be around when your tickets go on sale, and you start receiving funds that can then be paid out to vendors, etc.
221
+
222
+
This will help us pay for the following:
223
+
* Cloud hosting for our conference services, including the content and ticketing management platforms, as well as the password manager
224
+
* Cloud hosting for our Mastodon instance, social.devopsdays.org
225
+
* Domain name registration for devopsdays.org
226
+
* Google Workspace for devopsdays.org for the event mailing lists and backend management
227
+
228
+
We will continue to provide all of these tools and services to the entire DevOpsDays community. By accepting donations in this fashion, we can ensure a healthy future for events around the world, regardless of their location or situation.
229
+
230
+
Currently, we have the means and logistics in place to handle financial transactions in USD in the United States of America via ConferenceOps, and in official European currencies within the European Union via the Stichting DevOps Foundation. For this reason, we will be asking DevOpsDays events in those regions to participate in this sustainability programme from 1 January 2025. Events in other regions will be onboarded as we build out our capacity to manage them.
* Stichting DevOps Foundation [banking details](https://devops.foundation/)
234
+
235
+
236
+
### Sustainability Donation FAQs
237
+
238
+
Q: Our location doesn’t use USD or a European currency—what do we do?<br>
239
+
A: For now, nothing. We’ll contact events individually as we build out our capacity to accept worldwide currencies.
240
+
241
+
Q: Our event doesn’t charge for tickets—how much should we contribute?<br>
242
+
A: If the full ticket price is zero, then your donation is technically also zero; you may donate another amount if you want to.
243
+
244
+
Q: Our event is co-located and we don’t sell tickets directly—does this apply to us?<br>
245
+
A: If your event is ticketed, and the ticket costs money, then yes, this new policy does apply to you.
246
+
247
+
Q: What happens if we can’t afford to contribute the event fee?<br>
248
+
A: Then the cost of your event is prohibitively expensive for attendees too, and should be lowered to a reasonable amount.
249
+
250
+
Q: What if we don't use the conference services?<br>
251
+
A: At a minimum, your event uses the mailing lists, web hosting, and DNS by default.
252
+
253
+
Q: What if we don't work with ConferenceOps or Stichting DevOps Foundation?<br>
254
+
A: That’s fine—beyond this one instance, you don’t need to have any other interaction with either of these entities.
255
+
256
+
Q: Concretely, when should the event fee be contributed?<br>
257
+
A: At any point between the day when tickets become available and the first day of your event.
258
+
259
+
Q: What happens if we cancel our event but we’ve already sent the contribution?<br>
260
+
A: The contribution will be put towards your next event. Under exceptional circumstances, and on a case-by-case basis, we can arrange for the contribution to be refunded.
0 commit comments