<html>
  <head>
    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <br>
    <div class="moz-cite-prefix">On 26.06.2014 22:47, Jeff Backus wrote:<br>
    </div>
    <blockquote
cite="mid:CAF5ev_j+1DQzKEPf8N+hGM6rYgJZzw6H=S6z6kiRCDqwFZePyQ@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div class="gmail_extra"><br>
          <div class="gmail_quote">On Thu, Jun 26, 2014 at 12:42 PM,
            Kevin Fenzi <span dir="ltr">&lt;<a moz-do-not-send="true"
                href="mailto:kevin@scrye.com" target="_blank">kevin@scrye.com</a>&gt;</span>
            wrote:<br>
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
              I'm not sure the entire group of provenpackagers would
              like to be<br>
              notified of such trivial patches waiting. Is there a group
              of<br>
              provenpackagers who would be willing to query for and
              apply these?<br>
              <br>
            </blockquote>
          </div>
          <br>
        </div>
        <div class="gmail_extra">Maybe a simple way to allow
          non-provenpackagers to highlight these "trivial bug" patches
          would be via a perma-bug a-la FE-NEEDSPONSOR? That way there
          is a centralized place inclined provenpackages can check which
          doesn't require following a mailing list and is simple enough
          even us n00bs can figure it out. :) <br>
          <br>
          I presume the implementation cost is miniscule, so might at
          least be worth an experiment.<br>
          <br>
        </div>
      </div>
    </blockquote>
    So the thing that should be avoided IMO is not defining well enough
    how the procedure should work, to avoid getting swamped with patches
    which require additional work to apply. The requirement to fill out
    post a "New Package Request" style form to the bug should allow most
    of the work to be scripted, and ideally the proven packager would
    just need to look at the patch, and if happy, fire the script.<br>
    <br>
    So maybe such a policy could look something like this [1].
    Contrarily to what I wrote initially, I think it might actually make
    sense to allow also non-packagers to file such requests, and it
    would provide another way of showing off experience which will
    eventually lead to one getting sponsored.<br>
    <br>
     Sandro<br>
    <br>
    [1]
<a class="moz-txt-link-freetext" href="https://fedoraproject.org/wiki/User:Smani/Trivial_Patch_Policy_%28draft%29">https://fedoraproject.org/wiki/User:Smani/Trivial_Patch_Policy_%28draft%29</a><br>
  </body>
</html>