Your reasoning is circular and fallacious.
I do not know why the code hasn't been released, but I do have my own ideas of why it shouldn't (for a good cause).
Violating FCC regulations is not justification to break a license (GPL or otherwise).
I have tried my best to obtain a copy of the source from
@hggomes on numerous occasions in the past on this forum to no avail, with his most recent claims of "I don't have time, but I will
soon" being outright
fabrications in the end. I continue to strongly encourage folks considering this firmware to question
why @hggomes is so insistent on keeping the source closed. If he has time to continue developing the fork, there is
no reason the source cannot be uploaded to GitHub (assuming he has continued to commit on his local fork, it is a trivial matter of 2-3 commands and waiting for the initial push to complete).
I'm glad there are more members of this forum who are following the same logic that I am - the last time I discussed this, I felt like I was swimming upstream. In the end, none of us can directly control what fork someone is going to download and use, but I ask of anyone downloading this firmware,
how much do you trust @hggomes? Do you trust there isn't a backdoor in the firmware? Without the source, we have no idea what he's done to the firmware. Consider the Merlin and John forks - their source is open, available,
auditable. The HGG fork is not.
Just my 2c on the matter.