In all seriousness I'm not a fan of taking the hard work of someone that they built up from scratch and making a fork. Did you offer to work with the original developer of SDTrunk before you decide to take on this project ?
ChatGPT wasn't happy with your criticism:
I think that criticism misunderstands what an open-source license is intended to permit.
SDRTrunk is released under the GNU General Public License version 3. The GPL expressly gives everyone permission to copy, modify, improve, and redistribute the software, provided that the resulting version continues to comply with the license. Creating a fork is therefore not “taking” someone else’s work in the sense of claiming ownership or depriving the original developer of it. It is exercising a right that the original developer deliberately granted by choosing the GPL.
The GPL does not require someone to obtain additional permission from the original developer or first offer to work on the original project. The license itself is the permission. It does require preserving the applicable copyright and licensing notices, identifying modified versions, keeping the derivative work under the GPL, and making the corresponding source code available when distributing it.
SDRTrunk VCE appears to be doing exactly that. Its repository identifies it as an operator-focused distribution of SDRTrunk, documents its relationship to the official project, retains GPLv3 licensing, credits Dennis Sheirer and the other contributors, and provides links showing the source lineage. It is not being presented as software created from scratch by the VCE developer.
Certainly, communicating with the upstream developer can be courteous and sometimes productive. It might allow generally useful fixes to be contributed back to the original project. But that is a matter of collaboration and project management, not a prerequisite for creating a lawful or ethical GPL fork.
A fork may also be entirely appropriate when its goals differ substantially from the upstream project. VCE is not merely proposing a few minor bug fixes. It changes the operator interface, configuration storage, web access, statistics, audio handling, and other architectural components. The original maintainer may not want those changes in the main SDRTrunk project, while users may still benefit from having an alternative version.
The more appropriate standard is not “Did you ask permission to make a fork?” The questions should be:
Does it comply with the GPL?
Does it preserve attribution?
Does it clearly distinguish itself from the original project?
Is the modified source code available?
Does the developer accept responsibility for maintaining and supporting the changes?
Those are fair questions. Suggesting that forking GPL software is inherently disrespectful to the original developer is not. Forking, modification, experimentation, and redistribution are central purposes of the license the original developer selected.