Add platforms

9 files changed, 1212 insertions, 9 deletions

diff --git a/english/vote/2019/platforms/Makefile b/english/vote/2019/platforms/Makefile
new file mode 100644
index 00000000000..a85135285ee
--- /dev/null
+++ b/english/vote/2019/platforms/Makefile
@@ -0,0 +1,12 @@
+# If this makefile is not generic enough to support a translation,
+# please contact debian-www.
+
+WMLBASE=../../..
+CUR_DIR=vote/2017/platforms
+SUBS=
+
+include $(WMLBASE)/Make.lang
+
+index.$(LANGUAGE).html: index.wml \
+  $(wildcard $(ENGLISHSRCDIR)/$(CUR_DIR)/../../[0-9]*/vote_*.wml) \
+  $(TEMPLDIR)/template.wml $(TEMPLDIR)/votebar.wml
diff --git a/english/vote/2019/platforms/hartmans.wml b/english/vote/2019/platforms/hartmans.wml
new file mode 100644
index 00000000000..8bdfc67823d
--- /dev/null
+++ b/english/vote/2019/platforms/hartmans.wml
@@ -0,0 +1,67 @@
+#use wml::debian::template title="Platform for Sam Hartman" BARETITLE="true" NOHEADER="true"
+#include "$(ENGLISHDIR)/vote/style.inc"
+
+<header>
+<h1 class="title">Sam Hartman DPL 2019 Platform</h1>
+</header>
+<h2 id="biography">Biography</h2>
+<p>I joined Debian back in 2000. Large corporations had a lot of advantages by having enterprise infrastructure that provided centralized authentication, authorization and provisioning. By watching Project Athena at MIT, I was familiar with how valuable this infrastructure could be. I had been working on Kerberos upstream throughout my undergraduate career. I wanted to make sure the same infrastructure was available to the free software community. So, I started packaging Kerberos and related software.</p>
+<p>Back then, cryptographic software was split into the non-us distribution because of US export law. That made my work more difficult. I packaged the software, but also had to work with other maintainers to build support for Kerberos and other infrastructure technology into more and more packages.</p>
+<p>Ben Collins reached out to a group of people to see if we could get cryptographic software into the main archive. My contribution to that effort was on the legal side rather than the technical side. A group of friends and I spent several days going line by line through the US export regulations to prepare a set of questions for lawyers. With Bdale and HP's generous support, the answers to my questions gave us confidence in a legal path forward. Others did the technical work to allow dak to provide the necessary notifications to meet the silly regulations of the day. Eventually, we were able to move cryptographic software into main and retire the non-us distribution.</p>
+<p>I have continued to be involved in Debian since then. Some years I'm doing little more than maintaining packages; other years Debian becomes a key focus. In my work on <a href="http://www.project-moonshot.org/">Project Moonshot</a>, Debian was essential to demonstrating how a new security mechanism could be integrated into an operating system. My work on Kerberos and Project Moonshot was all free software. Sometimes my employers have focused more on proprietary work, although I've always found myself at companies that support involvement in the free software community. Over the years, free software has become more important to me, and I've found that the freeness of a solution matters more to me when I'm looking at how to solve my computing problems.</p>
+<p>I spent a number of years as the Chief Technologist at the MIT Kerberos Consortium. In that role we worked with a number of OS vendors and other stakeholders in Kerberos to balance the needs and evolution of our community. I also served a 3 year term as a Security Area Director of the <a href="https://www.ietf.org/">Internet Engineering Taskforce</a>.</p>
+<p>When I'm not working on Debian or my day job, I'm writing, reading, learning to sail, or living life to its fullest. Over the past year, I've been learning how to DJ. That ended up starting with writing my own DJ software because what's out there is too visual for a blind DJ to easily use. It's not packaged for Debian yet because I need to get one patch upstreamed and write enough documentation that someone else would have a chance to use it.</p>
+<p>Spirituality is very important to me: I spend a lot of time writing and thinking about how we can bring more compassion, connection and love into the world. Debian feels like home because it is such a diverse community and because we view our work as a way to make the world better, not as a vehicle for an ever larger paycheck.</p>
+<h2 id="keeping-debian-fun">Keeping Debian Fun</h2>
+<p>Lucas Nussbaum wrote an excellent <a href="https://lists.debian.org/20190313230516.zbgts5hwrhqzicj4@xanadu.blop.info">summary</a> of the DPL responsibilities. Of these, I think the most important is keeping Debian fun. We want people to enjoy contributing to Debian so that they prioritize it in their busy schedules. We want to make it easy for people to do work: processes and interactions should be streamlined. When people have concerns or things don't work out, we want to listen to them and consider what they want to say. We want Debian to be welcoming of new contributors.</p>
+<p>Debian is not fun when we face grueling, long, heated discussions. It is not fun when we are unable to move a project forward because we cannot figure out how to get our ideas considered or how to contribute effectively. Debian is not fun when processes or tools are cumbersome. When key teams break down or get stuck, Debian is not fun either for the members of those teams or for those who depend on them. <em>Debian is not fun when it isn't safe—when we are not respected, when we are harassed, or when we (rather than our ideas) are judged.</em> I support our Code of Conduct.</p>
+<p>There are several ways I plan to work to keep Debian fun:</p>
+<h3 id="listening-disagreement-without-escalation">Listening: Disagreement without Escalation</h3>
+<p>I had the pleasure to serve on the Debian Technical Committee. In that role the thing I look back to with the most pride is writing an <a href="https://lists.debian.org/debian-ctte/2015/03/msg00084.html">explanation</a> of why the release team might have rejected changes to busybox-static that the maintainer viewed as important. The maintainer didn't understand the release team decision and came to the technical committee asking us to either override the decision or help explain what was going on.</p>
+<p>The feelings matter; having our emotional needs met is a critical part of a community being fun and safe. Back in 2012, I ran across <a href="http://www.cnvc.org/">Nonviolent Communication</a>. NVC is an empathy framework that gave me the tools to work with and understand my emotions and where they came from. It's a framework for talking about things that are important to us and reaching connection, even when we disagree. When I realize that someone has heard what I am saying, my muscles relax and my breathing slows; I feel releaf and sometimes joy, often even if my preferred option is not chosen. <strong>Debian needs more of this.</strong></p>
+<p>My thoughts about taking care of our emotional needs have been evolving for years but are certainly influenced and inspired by Enrico Zini's notes on his <a href="https://www.enricozini.org/blog/2018/debian/multiple-people">Debconf 18 talk</a>.</p>
+<p>Debian is a community. We need to give each other the tools we need to succeed in Debian. Part of treating our community members with respect is listening to them. When you advocate someone, when you fill out an application manager report recommending that someone join our community, and when you agree to be a sponsor, you're saying that someone is valuable enough to our community that we should spend resources helping them succeed. Success in a community is emotional not just technical.</p>
+<p>However, explaining things, especially repeatedly, especially when others are focused more on convincing us they are right than starting by understanding, is draining. One reason I pick the example of busybox-static is that I wrote it, not the release team. They were off working on a Debian release, and I was busy trying to care for a member of our community.</p>
+<p>One of my key roles as DPL will be to make sure Debian is a community where we can be heard, and where we have the opportunity to reach understanding regardless of whether our ideas are chosen. I will do this by personally participating in such mediation and recruiting others to these mediation efforts. Eventually, I hope many of us will get better at seeking to understand and avoiding escalating discussions on our own. Since my <a href="https://lists.debian.org/debian-devel/2014/11/msg00133.html">mail about compassion and init systems</a>, I've been working to find a place to do this work. I talked about it when I <a href="https://lists.debian.org/debian-ctte/2015/03/msg00008.html">joined the TC</a>. The TC <a href="https://lists.debian.org/debian-ctte/2017/11/msg00011.html">ended up not being</a> the right place for that work.</p>
+<p>And yet the work continues to be important. What I wrote about a <a href="https://hartmans.livejournal.com/97174.html">maintainer</a> who gave up their package rather than work with the TC is just one of a long series of escalations. We are aware of people who have left because they have become frustrated. I am not worried about the turnover: Debian continues to be a vibrant community that is fun for a lot of us. If these people were leaving because their needs (or even Debian's focus) had changed, that would be fine. I hope we can do better at avoiding people stepping away from the project bitter and frustrated. I hope we can offer compassion.</p>
+<p>The mediation work is bigger than one person can handle. It's unclear how it should be organized. What is clear is that today, the DPL is at the center of that work. The antiharassment team also has a role. I volunteered to help them out at the beginning of the year and we're working to understand how I could fit into that process independent of the DPL race. Long term, it looks like the antiharassment team, account managers, and hopefully the DPL are planning a sprint. I think working on how to organize this mediation work so that we can succeed and avoid burn-out is an important agenda item.</p>
+<p>As DPL, mediation and bringing compassion to Debian will be one of my key focuses. I have specific ideas on how I'd like to try doing the work, so I will be personally involved. However, building a team so that we can handle more than one DPL's worth of mediation and so that future DPLs can choose their own focus is as important as the individual mediation successes.</p>
+<h3 id="decisions-that-take-forever">Decisions that Take Forever</h3>
+<p>We've lost a number of developers because they were frustrated with our tools and processes. One of the common complaints I've heard is that the wide variety of Debian workflows gets in the way when you want to contribute to a large number of packages. I know that for myself I find that our processes make it difficult enough for me to go fix an RC bug in a package that I don't maintain that I'm less likely to do so.</p>
+<p>More than just the frustration with the tools and processes is the perception that making changes is difficult. We have a lot of discussions about potential improvements, but sometimes it is hard to actually make a decision. As someone recently put it on IRC, it's hard to move forward when one person's frustration is another person's desired property of the system.</p>
+<p>I don't think the DPL can or should decide these issues. However, as DPL I would have a number of tools to drive these discussions forward, make sure we listen to our community, and eventually make a decision. Sometimes that decision will be that we like things the way they are. Even that is valuable: it brings closure to the discussion. If we do a good job, even proponents of other approaches will feel heard. Even if they leave it will be with more empathy and respect than we sometimes have today.</p>
+<p>I have many years of building consensus both within Debian and within organizations like the <a href="https://www.ietf.org/">IETF</a>. I know how to summarize where we are in a discussion, point out where we have consensus, and what issues seem to be blocking consensus.</p>
+<p>It is valuable for the DPL to consider these issues and figure out where having a decision would be beneficial. Generally that is areas where having wider support would help empower people trying to do work and where enough of the discussion has happened that we're in a position to reach a decision. Once we've decided a decision is beneficial, the DPL has a number of tools to drive that process even if a consensus is not possible.</p>
+<p>The DPL can refer issues to the technical committee. So can any developer, but I think the DPL can do so in a way that is less confrontational than an individual developer. “We've discussed this as much as we can as a project; I think a decision is valuable to the project; here is where we got in our discussions” seems much less confrontational than asking to override some maintainer.</p>
+<p>I think the DPL's ability to propose general resolutions is under-utilized. I think that having the DPL propose a GR including the major options could be a much less confrontational way to bring closure to an issue than having an individual developer propose a GR and seek seconds. If the process feels a lot more like polling the project and guiding the resolution to a policy discussion, I think voting can bring things to closure.</p>
+<p>I hope to find ways to reduce the stigma associated with bringing important issues to a wider audience. I think it will always be the case that overriding a specific decision will come with a high price. However, often when we do face a controversial decision, we realize that there are broader policy question that could be answered that would inform future decisions. Once we get some distance from the original decision, I think answering these policy questions can be valuable. Sometimes it will be useful to answer the policy questions in a forum broader than the group making the original decision. Broadening the forum like this should not be seen as a lack of trust in any of our teams or decision makers: instead, it is working together in a broad community.</p>
+<h2 id="point-of-contact-explaining-debian">Point of contact: Explaining Debian</h2>
+<p>The DPL serves an important role as a point of contact for Debian. The DPL has an opportunity to explain Debian to other organizations and to the press. The DPL has an opportunity to understand the concerns of other organizations and help get them in contact with the right parts of Debian to make forward progress.</p>
+<p>I think this work is very important and I think I'm good at it. I've had experience building these sorts of bridges in my former role as the Chief Technologist for the MIT Kerberos consortium as well as my roles within the IETF. I haven't had this role formally within Debian, but I regularly find myself as an advocate for Debian in other professional circles.</p>
+<h2 id="speaking-at-conferences">Speaking at Conferences</h2>
+<p>The DPL traditionally has played a role in representing Debian at conferences. Over the past couple of years I actually haven't attended many computer conferences at all. If I'm elected DPL, I look forward to spending more focus on conferences than I have recently. I think this is an area where I can grow.</p>
+<p>Even so, I may not spend as much time at conferences as some past DPLs. I think this is an area where working with a team would work well.</p>
+<h2 id="supporting-free-software">Supporting Free Software</h2>
+<p>The free software community balances some interesting tradeoffs. There is more free software than ever before. Linux and open source software are widely accepted. However, a number of well-funded groups are working very hard to make sure that they control exactly how much freedom their users enjoy. They are working to avoid copyleft and to use free software as a platform on which their proprietary solutions are built. Even when software is free, it often connects to non-free web services. A user's freedom would be limited by the agreements surrounding these web services and by not having control of their data.</p>
+<p>Debian plays a critical role in this community because we are a meeting place for upstreams, downstreams, and the entire spectrum of viewpoints on what free software should be and how we should protect our users' freedom. So long as you agree to follow the DFSG and Social contract in your Debian work, you are welcome here.</p>
+<p>I think the DPL has an important role in working in this environment. The specifics tend to differ from year to year; Debian has the opportunity to support certain initiatives or make its voice heard. I don't know what 2019 will bring but acknowledge that it will be important and something that I as a DPL will focus on.</p>
+<h2 id="supporting-ongoing-efforts">Supporting Ongoing Efforts</h2>
+<p>The DPL needs to support ongoing efforts. In many cases this involves simply staying out of the way until the DPL's help is needed. I support the ongoing effort in all of our delegated teams.</p>
+<p>I'd like to specifically call out the efforts of the Diversity and Outreach teams. These teams work on cultural improvements within Debian and work to bring new members into our community. Both of these longer-term efforts are important to making Debian a fun community in the future.</p>
+<h2 id="finances">Finances</h2>
+<p>I will continue supporting similar policies to approving expenditures followed by the current DPL. I specifically support approving expenses for attending Debian BSPs.</p>
+<p>I've worked with budgets as large as Debian both as a small business owner and as a manager in larger organizations. In those roles, I had more access to financial information than I expect to have as DPL. My understanding is our money is spread across multiple trusted organizations each with its own policies and procedures. As a result it is challenging for Debian to get a complete understanding of its finances.</p>
+<p>I will exercise an appropriate level of due diligence and will support the ongoing efforts of the treasury team. However, improving Debian finances and financial accountability is not something I expect to be a key focus if elected as DPL. It is great work, but this year, I think the human factors and keeping Debian fun are more important. I am very open to working with people who do want to move forward in this area.</p>
+<h2 id="dpl-team">DPL Team</h2>
+<p>There has been a lot of talk this year about making changes to Debian governance and creating a DPL team rather than a single DPL. I think that a DPL team is a great idea, but I don't see significant changes in governance required.</p>
+<p>I suspect that the existing publicity, treasury, and several other delegations started out as tasks that the DPL performed but that that grew to be too big for one person to handle. For some tasks formal delegation will be appropriate. For others, simply working with people will be sufficient.</p>
+<p>I think a team could help me in the following areas:</p>
+<ul>
+<li><p>The mediation work is big enough that we need to spread it across multiple people</p></li>
+<li><p>The responsibility of representing Debian at conferences could be split across a team</p></li>
+<li><p>I would like to spread some of the ongoing financial work to a team</p></li>
+</ul>
+<p>I'm open to using teams in other areas where the job proves to be bigger than we expect.</p>
+<hr />
+<p>Overall, I think Debian is a great community. The landscape surrounding operating systems is changing and evolving rapidly. People are finding new ways to use Debian and the tools and building blocks we provide. Our universality is more important than ever. We can succeed as a community by capturing, emrbracing and building on these efforts whether they come from our members or outside.</p>
+<p>I'm excited about Debian. I look forward to making a great community even better. I look forward to talking to all of you as we refine and explore the plans of all the DPL candidates over the next few weeks. Thanks for your consideration.</p>
diff --git a/english/vote/2019/platforms/index.wml b/english/vote/2019/platforms/index.wml
new file mode 100644
index 00000000000..1267d09c278
--- /dev/null
+++ b/english/vote/2019/platforms/index.wml
@@ -0,0 +1,15 @@
+#use wml::debian::template title="Platforms for Project Leader Candidates" BARETITLE="true"
+#use wml::debian::votebar
+#include "$(ENGLISHDIR)/vote/style.inc"
+
+    <p>
+      The following is the platform statement from the
+      candidates for the Debian Project Leader elections, 2019.
+    </p>
+    <ul>
+	<li><a href="joerg">Joerg Jaspert</a></li>
+	<li><a href="jcc">Jonathan Carter</a></li>
+	<li><a href="hartmans">Sam Hartman</a></li>
+	<li><a href="tbm">Martin Michlmayr</a></li>
+#	<li><a href="sjr">Simon Richter</a></li>
+    </ul>
diff --git a/english/vote/2019/platforms/jcc.jpg b/english/vote/2019/platforms/jcc.jpg
new file mode 100644
index 00000000000..d62d2bd4aec
--- /dev/null
+++ b/english/vote/2019/platforms/jcc.jpg
diff --git a/english/vote/2019/platforms/jcc.wml b/english/vote/2019/platforms/jcc.wml
new file mode 100644
index 00000000000..2f4ca8390f2
--- /dev/null
+++ b/english/vote/2019/platforms/jcc.wml
@@ -0,0 +1,315 @@
+#use wml::debian::template title="Platform for Jonathan Carter" BARETITLE="true" NOHEADER="true"
+#include "$(ENGLISHDIR)/vote/style.inc"
+
+{#style#:
+<STYLE type="text/css">
+.li-itemize{margin:1ex 0ex;}
+.li-enumerate{margin:1ex 0ex;}
+.dd-description{margin:0ex 0ex 1ex 4ex;}
+.dt-description{margin:0ex;}
+.toc{list-style:none;}
+.thefootnotes{text-align:left;
+              margin:0ex;}
+.dt-thefootnotes{margin:0em;}
+.dd-thefootnotes{margin:0em 0em 0em 2em;}
+.footnoterule{margin:1em auto 1em 0px;width:50%;}
+.caption{padding-left:2ex;
+         padding-right:2ex;
+         margin-left:auto;
+         margin-right:auto}
+.title{margin:2ex auto;
+       text-align:center}
+.center{text-align:center;
+        margin-left:auto;
+        margin-right:auto;}
+.flushleft{text-align:left;
+           margin-left:0ex;
+           margin-right:auto;}
+.flushright{text-align:right;
+            margin-left:auto;
+            margin-right:0ex;}
+DIV TABLE{margin-left:inherit;
+          margin-right:inherit;}
+PRE{text-align:left;
+    margin-left:0ex;
+    margin-right:auto;}
+BLOCKQUOTE{margin-left:4ex;
+           margin-right:4ex;
+           text-align:left;}
+TD P{margin:0px;}
+.boxed{border:1px solid black}
+.textboxed{border:1px solid black}
+.vbar{border:none;
+      width:2px;
+      background-color:black;}
+.hbar{border:none;
+      height:2px;
+      width:100%;
+      background-color:black;}
+.hfill{border:none;
+       height:1px;
+       width:200%;
+       background-color:black;}
+.vdisplay{border-collapse:separate;
+          border-spacing:2px;
+          width:auto;
+          empty-cells:show;
+          border:2px solid red;}
+.vdcell{white-space:nowrap;
+        padding:0px;
+        width:auto;
+        border:2px solid green;}
+.display{border-collapse:separate;
+         border-spacing:2px;
+         width:auto;
+         border:none;}
+.dcell{white-space:nowrap;
+       padding:0px;
+       width:auto;
+       border:none;}
+.dcenter{margin:0ex auto;}
+.vdcenter{border:solid #FF8000 2px;
+          margin:0ex auto;}
+.minipage{text-align:left;
+          margin-left:0em;
+          margin-right:auto;}
+.marginpar{border:solid thin black;
+           width:20%;
+           text-align:left;}
+.marginparleft{float:left;
+               margin-left:0ex;
+               margin-right:1ex;}
+.marginparright{float:right;
+                margin-left:1ex;
+                margin-right:0ex;}
+.theorem{text-align:left;
+         margin:1ex auto 1ex 0ex;}
+.part{margin:2ex auto;
+      text-align:center}
+.rfloat{float:right;}
+
+body{
+    font-family: "noto sans", sans-serif;
+    font-size: medium;
+    margin: 20%;
+    margin-bottom: 25px;
+    margin-top: 5px;
+    background-color: #2a6099;
+    }
+
+.main {
+    background-color: #fcfcfc;
+    padding-left: 20px;
+    padding-right: 20px;
+    }
+.subsection {
+    text-decoration: underline;
+    }
+
+h1, h2, h3, h4{font-weight: normal;
+}
+h1{font-size: 140%;}
+h2{font-size: 130%;
+border-bottom: solid 1pt;
+}
+h3{font-size: 115%;}
+h4{font-size: 105%;}
+.paragraph{font-size: 105%;
+font-weight: normal;
+/* text-decoration: underline; */
+}
+.alphaenum ol{list-style-type: lower-alpha;
+}
+.mantra{border: solid;
+border-width: 1px;
+border-color: #aaa;
+background: #eee;
+margin: 2pt;
+margin-left: 8%;
+margin-right: 8%;
+padding: 2pt;
+}
+.summary{border: solid;
+border-width: 3px;
+border-color: #2a6099;
+background: #d9ecff;
+margin: 2pt;
+padding: 10px;
+padding-bottom: 0px;
+}
+.quote{border: solid;
+border-width: 3px;
+border-color: #2a6099;
+background: #d9ecff;
+margin: 2pt;
+padding: 5px;
+padding-left: 20px;
+}
+
+
+a{text-decoration: none;}
+a:hover{text-decoration: underline;}
+.floatright{float: right;
+}
+.mini {font-size:.6em}
+</STYLE>
+:##}
+
+<DIV class="main">
+<TABLE CLASS="title">
+<TR><TD>
+<BR>
+<H1 CLASS="titlemain"><BIG><B>Jonathan Carter</B></BIG><BR>
+    <SMALL>DPL Platform</SMALL><BR>
+    <SMALL>2019-03-17</SMALL>
+</H1>
+<H3>
+<A HREF="mailto:jcc@debian.org"><TT>jcc@debian.org</TT></A><BR>
+<A HREF="https://jonathancarter.org"><TT>https://jonathancarter.org</TT></A><BR>
+<A HREF="https://wiki.debian.org/highvoltage"><TT>https://wiki.debian.org/highvoltage</TT></A>
+</H3>
+</TD></TR>
+</TABLE>
+
+<H2 CLASS="section">Executive summary</H2>
+<P>Hi, my name is <A HREF="https://wiki.debian.org/highvoltage">Jonathan Carter</A>, also known as <EM>highvoltage</EM> with the Debian account name of <EM>jcc</EM>, and I'm running for DPL. </P><DIV CLASS="summary">
+<B>Broad goals as DPL</B>:
+<UL CLASS="itemize">
+<LI CLASS="li-itemize"> My intention is not to persue big, hairy and audacious goals. Instead, I aim to improve communication to help enable our community to fix existing problems and help make ideas flourish.</LI>
+<LI CLASS="li-itemize"> I want to promote polish and help drive better quality all over Debian, whether that's in our final products or community processes.</LI>
+<LI CLASS="li-itemize"> I want Debian to be an attractive project to participate in. Every Debian developer should be outright proud to be associated with the project.</LI>
+<LI CLASS="li-itemize"> The above might come across as playing it safe, and not being very ambitious, but I think big things can be achieved with baby steps and I hope to convey that in my platform.</LI>
+</UL>
+</DIV>
+
+<H2 CLASS="section">1. Introduction</H2>
+
+<H3 CLASS="subsection">1.1. Who I am</H3>
+
+<div style="min-height: 200px;">
+<img style="float: left; padding-right: 10px;" src="jcc.jpg" height="190px" alt="" />
+<P>I am 37 years old and live in Cape Town, South Africa, where I'm also from.</P>
+<P>I work part time for an educational institute where I do sysadmin work and work on a Debian derivative that the institutional network use in their centres across Africa. The rest of the time I do mostly Debian related contract work.</P>
+<P> I'm a long-time free software advocate who has worked in commercial, non-profit, public sector and educational environments over the last 15 years.
+</div>
+
+<H3 CLASS="subsection">1.2 Brief history with Debian</H3>
+
+<P>I started using Linux in 1999, and in 2003, I was excited about it and wanted to teach kids about it in schools. I learned that a local non-profit was looking into similar initiatives and I started talking to them, volunteering, doing some contract work and then eventually working there full-time. My colleague at the time, Thomas Black re-introduced me to Debian. I was previously unimpressed with Debian because it's installer back then, boot-floppies, almost never worked for me and when it did everything was ancient. He introduced me to Debian unstable and I got hooked, he told me that I should learn packaging and apply for DD status and become 'highvoltage@debian.org'. When he suggested that it felt like a completely alien concept to me, I had never even thought of considering being part of something as cool as a Linux distribution project before, but the idea got firmly planted into my head.</P>
+
+<P>Later that year the first Ubuntu version was released, and I took a detour from Debian into the Ubuntuverse for a few years.</P>
+
+<P>During DebConf7, I discovered the live video streams and got hooked. I also read the new maintainer's guide for the first time around then. In 2012 I made it to my first DebConf in Nicaragua which was a great experience, and in 2016 we successfully hosted a DebConf in Cape Town. In 2017 I became part of the newly formed DebConf Committee. I've made various different contributions to DebConf over the years, even <a href="https://jonathancarter.org/files/debian/debconf/pollito-adventure.pdf">graphic</a> <a href="https://jonathancarter.org/files/debian/debconf/pollito-dc16-guide.pdf">stories</a> featuring the DebConf chicken.</P>
+
+<P>I became a Debian Maintainer in 2016, and a Debian Developer in 2017. That makes me a relatively young DD in terms of how long I've been a member. I now actively maintain over 60 packages and have recently joined the debian-live project to help improve the quality of our live images.</P>
+
+<P>I try to summarise my Debian activities on my <a href="https://wiki.debian.org/highvoltage">wiki page</a>, although it's not always easy keeping it up to date. That page also links to my monthly free software activity recaps.</P>
+
+<H3 CLASS="subsection"> 1.3. Confidence in Debian</H3>
+
+<P>I like the concept of the "Universal Operating System". To me it means that Debian is adaptable to different technologies, situations and use cases. I'm constantly amazed at the great work that Debian Developers and all the Debian contributors do in all shapes and forms on a daily basis.</P>
+
+<P>When Debian was founded, the average computer user was busy migrating from MS-DOS to Windows 3.1 and learning how to use a mouse. Windows 95 haven't even been released yet. Since then, so much has changed. The average internet user now know what a VPN is. We have common awareness of the dangers of mass surveillance, and the technology that we originally envisioned as providing answers to all the world's problems are now often used against our species as a whole.</P>
+
+<P>Immensely positive changes are also happening. The <a href="https://riscv.org/">RISC-V foundation</a> has been formed, making great strides in developing a high-end free hardware central processing unit. Their work has also lead to <a href="https://wavecomp.ai/mips-open/">MIPS following suite</a> who have announced that they will release open versions of the MIPS instruction set. At the same time, Purism is also working towards releasing a <a href="https://puri.sm/products/librem-5/">fully free phone.</a></P>
+
+<P>With all the good and bad things on our radar, Debian is more relevant than ever. The world needs a fully free system with stable releases and security updates that puts its users first, that's commercially friendly but at the same time doesn't have any hidden corporate agendas. Debian is unique and beautiful and important, and we shouldn't allow that message to get lost in the noise that exists out there.</P>
+
+<P>I want us to focus on our shared passion and vision for Debian instead of the very few places where we differ. Too often, the small things are blown out of proportion by a small minority or by the media. We can't let that drown out the vast positivity and goodness in our project that keeps our contributors churning out good work on a daily basis.</P>
+
+<H2 CLASS="section">2.  My DPL mission statement</H2>
+
+<H3> 2.1. High level goals </H3>
+
+<OL>
+<LI><B>I do not intend to solve every problem in Debian during this term:</B> I believe it's more beneficial to pull together as a community and work together to focus on our most pressing core issues and iterate over them.</LI>
+
+<LI><B>I don't want my role as DPL to be purely administrative:</B> I think it's critical that there's someone in the project who has a stoic view of the Debian project system-wide, since we often tend to get wrapped up in our own problems as individuals inside the project.</LI>
+
+<LI><B>DPL as enabler:</B> Some of my ideas can be implemented without being a DPL, but being DPL comes with some spotlight and attention and makes it a lot easier to drive certain ideas forward.</LI>
+
+<LI><B>Make community processes a a first class citizen in Debian:</B> As much as our technical processes are.</LI>
+<LI><B>Make the DPL more approachable:</B> Previous DPLs have been great at communicating their work to the project, I aim to make that more of a two-way street.</LI>
+<LI><B>Promote new ideas and experimentation in the project:</B> Track the most requested ideas in Debian and advertise these for teams who might be willing to take them up.</LI>
+<LI><B>Foster our community:</B> It's important to gain more contributors, but I think it's equally important to make contributing to Debian enjoyable for existing developers too. When things aren't going well, it feels futile recruiting new developers. If we make Debian a fantastic project to work in for all our existing developers, we will naturally attract more contributors.</LI>
+<LI><B>Small details matter:</B> We've become too accustomed to small things that don't work. If you're used to them, you're also used to working around them. Through the eyes of a newcomers though, the Debian experience can often feel like a case of death by a thousand papercuts.</LI>
+</OL>
+
+
+<h3> 2.2. Execution </H3>
+
+<P>Overall, I want to help Debian be better at talking about the actual issues that affect us more often, without having another daunting thread like some famous ones that had before. I want to go as far as to say that I care more about fixing communication and our internal problem solving mechanisms than the actual problems themselves. I hope to promote ways of working that will be beneficial to Debian long after I'm not DPL any more.</P>
+
+<P>Below are some of the ideas I am considering to implement in order to achieve the above. They are not stuck in stone, and I will consult with the community at large when implementing them. If they are deemed largely unsuitable, I will not mind backing off on any of these and we can work on alternative methods for solving those problems.</P>
+
+<OL>
+<LI><B>Promote and use #debian-meeting as a meeting room:</B> Many teams have IRC meetings in their own channel. It would bring a lot of visibility if Debian teams would instead use a slot in the #debian-meeting IRC channel. Not only would it make it easier for interested parties to keep up with what's going on in the scroll-back, but it might also help attract new members to your team as they become familiar with its problems.</LI>
+<LI><B>Weekly community meetings:</B> Have a project-wide community meeting on a weekly basis with the DPL and helpers (in whatever form they may exist) present. This would alternate in time to make it easier for people from various time-zones. The idea is to shine a light on the most pressing issues that concern the community, and work towards solutions. I'm sure some people dread the idea because of trolls, but we can moderate and/or limit participants if needed.</LI>
+
+<LI><B>Implement a 100 papercuts campaign:</B> Create a project to identify the 100 most annoying small problems with Debian. These would typically be items that can be solved with a day's worth of work. This could be a technical bug or a problem in the Debian project itself. The aim would be to fix these 100 bugs by the time Bullseye (Debian 10) is released. A new cycle can also be started as part of an iterative process that's based on time and/or remaining bug count.</LI>
+<LI><B>Hardware enablement project:</B> Between all the new architectures listed above, and new devices like free phones- hardware enablement becomes really important. I believe we should have budget available for getting hardware to developers who care about enabling Debian on those devices. I believe the DPL could also spend some time with hardware vendors to get some free (or loan) samples, as well as preferential pricing for all Debian Developers.</LI>
+<LI><B>Debian Woman Meetups: </B>As DPL, I wish to create a project where women in any city of the world can organise monthly meetings and Debian will cover the cost of the refreshments (similar to how it's done for bug squashing parties). We often talk about how serious we are about getting more women involved in the project, but if we're serious we have to be willing to put our money where our mouths are. These meetings could be as simple as just talking about Debian and demo'ing it. As soon as someone is interested and start using Debian, they immediately learn skills that they can transfer to someone else. We have a huge base of potential contributors that we're not targetting enough.</LI>
+<LI><B>Better financial understanding:</B> In the past, people have asked for better understanding of how Debian spends funds, and how much is available. The way that Debian's accounting works across trusted organisations can make real-time exact numbers really difficult, but I think that basic reports on a regular basis that lists all recent spending (sprints, DebConf, hardware, etc) along with recent balances will be enough to give a sufficient overview of how Debian is managing its funds.</LI>
+<LI><B>DPL pseudo-bugs:</B> As DPL, I will also endeavour to take some time off. I plan to not spend weekends working on DPL matters unless there is something really urgent (or exciting) that warrants attention. If any part of the DPL role becomes too demanding, I will consider it a bug and will file a public bug about it that. I recommend a DPL pseudo-package (<a href="https://www.debian.org/Bugs/pseudo-packages">more on those here</a>) that can be used to file bugs against the DPL role, and also be used to make common requests to the DPL (similar to how you can file ITP/RFS/O/etc bugs in the wnpp pseudo-package).</LI>
+<LI><B>Make it clear how processes work, and how to submit feedback:</B> I know it sounds redundant to say this, but every community process should be well documented in an obvious place, but in addition to that, there should also be a clear method to file bugs/objections/improvement to a process, just as we do with the Debian Policy Manual for packaging. Projects like DebConf could <I>really</I> benefit from this in my opinion.</LI>
+</OL>
+
+<P>None of the above is set in stone, and I will work with the community as I pursue these for feedback. Plans may certainly change, but I thing that working through the above may put the project on a good footing to strengthening our community and move on to larger ideas. I'll leave you with one of my favourite quotes:</P>
+
+<DIV CLASS="quote">
+<P>“Great minds discuss ideas. Average minds discuss events. Small minds discuss people.” <BR> <I> – Eleanor Roosevelt</I></P>
+</DIV>
+
+<H2> 3. Consequences to existing work </H2>
+
+<p>If elected, at least to some extent, I plan on cutting back on existing roles in Debian to maximise the amount of energy available for the DPL role:</p>
+
+<OL>
+<LI><B>DebConf:</B> I'll step down from the DebConf Committee, which shouldn't at all be a big disruption since our biggest recurring task is the bid decision for the next DebConf, which is now concluded for this year. I plan to remain involved in other DebConf areas. I will also step down from bursaries after DC19, but will work on contingency for next year.
+</LI>
+<LI><B>Package maintenance:</B> I plan to release any ITP bugs that I have filed and won't take on any invasive new packaging work. I will however continue maintaining my existing packages.</LI>
+<LI><B>Package sponsoring:</B> This is an activity I do when I have some spare time, I will continue doing so, but probably just less of it.</LI>
+<LI><B>Goofing around:</B> DPLs are supposed to always be serious, right?</LI>
+</OL>
+
+<H2> 4. Some factors to weigh up. </H2>
+
+<H3> 4.1. Reasons to consider me for DPL </H3>
+
+<OL>
+<LI><B>New energy:</B> With the above plans (or similar to those), I believe I can inject new energy into the Debian project. I think that Debian Developers deserve a project leader that can keep the positive energy flowing and make everyone proud to be part of the Debian project. </LI>
+
+<LI><B>Sanity:</B> I'm not going to introduce any wild ideas to the project, instead, I aim to find ways to keep it grounded and create stable platforms that we can use to build on towards bigger and more ambitious ideas.</LI>
+
+<LI><B>Timing:</B> This year happens to be a good time for me to be a DPL. My personal life is relatively uneventful right now, and I don't have a family to take care of and I have some flexibility work-wise without being overcommitted at all.</LI>
+</OL>
+
+<H3> 4.2. Weaknesses in my campaign </H3>
+
+<OL>
+<LI><B>Experience</B>: I don't have experience leading a project as large and complex (or even complicated) as Debian. I've also only been a Debian Developer for a relatively short period of time. However, I believe that being aware of this will at least prevent me from flying to close to the sun, my main goal for my term will be to reduce existing friction and mitigate or solve existing problems. </LI>
+<LI><B>Public appearances:</B> I live in a relatively remote part of the world, and due to visa requirements and travel time, I won't be able to travel and talk about Debian as much as previous DPLs were able to. I might be able to mitigate this by staying in an area for a slightly longer time and do a series of talks at a time, I can often work remotely which help makes this possible.
+</LI>
+<LI><B>Temperament:</B> I can be very emotional, and sometimes it bursts out a little. Over the years I've learned to channel my emotional energy into something more positive. I aim to practicea stoistic outlook  as DPL and spend some time reading up on diplomacy, if elected.</LI>
+</OL>
+
+<H2> 5. Acknowledgements </H2>
+
+<UL>
+<LI>I used <a href="https://www.debian.org/vote/2010/platforms/zack">Zack's platform layout</a> as a base for mine.</LI>
+</UL>
+
+<H2> 6. Changelog </H2>
+
+<P> This platform is version controlled in a <a href="https://salsa.debian.org/jcc/dpl-platform">git repository.</a> </P>
+
+<ul>
+<LI><a href="https://salsa.debian.org/jcc/dpl-platform/tags/1.00">1.00</a>: Initial release for public use.</LI>
+<LI><a href="https://salsa.debian.org/jcc/dpl-platform/tags/1.01">1.01</a>: Improve summary on high-level goals.</LI>
+</ul>
+
+<BR>
+
+</DIV> <!-- END MAIN -->
+
+
diff --git a/english/vote/2019/platforms/joerg.wml b/english/vote/2019/platforms/joerg.wml
new file mode 100644
index 00000000000..4ddf5ee1ddb
--- /dev/null
+++ b/english/vote/2019/platforms/joerg.wml
@@ -0,0 +1,311 @@
+#use wml::debian::template title="Platform for Joerg Jaspert" BARETITLE="true" NOHEADER="true"
+#include "$(ENGLISHDIR)/vote/style.inc"
+
+<div id="content">
+<h1 class="title">DPL Platform 2019</h1>
+<div id="table-of-contents">
+<h2>Table of Contents</h2>
+<div id="text-table-of-contents">
+<ul>
+<li><a href="#orgfb93861">1. Who am I?</a></li>
+<li><a href="#org781b5a7">2. Debian activities</a></li>
+<li><a href="#orga50bc7e">3. The Debian Project Leader in 2019</a></li>
+<li><a href="#org5f677db">4. The future</a></li>
+<li><a href="#org230864e">5. My part as DPL</a></li>
+<li><a href="#orgabc7e56">6. Time commitment</a></li>
+<li><a href="#orgb0cb51b">7. What with your delegations?</a></li>
+</ul>
+</div>
+</div>
+
+<div id="outline-container-orgfb93861" class="outline-2">
+<h2 id="orgfb93861"><span class="section-number-2">1</span> Who am I?</h2>
+<div class="outline-text-2" id="text-1">
+<p>
+I am a Debian Developer since 17 years now, having joined Debian in
+April 2002. Real life people think I am <b>THE ANSWER</b> since a few days,
+having turned 42 recently. I live right in the middle of Germany, in
+the nice medium sized town named Fulda.
+</p>
+</div>
+</div>
+
+<div id="outline-container-org781b5a7" class="outline-2">
+<h2 id="org781b5a7"><span class="section-number-2">2</span> Debian activities</h2>
+<div class="outline-text-2" id="text-2">
+<p>
+I manned various booth for Debian at a number of events over the
+years. There have been multiple LinuxTag, LinuxWorldExpos and Cebits
+as well as Chemnitzer LinuxTag, FrosCon and other smaller ones.
+Sometimes I just appeared, sometimes I handled the complete orga
+needed for it, including creating Debian CD/DVDs to hand out to
+visitors as well as organising merchandise. During the first such
+event I found (or rather, the upstream author of it found me) my
+first package to maintain.
+</p>
+
+<p>
+I have been an application manager for the NM process since shortly
+after I became DD and became Debian account manager assistant in 2004,
+full DAM in April 2008.
+</p>
+
+<p>
+In March 2005 I joined the FTP team as an assistant and became FTP
+Master in April 2008.
+</p>
+
+<p>
+After DebConf5 i joined the the DebConf orga with my main role being
+admin of the infrastructure, as back then it was seperate to Debian.
+Beside the admin stuff I helped with or lead various other teams, say
+content or travel sponsorship.
+</p>
+
+<p>
+I am part of the mirroradmin group, having written the base of the
+current master sync scriptset for the mirrors.
+</p>
+
+<p>
+I am one of the admins for our Debian Planet and am one of the admins
+for Debians gitlab service salsa.debian.org.
+</p>
+
+<p>
+I am also a staff (NOC) member at OFTC, the IRC network where
+irc.debian.org points too.
+</p>
+
+<p>
+Between August 2007 and February 2018 I have been a board member of
+SPI, Software in the Public Interest, with most of the time being
+VicePresident and main administrator. SPI is the legal umbrella that
+Debian sits in within the United States, and holds the majority of
+Debian's assets.
+</p>
+</div>
+</div>
+
+<div id="outline-container-orga50bc7e" class="outline-2">
+<h2 id="orga50bc7e"><span class="section-number-2">3</span> The Debian Project Leader in 2019</h2>
+<div class="outline-text-2" id="text-3">
+<p>
+It's this time of the year again. Many line up, ready to fire questions
+on the -vote list, with only five lined up to answer. It's DPL election
+time, long threads to surface at the list. Everyone wants to know how
+the next leader is going to lead us into the gloryful future of the
+universal OS.
+</p>
+
+<p>
+How to overcome all the challenges a distribution like ours faces, how
+to adapt to the ever faster changing world?
+</p>
+
+<p>
+How to become more attractive for all the commercial entities that are
+currently chosing to ignore Debian but select a derivative?
+</p>
+
+<p>
+How to become more attractive for developers?
+</p>
+
+<p>
+How to renew our tools to some more modern workflow? A common wish
+being to modernize the BTS (web interface anyone?). Or uploads with a
+git push.
+</p>
+
+<p>
+How to be more diverse? (Look a this years nominees&#x2026;)
+</p>
+
+<p>
+How to make large-scale changes in Debian simpler?
+</p>
+
+<p>
+How to deal with the "curl | sudo bash" mentality of newer languages
+and their environment? How to, usefully, include those languages?
+</p>
+
+<p>
+And I am sure, many many more.
+</p>
+</div>
+</div>
+
+<div id="outline-container-org5f677db" class="outline-2">
+<h2 id="org5f677db"><span class="section-number-2">4</span> The future</h2>
+<div class="outline-text-2" id="text-4">
+<p>
+I am not really good in predicting the future, but one thing I am
+willing to put a bet on is that Debian will continue to be relevant
+for the community. We have many users, directly or indirectly via
+derivatives. They continue to need a stable, predictable and simply
+working system, which we are good at delivering.
+</p>
+
+<p>
+We should not relax and accept just being a building ground for others
+though, we should look why people chose something different than
+Debian. And see if we can enhance Debian to provide the features,
+while balancing it with our current users.
+</p>
+
+<p>
+We need to ensure to cater to the millions of users we have. They
+range from those who want a really stable system and loath change to
+those that even find our unstable distribution to slow to change.
+</p>
+
+<p>
+Thats not an impossible task, we have some of the most brilliant
+people working with the project. We are the experts in making sure our
+software integrates. And we need to make sure that we keep those
+properties. And extend them to the new challenges.
+</p>
+
+<p>
+And some of those challenges are big. The current hypes on the current
+"perfect way of doing sysadmin/devops/&#x2026;" are seldom based on full
+distributions.
+</p>
+</div>
+</div>
+
+<div id="outline-container-org230864e" class="outline-2">
+<h2 id="org230864e"><span class="section-number-2">5</span> My part as DPL</h2>
+<div class="outline-text-2" id="text-5">
+<p>
+As the DPL is not the lead of actual technical development, it is not
+for the DPL to find technical solutions for the challenges we face. Or
+to find the perfect answers to the series of questions (and all the others
+that are out there) I put above.
+</p>
+
+<p>
+But the DPL ought to enable other project members to do so, and that
+is one major part I will focus on. Many of the above points are
+nothing that can be implemented in short terms like a year, but at
+least one can start on them. Some may already get worked on, then it
+is important to continue work and keep people engaged.
+</p>
+
+<p>
+The DPL should work removing blockers and let developers get on with
+their jobs.
+</p>
+
+<p>
+It's also the job of the DPL to listen. And be guided by the
+community.
+</p>
+
+<p>
+Debian does not only consist of packaging and similar technical
+activities, we have a lot of other contributions that are equally
+important. We need to encourage more people who aren't well versed in
+the technical work to contribute in various non-technical ways. That
+can range from writing documentation, translations, help with the
+website, design work, help users with their problems or representing
+Debian at events. Or organizing such events, like BTS or local
+"miniconf" gatherings. All of that is as important as the packagers
+work.
+</p>
+
+<p>
+I will work with anyone who wants to improve processes within Debian
+to identify non-trivial bottlenecks, to reduce our complexity and to
+improve communication between teams, where needed.
+</p>
+
+<p>
+I intend to continue the transparent ways from Chris (and other former
+DPLs) with regular activity reports, though my style naturally will be
+different.
+</p>
+
+<p>
+Also, as we are a really big project, there will be areas where I
+simply not know enough (or anything) about. I'm not afraid asking for
+help.
+</p>
+</div>
+</div>
+
+<div id="outline-container-orgabc7e56" class="outline-2">
+<h2 id="orgabc7e56"><span class="section-number-2">6</span> Time commitment</h2>
+<div class="outline-text-2" id="text-6">
+<p>
+The DPL job is one that takes a lot of time and energy. Having a
+fulltime job and a family with 2 kids does not make it easier. As such
+I discussed it with all involved and got full support for my
+nomination.
+</p>
+
+<p>
+To be a bit more precise: My company calculates with a full 45
+workdays that I spend on DPL duties (out of the approximately 250
+workdays during a DPL term). Additionally to my usual vacation days.
+</p>
+
+<p>
+The time I take will depend on the actual DPL tasks and can range from
+just hours a day to full absence when traveling to some event.
+</p>
+
+<p>
+That is just what I take out of work time, the actual time I can spend
+on DPL duties will be higher, but I am not going to put up a definite
+number. It will adjust to what is needed, when it is needed.
+</p>
+</div>
+</div>
+
+<div id="outline-container-orgb0cb51b" class="outline-2">
+<h2 id="orgb0cb51b"><span class="section-number-2">7</span> What with your delegations?</h2>
+<div class="outline-text-2" id="text-7">
+<p>
+Lets start with the most important one in this context, DAM. The
+constitution is simple there. $8.1.2 is specific for this. It says:
+</p>
+
+<blockquote>
+<p>
+The Project Leader's Delegates:
+</p>
+
+<p>
+[&#x2026;]
+</p>
+
+<p>
+may make certain decisions which the Leader may not make directly,
+including approving or expelling Developers or designating people
+as Developers who do not maintain packages. This is to avoid
+concentration of power, particularly over membership as a
+Developer, in the hands of the Project Leader.
+</p>
+</blockquote>
+<p>
+The simple takeaway here is that, should I get elected, I will resign
+from DAM.
+</p>
+
+<p>
+Besides the above quote the constitution only forbids the secretary
+and the chair of the CTTE to be DPL, so I do not see any conflict with
+keeping my other delegation, FTPMaster. That is, until the moment I
+would need to update it, then I would need to resign from that, as a
+DPL may not delegate to themself.
+</p>
+</div>
+</div>
+</div>
+<div id="postamble" class="status">
+<p class="author">Author: Joerg Jaspert</p>
+<p class="date">Created: 2019-03-18 Mon 21:26</p>
+</div>
diff --git a/english/vote/2019/platforms/tbm.jpg b/english/vote/2019/platforms/tbm.jpg
new file mode 100644
index 00000000000..afb880a805a
--- /dev/null
+++ b/english/vote/2019/platforms/tbm.jpg
diff --git a/english/vote/2019/platforms/tbm.wml b/english/vote/2019/platforms/tbm.wml
new file mode 100644
index 00000000000..79bf61c349f
--- /dev/null
+++ b/english/vote/2019/platforms/tbm.wml
@@ -0,0 +1,487 @@
+#use wml::debian::template title="Platform for Martin Michlmayr" BARETITLE="true" NOHEADER="true"
+#include "$(ENGLISHDIR)/vote/style.inc"
+
+<h2>Introduction</h2>
+
+<p>
+
+I will start with a confession.  For a few years now, I've been thinking
+that it's time to retire from the Debian project.  This is partly
+because my interests have changed over the years, but partly because...
+Debian just doesn't seem all that exciting anymore.  The only reason I
+haven't actually resigned is because Debian and the Debian community
+plays such an important role in my life and I don't want to let go.
+
+</p>
+
+<p>
+
+I believe my mixed feelings about Debian are not that unusual.  We've
+seen a number of prominent contributors leave the project in recent
+times out of frustration or sheer boredom and I think there are many who
+stick around but who have essentially checked out mentally.
+
+</p>
+
+<p>
+
+Seeing that there was no candidate for the Debian Project Leader (DPL)
+position, which I see as a symptom of grave underlying problems, got me
+thinking.  I &mdash; like everyone who chooses to contribute to Debian
+&mdash; have two options: I can resign, run away in frustration, or I
+can help to discuss, confront, tackle and solve these problems.
+
+</p>
+
+<h2>Debian today</h2>
+
+<p>
+
+Debian appears to be in a very peculiar situation right now.  About
+10-15 years ago, Debian faced an existential crisis.  A number of
+factors contributed to Debian becoming less relevant.  This includes the
+introduction of Ubuntu (which offered a more polished desktop at that
+time and long term support for servers), the move towards Apple's macOS
+(among the general public and even among open source developers,
+especially in the web space), and a general shift towards mobile
+devices.
+
+</p>
+
+<p>
+
+Today, things are vastly different however.  Debian is more popular than
+ever on servers.  There is a renewed understanding of the importance of
+Debian and a new wave of adoption in the cloud and container space where
+a stable operating system is key.  Debian is everywhere.  It runs large
+parts of our society's IT infrastructure and also constitutes the
+building blocks for many other solutions.  Users and corporations
+appreciate not just the quality of the Debian system, but also the
+maturity of our community and the open nature of our development process
+which is not dominated by a single vendor.
+
+</p>
+
+<p>
+
+So, despite this success and importance, why does it sometimes feel that
+Debian has become somewhat irrelevant?  Why is there no buzz around
+Debian that reflects Debian's success in so many areas?
+
+</p>
+
+<h2>Problems and solutions</h2>
+
+<p>
+
+I recently read Michael Stapelberg's post on <a href =
+"https://michael.stapelberg.ch/posts/2019-03-10-debian-winding-down/">winding
+down his Debian involvement</a> in which he describes how stagnant
+Debian's infrastructure and processes have become.  His well-reasoned
+post resonates with me, although I believe the problems are even bigger
+than that.
+
+</p>
+
+<p>
+
+The open source world has fundamentally changed in the last 5-10 years
+in many ways.  Yet, if you look at Debian, we mostly operate the same
+way we did 20 years ago.  Debian used to be a pioneer, a true leader.
+Package managers, automatic upgrades, and packages builds on 10+
+architectures &mdash; they were all novel, true innovations at the time.
+The only significant innovation I can think of that came out of Debian
+in recent years are reproducible builds.  Reproducible builds solve an
+important problem and the idea has spread beyond Debian to the whole
+FOSS world.
+
+</p>
+
+<p>
+
+I hate when large companies talk about being "nimble" or similar
+business buzz words.  But looking at Debian, I finally understand what
+they mean &mdash; the project has evolved in a way that makes change
+difficult.  We have failed to adopt to the new environment we find
+ourselves in and we're struggling to keep up with an ever-faster
+changing world.
+
+</p>
+
+<h3>Sustainability</h3>
+
+<p>
+
+When I got involved in free software in the 1990s, it was out of
+technical curiosity and a passion for software freedom.  It was a hobby
+and I never imagined making a career out of it.  But then more and more
+companies discovered the technical superiority of software developed
+with collaborative FOSS models coupled with the practical freedoms
+offered by FOSS and the industry took off.  Many of us are nowadays
+fortunate to contribute to FOSS not just in our spare time but as part
+of our jobs.
+
+</p>
+
+<p>
+
+Today, the majority of successful FOSS projects rely on (and thrive
+from!) paid contributors.  This is not a failure, but a reflection of
+the success of FOSS.  Unfortunately, compared to other successful
+projects, the proportion of contributors who are paid is much smaller in
+Debian and I see that as a failure.
+
+</p>
+
+<p>
+
+Over the years, I have seen many valuable Debian contributors leave
+after they graduate from university and get a job (often working on
+FOSS, just not Debian; or working <em>with</em> Debian, but not
+<em>on</em> Debian).  I have seen many dedicated contributors who
+essentially have two jobs &mdash; a paid job during the day, and an
+unpaid gig at Debian working long evenings and weekends.  I have met
+many contributors who make huge sacrifices in order to contribute to
+Debian.  Unfortunately, I have seen a lot of burnout, too (and
+experienced it myself)!
+
+</p>
+
+<p>
+
+If you want to work on Debian as a hobby, great!  But if you want to
+make Debian your career, you should be able to do so.  While there are
+some paid opportunities around Debian, I believe they are currently too
+scarce and that we can take a number of actions so more contributors can
+make Debian their careers.
+
+</p>
+
+<p>
+
+First, we can help more companies get involved in Debian.  This does not
+mean that we will sacrifice our neutrality or focus on quality.  It
+means that we'll bring more contributors on board who will work towards
+improving Debian for everyone.  We already have a number of companies
+(Arm, credativ, Google, just to name a few) who make strategic
+investments in Debian and pay engineers to work on Debian.
+
+</p>
+
+<p>
+
+We can encourage more companies to get involved.  We can make it easier
+for them to contribute, we can show companies that rely on Debian the
+importance of actively getting engaged (and help them develop the
+business case for it), and we can provide more incentives, such as
+acknowledging their contributions better.
+
+</p>
+
+<p>
+
+Second, grants are becoming a popular way to fund R&amp;D projects and
+FOSS development.  The Reproducible Builds project is funded through
+grants from the Linux Foundation and other organisations.  I doubt they
+would have achieved as much as they did in relatively little time
+without this funding.  We have a lot of smart people in Debian with good
+ideas &mdash; the DPL can identify grants and help them apply for
+funding.
+
+</p>
+
+<p>
+
+Third, we need to work with the wider FOSS community to find more
+sustainable ways to fund FOSS development.  The OpenSSL debacle has
+shown that society depends on FOSS without making the necessary
+investments.  Many independent FOSS developers struggle to make a living
+from their work.  Platforms like Patreon exist but few can live from
+this since there's not enough awareness that people need to invest in
+and sponsor FOSS.
+
+</p>
+
+<p>
+
+I'm sure there are other ways.  Overall, I believe it will become
+increasingly difficult for significant projects with unpaid contributors
+to compete with efforts where everyone is paid full-time and I think
+that partly explains why Debian has struggled to keep up.  More
+fundamentally, we also have to ask ourselves what kind of project we
+want to be.  The world around us has changed and it's time to
+acknowledge that.
+
+</p>
+
+<p>
+
+The Long Term Support effort organised by Raphaël Hertzog of Freexian
+has been spectacularly successfully.  Reproducible Builds has attracted
+significant funding to improve an important aspect of Debian.  Is it
+time to bring these efforts in and do them as Debian?  Or should we
+encourage more such efforts around Debian and give them a helping hand?
+Is it time to use our funds for certain things?
+
+</p>
+
+<p>
+
+These are big questions we'll have to answer as a project eventually.
+However, we can start by inviting more companies to participate in our
+community and by encouraging those who depend on Debian to contribute.
+
+</p>
+
+<h3>Leadership and culture</h3>
+
+<p>
+
+I see a lack of leadership in Debian.  I don't only mean DPL-style
+leadership, but lack of leadership in general.  The beauty of FOSS is
+that anyone can make a contribution.  You don't need to get permission
+to be a leader.  If you have a great idea, just do it!
+
+</p>
+
+<p>
+
+Unfortunately, while we have many talented people in Debian, I think
+we've reached a point where people are afraid to make or propose
+changes, especially big, far-reaching changes.  They are afraid of the
+resulting flame-war or other fallout (or simply tired of the cat herding
+involved in getting the change adopted everywhere).
+
+</p>
+
+<p>
+
+Why is it that our community makes people so afraid to speak?  Why have
+we stalled?  It seems to me that Debian has developed a number of toxic
+anti-patterns over the years that we have to move away from.
+
+</p>
+
+<p>
+
+What I'm going to say now will be very controversial.  Debian prides
+itself on being the universal operating system.  This is a great goal,
+on many levels.  However, it's also important to acknowledge that you
+cannot do everything &mdash; that doing everything slows things down.
+We can't always wait for everyone, otherwise we'd never get things done.
+Not everything is equally as important.  Sometimes it's important to set
+priorities and to tell people "no".  Again, we're afraid to do that.
+The universal operating system, and the underlying culture, while
+laudable in practice, has become toxic in practice on some levels.
+
+</p>
+
+<p>
+
+Same with technical excellence, another laudable goal, that becomes
+toxic when taken to the extreme.  We talk and talk... and talk.  We
+should remember that not every battle is worth fighting for and that not
+every argument needs to be discussed till the bitter end.  It's fine to
+agree to disagree sometimes.  We have to remind ourselves to pause,
+reflect and ask: is it really worth it?  Do I really have to send this
+email?  What about the social cost?  Let's stop draining energy from our
+community!  We're not a debate club.  We're here to solve problems in a
+practical manner and to ship solutions to users.
+
+</p>
+
+<p>
+
+In addition to more leaders, we need more cheerleaders.  We have to
+thank people.  We have to appreciate contributions.  We have to create a
+buzz around Debian.  We should celebrate, and build upon, our success.
+(And yes, I appreciate the irony of saying this in a platform which
+essentially consists of a critique of Debian.  However, as DPL and as a
+community member in general, I aim to say "thank you" more often and to
+encourage other people to do the same.)
+
+</p>
+
+<h3>Influence</h3>
+
+<p>
+
+Debian plays a very special and important role in the FOSS ecosystem.
+We are respected and our contributions are appreciated.  Debian
+contributors tend to be leaders in the FOSS space.  We pride ourselves
+not only on packaging software from upstream but on maintaining good
+relationships.  This often results in us getting involved upstream and
+taking on leadership roles there.  You can also look at current and past
+board members of the Open Source Initiative (OSI) and again you'll see
+many Debian people.
+
+</p>
+
+<p>
+
+While Debian people play important roles everywhere, they often don't
+represent the Debian project.  We need to learn to develop and speak as
+a single voice.  Overall, I believe we, as a project, need to be more
+vocal and take a more active role in influencing the FOSS ecosystem.
+Debian has an incredible reputation but we don't use our clout for
+important change.
+
+</p>
+
+<p>
+
+While we're fairly good at influencing technical aspects, we have little
+sway in the business world of FOSS.  And let's be honest &mdash; open
+source has become a big business.  We're missing out of important
+opportunities because this is a game we don't play well.  We need to
+take a seat at the table (and, yes, that's often an actual table or a
+conference call, and not email).
+
+</p>
+
+<h2>Background</h2>
+
+<p><img src="tbm.jpg" alt="Photo of Martin Michlmayr" align="right"></p>
+
+<p>
+
+Who am I and how do I see the role of the DPL?  I have been a Debian
+Developer since 2000 and I worked on a number of areas over the years.
+I worked as an Application Manager, helping new contributors join the
+project, and also managed the New Member Front Desk.  I contributed to
+various Quality Assurance efforts, filed bug reports and introduced the
+Missing in Action (MIA) process.  I ported Debian to various ARM and
+MIPS devices and wrote documentation for it.  I served as Debian Project
+Leader from 2003-2005.  Most of my contributions to Debian recently have
+been indirectly through Software Public in the Interest, one of Debian's
+trusted organisations.
+
+</p>
+
+<p>
+
+I worked for Hewlett Packard for nine years, facilitating and leading
+various internal and external FOSS activities.  I served on the board of
+the Open Source Initiative for six years and on the board of Software in
+the Public Interest for close to five years.  I currently serve on the
+board of Software Freedom Conservancy, the home of the Debian Copyright
+Aggregation Project.  Over the years I've become an open source
+accounting geek and I contribute to ledger, beancount, and
+ledger2beancount.
+
+</p>
+
+<p>
+
+There are various opinions on what kind of time commitment being DPL
+takes, ranging from proposals to a "leaderless" Debian to the DPL being
+a full-time job.  Based on my experience as DPL in the past, I'm firmly
+in the latter camp.  When I was DPL in the past, I was a student and had
+(what looking back seems like) unlimited time.  I'm now a FOSS
+consultant and every hour I'd spend as DPL takes away from that work.  I
+am, however, willing to devote significant time to Debian.  (I might
+also set up a virtual tin cup.)
+
+</p>
+
+<p>
+
+The role of DPL is very unique.  In Debian you don't typically get
+"promoted" in the traditional sense.  You start doing the work and
+eventually people recognise you for it.  It's all based on reputation
+and ideally we want a DPL who has already earned the reputation for
+being a leader.  I gave a talk about FOSS culture at an event some time
+ago and I emphasised the importance of building up a good reputation.
+To illustrate the point, I said there's this one particular person in
+Debian and when this person sends an email, people will listen because
+they know that the email will contain genuine wisdom written in a calm
+tone.  Despite Debian having over a thousand <em>incredible</em>
+contributors, this description was enough for some Debian Developers in
+the audience to nod their heads with a shared understanding of whom I
+was talking about (without ever mentioning the person's name).  This is
+the kind of reputation you want to build up!  (And there are many other
+contributors I could describe for their very unique ways of contributing
+to Debian!)
+
+</p>
+
+<p>
+
+Unfortunately, I haven't been active in Debian lately and so I don't
+have the reputation that I would hope to see from a DPL.  While many
+old-timers are familiar with my work, I'm a blank canvas for many new
+contributors.  I am aware of this, and if elected, I will work hard to
+earn their trust.
+
+</p>
+
+<h2>The DPL</h2>
+
+<p>
+
+The role of DPL is often described as having an internal and an external
+function and both are absolutely vital.  I believe you can also define
+three roles of the DPL: the DPL as administrator, facilitator, and
+leader.
+
+</p>
+
+<p>
+
+While I enjoy getting things done, I also find it immensely rewarding to
+help other people get work done.  In this way, I see the DPL as a
+facilitator.  I just attended FOSSASIA where someone compared managing
+communities to conducting an orchestra.  When you look at orchestra
+conductors, you may wonder what they are doing apart from waving their
+hands around.  You don't see all the coordination and practice that was
+necessary for a flawless performance.  DPLs have in the past been
+criticised for not being active in part because you don't see a lot of
+the day to day work.  You only see if something doesn't get done or goes
+wrong!
+
+</p>
+
+<p>
+
+Facilitation includes a lot of coordination.  It involves helping people
+do their work effectively, removing problems, connecting people, using
+delegation and following up.  It involves listening to people.  It also
+involves asking people to do certain tasks.  You'd be surprised how
+effective it can be to ask someone to help out.  If you don't ask, it
+doesn't get done.  Facilitation doesn't have to be <em>reactive</em> as
+it's often been.  I'd like to be pro-active in terms of resolving
+problems and identifying areas that need to be tackled.
+
+</p>
+
+<p>
+
+The external leadership role is also important.  There are discussions
+about replacing the DPL with a board or committee, and while it's
+important to have these conversations and to evolve our governance, I
+think we should not discount various human factors.  Companies, the
+press and others often want to talk to the leader of the project.  They
+don't want to talk to a mailing list, or a committee and sometimes not
+even to a delegate.  As DPL, I intend to work with delegates on forming
+more connections and partnerships; on building bridges with our allies.
+I'd also like to start an honest conversation about the state of Debian.
+How can we improve our culture?  What are the things holding us back?
+
+</p>
+
+<p>
+
+Finally, it's important to take a step back and look at the big picture.
+This platform is highly critical of Debian in many ways.  I should say
+that I'm a critical person by nature and I tend to emphasise the
+negative side.  Fortunately, I've been able to use that personality flaw
+in positive ways, such as through my QA work where I identify bugs and
+that feedback is used to improve the software.  But it's important to
+highlight the good aspects.  Debian is so unique, so wonderful and so
+special in many ways.  If I didn't believe in Debian, I wouldn't run in
+this DPL election.  I acted as DPL before and know how difficult being
+the DPL can be sometimes.  Yes, I see severe problems in Debian, but I
+firmly believe that together we can solve them!
+
+</p>
+
diff --git a/english/vote/2019/vote_001.wml b/english/vote/2019/vote_001.wml
index 58c3e424661..9c06066c168 100644
--- a/english/vote/2019/vote_001.wml
+++ b/english/vote/2019/vote_001.wml
@@ -57,16 +57,12 @@
     
           <vnominations />
             <ol>
-                <li>Joerg Jaspert [<email joerg@debian.org>] [<a href='https://lists.debian.org/debian-vote/2019/03/msg00039.html'>nomination mail</a>]
-#			[<a href="platforms/joerg">platform</a>]
-                <li>Jonathan Carter [<email jcc@debian.org>] [<a href='https://lists.debian.org/debian-vote/2019/03/msg00040.html'>nomination mail</a>]
-#			[<a href="platforms/jcc">platform</a>]
-                <li>Sam Hartman [<email hartmans@debian.org>] [<a href='https://lists.debian.org/debian-vote/2019/03/msg00044.html'>nomination mail</a>]
-#			[<a href="platforms/hartmans">platform</a>]
-                <li>Martin Michlmayr [<email tbm@debian.org>] [<a href='https://lists.debian.org/debian-vote/2019/03/msg00054.html'>nomination mail</a>]
-#			[<a href="platforms/tbm">platform</a>]
+                <li>Joerg Jaspert [<email joerg@debian.org>] [<a href='https://lists.debian.org/debian-vote/2019/03/msg00039.html'>nomination mail</a>] [<a href="platforms/joerg">platform</a>]
+                <li>Jonathan Carter [<email jcc@debian.org>] [<a href='https://lists.debian.org/debian-vote/2019/03/msg00040.html'>nomination mail</a>] [<a href="platforms/jcc">platform</a>]
+                <li>Sam Hartman [<email hartmans@debian.org>] [<a href='https://lists.debian.org/debian-vote/2019/03/msg00044.html'>nomination mail</a>] [<a href="platforms/hartmans">platform</a>]
+                <li>Martin Michlmayr [<email tbm@debian.org>] [<a href='https://lists.debian.org/debian-vote/2019/03/msg00054.html'>nomination mail</a>] [<a href="platforms/tbm">platform</a>]
                 <li>Simon Richter [<email sjr@debian.org>] [<a href='https://lists.debian.org/debian-vote/2019/03/msg00058.html'>nomination mail</a>]
-#			[<a href="platforms/sjr">platform</a>]
+# [<a href="platforms/sjr">platform</a>]
                 </li>
             </ol>