No it does not. The splash window highlights the succession of development from Marcel Beck to YAM Development Team to us.
Let's say that tomorrow some crazy guys from the community pushes changes to the Yam repository and a new version can be created. This will be Yam v2.10, based on the repo versioning. But there will also be Yam v2.10, the one you released. Both of these versions have different features and fixes. Which is the official, and which is the fake? Can you see the huge problem you are causing here?
I wonder if the Yam development team provided you any licence or the freedom to release new versions of Yam, outside their channels. Or if you bought the rights to release Yam from now on. I haven't seen any announcement, that's why I am asking.
And before I am accused of having my own agenda, just because I do not agree with your practices, I would like to clarify that I am happy you are updating Yam.
But you have to do it in the right way, following the licence and respecting the original authors and the Amiga community. And the Amiga community is not only our customers.
If you want to make things right, but you do not know how, here are some tips for you:
1. Share the changes to the official Yam repo by creating PRs
2. Reverse the changes in the About window to the original ones, and do not claim that you have a copyright on the application, when you do not
3. Reverse the version to the original one, as it is in the repo.
4. Teach the developers of your team how to respect others' work
5. Apologise to the community for what you have done and the wrong decisions you took.
If you do not want to do the above, then you should:
1. Create a new product with an entirely different name and versioning, like all the forks are done in the open-source world
2. Keep on providing the source code to anyone who asks for it, giving plenty of information in the documentation that comes with your app
3. Provide the Yams licence files with the source code
4. If you need to close parts of your changes, do it in a separated library.
If you fail to do any of the above, that will be a proof that you want to trick your own customers, providing them stolen applications, presenting yourself as the successor when you are not.
So, as you can see, you have options. Do the right thing.
