@mrmasterkeyboard @xinit the #RightToFork is elemental to #FLOSS and necessary for #OpenSource to exist.

  • As much as I'm not a fan of seemingly abandoned forks of my works, I am not in the position to restrict or ban those.
    • And people OFC have their right to make a #fork whenever they want to do so!

We ain't criticizing corporations that maintain outdated inhouse forks out of principle, and I think that #evi isn't a "fork for the sake of forking" but actually does things different and apparenty "irreconcileable" to the mainline Project.

Nit to mention EVERYTHING IS "#POLITICAL" - including "apoliticalness"!

Forks · greyhat-academy/lists.d

List of useful things. Contribute to greyhat-academy/lists.d development by creating an account on GitHub.

GitHub

Today I am #ThursdayThankful for the #NGinX #FreeSoftware web server project.

It turns out that #SoftwareFreedom is essential: When a #corporate owner decides they will dismiss freedom for users and developers, the #RightToFork the project under a different name, gives much-needed continuity and allows the community to continue.

https://www.phoronix.com/news/Nginx-Forked-To-Freenginx

Core NGINX Developer Forks Web Server Into Freenginx

Maxim Dounin as one of the longtime core developers of the Nginx web server announced the creation today of a new fork of the project called Freenginx.

@brembs FLOSS is a necessary condition for the #RightToFork.
https://eve.gd/2023/07/26/whats-the-point-of-having-open-scholarly-infrastructures-and-how-do-we-test-their-resilience/

As for #protocols.io, the terms of use are very clear that it's proprietary https://www.protocols.io/terms, with some parts being CC-BY. To be properly forkable it would need
1) the website itself and its software to be freely licensed,
2) the database to be CC-0 (it's only metadata anyway),
3) data dumps to be published somewhere (at least PMC?).

@adam42smith @timolueke @RenkeSiems @rmounce

What’s the point of having open scholarly infrastructures and how do we test their resilience?

It is sometimes easy, when discussing openness, to get bogged down in the technical weeds. People often want detail and specifics: what open license should I use? Precisely how much revenue do I need to keep in reserve safely to wind-down an organization? When does advocacy become lobbying?

Martin Paul Eve