<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    +1 for RFC because it's a "standard" and there's already enough
    acronyms around.<br>
    <br>
    <br>
    <div class="moz-cite-prefix">On 02.09.2014 15:53, Nathan Woodrow
      wrote:<br>
    </div>
    <blockquote
cite="mid:CAAi8Yg_jdcAEsBSa4Gfcuy=cFkBg=sRwRq5Ga2-=DDkvVDtGUw@mail.gmail.com"
      type="cite">
      <p dir="ltr">+1 to QEP</p>
      <p dir="ltr">Mainly because the name is clear. I didn't know what
        RFC was when I first started so google sorted that out and it
        will for QEP for new users. If you are going to write a QEP/RFC
        you are already involved so you will know what it is, we will
        make it clear on the website. Its also nice and personal for the
        project like PEP is for Python.</p>
      <div class="gmail_quote">On Sep 2, 2014 11:19 PM, "Andreas
        Neumann" <<a moz-do-not-send="true"
          href="mailto:a.neumann@carto.net">a.neumann@carto.net</a>>
        wrote:<br type="attribution">
        <blockquote class="gmail_quote" style="margin:0 0 0
          .8ex;border-left:1px #ccc solid;padding-left:1ex">
          Hi,<br>
          <br>
          I also prefer RFC.<br>
          <br>
          Andreas<br>
          <br>
          Am <a moz-do-not-send="true" href="tel:02.09.2014%2013"
            value="+61209201413">02.09.2014 13</a>:06, schrieb Marco
          Hugentobler:<br>
          > +1 for RFC, since universally understood.<br>
          ><br>
          > Regards,<br>
          > Marco<br>
          ><br>
          > On <a moz-do-not-send="true" href="tel:02.09.2014%2015"
            value="+61209201415">02.09.2014 15</a>:01, Larry Shaffer
          wrote:<br>
          >> Hi,<br>
          >><br>
          >> I need to start using the new QEP/RFC setup (today
          actually),<br>
          >> specifically for some sponsored work. I don't want
          the sponsor to<br>
          >> think the QGIS project is indecisive, so I propose a
          vote on the<br>
          >> naming of the process, since there is some
          disagreement.<br>
          >><br>
          >> QEP or RFC?<br>
          >><br>
          >> +0 for QEP (I'm fine with RFC, as well).<br>
          >><br>
          >> I think RFC is a bit dry, though universally
          understood. QEP should<br>
          >> not confuse the public, since the dev group actually
          interested in<br>
          >> using them is fairly small. QEP is clearly spelled
          out in the repo<br>
          >> name. QEP shows a renewed configuration over the
          older, existing RFC<br>
          >> process.<br>
          >><br>
          >> Lastly, QEP pays homage to Python's PEP. I think QGIS
          would not be as<br>
          >> popular as it is today if it were not for Python
          integration.<br>
          >><br>
          >> Regards,<br>
          >><br>
          >> Larry Shaffer<br>
          >> Dakota Cartography<br>
          >> Black Hills, South Dakota<br>
          >><br>
          >><br>
          >> _______________________________________________<br>
          >> Qgis-developer mailing list<br>
          >> <a moz-do-not-send="true"
            href="mailto:Qgis-developer@lists.osgeo.org">Qgis-developer@lists.osgeo.org</a><br>
          >> <a moz-do-not-send="true"
            href="http://lists.osgeo.org/mailman/listinfo/qgis-developer"
            target="_blank">http://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br>
          ><br>
          ><br>
          > --<br>
          > Dr. Marco Hugentobler<br>
          > Sourcepole -  Linux & Open Source Solutions<br>
          > Weberstrasse 5, CH-8004 Zürich, Switzerland<br>
          > <a moz-do-not-send="true"
            href="mailto:marco.hugentobler@sourcepole.ch">marco.hugentobler@sourcepole.ch</a>
          <a moz-do-not-send="true" href="http://www.sourcepole.ch"
            target="_blank">http://www.sourcepole.ch</a><br>
          > Technical Advisor QGIS Project Steering Committee<br>
          ><br>
          ><br>
          ><br>
          > _______________________________________________<br>
          > Qgis-developer mailing list<br>
          > <a moz-do-not-send="true"
            href="mailto:Qgis-developer@lists.osgeo.org">Qgis-developer@lists.osgeo.org</a><br>
          > <a moz-do-not-send="true"
            href="http://lists.osgeo.org/mailman/listinfo/qgis-developer"
            target="_blank">http://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br>
          ><br>
          <br>
          _______________________________________________<br>
          Qgis-developer mailing list<br>
          <a moz-do-not-send="true"
            href="mailto:Qgis-developer@lists.osgeo.org">Qgis-developer@lists.osgeo.org</a><br>
          <a moz-do-not-send="true"
            href="http://lists.osgeo.org/mailman/listinfo/qgis-developer"
            target="_blank">http://lists.osgeo.org/mailman/listinfo/qgis-developer</a></blockquote>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
Qgis-developer mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Qgis-developer@lists.osgeo.org">Qgis-developer@lists.osgeo.org</a>
<a class="moz-txt-link-freetext" href="http://lists.osgeo.org/mailman/listinfo/qgis-developer">http://lists.osgeo.org/mailman/listinfo/qgis-developer</a></pre>
    </blockquote>
    <br>
  </body>
</html>