https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25870
--- Comment #72 from David Cook <[email protected]> --- (In reply to Blou from comment #70) > We (inLibro) had a different solution for the autocomplete, but were told it > needed to be built over this. I can't see this in the bug reports. Was it mentioned in a dev meeting or an email or something? > Of course, we haven't waited, to the benefit of our users base. But I find > very dumb to prevent Koha from having it for six years because of > architectural zealotism (bz27113 depending on this, not "making 25870 one > right" I clarify). @Blou, I would suggest that you re-read the Koha Community Code of Conduct and review the language that you're using: https://koha-community.org/about/policy/code-of-conduct/ . While it was designed for events, I think it's something that we still try to adhere to more broadly. -- Personally, I don't think I've seen any zealotry, but I think we do sometimes have overly dogmatic approaches to certain architectural decisions for sure. I think it comes from a place of wanting to build a standards-based system that is maintainable by many people and for a long-time, but sometimes mistakes are made or things go in a suboptimal way. I've had some very high performance changes never make it into Koha for a number of reasons, and that's unfortunate but it also happens in group projects sometimes. I think instead of getting frustrated with each other, we can communicate and work together to find a solution. I think everyone is trying their best and has good intentions. -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list -- [email protected] To unsubscribe send an email to [email protected] website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
