I’ve been wrestling with how to ask this question for a long time. For the most part, I like open source and I definitely understand the benefits. Some great people have contributed to my projects over these past few months. But it seems to me like it’s a double-edged sword. If I don’t take seriously these 240 pr’s in AVM, what will stop this individual from taking their fork of my project and passing it off as their own work? They are already hosting it on their own site. Now it could be that the changes they have implemented are mostly or all good, and I will merge them to main, but I don’t know this person, so I don’t know if I trust them not to steal my work. Doesn’t the very nature of open source coding open developers up to potential theft and backstabbing? Am I making a mountain out of a molehill? Is there something I’m not understanding? I’m eager to hear the thoughts of others because mine are not accomplishing anything except leading to more questions.
Welcome to Friendica.Eskimo.Com
Home of Censorship Free Hosting

Dane Stange
in reply to Allison Meloy • • •Brandon
in reply to Allison Meloy • • •Liam Erven
in reply to Allison Meloy • • •Allison Meloy
in reply to Liam Erven • • •Brandon
in reply to Allison Meloy • • •Liam Erven
in reply to Brandon • • •Allison Meloy
in reply to Brandon • • •Liam Erven
in reply to Allison Meloy • • •Brandon
in reply to Allison Meloy • • •Liam Erven
in reply to Allison Meloy • • •Eden Linnea
in reply to Allison Meloy • • •Joe Brockmeier
in reply to Allison Meloy • • •@lerven "Control" and "open source" do not go together. That's sort of the point.
If having control of something is more important to you than sharing it and letting other people use it, modify it, and redistribute it, then you probably don't want to do open source. Which is fine*, but FOSS is about giving up control beyond what the license requires.
"Stealing" someone's work assumes that work wasn't given freely -- but if you attach a FOSS license to something and put it online, you're inviting anybody and everybody take the code and modify it, redistribute it, etc. You can, of course, put conditions on use of a trademarked name or similar to make sure nobody is distributing something modified lord-knows-how under your project's name. That's fair and allowed.
If you just want to let people use your software without redistributing it, etc., there are non-FOSS licenses that you could use. As long as you're not calling it "open source" nobody has a reason to complain if you do that. I mean, they *will* probably because humans...
* Fine as long as you're not distributing something that, say, is derived from a GPL'ed project. In that case, of course, you're obligated to do what the upstream license(s) require.
Allison Meloy
in reply to Joe Brockmeier • • •Liam Erven
in reply to Joe Brockmeier • • •Justin Ekis
in reply to Allison Meloy • • •x0
in reply to Liam Erven • • •x0
in reply to x0 • • •Liam Erven
in reply to x0 • • •Nanook
in reply to Allison Meloy • •Brett Coulstock
in reply to Nanook • • •Nanook
in reply to Brett Coulstock • •Brett Coulstock
in reply to Nanook • • •Nanook
in reply to Brett Coulstock • •bscross32
in reply to Allison Meloy • • •Tech Singer
in reply to bscross32 • • •Tech Singer
in reply to Allison Meloy • • •Alex Chapman
in reply to Allison Meloy • • •Dane Stange
in reply to Alex Chapman • • •Alex Chapman
in reply to Dane Stange • • •JimmyChezPants 🇨🇦
in reply to Allison Meloy • • •Do you categorize Open Source and Free Software differently in your mind?
I'm not sure how to answer this in actuality, but in a spirit of trying to help: Free Software is given freely, and basically, you've got the creation date of your git repo and the git blame record to show who came up with which ideas. But that's just medals for your chest; Free software is free as in speech, but also free as in beer.
The only reason you would be concerned about someone "stealing" your code, is if you intend to close your source at some point and profit from it. In which case, why open it in the first place?
It would be pretty crass, I should say, to start out with an "Open" model which is not, in fact, shared freely with the world, and which you intend to slam the door on at some point in the future. That has been Silicon Valley's grift, these last few decades, and the guillotine plans are being drawn up in many towns and villages.
I don't think you have those intentions, but maybe you have ingrained capitalist anxiety about merely sharing the product of your work with the world, in hopes it helps someone.
ZynAddSubFX is one of my favorite virtual synthesizers to use.
It has a fork project called Yoshimi, which as far as I can tell, just changes the UI somewhat.
Both work fine, both are members of the Free Software music palette. In the end, you have control of what you pull and what you don't, because it's your project, and if this person doesn't feel appreciated and forks your project so they can install all of their enhancements, as long as you both are using the GPL, you will still be free to pull in the features you like from the fork, and everyone will be happily using your stuff to get through their day.
Only the slop machines steal work. Forking and changing and making your fork available for those who prefer your vision is not just legit, it's the right way to do things.
Ethin Probst
in reply to Allison Meloy • • •Elijah Massey
in reply to Ethin Probst • • •Allison Meloy
in reply to Elijah Massey • • •Ethin Probst
in reply to Allison Meloy • • •Allison Meloy
Unknown parent • • •Allison Meloy
Unknown parent • • •Allison Meloy
Unknown parent • • •