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

[Eric Bégin]

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 
> <mailto: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 <mailto:cgdavis at uintah.utah.gov>
>     (435) 789-0091 ext.261 <tel:%28435%29%20789-0091%20ext.261>
>     uintahlibrary.org <http://uintahlibrary.org>
>     basinlibraries.org <http://basinlibraries.org>
>     facebook.com/uintahcountylibrary
>     <http://facebook.com/uintahcountylibrary>
>     instagram.com/uintahcountylibrary
>     <http://instagram.com/uintahcountylibrary>
>
>
>     On Tue, May 31, 2016 at 1:01 PM, Owen Leonard <oleonard at myacpl.org
>     <mailto: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
>     <mailto: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
>     <mailto: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/

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20160531/1643a344/attachment.html>