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.
in reply to Allison Meloy
I think about this all the time. I’m one of these weird people who like, I like credit, but at the same time I would make my own and others's software because of problems I see. Although to be honest, I haven’t vibe coated much because I don’t really know how to speak to people or AI very well, like I don’t know the words to say to make a program the propper way. I’m very low on confidence. If I were going to do this, though, it would be for the benefit of everyone who would use it, and I mean, if somebody steals my work and makes it theirs, I will be a little bit upset, maybe, because I mean give credit where credit is due eh? At the same sleepy token, I’m one of these weird Americans, who don’t care too much about recognition. Sorry this isn’t a very useful answer to your question, I would just honestly say, you know your own worth for your people. That’s what matters. I hope you have a good day though. Thank you for all your work, and I’m sorry that you are getting spammed with so much stress. I honestly am kind of wondering if the 200 requests were from a bot? This is one problem with modern AI stuff like this, AI like people are using AI to find innocent projects and spam them with pole requests.
in reply to Liam Erven
@lerven That’s just it. I don’t like feeling like I’m not in control. Yes, I realize that makes me sound like a control freak, and maybe in some ways I am, but at least I’m honest. But I poured my heart and soul into this, you know?
in reply to Brandon
@serrebi And it’s different if one of you were to submit a PR or to fork the project, like you did with BlindTerm, Brandon. I know you. I trust you. I know you gave me proper credit. @lerven
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.

in reply to Allison Meloy
Sorry you're dealing with all this. It's a tricky situation. I hate that someone overwhelmed you like that. Whatever you decide to do, your work will still be appreciated. I don't have a mac anymore, but I know how much I always wanted something like this. I'll be sure to recommend AVM to anyone looking for a solution. You've got this. @lerven
in reply to Liam Erven
@lerven Technically, the license can require they give you credit, and some of them might even need you to do so in the binary, and definitely in the source code. But the only thing enforcing that is ethics, unless you want to get actually legal about it. If you assume that people you don't know are out to get you, steel your code, pass it off as their own, and gain attention from it, then FOSS isn't the model you want. Most people aren't typically like that, far more common is benefiting from it and not contributing, financially or otherwise, to its continued development. But of course the GNU licenses are viral, so if you use code licensed under a GPL you have to release it. You do still hold the copyrights, though. That's the protection. The licenses do not wave copyright, that's a public domain dedication. Instead they give people rights to do things with your code including distributing modified versions, many of which must credit the original author. Blind people, though, is a difficult audience for this, because many have a history of licensing be damned and doing exactly what you're afraid of. Anyone who has been involved in the blind gaming space over the past decade knows very well about this. @technocounselor
in reply to x0
@lerven There's also the matter that AI-generated code is in this murky area where we're not even sure if it's copyrightable right now as it moves through the courts. If you do not hold copyright to your code, then you cannot license it in any form, FOSS or otherwise. @technocounselor
This entry was edited (Wednesday, November 11, 2026, 9:43 PM)
in reply to Brett Coulstock
@Brett Coulstock @Allison Meloy You can't steal something that is free. If you want to make a commercial product then by all means copyright and make it restrictive so others can't legally build on it, else accept open source for what it is.
in reply to Brett Coulstock
@Brett Coulstock @Allison Meloy I respect the license and I respect the efforts others have put into it so I certainly am willing to provide attribution, but I understand the license is the obligation and if it doesn't require attribution one shouldn't feel butt hurt if they don't get it. If you want that state it in the license. I'm personally someone that just wants to solve problems and it's not important to me to get credit but I'm old, married, not chasing anything in particular so perhaps my needs are different or my ego.
in reply to Allison Meloy
It can happen, and people who care about the code probably don't want open source. I don't care about the code, I care about the results. If someone takes what I did and makes a better version of it, I'm cool with it.
in reply to bscross32
@bscross32 This is particularly true of LLM-generated code. I know what I generate is going to be bad code, if anyone wants it, there's no issue first, because it could hardly be worse, I know I've missed something, and secondly, because the point is to get stuff done, the how and who is not as important as the what. If the forker can get things done better, I'm overjoyed.
in reply to Allison Meloy
I would suggest that the same thing which stops someone from taking your closed source project and reverse-engineering it stops someone from taking a FOSS project, forking it, and claiming it as his own work. That would be the license. I grant you that nobody is going to court over a hobby project, but nobody is going to court over even a cracked trial, let alone a project based on someone's software, either, in most cases. Until a few years ago, you could argue that reverse-engineering a project was hard, but that's far less the case now. The vast majority of licenses insist, quite reasonably, on attribution. To be fair, I have very rarely, I can't remember even one instance, seen someone take FOSS work, fork it, and not attribute to the original author.
in reply to Allison Meloy
As others have suggested I'd just get Claude to review them and ones that are contributing good things can be merged, others its not sure about it can put aside for you to confirm. As for the whole open source Vs having more control, when I make software, I'd obviously be pissed off if people were trying to pass their forks off as their own and not crediting me, but at the end of the day I'm not gonna make my shit proprietary because of it. My reasoning for open sourcing is that I can show that I am making good software, even with the assistance of AI, and I hope one of these days some employer out there may come across my GitHub profile and see all the contributions I've made and stuff I've done myself, and that might increase my potential of being hired. Not just that, I am one of those that gives back, and having total control wouldn't really bring much benefit.
in reply to Alex Chapman
@alexchapman Thank God you’re not all about yourself. You’re awesome Alex, I love you bro. Also, Allison is absolutely wonderful for all of the things that she does for this community. She definitely deserves all the credit for everything she does.
in reply to Dane Stange
@danestange Thanks, and I agree. I also get where Liam is coming from in his replies but I honestly don't see any net positive going down the proprietary rout, if I'm giving something away for free and not making money from it, then I might as well let people have the code. Someone doesn't like a particular way I've layed out the menu, no problem, they can change that. That's just an example of something where there may be one particular person who wants something different but not everyone else wants that change. @technocounselor
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.

in reply to Allison Meloy
Your overthinking it. The entire point of FOSS is that the source code is available and that anybody can take your code and modify it to do whatever they like. It isn't theft, at least legally, because the license requires that the code be open, at least usually. Depending on the license, there may be requirements of attribution for modified source, or the code may be be required to be opened upon request, or similar
in reply to Ethin Probst
@draeand Yes, the license makes it impossible for someone to pass a fork off as their own work, since almost all open-source licenses require attribution, meaning they are required to give you credit for your work. Theft is also impossible, because the license explicitly allows people to modify and distribute the code, and people exercising rights you have explicitly granted them is not theft. For most licenses, people making money off of a fork of your project is also not theft, because it is allowed in the license, and distributing a fork of someone else's project is not back-stabbing either, because you explicitly permitted anyone to do that because that is in the license.
in reply to Allison Meloy
But as others have stated upthread, the entire point of open-source software is to give up control to benefit everyone. If you go out of business, or you stop maintaining the software, I can pick up where you left off and continue it's development in my own way, and I don't need to ask you because the permission grant was in the license. Theft is not theft if I had permission by virtue of an OSS license.
Unknown parent
@DavidGoldfield You know what, it’s fine. I could wish that they would’ve given it a different name to avoid confusion, but at least it’s out there and being used. @emassey0135 @draeand

This website uses cookies. If you continue browsing this website, you agree to the usage of cookies.