Owen, You bring up a good question? Could the new features which you are proposing be optional? I know that having the features optional would just "kick the can" on interface consensus down the road until the next interface design surfaces. -- Christopher Davis, MLS Systems & E-Services Librarian Uintah County Library cgdavis@uintah.utah.gov (435) 789-0091 ext.261 uintahlibrary.org basinlibraries.org facebook.com/uintahcountylibrary instagram.com/uintahcountylibrary On Tue, May 31, 2016 at 12:30 PM, Owen Leonard <oleonard@myacpl.org> wrote:
Do we need a procedure for getting consensus on Koha interface changes?
I'm thinking about this issue in part because of a couple of interface changes I've been working on. One for Bug 16421:
Move hold edit actions into dropdown menu https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16421 (screenshot: https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=51111)
...and another for Bug 11375:
Patron permission names are untranslatable https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11375 (screenshot: https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=51847)
When proposing a change like that should there be a more inclusive process than getting one sign-off and one QA approval? If so, how do we decide what kind of changes require wider approval? How do we solicit opinions from a wider audience?
Or is the process working well as-is?
-- Owen
-- Web Developer Athens County Public Libraries http://www.myacpl.org _______________________________________________ Koha-devel mailing list Koha-devel@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/