ists.koha-community.org] On Behalf Of Owen Leonard
> Sent: Wednesday, 1 June 2016 4:30 AM
> To: koha-devel@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?
Salvete!
> For my part, I'd love to see Owen as benevolent dictator of Koha's GUI.
> I
> think he has the most experience, interest, and skill out of all of us in
> this area.
This is +1 from me, but I should hope this discussion migrates over to the
plain vanilla Koha list. It is where a
Lots of great comments here from everyone.
For my part, I'd love to see Owen as benevolent dictator of Koha's GUI. I
think he has the most experience, interest, and skill out of all of us in
this area.
If he's happy to let us rule ourselves using interface guidelines located in
the developer
It sounds like there is no urgent desire to change the workflow, which
is good because I think that means nobody is upset about any recent
interface changes.
I think that maintaining the interface guidelines and pattern
documentation is a good idea, and I will continue to do so. I don't
think
Yes, I think we need one single document for all developer guidelines, and
I think the Developer's Handbook is the way to go. I think I can highlight
the problem by confessing that I've never even seen ( or least didn't
remember ) that Interface Patterns page before! We need a single source for
rg
Onderwerp: Re: [Koha-devel] How do we find consensus on interface changes?
+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
+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 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
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
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
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
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?
12 matches
Mail list logo