YAM Licence

[nbache]

@amigakit

As I understood it, the previous maintainers (Jens and Thore) just resigned from the project, leaving it without current maintainers, but with the github and other infrastructure still intact. Since the project is open source, it would be natural, if you needed new features, to add them into the existing project, causing new nightly builds to emerge with those features for all supported platforms.

Or have I missed something?

Either way, yes, please, it would be very nice to get a new OS4 version with those "important bug fixes" you mentioned, even if it were only with the status of a fresh nightly dev build.

Best regards,

Niels

[djbase]

@nbache
We have already added up to date AmiSSL 5 support and fixed some important issues.

Was already done so nothing new...

https://amiga-news.de/en/news/AN-2022-07-00047-EN.html
https://amiga-news.de/en/news/AN-2024-03-00062-EN.html

Also where are the changed files? YAM is GPL-2.0

[walkero]

I haven't as yet.
Just tried for a quick test whilst building something else on the other machine, and  it needs a bit of attention to  build with the recent OS4 SDK when I have more time I might take bit more in depth look. Might be just used the wrong makefile options as it generated alot more warnings than I would expect.

I am pretty sure that it can be compiled for OS4 with the latest SDK. I have done that many times, and I am using that version for my emails.

[futaura]

We have already added up to date AmiSSL 5 support and fixed some important issues.   An OS4 port would be perfectly feasible too.

Excuse me?!
https://github.com/jens-maus/yam/commit/ae0c0504e465741f53a1ec600b41ad3a3c211a2e

[amigakit]

@futura

:-) thank you ! We don’t forget that your work and advice helped us add AmiSSL 5 support to YAM A600GS

[futaura]

As I understood it, the previous maintainers (Jens and Thore) just resigned from the project, leaving it without current maintainers, but with the github and other infrastructure still intact. Since the project is open source, it would be natural, if you needed new features, to add them into the existing project, causing new nightly builds to emerge with those features for all supported platforms.

Or have I missed something?

No, you haven't. The whole point of making YAM open source was to allow development to continue. Jens and Thore did a great job with the build environment, ensuring nightly builds are automatically built online at GitHub. It is released under GPL, so I cannot explain why Amigakit are attempting to steal the code (including the few changes I have made since Jens and Thore stopped working on it, claiming them as their own). Why not just contribute to the YAM repository so everyone can benefit and contribute?

It is like me reverting AmiSSL to closed source, after I took over all development - it would not have been the right thing to do.

[futaura]

@futura

:-) thank you ! We don’t forget that your work and advice helped us add AmiSSL 5 support to YAM A600GS

Um, pardon? I added it myself to the YAM repository in July 2022! YAM 2.10-dev with AmiSSL v5 support has been available to everyone shortly afterwards

[amigakit]

@futaura

Any source code request will be honoured to any recipient.  We are not stealing anything.  That’s a sensationalist thing to say.

The changes and bugs we found with the timer have already been fed straight back to the Yam bug reports:  https://github.com/jens-maus/yam/issues/727

This will continue with the latest bugs we found in the last few days.

This work took many hours to hunt and fix the bugs.  The information fed back is for the benefit of the community.

Um, pardon? I added it myself to the YAM repository in July 2022! YAM 2.10-dev with AmiSSL v5 support has been available to everyone shortly afterwards

Yes I know, I think you are reading my comments wrong or I have not been as explicit enough with what I have written.  We needed to add AmiSSL v5.17 support to our branch at the time.  Your code, help and support made it possible for us to do that without having to reimplement it ourselves.  That was appreciated.

[nbache]

our branch

Why branch at all?

Best regards,

Niels

[amigakit]

@nbache

YAM will have specific features for the A600GS and A1200NG that are not applicable to the other platforms such as the Update system, ARM native features and integration with other A600GS system programs.   We would not want to entangle the main line code with those platform specific features.

[futaura]

@futaura
The changes and bugs we found with the timer have already been fed straight back to the Yam bug reports:  https://github.com/jens-maus/yam/issues/727

This will continue with the latest bugs we found in the last few days.

This work took many hours to hunt and fix the bugs.  The information fed back is for the benefit of the community.

That's not how GitHub works. Bug fixes like this should be added as pull requests, not in bug reports, as I and others who have contributed to the project have done in the past.

[walkero]

@nbache

YAM will have specific features for the A600GS and A1200NG that are not applicable to the other platforms such as the Update system, ARM native features and integration with other A600GS system programs.   We would not want to entangle the main line code with those platform specific features.

I am pretty sure you and your developers know that there is a way to have parts of code that are compiled only under specific hardware. This can be done at the level of the compiler.
So, you can still separate your code from the rest of the code base by using these technics, and still share the source with the official repository.

Now, if you do not want to share the custom HW specific code, you can have it in a separated library that will be your own with your own licence. So what you write above is not an excuse.

[kolla]

@walkero

developers

It’s just Broadblues, no need for plural.

Btw, the problem I see here is AmigaKit claiming copyright for YAM, that’s pure BS - they only have copyright for the specific code they added, the certainly cannot claim copyright on any of the code they did not write. The copyrights of everyone else who has contributed doesn’t magically vanish when you add your own code to it, this is not like “corporate” code where you can buy the whole thing and slap your copyrights on it - clearly AmigaKit does _not_ grasp GPL.

[amigakit]

@kolla

Once again you are trying to create negativity about us and our projects.  It is becoming a regular event.

We are not claiming the entire copyright.  That is the precise reason we have left the other copyright notices inside the program to acknowledge the previous contributors. 

Our copyright is the most recent covering the specific changes we have made.

Have you read any of the licence documentation we distribute with YAM ? My guess is No.

[kolla]

@kolla
Once again you are trying to create negativity about us and our projects. It is becoming a regular event.

I am not creating negativity, all the creation here is by yourself, I am merely pointing it out.

We are not claiming the entire copyright.  That is the precise reason we have left the other copyright notices inside the program to acknowledge the previous contributors.

The splash gives the impression that you consider yourself the only current copyright holder, as if you have been granted all rights by previous developers and contributors.

Our copyright is the most recent covering the specific changes we have made.

Then to avoid this kind of turmoil, I suggest you change the splash to reflect that.

Have you read any of the licence documentation we distribute with YAM ? My guess is No.

Of course I have, it is GPL-2, and you cannot just change that. Are you saying you distribute YAM with other license documentation than that?