One thing that some people are miserably failing to understand is that I have opt.ed in to a #FLOSS project to help and make it better, and I never opted in to tolerate you bad attitude or do online searching for you. If you cannot be bothered to search among the open and closed issues, or you are aggressive and hostile, then I should not be bothered to even recognize your issue either! Capiche?
The second maintenance release of the 24.02 series is out with performance optimizations when moving clips in the timeline and across multiple project bins, packaging improvements to macOS and Windows versions and fixes to copy/paste of effects, rotoscoping, Nvidia encoding among others.
If FLOSS is built on the four freedoms, and FLOSS has created an environment that is brittle, then perhaps it’s time for FLOSS to similarly augment the four freedoms.
We have to address this in a fundamental way. The alternative may well be the (eventual) end of FLOSS as we know it.
> Every participant in the FLOSS ecosystem has the right to have their needs met according to the abilities of the other participants.
I like this article a lot. Though struggle with the word "ability" in this formulation. As people have more abilities than they are obliged to give to another single participant in #FLOSS.
The balance giving vs. taking should be added to the definition. You can only expect reasonable reciprocity.
That gives an indication of how hard it is to define the legal aspect.
How do you exercise this right, if you observe it is not honored? Do you claim contribution? And how much do you claim? And do you deny use of the #FLOSS work until proper contribution is forthcoming?
Maybe the #ReciprocalLicense contains a binding vow to contribute within reason and ability and when requested, such that the reasonability of honoring the right can be judged fairly in case of a dispute.
Love free/open/libre software and its community? Come join us! We are looking for coordinators and general volunteers to help us keep and improve this great conference.
Do you contribute to Free/Libre Open Source #FLOSS projects, with work or money? If you do, which one?
If you don't, consider doing it. I could really use some support so I can work on my open #Pythonteaching materials and continue working on #py5.
I love the work that I do, the teaching and these contributions to "the commons", but things have been terrible economically for me this year and my anxiety is going through the roof :(
#Introduction
Hi! I've been on mastodon since summer 2023, but this is my brand new account. I'm interested in #FreeOpenSource#privacy respecting software, #OpenAccess science, and overall community driven spaces. I study #physics, I'm a beginner-level programmer, and would like to start contributing to some #foss#floss projects or sharing my own code. I thought I'd join floss.social to be in a community of like-minded people. I also like #flowers. That's all for now. Have a nice day!
Ich bereite gerade einen größeren Workshop vor mit dem Titel "Kriterien für nachhaltige digitale Werkzeuge"
Was darf eurer Meinung nach auf keinen Fall fehlen? (z.B. #OpenSource / #FLOSS ; #datenschutz 😉 )
So, I don't really do online subscriptions. But since @bitwarden is FOSS and has a real cheap pro account option, I pay for that, even though I never use the pro features.
I try to donate a bit to other FOSS stuff too, but not nearly as regularly, even though I know it's possible to set up auto donations.
I was wondering, could other FOSS stuff use this same model, would it be easier to give regularly if it was framed as an account or membership or something?
Like, would you be more likely to sign up for a "pro account" or a membership or something like that for for example #Gnome, #LibreOffice, #Firefox, #Gimp, #Inkscape, or any other FOSS tool you use regularly, than you are likely to set up an automatic recurring donation – even if the status didn't actually come with any extra features or perks of any kind, other than being a member and supporting something you love?