<html>
  <head>
    <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    I like the idea of having a role like 'GUI manager' and also the
    idea of having style guidelines for the interfaces. Actually, I
    think. we already have both of those, as Owen has been working on
    writing documentation about existing patterns on the wiki.<br>
    <br>
    I am not in favor of approving every change that would change the
    screenshots, as that would make the clean-up work much harder, that
    Owen, Aleisha and others have done recently. For bigger changes I'd
    try sending links to screenshots/bug reports to the mailing list to
    get some opinions - if there is no clear direction, we can still
    schedule an official discussion/vote at a meeting.<br>
    <br>
    Katrin<br>
    <br>
    <div class="moz-cite-prefix">On 31.05.2016 23:54, Kyle Hall wrote:<br>
    </div>
    <blockquote
cite="mid:CACpVHfz1u=D9tVnM=AdXYdNYAmCQtu2GENEsweBiXz4yoU=GGQ@mail.gmail.com"
      type="cite">
      <p dir="ltr">Love it! I'd say this is a much better idea!</p>
      <p dir="ltr">Kyle</p>
      <p dir="ltr">Sent from my phone. Please excuse my brevity.</p>
      <div class="gmail_quote">On May 31, 2016 4:25 PM, "Eric Bégin"
        <<a moz-do-not-send="true"
          href="mailto:eric.begin@inlibro.com">eric.begin@inlibro.com</a>>
        wrote:<br type="attribution">
        <blockquote class="gmail_quote" style="margin:0 0 0
          .8ex;border-left:1px #ccc solid;padding-left:1ex">
          <div text="#000000" bgcolor="#FFFFFF"> <font face="Verdana">I
              would rather have a Interface guideline the same way we
              have coding guidelines.<br>
              <br>
              I'm pretty sure that there are some UX design patterns
              available somewhere.<br>
              <br>
              If we would like to have a rules, I would suggest that
              something that changes the screenshot used in the user
              documentation should be approved, especially when it
              doesn't add features.<br>
              <br>
              Eric<br>
            </font><br>
            <div>On 2016-05-31 15:49, Kyle Hall wrote:<br>
            </div>
            <blockquote type="cite">
              <p dir="ltr">I'm concerned that we are going down a road
                where every patch submitted to the Koha project will end
                up requiring a community vote. I think it would be more
                reasonable and efficient to add a community UI manager
                role to the project. Someone who is empowered to make
                executive decisions on this matter. Either that or
                accept that the way team rules on this matter. The
                community votes them in after all!</p>
              <p dir="ltr">Kyle </p>
              <p dir="ltr">Sent from my phone. Please excuse my brevity.</p>
              <div class="gmail_quote">On May 31, 2016 3:32 PM,
                "Christopher Davis" <<a moz-do-not-send="true"
                  href="mailto:cgdavis@uintah.utah.gov" target="_blank">cgdavis@uintah.utah.gov</a>>

                wrote:<br type="attribution">
                <blockquote class="gmail_quote" style="margin:0 0 0
                  .8ex;border-left:1px #ccc solid;padding-left:1ex">Owen,<br>
                  <br>
                  I think that Koha users should voice their
                  opinion/votes as that the<br>
                  Koha software, more or less, belongs to them. Now,
                  what vehicle should<br>
                  we use to collect everyone's opinion/vote (like Survey
                  Monkey, Google<br>
                  forms, IRC voting, etc.) and should there be a
                  committee formed for<br>
                  this purpose? Maybe decisions such as this one should
                  be voted on<br>
                  during Koha Devl IRC meetings?<br>
                  <br>
                  My $0.02 worth,<br>
                  <br>
                  Christopher Davis, MLS<br>
                  Systems & E-Services Librarian<br>
                  Uintah County Library<br>
                  <a moz-do-not-send="true"
                    href="mailto:cgdavis@uintah.utah.gov"
                    target="_blank">cgdavis@uintah.utah.gov</a><br>
                  <a moz-do-not-send="true"
                    href="tel:%28435%29%20789-0091%20ext.261"
                    value="+14357890091" target="_blank">(435) 789-0091
                    ext.261</a><br>
                  <a moz-do-not-send="true"
                    href="http://uintahlibrary.org" rel="noreferrer"
                    target="_blank">uintahlibrary.org</a><br>
                  <a moz-do-not-send="true"
                    href="http://basinlibraries.org" rel="noreferrer"
                    target="_blank">basinlibraries.org</a><br>
                  <a moz-do-not-send="true"
                    href="http://facebook.com/uintahcountylibrary"
                    rel="noreferrer" target="_blank">facebook.com/uintahcountylibrary</a><br>
                  <a moz-do-not-send="true"
                    href="http://instagram.com/uintahcountylibrary"
                    rel="noreferrer" target="_blank">instagram.com/uintahcountylibrary</a><br>
                  <br>
                  <br>
                  On Tue, May 31, 2016 at 1:01 PM, Owen Leonard <<a
                    moz-do-not-send="true"
                    href="mailto:oleonard@myacpl.org" target="_blank"><a class="moz-txt-link-abbreviated" href="mailto:oleonard@myacpl.org">oleonard@myacpl.org</a></a>>

                  wrote:<br>
                  >> Could the new features which you are
                  proposing be optional?<br>
                  ><br>
                  > They're not really new features, they're just
                  changes to the way<br>
                  > existing features look. We can't build options
                  for every change we<br>
                  > want to make to the interface. We need to make
                  educated choices about<br>
                  > what we think is the best way for things to work.
                  We may not always<br>
                  > get it right, but it's our job to make the
                  choice.<br>
                  ><br>
                  >   -- Owen<br>
                  ><br>
                  > --<br>
                  > Web Developer<br>
                  > Athens County Public Libraries<br>
                  > <a moz-do-not-send="true"
                    href="http://www.myacpl.org" rel="noreferrer"
                    target="_blank">http://www.myacpl.org</a><br>
                  > _______________________________________________<br>
                  > Koha-devel mailing list<br>
                  > <a moz-do-not-send="true"
                    href="mailto:Koha-devel@lists.koha-community.org"
                    target="_blank">Koha-devel@lists.koha-community.org</a><br>
                  > <a moz-do-not-send="true"
href="http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel"
                    rel="noreferrer" target="_blank">http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel</a><br>
                  > website : <a moz-do-not-send="true"
                    href="http://www.koha-community.org/"
                    rel="noreferrer" target="_blank">http://www.koha-community.org/</a><br>
                  > git : <a moz-do-not-send="true"
                    href="http://git.koha-community.org/"
                    rel="noreferrer" target="_blank">http://git.koha-community.org/</a><br>
                  > bugs : <a moz-do-not-send="true"
                    href="http://bugs.koha-community.org/"
                    rel="noreferrer" target="_blank">http://bugs.koha-community.org/</a><br>
                  _______________________________________________<br>
                  Koha-devel mailing list<br>
                  <a moz-do-not-send="true"
                    href="mailto:Koha-devel@lists.koha-community.org"
                    target="_blank">Koha-devel@lists.koha-community.org</a><br>
                  <a moz-do-not-send="true"
href="http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel"
                    rel="noreferrer" target="_blank">http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel</a><br>
                  website : <a moz-do-not-send="true"
                    href="http://www.koha-community.org/"
                    rel="noreferrer" target="_blank">http://www.koha-community.org/</a><br>
                  git : <a moz-do-not-send="true"
                    href="http://git.koha-community.org/"
                    rel="noreferrer" target="_blank">http://git.koha-community.org/</a><br>
                  bugs : <a moz-do-not-send="true"
                    href="http://bugs.koha-community.org/"
                    rel="noreferrer" target="_blank">http://bugs.koha-community.org/</a><br>
                </blockquote>
              </div>
              <br>
              <fieldset></fieldset>
              <br>
              <pre>_______________________________________________
Koha-devel mailing list
<a moz-do-not-send="true" href="mailto:Koha-devel@lists.koha-community.org" target="_blank">Koha-devel@lists.koha-community.org</a>
<a moz-do-not-send="true" href="http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel" target="_blank">http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel</a>
website : <a moz-do-not-send="true" href="http://www.koha-community.org/" target="_blank">http://www.koha-community.org/</a>
git : <a moz-do-not-send="true" href="http://git.koha-community.org/" target="_blank">http://git.koha-community.org/</a>
bugs : <a moz-do-not-send="true" href="http://bugs.koha-community.org/" target="_blank">http://bugs.koha-community.org/</a></pre>
            </blockquote>
            <br>
          </div>
        </blockquote>
      </div>
      <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>