if your project is so difficult to compile into a usable binary that not even seasoned maintainers can do it, are you really making #FreeSoftware, or is it a "letter of the law but not the spirit of the law" situation?
I wonder what the opinion of actual devs and distro maintainers are.
If a #FreeSoftware program on #Linux would be like "you can not open two files of the same name at the same time from two different directories", people would be complaining how #OpenSource and Linux are just not ready for massive adoption.
When Microsoft Excel does this for 30 years straight, it's just "it is what it is".
I love Inkscape. I use it in my personal life, I use it to make illustrations for my papers and teaching materials in my professional life.
It is the best vector graphic software. It can do curves, shapes, turn bitmaps into curves and shapes. Turn curves and shapes into bitmaps. What else do you need? Triangles? It has them, too!
Also, follow the great @doctormo for devlogs and news about the project.
It is that time of the year (I see some people boosting my posts from last year), so let's do another #FreeSoftwareAdvent to appreciate all the great #FreeSoftware out there. I have definitely explored and made use of a bunch of software for the first time this year, so let's shout some out.
Now that the release of GIMP 3 is on the horizon, maybe it would be a great time to change its controversial name to something more fitting for the GNU/Linux environment.
I was thinking about changing it to "GIMP Image Manipulation Program" so it can finally ascend to the plane of recursive acronyms. 😂
I use "permissive" for MIT and BSD licenses, because they are not restricting developers. Free software is freedom for the users, not the developers. "Permissive" means that the developers are permitted to take away the right of their users by locking down a derivative or redistributed work that was originally free software.
Like, how a "Permissive" regulation might let you cause damage to others without consequence.
What I found strange is how they separate licenses by being #OpenSource or #FreeSoftware. AFAIK, most popular licenses like GPL, MIT, BSD, MPL, etc. conform to both the #FSF and the #OSI standards. I guess what they meant was #CopyLeft vs permissive licenses?
@smxi honestly, I don't really mind that much what RedHat is doing. No one is entitled to get updates to a software from you just because you gave them an earlier version.
As long as they don't restrict your GPL guaranteed rights for the software itself, they can condition the future business relationship with their customers on whatever they want.
@clacke@smxi I don't think what you describe here is correct. I think what you describe here is true for their publicly available repositories. As a customer you have the right to ask for the exact source code that your binary packages were compiled from, and I am not aware of any instance of them not honoring them.
@clacke@smxi The GPL does not have any clause that makes a user entitled to any future versions or any tech support.
Therefore, it is not a violation of the GPL to terminate business relationship based on an action that is allowed by the license but not allowed by the business agreement.
Red Hat can't come and take away the code they already gave you, and can't stop you redistributing it. They have all the rights to not talk to you any more though.
@smxi if at least developers used #GPL / #AGPL, the corporations at least were forced to contribute back in one way or an other, but due to the rampant use of MIT and BSD licenses, they can literally get away without doing anything beneficial for the wider ecosystem while using other people's code (those other people let them do it).
I think the proliferation of MIT and BSD licenses really made the #FreeSoftware free rider problem much worse than it should be.
@smxi I think that the huge rate of burnout in developers that cause issues time and time again can be traced back to this attitude of "I will license it permissively to get it into everything". When the code gets into everything without compensation, the pressure of responsibility mounts, and bad things happen.
It is my personal belief that one's mental health doesn't worth the "bragging right" of one's code getting into a wide range of proprietary garbage.
hi @organicmaps, I have mapped the sidewalks (with bike paths) around one of the largest avenues in Seoul, Songpa-daero in #openStreetMap
When I plan a cycle route along this road however, the app makes some weird decisions, like crossing from left to right side multiple times, sometimes not even on the crosswalks.
Did I use an improper tagging scheme? or did I create some edge case the app is not prepared for?
@ianthetechie@organicmaps I at least would expect the use of crossings to be minimized with some type of expected time penalty on those, but I know nothing about routing engines, so idk.