<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html;
      charset=windows-1252">
  </head>
  <body>
    Mathias,
    <blockquote type="cite"
cite="mid:PAXPR02MB7326F8DFC631B031B3837ABAF7589@PAXPR02MB7326.eurprd02.prod.outlook.com">
      <meta http-equiv="Content-Type" content="text/html;
        charset=windows-1252">
      <meta name="Generator" content="Microsoft Word 15 (filtered
        medium)">
      <style>@font-face
        {font-family:Wingdings;
        panose-1:5 0 0 0 0 0 0 0 0 0;}@font-face
        {font-family:"Cambria Math";
        panose-1:2 4 5 3 5 4 6 3 2 4;}@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0cm;
        font-size:10.0pt;
        font-family:"Calibri",sans-serif;}a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:blue;
        text-decoration:underline;}p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
        {mso-style-priority:34;
        margin-top:0cm;
        margin-right:0cm;
        margin-bottom:0cm;
        margin-left:36.0pt;
        font-size:11.0pt;
        font-family:"Calibri",sans-serif;}.MsoChpDefault
        {mso-style-type:export-only;
        font-size:10.0pt;}div.WordSection1
        {page:WordSection1;}ol
        {margin-bottom:0cm;}ul
        {margin-bottom:0cm;}</style>
      <div class="WordSection1">
        <div>
          <p class="MsoNormal"><a name="Name" moz-do-not-send="true"><span
                style="font-size:11.0pt" lang="EN-US">Hi Even, hi
                everyone,<o:p></o:p></span></a></p>
          <p class="MsoNormal"><span style="mso-bookmark:Name"><span
                style="font-size:11.0pt" lang="EN-US"><o:p> </o:p></span></span></p>
          <p class="MsoNormal"><span style="mso-bookmark:Name"><span
                style="font-size:11.0pt" lang="EN-US">As we (SAP) are
                probably one of the triggers for formalizing this
                policy, let me take a first stab from the perspective of
                a new contributor trying to make a substantial
                contribution:<br>
              </span></span></p>
        </div>
      </div>
    </blockquote>
    (My personal position is that a first contribution that is a
    substantial one is probably not the best way to engage and socialize
    with a project. End of bracket)<br>
    <blockquote type="cite"
cite="mid:PAXPR02MB7326F8DFC631B031B3837ABAF7589@PAXPR02MB7326.eurprd02.prod.outlook.com">
      <div class="WordSection1">
        <div>
          <p class="MsoNormal"><span style="mso-bookmark:Name"><span
                style="font-size:11.0pt" lang="EN-US">
                <br>
                <o:p></o:p></span></span></p>
          <ul style="margin-top:0cm" type="disc">
            <li class="MsoListParagraph"
              style="margin-left:0cm;mso-list:l0 level1 lfo3"><span
                style="mso-bookmark:Name"><span lang="EN-US">Having such
                  a policy greatly increases transparency on what has to
                  be done to make a driver contribution. The outlined
                  criteria reduces the need for lengthy discussions.<br>
                  <br>
                  <o:p></o:p></span></span></li>
            <li class="MsoListParagraph"
              style="margin-left:0cm;mso-list:l0 level1 lfo3"><span
                style="mso-bookmark:Name"><span lang="EN-US">I do
                  specifically like the idea of having a list of
                  responsible contacts. It makes it easier to track
                  personas – even if people change. Still, the list
                  could be outdated at some point. Maybe a regular
                  check-in (via email, virtual meeting, etc.) would be
                  beneficial.
                  <br>
                </span></span></li>
          </ul>
        </div>
      </div>
    </blockquote>
    It is the responsibility of a maintainer listed the contacts that
    can no longer occupy this position to update the list: preferably
    with a replacement maintainer, or if not with an empty name.<br>
    <blockquote type="cite"
cite="mid:PAXPR02MB7326F8DFC631B031B3837ABAF7589@PAXPR02MB7326.eurprd02.prod.outlook.com">
      <div class="WordSection1">
        <div>
          <ul style="margin-top:0cm" type="disc">
            <li class="MsoListParagraph"
              style="margin-left:0cm;mso-list:l0 level1 lfo3"><span
                style="mso-bookmark:Name"><span lang="EN-US">
                  <br>
                  <o:p></o:p></span></span></li>
            <li class="MsoListParagraph"
              style="margin-left:0cm;mso-list:l0 level1 lfo3"><span
                style="mso-bookmark:Name"><span lang="EN-US">To me, the
                  term “significant code addition” should be defined
                  more precisely. Not only in terms of quantity, but
                  also complexity. New drivers typically have a
                  significant footprint in terms of code quantity, but
                  they are isolated. Whereas there may be other
                  contributions with less code, but spanning several
                  software components.<br>
                </span></span></li>
          </ul>
        </div>
      </div>
    </blockquote>
    If you know how to define that more precisely, please propose. But
    this RFC is more about giving a general message, and as noted at the
    end the PSC is the ultimate adjudicator.<br>
    <blockquote type="cite"
cite="mid:PAXPR02MB7326F8DFC631B031B3837ABAF7589@PAXPR02MB7326.eurprd02.prod.outlook.com">
      <div class="WordSection1">
        <div><br>
          <ul style="margin-top:0cm" type="disc">
            <li class="MsoListParagraph"
              style="margin-left:0cm;mso-list:l0 level1 lfo3"><span
                style="mso-bookmark:Name"><span lang="EN-US">At least
                  for corporate contributors, the bullet point of
                  participating in the day-to-day activities is too
                  vague to be seriously accomplishable. While I do well
                  understand, what the goal of the statement is, I still
                  think, the responsibilities have to be defined (and
                  quantified) more clearly as the current description
                  may be interpreted as a bottomless pit for development
                  resources.
                </span></span></li>
          </ul>
        </div>
      </div>
    </blockquote>
    <p>I'm not sure how we can quantify, and I don't like the artificial
      division about "corporate contributors" vs "non-corporate
      contributors". Are non-corporate contributors expected to spend
      their nights & weekends doing all the boring & thankless
      tasks that corporate contributors don't "quantify" as being in
      their area of responsibility ? The message here is that the
      project can't work if people wear blinders and only care about the
      part that they contributed to without considering & investing
      in the project as a whole. Maintaining a project of this size is
      close to be a bottomless pit.</p>
    <p>Even<br>
    </p>
    <pre class="moz-signature" cols="72">-- 
<a class="moz-txt-link-freetext" href="http://www.spatialys.com">http://www.spatialys.com</a>
My software is free, but my time generally not.</pre>
  </body>
</html>