https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42164
--- Comment #11 from Mark Hofstetter <[email protected]> --- I am a fan of the core plugin idea. Koha development itself is hard enough and therefore slow. Making well defined interfaces/contracts to/for an outside plugin will make it possible to phase in larger developments more easy. (search, aquisition etc) In the epoch of AI we will see and need more and more of this approach, because we should make it easy to replace huge chunks of the software but keep the core business reliable. For this problem-domain (ie search) this approach is really well suited because: + people using elastic don't have to care + zebra can be kept as long as people dare + search is a somewhat soft topic: + it's easy to test for simple case, just switch the engine + the results are somewhat "open" I therefore suggest phasing it in slowly, ie incorporate this patch which does nothing bad, and let early adopters, very small libraries test it out Then we can flesh out the core plugin idea -- You are receiving this mail because: You are the assignee for the bug. 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/
