So, I make bits of software, mostly plug-ins for platforms like #DaVinciResolve or #Blender, mostly because I have a particular thing that needs doing that no-one has catered to. And I yoik them up to Codeberg and if I'm feeling organised I'll write them up on my blog, so that anyone else that has the same particular need can benefit too. I have no intention of selling them, because marketing stuff is not something I remotely enjoy doing, testing and bug fixing is too time consuming, and because I consider it payment for all the free software I get to use.
Generally I release everything under the #GPL3, because it's the one I know about. I'm not really a #coder, and I'm far less a #lawyer, so I have no idea if this is the best option.
So the question I want to #AskFedi is: what do you do with small #code projects you write? What license do you release them under and why, and how do you go about distributing them?
I've only ever had one or two people fork my code or make PRs, I don't think a lot of people in my industry also code, so everything I do is a solo project. So I'd be interested in how people find collaborators for stuff they do.
#OpenSource #FreeSoftware #FOSS

Czy jest gdzieś jakieś oficjalne lub prawie oficjalne, ogólnodostępne tłumaczenie licencji GNU GPLv3 na polski?

Krita is a great open source tool for Digital art under GNU General Public License (GPL), version 3.

https://krita.org/en/get-involved/

Someone has a deep knowledge about GPL licenses? I have an existential doubt.

Certain software I use has been releasing new updates without updating the source code, time keeps passing and they don't update it. This attitude represents a violation of the GPL-3 license? I mean: releasing updates of a supposed open source software without updating or showing the changes of the code.

I published a new version of tablizer, a command line tool to manipulate tabular data. New in version 1.3.0:

- it's now possible to modify cells
- lisp support has been removed
- added more unit tests using golang's testscript
- various enhancements and small bug fixes

https://github.com/TLINDEN/tablizer/releases/tag/v1.3.0

@debacle to me the explanation and the Debian vote make sense.
I agree with their opinions even tho I understand the intentions behind the clauses the FSF included in GFDL. The first clause efficiently doesn't affect anything since you can't relicense without compatibility.
The second license is harmful to me, there are environments where drm or other methods to prevent modifications are necessary such as for example medical equipment. This issue also exists in #gpl3

@bitwarden es blinda amb la GPL3 perquè no hi hagi dubtes: és programari lliure

https://www.muylinux.com/2024/11/07/bitwarden-gpl3/

I spent the last two days reviewing code for several pull requests on the #FidoCadJ project.
It is nice to see that it still interests some people! https://github.com/DarwinNE/FidoCadJ #OpenSource #gpl3

Hello Dears! The day has come!
It is with great and undisguised joy that I inform you that my Better /kbin browser extension is officially available under the GPL 3.0 with source code, so you can not only make sure that the extension is safe, but also create forks and almost freely modify it to suit yourself.
https://github.com/MStankiewiczOfficial/BetterKbin

Cześć Kochani! Nadszedł ten dzień!
Z ogromną i nieukrywaną radością informuję Was, że moje rozszerzenie do przeglądarek Better /kbin jest oficjalnie dostępne na licencji GPL 3.0 wraz z kodem źródłowym, dzięki czemu możecie nie tylko upewnić się, że rozszerzenie jest bezpieczne, lecz także tworzyć forki i prawie dowolnie modyfikować je pod siebie.
https://github.com/MStankiewiczOfficial/BetterKbin

RustDesk - це програма для керування віддаленим робочим столом, написана на Rust. Працює з коробки, не потребує додаткового налаштування. Чудова альтернатива TeamViewer та AnyDesk.

Me when I see people complain that GPL3 makes a project hard to monetise because it's incompatible with their proprietary licenses.
#GPL3

@fsfe With the growing popularity of statically linked languages like Rust, Go etc IMHO it could be useful to have a standardized 'LGPL-3.0-or-later WITH LGPL-3.0-linking-exception' ideally with a shorter name. #gpl3 #lgplv3 #gpl

Klipper is a 3d-Printer firmware, it's free software #GPL3 #3dprinting

https://www.klipper3d.org

I'm here pulling my hairs trying to use #scala ScalablyTyped converted sbt plugin to read some typescript library and generate scala code to work under scala.js and just noticed the interesting particularity of it being #gpl3... Now I'm thinking how this affects the building and the license of the resulting thing

I'm slowly developing my own #unix-style #photolibrary application. I licensed it with #GNU #GPL3 license because I want it to be free.

Yesterday night I created automated build pipeline using #Github Actions. It feels so wrong to use proprietary platform to develop #freesoftware . What kind of alternatives there are?

By the way, here's the code:
https://github.com/heikkiket/gallery

Fascinating to see that none of the #Python library to generate #pdf is released under a permissive license. They all use a variation of #GPL3 (LGPL3 or AGPL3). Makes my life less simple than I want.

Why on earth uses #GitHub one of the most stupid and useless license checks for its automatic license detection? This #licensee thing just entirely fails badly as soon as you add #BSD3 code to your #GPL3 and try to attribute it.

Ich hoffe auf eure Erfahrung zu einer #rechtlichen Frage:

Ein Schulbuchverlag möchte Screenshots der MintApps in seinen kommerziellen Büchern nutzen.

Die MintApps selbst stehen unter der #GPL3 - aber was gilt für die generierten Ausgaben?

Ich freue mich über Tipps und Hinweise!

(TK)