Dear Colleagues,
For what it's worth, consider how Mozilla offers Firefox with its
"market place" of extensions/plug-ins. Yes many of the extensions
overlap and have duplicate features, but that just makes Firefox that
much more flexible, open, and lovable (IMHO). Sure there might be
neglected
devel-boun...@lists.koha-community.org] För Tajoli Zeno
Skickat: den 11 februari 2016 10:47
Till: Magnus Enger <mag...@enger.priv.no>; koha-devel@lists.koha-community.org
Ämne: Re: [Koha-devel] Country-specific forks?
Hi Magnus and all,
Il 11/02/2016 10:38, Magnus Enger ha scritto:
> So
Hi Magnus and all,
Il 11/02/2016 10:38, Magnus Enger ha scritto:
So do we want one Koha to rule them all, including country-specific
features, or do we want one fork per country?
Personally, I prefer the former. In the case of the Norwegian patron
DB, that is one of the 2-3 "must have"
A really easy solution to implement would be to watch a directory (say
plugins) during the very end of the compilation time.
Using something like Sub::Override
(http://search.cpan.org/~ovid/Sub-Override-0.09/lib/Sub/Override.pm)
would allow the plugin to redefine behaviors.
2016-02-11 11:47
I think that specific dev should have been generalized as a way to sync
external sources (as we do with LDAP). A "plugin" could provide a specific
configuration/maintenance script.
2016-02-11 15:59 GMT-03:00 Jesse :
> Magnus, as the original dev of the NorwegianPatronDB
lists.koha-community.org
[mailto:koha-devel-boun...@lists.koha-community.org] Namens Julian Maurice
Verzonden: donderdag 11 februari 2016 11:24
Aan: koha-devel@lists.koha-community.org
Onderwerp: Re: [Koha-devel] Country-specific forks?
+1 to "one Koha to rule them all"
+1000 to a more po
That sounds awesome! I'd love to see a proof on concept for that, or maybe
a full patch! ; )
http://www.kylehall.info
ByWater Solutions ( http://bywatersolutions.com )
Meadville Public Library ( http://www.meadvillelibrary.org )
Crawford County Federated Library System ( http://www.ccfls.org )
Problems that quickly come to mind with this solution:
* It will prevent 2 different plugins to redefine the same subroutine
* If the subroutine "signature" change, the compatibility with existing
plugins will be broken
Le 11/02/2016 13:14, Jonathan Druart a écrit :
> A really easy solution to