Send Koha-devel mailing list submissions to
    koha-devel@lists.koha-community.org

To subscribe or unsubscribe via the World Wide Web, visit
    https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
or, via email, send a message with subject or body 'help' to
    koha-devel-request@lists.koha-community.org

You can reach the person managing the list at
    koha-devel-owner@lists.koha-community.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Koha-devel digest..."


Today's Topics:

1. Re: Elasticsearch vs OpenSearch (Victor Grousset/tuxayo)
2. Re: Why is config ($KOHA_CONF) stored in memcached ?
(dcook@prosentient.com.au)


----------------------------------------------------------------------

Message: 1
Date: Mon, 3 May 2021 17:45:16 +0200
From: Victor Grousset/tuxayo <victor@tuxayo.net>
To: dcook@prosentient.com.au, koha-devel@lists.koha-community.org
Subject: Re: [Koha-devel] Elasticsearch vs OpenSearch
Message-ID: <2ba45522-9de1-d469-9ee3-681f0ec8a487@tuxayo.net>
Content-Type: text/plain; charset=utf-8; format=flowed

Hi :)

Found another legal analysis that contradicts the first one:
https://writing.kemitchell.com/2021/01/20/Righteous-Expedient-Wrong.html

Even if contradictory, that still helps to understand the situation.
Divergence still means something about the eventual risks.

Some thoughts after reading:
"SaaS capture”, “Amazon problem”, “Google problem” are legitimate
concerns. But this controversy shows how hard it is to address it.

Even if the copyleft doesn't affect Koha. It seems clear that it affects
management services (what is the extent of that?).
So what about if a hosting management tool is under a copyleft license?
IIUC it can't be released under the SSPL. So that would force to only
use permissive licensed management tools.
So it's not a legal blocker but that restrict possibilities. And
actually leads to a loss of freedom on these tools because copyleft
software help about that.

Some non-Koha thoughts:
1. Does having the hosting management tools of Amazon or Google or
Microsoft would really help not them having a quasi monopolistic share
on the hosting of databases et other tools? (public interest PoV)
Well actually it's to have them buy the version with the other license.

2. Do ElasticSearch actually lacks money to maintain the same level of
work on the ES stack and give the investors a reasonable return of
investment? (accounting that it was a risky one so the return should be
more than the average)
As for the second part, there is actually no limit on the ROI (imagine
if loans worked like that, lol), especially with venture capital. So
there can be doubt on the legitimacy of the additional need of revenue.

Cheers,

--
Victor Grousset/tuxayo


------------------------------

Message: 2
Date: Tue, 4 May 2021 13:35:23 +1000
From: <dcook@prosentient.com.au>
To: "'Julian Maurice'" <julian.maurice@biblibre.com>,
    <koha-devel@lists.koha-community.org>
Subject: Re: [Koha-devel] Why is config ($KOHA_CONF) stored in
    memcached ?
Message-ID: <042101d74096$843ef6f0$8cbce4d0$@prosentient.com.au>
Content-Type: text/plain;    charset="utf-8"

Oh I am very interested. I've been wanting to get rid of XML::Simple for many years, and this would be a huge step forward.

I'll have to review this sometime...

David Cook
Software Engineer
Prosentient Systems
Suite 7.03
6a Glen St
Milsons Point NSW 2061
Australia

Office: 02 9212 0899
Online: 02 8005 0595

-----Original Message-----
From: Koha-devel <koha-devel-bounces@lists.koha-community.org> On Behalf Of Julian Maurice
Sent: Monday, 3 May 2021 5:06 PM
To: koha-devel@lists.koha-community.org
Subject: Re: [Koha-devel] Why is config ($KOHA_CONF) stored in memcached ?

If you're interested there is also bug 28278 that divides by 3 the time needed to parse $KOHA_CONF:
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28278

Le 02/05/2021 à 14:52, Julian Maurice a écrit :
> Patch is ready to be tested at
> https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28276 ;)
>
> Le 01/05/2021 à 14:53, Tomas Cohen Arazi a écrit :
>> I vote for fixing it so the file is only hit the first time.
>>
>> El vie, 30 abr 2021 a las 14:19, Julian Maurice
>> (<julian.maurice@biblibre.com <mailto:julian.maurice@biblibre.com>>)
>> escribió:
>>
>> Hi all,
>>
>> Maybe it's a dumb question, but I don't understand why the config
>> is
>> stored in memcached as:
>> - memcached server address is in this config, so we need to read
>> $KOHA_CONF file first in order to connect to memcached server
>> - config is kept in memory forever ($C4::Context::context), so we
>> shouldn't need the cache once starman has started.
>>
>> If you add a warning in Koha::Config::read_from_file, you'll see
>> that
>> the file is read 3 times per worker, even when the config already
>> exist
>> in cache (it's read 4 times when the cache is empty).
>> It's read each time we call Koha::Cache->new (+ in
>> C4::Context->new if
>> the cache is empty)
>>
>> Shouldn't we read the file only in C4::Context->new (without
>> using
>> cache), and make Koha::Cache use C4::Context->config instead ?
>>
>> -- Julian Maurice
>> BibLibre
>> _______________________________________________
>> Koha-devel mailing list
>> Koha-devel@lists.koha-community.org
>> <mailto:Koha-devel@lists.koha-community.org>
>>
>> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
>>
>> <https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
>> >
>> website : https://www.koha-community.org/
>> <https://www.koha-community.org/>
>> git : https://git.koha-community.org/
>> <https://git.koha-community.org/>
>> bugs : https://bugs.koha-community.org/
>> <https://bugs.koha-community.org/>
>>
>>
>>
>> --
>> Tomás Cohen Arazi
>> Theke Solutions (http://theke.io <http://theke.io/>) ✆ +54 9351
>> 3513384
>> GPG: B2F3C15F
>

--
Julian Maurice
BibLibre
_______________________________________________
Koha-devel mailing list
Koha-devel@lists.koha-community.org
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : https://www.koha-community.org/ git : https://git.koha-community.org/ bugs : https://bugs.koha-community.org/




------------------------------

Subject: Digest Footer

_______________________________________________
Koha-devel mailing list
Koha-devel@lists.koha-community.org
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : https://www.koha-community.org/
git : https://git.koha-community.org/
bugs : https://bugs.koha-community.org/


------------------------------

End of Koha-devel Digest, Vol 186, Issue 4
******************************************