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

[David Cook]

Did this discussion ever go anywhere?

David Cook
Systems Librarian
Prosentient Systems
72/330 Wattle St
Ultimo, NSW 2007
Australia

Office: 02 9212 0899
Direct: 02 8005 0595


> -----Original Message-----
> From: koha-devel-bounces at lists.koha-community.org [mailto:koha-devel-
> bounces at lists.koha-community.org] On Behalf Of Owen Leonard
> Sent: Wednesday, 1 June 2016 4:30 AM
> To: koha-devel at lists.koha-community.org
> Subject: [Koha-devel] How do we find consensus on interface changes?
> 
> 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 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/