[Koha-devel] How do we find consensus on interface changes?

[Kyle Hall]

I think you've summarized everything nicely. If Owen were interested in
taking some official mantel I would not be opposed ; )

I think we need to focus on expediency and uniformity primarily. I think we
basically have those two things, but they could both be improved. I would
be more than happy to work on adding a UI guidelines section to the wiki.
For those interested, here is what I've done so far:
https://wiki.koha-community.org/wiki/Developers_Handbook

It's a bit rough now because it's really guideline-centric, but I think
over time it will come into its own quite nicely. Constructive criticism is
welcome!

Kyle

<https://secure2.convio.net/cffh/site/Donation2?df_id=1395&FR_ID=4715&PROXY_ID=2706639&PROXY_TYPE=20&1395.donation=form1&s_src=CHORUS&s_subsrc=CHAADOEB>

http://www.kylehall.info
ByWater Solutions ( http://bywatersolutions.com )
Meadville Public Library ( http://www.meadvillelibrary.org )
Crawford County Federated Library System ( http://www.ccfls.org )

On Tue, May 31, 2016 at 5:26 PM, Katrin <katrin.fischer.83 at web.de> wrote:

> 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.
>
> 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.
>
> Katrin
>
>
> On 31.05.2016 23:54, Kyle Hall wrote:
>
> Love it! I'd say this is a much better idea!
>
> Kyle
>
> Sent from my phone. Please excuse my brevity.
> On May 31, 2016 4:25 PM, "Eric Bégin" <eric.begin at inlibro.com> wrote:
>
>> I would rather have a Interface guideline the same way we have coding
>> guidelines.
>>
>> I'm pretty sure that there are some UX design patterns available
>> somewhere.
>>
>> 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.
>>
>> Eric
>>
>> On 2016-05-31 15:49, Kyle Hall wrote:
>>
>> 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!
>>
>> Kyle
>>
>> Sent from my phone. Please excuse my brevity.
>> On May 31, 2016 3:32 PM, "Christopher Davis" <cgdavis at uintah.utah.gov>
>> wrote:
>>
>>> Owen,
>>>
>>> I think that Koha users should voice their opinion/votes as that the
>>> Koha software, more or less, belongs to them. Now, what vehicle should
>>> we use to collect everyone's opinion/vote (like Survey Monkey, Google
>>> forms, IRC voting, etc.) and should there be a committee formed for
>>> this purpose? Maybe decisions such as this one should be voted on
>>> during Koha Devl IRC meetings?
>>>
>>> My $0.02 worth,
>>>
>>> Christopher Davis, MLS
>>> Systems & E-Services Librarian
>>> Uintah County Library
>>> cgdavis at uintah.utah.gov
>>> (435) 789-0091 ext.261 <%28435%29%20789-0091%20ext.261>
>>> uintahlibrary.org
>>> basinlibraries.org
>>> facebook.com/uintahcountylibrary
>>> instagram.com/uintahcountylibrary
>>>
>>>
>>> On Tue, May 31, 2016 at 1:01 PM, Owen Leonard < <oleonard at myacpl.org>
>>> oleonard at myacpl.org> wrote:
>>> >> Could the new features which you are proposing be optional?
>>> >
>>> > They're not really new features, they're just changes to the way
>>> > existing features look. We can't build options for every change we
>>> > want to make to the interface. We need to make educated choices about
>>> > what we think is the best way for things to work. We may not always
>>> > get it right, but it's our job to make the choice.
>>> >
>>> >   -- Owen
>>> >
>>> > --
>>> > Web Developer
>>> > Athens County Public Libraries
>>> > http://www.myacpl.org
>>> > _______________________________________________
>>> > Koha-devel mailing list
>>> > Koha-devel at lists.koha-community.org
>>> > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
>>> > website : http://www.koha-community.org/
>>> > git : http://git.koha-community.org/
>>> > bugs : http://bugs.koha-community.org/
>>> _______________________________________________
>>> Koha-devel mailing list
>>> Koha-devel at lists.koha-community.org
>>> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
>>> website : http://www.koha-community.org/
>>> git : http://git.koha-community.org/
>>> bugs : http://bugs.koha-community.org/
>>>
>>
>>
>> _______________________________________________
>> Koha-devel mailing listKoha-devel at lists.koha-community.orghttp://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
>> website : http://www.koha-community.org/
>> git : http://git.koha-community.org/
>> bugs : http://bugs.koha-community.org/
>>
>>
>>
>
> _______________________________________________
> Koha-devel mailing listKoha-devel at lists.koha-community.orghttp://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : http://www.koha-community.org/
> git : http://git.koha-community.org/
> bugs : http://bugs.koha-community.org/
>
>
>
> _______________________________________________
> Koha-devel mailing list
> Koha-devel at lists.koha-community.org
> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : http://www.koha-community.org/
> git : http://git.koha-community.org/
> bugs : http://bugs.koha-community.org/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20160531/3a12b8c9/attachment.html>