<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Just so I do not sound like a Norwegian-hater (which would be very
hard, I can't imagine anyone hating Norwegians! ), I want to specify
that my comment was not suggesting a specific fork. That would be
messy.<br>
<br>
I would have thought this feature could have been generalized enough
to be named something else than "Norvegian", and if something needed
to be hardcoded, it could be a patch easily downloadable, maintained
by the Norwegian community. (Not sure what that implies, so please
use salt...:) )<br>
<br>
But then again, I don't mind the name as much as the fact that it
brought a lot with it, filled my logs, forced me to update my
servers and realise that it must be "compiling" (and failing) every
single time i get on those pages, thus impacting performance...
Then writing an email and sounding like Norwegians are the worst :-)<br>
<br>
I hope to visit Norway one day...<br>
<br>
<br>
<div class="moz-signature">
<style type="text/css">
.moz-signature {
color: #FFFFFF;
}
.sig_inlibro {
padding-top : 2px;
color: #888888;
font-family : "Trebuchet MS", verdana;
font-size: 90%;
}
.sig_content {
border-top: 2px solid #DDDDDD;
border-bottom: 2px solid #BFD13D;
background-color : #F6F6F6;
padding-left:10px;
}
.sig_inlibro a:visited, .sig_inlibro a:hover, .sig_inlibro a:link {
text-decoration: none;
color: #005B85;
}
.nom {
color: #005B85;
font-weight : bold;
}
.inlibro, .in {
color: #BFD13D;
}
.libro {
color: #005B85;
}
.in, .libro {
font-size : 120%;
}
.desc {
margin-bottom: 0;
padding-bottom: 5px;
}
.small {
font-size: 80%;
}
.tagline {
color : #00BCE4;
}
.sig_footer {
padding-left : 10px;
background-color : #EEEFEA;
}
</style>
<div class="sig_inlibro">
<div class="sig_content"> <span class="nom">Philippe Blouin,</span><br>
<span class="tagline small">Responsable du développement
informatique</span><br>
<p class="desc small"> Tél. : (888) 604-2627<br>
<a href="mailto:philippe.blouin@inLibro.com">philippe.blouin@inLibro.com</a>
</p>
</div>
<div class="sig_footer"> <span class="in">in</span><span
class="libro">Libro</span> <span class="tagline small">|
pour esprit libre |</span> <a class="small"
href="http://www.inLibro.com">www.inLibro.com</a> </div>
</div>
</div>
<div class="moz-cite-prefix">On 02/11/2016 04:38 AM, Magnus Enger
wrote:<br>
</div>
<blockquote
cite="mid:CABg6UYGVgYvQg5P_XXo_rsEvLu496iBJwukkQT3dhNGwvD8bgA@mail.gmail.com"
type="cite">
<pre wrap="">Dear Community!
A quote from another thread on koha-devel:
"I look at the code, and beside wondering why that custom feature
[Norwegian patron DB] is so profoundly imbricated into master Koha, I
was wondering what is not working."
I think this raises an interesting question. Should we let features
into Koha that are only of interest to libraries in one or a small
number of countries? Or should we confine those features to
country-specific forks?
The quote above implies (I think) that support for the Norwegian
patron DB should be in a country-specific fork.
On the other hand, the project implementing Koha for public libraries
in Turkey has been criticized for not integrating their customizations
into Koha. To which someone replied that the customizations were not
of much interest to libraries outside Turkey.
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" features that all Norwegian
public libraries will be looking for when they are choosing between
Koha or some proprietary system. Should we be telling them "Nope, you
can't use the real Koha, but you can use this fork over here"? That
will not increase their confidence in choosing Koha, I suspect.
That said, I do think some principles should be applied:
- Strive to make even the country specific features as general as
possible, so that others can use them as starting points for similar
features.
- Strive to make the features as unobtrusive as possible.
And maybe, in time, the plugin system can be made powerful enough that
it can handle some or all of the country-specific features?
Thoughts?
Best regards,
Magnus Enger
Libriotech
_______________________________________________
Koha-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Koha-devel@lists.koha-community.org">Koha-devel@lists.koha-community.org</a>
<a class="moz-txt-link-freetext" href="http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel">http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel</a>
website : <a class="moz-txt-link-freetext" href="http://www.koha-community.org/">http://www.koha-community.org/</a>
git : <a class="moz-txt-link-freetext" href="http://git.koha-community.org/">http://git.koha-community.org/</a>
bugs : <a class="moz-txt-link-freetext" href="http://bugs.koha-community.org/">http://bugs.koha-community.org/</a>
</pre>
</blockquote>
<br>
</body>
</html>