Welcome, Guest. Please login or register.

Author Topic: YAM Licence  (Read 15876 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline futaura

Re: YAM Licence
« on: February 28, 2025, 09:24:05 PM »
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
 

Offline futaura

Re: YAM Licence
« Reply #1 on: February 28, 2025, 09:55:06 PM »
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.
 

Offline futaura

Re: YAM Licence
« Reply #2 on: February 28, 2025, 10:00:11 PM »
@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
 

Offline futaura

Re: YAM Licence
« Reply #3 on: February 28, 2025, 10:28:58 PM »
@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.