Minor improvments to jcc's platform

1 files changed, 8 insertions, 7 deletions

diff --git a/english/vote/2019/platforms/jcc.wml b/english/vote/2019/platforms/jcc.wml
index 7572d9002eb..7d6e05b9987 100644
--- a/english/vote/2019/platforms/jcc.wml
+++ b/english/vote/2019/platforms/jcc.wml
@@ -74,7 +74,7 @@
 
 <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 community processes 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>
@@ -92,9 +92,9 @@
 <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>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 Buster (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 Women 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>
@@ -133,10 +133,10 @@
 <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>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 too 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>
+<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 practice a stoistic outlook  as DPL and spend some time reading up on diplomacy, if elected.</LI>
 </OL>
 
 <H2> 5. Acknowledgements </H2>
@@ -150,9 +150,10 @@
 <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.00">1.00</a>: Initial public release.</LI>
 <LI><a href="https://salsa.debian.org/jcc/dpl-platform/tags/1.01">1.01</a>: Improve summary on high-level goals.</LI>
 <LI><a href="https://salsa.debian.org/jcc/dpl-platform/tags/1.02">1.02</a>: Build a styled html, plain wml and plain text version of this page, fix photo, no text changes.</LI>
+<LI><a href="https://salsa.debian.org/jcc/dpl-platform/tags/1.03">1.03</a>: Merge <a href="https://salsa.debian.org/jcc/dpl-platform/merge_requests/1">MR#1</a> and <a href="https://salsa.debian.org/jcc/dpl-platform/merge_requests/2">MR#2</a>, fixing various mistakes. Fix minor style issue and changelog wording.</LI>
 </ul>
 
 <BR>