Wiki source code of Carrez2021
Version 2.1 by Deb Nicholson on 2021/02/17 20:02
Show last authors
author | version | line-number | content |
---|---|---|---|
1 | Hi! I'm Thierry Carrez. I'm running for election for an affiliate member | ||
2 | seat on OSI board of directors, on behalf of the Open Infrastructure | ||
3 | Foundation (formerly known as the OpenStack Foundation). Continue | ||
4 | reading to learn more about me and why I'm running! | ||
5 | \\Bio | ||
6 | ~-~-- | ||
7 | \\I'm 48, based in France, working from home on open source software in a | ||
8 | small village since 2008. A Mechanical Systems engineer by trade, I'm | ||
9 | currently the VP of Engineering at the Open Infrastructure | ||
10 | Foundation[0], in charge of the health of the open source projects we | ||
11 | support. Prior to that, I've been a contractor helping with OpenStack | ||
12 | Release Management (2010-2013), a Technical Lead for Ubuntu Server at | ||
13 | Canonical (2008-2010), and an IT Manager at various companies before that. | ||
14 | \\[0] [[https:~~/~~/openinfra.dev>>url:https://openinfra.dev]] | ||
15 | \\My relationship with F/OSS | ||
16 | ~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~- | ||
17 | \\I've been using free and open source software in one form or another, | ||
18 | personally and professionally, since 1995. I started with Red Hat Linux, | ||
19 | then moved to Gentoo Linux in 1998. Noticing a gap in vulnerability | ||
20 | management, I proposed to help and started actively contributing to | ||
21 | Gentoo Linux in 2002, becoming the Security team manager, driving the | ||
22 | reform[1] toward an open governance, and finally getting elected to the | ||
23 | Gentoo Council in 2005. | ||
24 | \\[1] | ||
25 | [[https:~~/~~/mgorny.pl/articles/the-story-of-gentoo-management.html#gentoo-council>>url:https://mgorny.pl/articles/the-story-of-gentoo-management.html#gentoo-council]] | ||
26 | \\I got hired by Canonical in 2008 to work from home as a technical lead | ||
27 | on Ubuntu Server. In 2010 I followed a couple of ex-Canonical folks to | ||
28 | work on a nascent open source alternative to the big proprietary clouds, | ||
29 | called OpenStack. This project was formed on strong principles of open | ||
30 | collaboration: open source of course, but also open development | ||
31 | (accessibility to all), open design (design done in the open), and open | ||
32 | community (any contributor can get elected to governing bodies). When | ||
33 | the OpenStack Foundation was formed in 2013, I was part of the initial | ||
34 | staff there, and still am to this day. | ||
35 | \\Early 2019, the OSI's legitimacy came under attack as pseudo-open | ||
36 | licenses were developed to preserve specific business models. This | ||
37 | prompted the OSI to put out a strong Affirmation of the Open Source | ||
38 | Definition[2], which the OpenStack Foundation joined and signed. To | ||
39 | further support the legitimacy of the OSI[3], the OpenStack Foundation | ||
40 | formally became an Affiliate organization of the OSI in 2019. | ||
41 | \\[2] [[https:~~/~~/opensource.org/OSD_Affirmation>>url:https://opensource.org/OSD_Affirmation]] | ||
42 | [3] [[https:~~/~~/opensource.org/node/1003>>url:https://opensource.org/node/1003]] | ||
43 | \\Why I'm running | ||
44 | ~-~-~-~-~-~-~-~-~-~-~-~-~-~-- | ||
45 | \\Open source in 2021 is at a crossroads. Its benefits for users and the | ||
46 | strength of its collaboration model has made it very popular and | ||
47 | successful against its proprietary alternatives. However, as we were | ||
48 | "winning", the landscape evolved. Software companies trying to | ||
49 | capitalize on the "open source" brand have created development models | ||
50 | and played licensing tricks that make them much closer to proprietary | ||
51 | software than to openly-developed open source software. Worse, they | ||
52 | actively dilute the meaning of "open" and "open source" by trying to | ||
53 | associate their software with it, and attacking the legitimacy of the | ||
54 | Open Source Definition and the OSI as its guardian. |