Just adding a link
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10459
This reports contains some (older) discussions on this topic.
Note that timestamps are not per se updated automatically.
Van: koha-devel-boun...@lists.koha-community.org
namens
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
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 Librari
> 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
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?
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
matte
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
a
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" 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
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 cha
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
+1 for 'Style guidelines' and 'GUI manager'
Regarding the Wiki:
https://wiki.koha-community.org/wiki/Interface_patterns
https://wiki.koha-community.org/wiki/Developers_Handbook (1.2 User
Interface)
Should this be consolidated in one document?
Marc
Am 01.06.2016 um 02:43 schrieb Kyle Hall:
I
We are getting too much managers here :)
Van: koha-devel-boun...@lists.koha-community.org
namens Marc Véron
Verzonden: woensdag 1 juni 2016 08:13:30
Aan: koha-devel@lists.koha-community.org
Onderwerp: Re: [Koha-devel] How do we find consensus on interface change
12 matches
Mail list logo
