<html>
  <head>
    <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <p>+1 requite and inline<br>
    </p>
    <br>
    <div class="moz-cite-prefix">On 11.01.2017 19:25, Chris Cormack
      wrote:<br>
    </div>
    <blockquote
      cite="mid:761584F9-B9A1-43B9-A5CC-D0358915E78E@catalyst.net.nz"
      type="cite">Yes to the requiring POD and 1 vote for inline (the
      majority is inline already)<br>
      <br>
      Chris<br>
      <br>
      <div class="gmail_quote">On 12 January 2017 7:21:49 AM NZDT, Nick
        Clemens <a class="moz-txt-link-rfc2396E" href="mailto:nick@bywatersolutions.com"><nick@bywatersolutions.com></a> wrote:
        <blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt
          0.8ex; border-left: 1px solid rgb(204, 204, 204);
          padding-left: 1ex;">
          <div dir="ltr">
            <div>
              <div>
                <div>
                  <div>
                    <div>
                      <div>
                        <div>
                          <div>Hello Koha developers,<br>
                            <br>
                          </div>
                          At the last developers meeting there was some
                          discussion about guidelines for requiring POD
                          during QA.<br>
                          <br>
                        </div>
                        Our current guideline is here:<br>
                        <a moz-do-not-send="true"
href="https://wiki.koha-community.org/wiki/Coding_Guidelines#PERL13:_POD">https://wiki.koha-community.org/wiki/Coding_Guidelines#PERL13:_POD</a><br>
                        <br>
                      </div>
                      The discussion centered on a few questions:<br>
                    </div>
                    1 - Should (basic) POD be required when making a
                    small change to a module that has no existing POD.
                    The answer to this seemed to be generally yes, and
                    Barton volunteered to assist. Anyone else wanting to
                    help add POD is more than welcome to join him :-)<br>
                    <br>
                  </div>
                  2 - Where should POD go? Inline or after __END__
                  Please offer your opinion if you feel strongly.<br>
                  <br>
                </div>
                As I am cutting it close to sending before the meeting I
                think we can push off adding/updating the guideline
                until the February meeting.<br>
                <br>
              </div>
              Thanks!<br>
              <br>
            </div>
            Nick (kidclamp)<br>
            <br>
          </div>
        </blockquote>
      </div>
      <br>
      -- <br>
      Sent from my Android device with K-9 Mail. Please excuse my
      brevity.
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
Koha-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Koha-devel@lists.koha-community.org">Koha-devel@lists.koha-community.org</a>
<a class="moz-txt-link-freetext" href="http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel">http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel</a>
website : <a class="moz-txt-link-freetext" href="http://www.koha-community.org/">http://www.koha-community.org/</a>
git : <a class="moz-txt-link-freetext" href="http://git.koha-community.org/">http://git.koha-community.org/</a>
bugs : <a class="moz-txt-link-freetext" href="http://bugs.koha-community.org/">http://bugs.koha-community.org/</a></pre>
    </blockquote>
    <br>
  </body>
</html>