Post #2919543

2026-04-23 15:24 UTC

@fossham@mastodon.radio I don’t see me forking - can you highlight what bit I forked? You’re describing to me what I have done. I am using Debian stable repo, Debian backports repo and 1 custom repo containing a few packages. They are used to build the image and if you cat the apt sources list, they’re Debian. We’re benefitting from Debian’s time proven infrastructure and processes because that is where the packages come from, and 95% of my work on this is upstreamed by me being on the team. You can check my ddpo & Debian portfolio if you need to see my packages, backports, sponsors and the like to see what I’m doing upstream already. No one else on the hams team wants to generate, test and maintain it so I’m not doing it under the banner of the team or the distribution or hosting a download link at Debian.org or debian.net.

Replies (2)

@fossham@mastodon.radio 2026-04-23 15:34

@red@woof.tech Sure; happy to help you with this: 1. New name has historically communicated "THIS IS A FORK" very loudly and clearly in the FOSS world. 2. Separate installer images, outside of Debian proper. 3. Separate website that describes the product as "Packet, Digital Modes and Portable Ham Radio on Linux", failing to mention Debian (and that Debian also provides these functions). 1/2

Open ##2919544
@fossham@mastodon.radio 2026-04-23 15:40

@red@woof.tech In the 21st century, Linux users know that security response is priority: distros like Debian and Fedora have huge communities so there are always developer eyeballs and capability, despite national holidays, vacations, illnesses. 0-days are more likely to be fixed in such a large team. One-off forks have proven to be single points of failure. If you'd like to be the exception to that rule, be more clear about the 95% Debian / 5% you, and what your cybersecurity plan is for that 5%. 2/2

Open ##2919545