Skip to content

Commit 1819cf6

Browse files
DaanHooglandDaan Hoogland
andauthored
Wido as the new VP (#419)
Co-authored-by: Daan Hoogland <dahn@apache.org>
1 parent 4a55dcb commit 1819cf6

File tree

5 files changed

+136
-0
lines changed

5 files changed

+136
-0
lines changed
137 KB
Loading
451 KB
Loading
5.81 MB
Loading
6.75 MB
Loading
Lines changed: 136 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,136 @@
1+
---
2+
layout: post
3+
title: 'Meet the New VP of CloudStack: Wido den Hollander'
4+
tags: [community, news]
5+
authors: [jamie]
6+
slug: new-vp-wido-den-hollander
7+
---
8+
9+
# Meet the New VP of CloudStack: Wido den Hollander
10+
11+
![](Banner.png "Blog Header Image")
12+
13+
## Wido den Hollander Voted as VP of Apache CloudStack
14+
15+
The Apache Software Foundation community has voted [Wido den
16+
Hollander](https://www.linkedin.com/in/widodh/) as the new Vice
17+
President of Apache CloudStack. A long-time PMC member and
18+
contributor, Wido has been working on CloudStack for over 15 years,
19+
bringing deep technical experience and real-world operational insight
20+
from the cloud industry. This blog shares key snippets from Wido’s
21+
first interview since being voted CloudStack VP for 2026.
22+
23+
<!-- truncate -->
24+
25+
## Getting started with CloudStack
26+
27+
![](WidoInPanel.jpg "Wido discussing ACS in a Panel")
28+
29+
Wido’s journey into CloudStack is rooted in practical experience. He
30+
has been active in the hosting industry since 2004, building and
31+
operating infrastructure for over two decades.
32+
33+
“I've been in the hosting and IT industry since 2004, so it's about 23
34+
years now. My background is hosting and I've been a user, a
35+
contributor, and PMC member, and actually a VP member before of the
36+
Apache CloudStack project.”
37+
38+
His introduction to CloudStack came from a need to move beyond custom-built infrastructure:
39+
40+
“I always ran a web hosting company... during that journey we had our
41+
KVM environment built with bash scripts, and we looked for something
42+
else. This is when I stumbled upon what was cloud.com from citrix,
43+
which was about to be donated to the Apache Software Foundation. So,
44+
through that journey we started adopting Apache CloudStack in my
45+
hosting company and we have been using it ever since.”
46+
47+
Wido’s first contribution dates back to 2011, focusing on improving packaging:
48+
49+
“My first contribution to the project was actually an improvement in
50+
the Debian and Ubuntu packaging... I sent my first patches to improve
51+
the packaging for Ubuntu.”
52+
53+
## Perspective on the CloudStack project
54+
55+
![](Panel.jpg "People discussing ACS in a Panel")
56+
57+
Over the years, he has remained deeply involved in both development
58+
and governance. His appointment as VP reflects this long-standing
59+
commitment.
60+
61+
“I would say the VP is somebody who keeps everybody together, talks
62+
with the ASF, is the face of the project for a year.”
63+
64+
A key theme in Wido’s perspective is reliability:
65+
66+
“CloudStack is a reliable foundation to build your company upon. There
67+
have been many great features, bugs have been resolved, enhancements
68+
in CloudStack. But the main thing is it is reliable”.
69+
70+
He also highlights governance as a critical differentiator:
71+
72+
“The governance of the ASF - that's a truly reliable foundation to run
73+
your company upon.”
74+
75+
## Evolution for the technology
76+
77+
Looking ahead, Wido sees CloudStack continuing to evolve:
78+
79+
“I think it's going to be evolutions within CloudStack. We are quite
80+
feature-ready If you look at IaaS, there are a few upcoming features I
81+
am looking forward to. For example, the DNS provider where you can
82+
manage DNS from CloudStack. So, you have a single environment where
83+
you can manage VMs, object storage, and then also DNS connected to
84+
different providers. And I would like to personally investigate a
85+
possibility where we can get some telemetry back to the project on an
86+
opt-in basis.”
87+
88+
Importantly, Wido wants to challenge the perception that CloudStack is
89+
only for large-scale deployments:
90+
91+
“CloudStack still seems like this giant monster for some
92+
people. That's a myth I would like to bust, because even with just a
93+
few servers, you could have a great Apache CloudStack deployment.”
94+
95+
He reinforces this with a real-world example of a compact deployment
96+
that still delivers enterprise-grade features.
97+
98+
## Community
99+
100+
Wido is also passionate about community:
101+
102+
“The culture should be that everybody is welcome and we should respect
103+
everybody and be grateful for anything somebody contributes.”
104+
105+
He encourages new contributors to get involved:
106+
107+
“We should be open to anybody submitting a pull request in
108+
GitHub. What I heard from feedback from some developers is that it
109+
sometimes feels very scary to send your first pull request to a GitHub
110+
project which has been around for 15 years and then you come along
111+
from somewhere on this planet and you send your first pull
112+
request. You're like, oh, what's going to happen? Are they going to be
113+
angry with me if I make a mistake? No, everybody should be welcome to
114+
open their first PR.”
115+
116+
![](WidoOnStage.jpg "Wido addressing the community")
117+
118+
## Growth
119+
120+
Despite often operating behind the scenes, CloudStack continues to grow:
121+
122+
“It is still growing, yes. And I think that is a misconception which
123+
sometimes exists because CloudStack just is there as an IaaS, powering
124+
these enormous environments, but also many smaller environments. But
125+
it's taken for granted by so many people. So, it's no longer in the
126+
really big hype cycle. As I said, there's evolutions, no longer
127+
revolutions.”
128+
129+
Wido concludes with a message to the community:
130+
131+
“I want to thank everybody for contributing, for being part of the
132+
project. I would like to encourage everybody to contribute more and
133+
new users to step into the community, be active, stand up, and you are
134+
more than welcome to send in contributions which can be documentation,
135+
pull requests for code. But be at events, be vocal, or just help
136+
somebody on the mailing lists.”

0 commit comments

Comments
 (0)