I have to say I also don't see the issue.
The original source is clearly licensed GPLv3. GPLv3 specifies:
- anyone may copy and use the source
- anyone may modify the source and publish that modified source, as long as the GPLv3 license remains in tact (i.e. the modified source is also converted by GPLv3)
- modifications should be marked clearly as to protect the original author from changes made by others
- there are no specific instructions as to attribution, on the contrary.
As to the macro MODULE_AUTHOR, there are two trains of thought as how to use this:
- a full list of all authors of the code, MODULE_AUTHOR can appear multiple times
- the name of the person or organisation to contact about the (copy of the) code
If I look at the OE-A repo, I see that for MODULE_AUTHOR, the second option is chosen. Imho logical, as the original also doesn't mention all authors of the code but the current maintainer of "that" copy.
There is no specific requirement in the GPLv3 license with regards to attribution, but OE-A attributes both the OpenVision developers and the original Duckbox developers, something the OpenVIsion and OpenEnigma2 repositories don't do.
And yes, the repo doesn't have any commit history, but there is no reason why that should be the case, if the source was retrieved using a zip download, or a floppy in the post, there would also be no commit history.
The strength of open source is that everyone uses what is available, to avoid reinventing wheels, and to make a better product as a result. And that works both ways. The Enigma2 codebase makes that very clear, it is the result of 15+ years of copying back and forth, and cross-contributing. OpenVision would not exist if not because they started off copying everything of OpenPLi (which the license allows, so no complaints from us).
So my conclusion is that OE-A does a better job than OpenVision, by attributing the people/groups at the basis of the source, where OpenVision doesn't do that (which is not in the spirit of open source), which makes the fact this seems to be more about PP's ego than anything else even stranger to me, as he isn't the author of the code either, the concept and most of the logic, even the filenames, is derived from the Duckbox project.
Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)
Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.
Many answers to your question can be found in our new and improved wiki.