SSPL :: Remember, remember, the velvet November


node:	SSPL
template:	4
parent:	open source a slobodny softver
owner:	Ljubes
viewed by:
created:	18.01.2021 - 09:46:50

cwbe coordinatez:
101
63540
63542
63747
8829535

ABSOLUT
KYBERIA

permissions
you:	r,
system:	public
net:	yes

Neviem ci ste to postrehli ale po MongoDB prechadza na SSPL uz aj ElasticSearch/Kibana :-(

Ak teda poskytujete tretim stranam sluzbu (ktora vyuziva ELK/MongoDB) tak mate na vyber:
1. ostat na verzii (ktora nie je pod SSPL) a zamrznut v case
2. prejst na novu verziu, dalej pouzivat ju bez platenia ale zverejnit kod svojej sluzby
3. prejst na novu verziu, zacat platit a nezverejnit kod svojej sluzby
4. najst alternativu a prestat pouzivat to co je pod SSPL

src: https://anonymoushash.vmbrasseur.com/2021/01/14/elasticsearch-and-kibana-are-now-business-risks

co si o tom myslite?

000001010006354000063542000637470882953508890994

Asi hlupa otazka, ale snazim sa v tom zorientovat. Podla toho co citam, SSPL vravi o poskytovani softveru ako "service", typickym prikladom je teda napriklad AWS.

Takze moja otazka je: Ked niekto vytvori produkt (softver), ktory na pozadi pouziva MongoDB a tento produkt predava tretim stranam nie ako sluzbu, ale ako hotovy produkt, musi tiez postupvoat podla tejto licencie a teda bud zverejnit kod svojho produktu alebo platit?

00000101000635400006354200063747088295350889099408891012

Musi im poskytnut zdrojaky (SSPL je odvodena od GPL-3) a tie tretie strany su tiez viazane SSPL. Ci sa to vztahuje na celu aplikaciu ze musi byt relicencovana SSPL len preto ze vola mongo, to nie je jasne.

GPL len hovori ze komu das skompilovany program (jedno ci zadarmo alebo za peniaze to GPL neriesi), ten musi mat pristup ku zdrojakom. To neznamena ze sa zdrojaky GPL musia zverejnit, iba ze prijemcu nesmies obmedzovat ako s nimi dalej nalozi.

000001010006354000063542000637470882953508890981

2021-07-12: OpenSearch 1.0 is released!

Today is a really good day for the OpenSearch project. Since its start, the goal has been to quickly produce a version of OpenSearch that’s ready to use in production environments. After a ton of work by the OpenSearch community, we’re thrilled to announce the first general availability (GA) release of OpenSearch 1.0. Everyone in this highly-engaged and diverse community should be proud of the accomplishment in reaching this milestone together.

OpenSearch is a community-driven, open source search and analytics suite derived from Apache 2.0 licensed Elasticsearch 7.10.2 & Kibana 7.10.2. It consists of a search engine daemon (OpenSearch), a visualization and user interface (OpenSearch Dashboards), and advanced features from Open Distro for Elasticsearch like security, alerting, anomaly detection and more.

src: https://opensearch.org/blog/updates/2021/07/opensearch-general-availability-announcement/

000001010006354000063542000637470882953508831424

AWS bude maintainovat svoje forky
https://aws.amazon.com/blogs/opensource/stepping-up-for-a-truly-open-source-elasticsearch/

000001010006354000063542000637470882953508830044

Vie niekto popisat, kde konci "every supporting piece of software"? Spustim si elastic niekde, tak povedzme musim zverejnit pluginy a pod, ale nejake sluzby s tym komunikujuce uz su mimo, nie?

00000101000635400006354200063747088295350883004408830431

jak sa pise na tom blogu - to asi rozhodnu az pravnici/sudy.

000001010006354000063542000637470882953508829844

podla mna mali nechat oddeleny plateny xpack a nechat zakladne featury.
takto (dufam) pomozu viac projektorm ako odfe (open distro for elasticsearch), lebo tie su momentalne v stave "nejak to funguje.." a evidentne maju problem dalej sledovat a "backportovat" zmeny v elasticu, ktorych je neurekom a u niektorych mam pocit ze su robene vyslovene len preto (resp takym sposobom) aby vysachovali "konkurenciu', ktora si nieco postavila na ich starsom kode.
taka tragikomedia..

000001010006354000063542000637470882953508829771

nechapem co zmenou licencie z AGPL na SSPL ziskali - ma ich ta nova licencia viac ochranit pred Amazonom?

ked im Amazon kaslal na AGPL tak sa im asi vykasle aj na toto, nie?

edit: pisem o MongoDB, nie o Elastic-u

00000101000635400006354200063747088295350882977108829782

Oni nemali agpl, mali https://www.apache.org/licenses/LICENSE-2.0 ak dobre pozeram. (https://www.elastic.co/blog/licensing-change)

0000010100063540000635420006374708829535088297710882978208829938

pardon, ja pisem o MongoDB a ti mali AGPL pre core, Apache pre drivery

ak mali Elastic ASL 2.0 tak to bola ich blbost :)

000001010006354000063542000637470882953508829683

Ked to tak chucu mat, tak preco nie?
GPL a spol boli vymyslene vo svete kde takych sluzieb bolo minimum, ked sa zacali rozbiehat sluzby, vzniklo AGPL.

000001010006354000063542000637470882953508829559

zaujimave. treba asi vydat vlastnu livenciu pre inu cast softwaru, ktora povie, ze nesmies zverejnit ziadnu cast kodu. akceptujes ju az po akceptovani licencie pre ELK. tym zrusis platnost tej SSPL.

SSPL je nejaky pravnicky joke

00000101000635400006354200063747088295350882955908829561

co ja viem; kamos to zhrnul takto:
"toto je podla na dlhsiu debatu, realne to podla man cele zacalo s aws
oni robia to ze zoberu opensource tool, zautomatizuju to jebnu k sebe do infra ako service, takze tito chlapici nemaju co zrat lebo svoj cloud nepredaju nikomu
tam nastala prva zmena licencie napr u redisu a okrem inych aj elasticu
ta zmena znamenala ze sa coraz tazsie dalo deploynut v aws, aws konkretne pri ES reagoval vytvorenim OpenDistro projektu - co je vlastne skopceny ES doplneny o nejake features ktore elastic hodil za paywall"

0000010100063540000635420006374708829535088295590882956108829714

nieco na tom bude. pise sa tam "It also protects our continued investment in developing products that we distribute for free and in the open by restricting cloud service providers from offering Elasticsearch and Kibana as a service without contributing back."

000001010006354000063542000637470882953508829559088295610882971408829740

tak je to pochopitelne spindirna to predavat ako produkt ... na druhu stranu sa mali snazit asi o nejaku dohodu s aws / etc

000001010006354000063542000637470882953508829559088295610882971408829715

no a potom je https://opendistro.github.io/for-elasticsearch/
:))))