Skip to content

Commit cf6b7b0

Browse files
committed
Update devroom name & description for 2024
in 2024 FOSDEM staff has decided to merge the CI/CD devroom into Testing and Automation which warrants some name & devroom managers updates. I am also updating the Archive section with links to archives from previous years that I could find.
1 parent 1a64314 commit cf6b7b0

File tree

2 files changed

+62
-31
lines changed

2 files changed

+62
-31
lines changed

README.md

Lines changed: 10 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,14 @@
1-
Testing and Automation devroom is coming again to
1+
Testing and Continuous Delivery devroom is coming again to
22
[FOSDEM](https://fosdem.org/). This room is about building better
3-
software through a focus on testing and automation at all layers of
4-
the stack. From creating libraries and end-user applications all the
5-
way down to packaging, distribution and deployment. Testing and
6-
automation is not isolated to a single toolchain, language or
7-
platform, there is much to learn and share regardless of background!
3+
software through a focus on testing and continuous delivery practices
4+
across all layers of the stack. The purpose of this devroom is to
5+
share good and bad examples around the question
6+
“how to improve quality of our software by automating tests, deliveries or deployments”
7+
and to showcase new open source tools and practices.
8+
9+
**Note:** for FOSDEM 2024 this devroom is a merger between the former
10+
*Testing and Automation* and *Continuous Integration and Continuous Deployment*
11+
devrooms and is jointly co-organized between devroom managers in previous FOSDEM editions!
812

913
For more information, please see
1014
https://fosdem-testingautomation.github.io

index.html

Lines changed: 52 additions & 25 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@
88

99
<link rel="stylesheet" type="text/css" media="screen" href="stylesheets/stylesheet.css">
1010

11-
<title>FOSDEM Testing and Automation Developer Room</title>
11+
<title>FOSDEM 2024 Testing and Continuous Delivery Developer Room</title>
1212
</head>
1313

1414
<body>
@@ -18,7 +18,7 @@
1818
<header class="inner">
1919
<a id="forkme_banner" href="https://github.com/fosdem-testingautomation">View on GitHub</a>
2020

21-
<h1 id="project_title">FOSDEM Testing and Automation Developer Room</h1>
21+
<h1 id="project_title">FOSDEM 2024 Testing and Continuous Delivery Developer Room</h1>
2222
<h2 id="project_tagline"></h2>
2323

2424
</header>
@@ -30,32 +30,45 @@ <h2 id="project_tagline"></h2>
3030
<h1>
3131
<a name="why" class="anchor" href="#why"><span class="octicon octicon-link"></span></a>Why</h1>
3232

33-
<p>Testing and Automation devroom is coming again to
33+
<p>Testing and Continuous Delivery devroom is coming again to
3434
<a href="https://fosdem.org/">FOSDEM</a>. This room is about building better
35-
software through a focus on testing and automation at all layers of
36-
the stack. From creating libraries and end-user applications all the
37-
way down to packaging, distribution and deployment. Testing and
38-
automation is not isolated to a single toolchain, language or
39-
platform, there is much to learn and share regardless of background!</p>
35+
software through a focus on testing and continuous delivery practices
36+
across all layers of the stack. The purpose of this devroom is to
37+
share good and bad examples around the question
38+
“how to improve quality of our software by automating tests, deliveries or deployments”
39+
and to showcase new open source tools and practices.
40+
41+
<strong>Note:</strong> for FOSDEM 2024 this devroom is a merger between the former
42+
<em>Testing and Automation</em> and <em>Continuous Integration and Continuous Deployment</em>
43+
devrooms and is jointly co-organized between devroom managers in previous FOSDEM editions!
44+
</p>
4045

4146
<h1>
4247
<a name="what" class="anchor" href="#what"><span class="octicon octicon-link"></span></a>What</h1>
4348

44-
<p>Since Testing and Automation devroom has been a regular at FOSDEM, here are some
49+
<p>Since this devroom has been a regular at FOSDEM, here are some
4550
ideas of what we would like to see, and what worked in prior years, they&#39;re just
4651
ideas though. Check out the <a href="#archive">Archive</a> for inspiration.
4752
</p>
4853
<h3 id="testing-in-the-real-open-source-world">Testing in the real, open source world</h3>
4954
<ul>
55+
5056
<li>War stories/strategies for testing large scale or complex projects</li>
51-
<li>Demistyfy resource e.g. systems/device/cloud provisioning in a CI loop</li>
5257
<li>Tools that extend the ability to test low-level code, e.g. bootloaders, init systems, etc.</li>
5358
<li>Projects that are introducing new/interesting ways of testing &quot;systems&quot;</li>
5459
<li>Address the automated testing frameworks fragmentation</li>
55-
<li>Lessons learned from testing</li>
60+
<li>Stories from end-users (e.g. success/failure)</li>
61+
<li>Continuous Integration</li>
62+
<li>Continuous Delivery</li>
63+
<li>Continuous Deployment</li>
64+
<li>Security in Software Supply Chain</li>
65+
<li>Pipeline standardization</li>
66+
<li>Interoperability in CI/CD</li>
67+
<li>Lessons learned</li>
5668
</ul>
5769
<h3 id="cool-tools-good-candidates-for-lightning-talks-">Cool Tools (good candidates for lightning talks)</h3>
5870
<ul>
71+
<li>Project showcases, modern tooling</li>
5972
<li>How your open source tool made developing quality software better</li>
6073
<li>What tools do you use to setup your CI/CD</li>
6174
<li>Combining projects/plugins/tools to build amazing things &quot;Not enough
@@ -115,27 +128,41 @@ <h1>
115128

116129

117130
<ul>
118-
<li><a href="https://github.com/atodorov">A. Todorov</a> - Kiwi TCMS, QA &amp; project lead</li>
119-
<li><a href="https://www.linkedin.com/in/zaklina-stojnev/">Z. Stojnev</a> - Kiwi TCMS, Test Engineer</li>
120-
<li><a href="https://github.com/roxell">A. Roxell</a> - Linaro, QA and Kernel Engineer</li>
121-
<li><a href="https://github.com/metan-ucw">C. Hrubis</a> - SUSE</li>
131+
<li><a href="https://github.com/atodorov">Alex Todorov</a> - Kiwi TCMS, QA &amp; project lead</li>
132+
<li><a href="https://github.com/roxell">Anders Roxell</a> - Linaro, QA and Kernel Engineer</li>
133+
<li><a href="https://github.com/metan-ucw">Cyril Hrubis</a> - SUSE</li>
134+
<li><a href="#">Fabrizio Manfredi</a> - </li>
135+
<li><a href="#">Jan Willies</a> - </li>
136+
<li><a href="https://github.com/olblak">Olivier Vernin</a> - SUSE</li>
122137
</ul>
123138

124139

125140
<h1><a name="archive" class="anchor" href="#archive"><span class="octicon octicon-link"></span></a>Archive</h1>
126141

127142
<ul>
128143
<li><a href="https://fosdem.org/2024/schedule/track/testing-and-automation-devroom/">2024</a></li>
129-
<li><a href="https://archive.fosdem.org/2023/schedule/track/testing_and_automation/">2023</a></li>
130-
<li><a href="https://archive.fosdem.org/2022/schedule/track/testing_and_automation/">2022</a></li>
131-
<li><a href="https://archive.fosdem.org/2021/schedule/track/testing_and_automation/">2021</a></li>
132-
<li><a href="https://archive.fosdem.org/2020/schedule/track/testing_and_automation/">2020</a></li>
133-
<li><a href="https://archive.fosdem.org/2018/schedule/track/testing_and_automation/">2018</a></li>
134-
<li><a href="https://archive.fosdem.org/2017/schedule/track/testing_and_automation/">2017</a></li>
135-
<li><a href="https://archive.fosdem.org/2016/schedule/track/testing_and_automation/">2016</a></li>
136-
<li><a href="https://archive.fosdem.org/2015/schedule/track/testing_and_automation/">2015</a></li>
137-
<li><a href="https://archive.fosdem.org/2014/schedule/track/testing_and_automation/">2014</a></li>
138-
<li><a href="https://archive.fosdem.org/2013/schedule/track/testing_and_automation/">2013</a></li>
144+
<li>
145+
<a href="https://archive.fosdem.org/2023/schedule/track/testing_and_automation/">Testing and Automation 2023</a>
146+
<a href="https://archive.fosdem.org/2023/schedule/track/continuous_integration_and_continuous_deployment/">Continuous Integration and Continuous Deployment 2023</a>
147+
</li>
148+
<li>
149+
<a href="https://archive.fosdem.org/2022/schedule/track/testing_and_automation/">Testing and Automation 2022</a>
150+
<a href="https://archive.fosdem.org/2022/schedule/track/continuous_integration_and_continuous_deployment/">Continuous Integration and Continuous Deployment 2022</a>
151+
</li>
152+
<li>
153+
<a href="https://archive.fosdem.org/2021/schedule/track/testing_and_automation/">Testing and Automation 2021</a>
154+
<a href="https://archive.fosdem.org/2021/schedule/track/continuous_integration_and_continuous_deployment/">Continuous Integration and Continuous Deployment 2021</a>
155+
</li>
156+
<li>
157+
<a href="https://archive.fosdem.org/2020/schedule/track/testing_and_automation/">Testing and Automation 2020</a>
158+
<a href="https://archive.fosdem.org/2020/schedule/track/continuous_integration_and_continuous_deployment/">Continuous Integration and Continuous Deployment 2020</a>
159+
</li>
160+
<li><a href="https://archive.fosdem.org/2018/schedule/track/testing_and_automation/">Testing and Automation 2018</a></li>
161+
<li><a href="https://archive.fosdem.org/2017/schedule/track/testing_and_automation/">Testing and Automation 2017</a></li>
162+
<li><a href="https://archive.fosdem.org/2016/schedule/track/testing_and_automation/">Testing and Automation 2016</a></li>
163+
<li><a href="https://archive.fosdem.org/2015/schedule/track/testing_and_automation/">Testing and Automation 2015</a></li>
164+
<li><a href="https://archive.fosdem.org/2014/schedule/track/testing_and_automation/">Testing and Automation 2014</a></li>
165+
<li><a href="https://archive.fosdem.org/2013/schedule/track/testing_and_automation/">Testing and Automation 2013</a></li>
139166
</ul>
140167

141168
</section>

0 commit comments

Comments
 (0)