last platform version

diff --git a/hacking/debian/dpl-2009/platform.html b/hacking/debian/dpl-2009/platform.html
index 82fe520..24a0da9 100644 (file)
--- a/hacking/debian/dpl-2009/platform.html
+++ b/hacking/debian/dpl-2009/platform.html
@@ -100,14 +100,14 @@ The <B>main points</B> of my platform are as follows:
 in discussions and as the responsible of the project agenda.</I></LI><LI CLASS="li-itemize"><I>I will provide a constant stream of DPL
 activity news, to be frozen and posted </I><I><EM>monthly</EM></I><I> to
 </I><I><TT>d-d-a</TT></I><I>.</I></LI><LI CLASS="li-itemize"><I>To resolve the impasse of vocal
-minorities, I will apply mechanisms that makes rough
-</I><I><EM>consensus</EM></I><I> emerge when it exists.</I></LI><LI CLASS="li-itemize"><I>I will push for more </I><I><EM>gradual</EM></I><I> and
+minorities, I will apply mechanisms that make rough </I><I><EM>consensus</EM></I><I>
+emerge when it exists.</I></LI><LI CLASS="li-itemize"><I>I will push for more </I><I><EM>gradual</EM></I><I> and
 </I><I><EM>rewarding</EM></I><I> access paths to Debian.</I></LI><LI CLASS="li-itemize"><I>I will push to diminish </I><I><EM>strong package
-ownership</EM></I><I> whenever it conflicts with package quality.</I></LI><LI CLASS="li-itemize"><I>I will do my best to help out, with money
-and other resources, to support contributors get-togethers.</I></LI></UL></DIV><P>The reminder of this platform provides background information about me
-(Section <A HREF="#sec:intro">1</A>), describes the above points with more
-details (Section <A HREF="#sec:goals">2</A>), and also highlights some more
-focused plans for my term (Section <A HREF="#sec:itches">2.3</A>).</P><!--TOC section Introduction-->
+ownership</EM></I><I> when it conflicts with package quality.</I></LI><LI CLASS="li-itemize"><I>I will do my best to support, with money
+and other resources, contributors get-togethers.</I></LI></UL></DIV><P>The reminder of the platform provides background information about me
+(Section <A HREF="#sec:intro">1</A>), describes the above points in more detail
+(Section <A HREF="#sec:goals">2</A>), and highlights more specific plans for my
+term (Section <A HREF="#sec:itches">2.3</A>).</P><!--TOC section Introduction-->
 <H2 CLASS="section"><!--SEC ANCHOR --><A NAME="htoc1">1</A>  Introduction</H2><!--SEC END --><P>
 <A NAME="sec:intro"></A></P><!--TOC subsection Who am I-->
 <H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc2">1.1</A>  Who am I</H3><!--SEC END --><P>
@@ -277,7 +277,7 @@ activities</A>). In those cases, we should suggest—or even force if
 needed—collaborative maintenance. It can provide a more acceptable
 exit strategy than public, yet useless, shaming.</P><DIV CLASS="mantra">
 <DIV CLASS="center"><I>I will push to diminish </I><I><EM>strong package
-ownership</EM></I><I> whenever it conflicts with package quality.</I></DIV>
+ownership</EM></I><I> when it conflicts with package quality.</I></DIV>
 </DIV><!--TOC paragraph Vocal minorities-->
 <H5 CLASS="paragraph"><!--SEC ANCHOR -->Vocal minorities</H5><!--SEC END --><P>
 Our mailing lists have substantially improved over the last 5
@@ -304,8 +304,8 @@ fests) that they are in disagreement with the rest of the project and
 better stop beating the dying horse, or indicate that they are on the
 right path.</P><DIV CLASS="mantra">
 <DIV CLASS="center"><I>To resolve the impasse of vocal
-minorities, I will apply mechanisms that makes rough
-</I><I><EM>consensus</EM></I><I> emerge when it exists.</I></DIV>
+minorities, I will apply mechanisms that make rough </I><I><EM>consensus</EM></I><I>
+emerge when it exists.</I></DIV>
 </DIV><!--TOC paragraph Face-to-face meetings-->
 <H5 CLASS="paragraph"><!--SEC ANCHOR -->Face-to-face meetings</H5><!--SEC END --><P>
 Meetings are essential to improve the quality of collaboration within
@@ -323,8 +323,8 @@ possible joining others to work on specific topics.</P><P>A simple metric for de
 required amount of money, can be the number <I>x</I> of other developers
 asking for that. If and <EM>when</EM> money will become an issue, I do
 not see any showstopper in organizing specific sponsoring campaigns.</P><DIV CLASS="mantra">
-<DIV CLASS="center"><I>I will do my best to help out, with money
-and other resources, to support contributors get-togethers.</I></DIV>
+<DIV CLASS="center"><I>I will do my best to support, with money
+and other resources, contributors get-togethers.</I></DIV>
 </DIV><!--TOC paragraph Derivatives-->
 <H5 CLASS="paragraph"><!--SEC ANCHOR -->Derivatives</H5><!--SEC END --><P>
 We are part of the FOSS ecosystem, in which patches flow both

diff --git a/hacking/debian/dpl-2009/platform.pdf b/hacking/debian/dpl-2009/platform.pdf
index c176322..a2f7cc1 100644 (file)
Binary files a/hacking/debian/dpl-2009/platform.pdf and b/hacking/debian/dpl-2009/platform.pdf differ

diff --git a/hacking/debian/dpl-2009/platform.txt b/hacking/debian/dpl-2009/platform.txt
index 035d5d6..bddd135 100644 (file)
--- a/hacking/debian/dpl-2009/platform.txt
+++ b/hacking/debian/dpl-2009/platform.txt
@@ -25,17 +25,17 @@ running for DPL. summary The main points of my platform are as follows:
    - I will provide a constant stream of DPL activity news, to be frozen
    and posted monthly to d-d-a.
    - To resolve the impasse of vocal minorities, I will apply mechanisms
-   that makes rough consensus emerge when it exists.
+   that make rough consensus emerge when it exists.
    - I will push for more gradual and rewarding access paths to Debian.
-   - I will push to diminish strong package ownership whenever it
-   conflicts with package quality.
-   - I will do my best to help out, with money and other resources, to
-   support contributors get-togethers.
+   - I will push to diminish strong package ownership when it conflicts
+   with package quality.
+   - I will do my best to support, with money and other resources,
+   contributors get-togethers.
   
   
-  The reminder of this platform provides background information about me
-(Section 1), describes the above points with more details (Section 2),
-and also highlights some more focused plans for my term (Section 2.3).
+  The reminder of the platform provides background information about me
+(Section 1), describes the above points in more detail (Section 2), and
+highlights more specific plans for my term (Section 2.3).
   
 
 1  Introduction
@@ -205,7 +205,7 @@ activities (37)). In those cases, we should suggest—or even force if
 needed—collaborative maintenance. It can provide a more acceptable
 exit strategy than public, yet useless, shaming.
   mantra 
-  I will push to diminish strong package ownership whenever it conflicts
+    I will push to diminish strong package ownership when it conflicts
                          with package quality.
     
 Vocal minorities
@@ -235,7 +235,7 @@ stop beating the dying horse, or indicate that they are on the right
 path.
   mantra 
    To resolve the impasse of vocal minorities, I will apply mechanisms
-           that makes rough consensus emerge when it exists.
+            that make rough consensus emerge when it exists.
     
 Face-to-face meetings
    Meetings are essential to improve the quality of collaboration within
@@ -255,8 +255,8 @@ required amount of money, can be the number x of other developers asking
 for that. If and when money will become an issue, I do not see any
 showstopper in organizing specific sponsoring campaigns.
   mantra 
-    I will do my best to help out, with money and other resources, to
-                  support contributors get-togethers.
+      I will do my best to support, with money and other resources,
+                      contributors get-togethers.
     
 Derivatives
    We are part of the FOSS ecosystem, in which patches flow both