YAM Licence

[amigakit]

@futura

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

[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.

[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.

[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.

[amigakit]

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

No, I fully understand your agenda.  Your past comment to my colleague about not liking AmigaKit made that very clear.

There are hundreds of A600GS users who are now enjoying the new YAM.  Why are you not celebrating this new development?  YAM has languished in nightly build status for years, untouched for years.   I would imagine that welcome comments would be the first natural response rather than negativity?  I do not see this from you or the few others who have hijacked this thread.  This has to be questioned.

The splash gives the impression that you consider yourself the only current copyright holder

No it does not.  The splash window highlights the succession of development from Marcel Beck to YAM Development Team to us. 

The crux of the matter is that you do not like seeing AmigaKit investing time and resources into further development of Marcel Beck's creation.   You also do not like to see the AmigaKit name added to this list of developers.

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?

We have not removed or diminished any of the legal notices.  In fact we have ensured that past contributors to the project have been documented.

[amigakit]

@walkero

We are not going to be bullied by your aggressive behaviour or any others in your cabal.

We will adhere to the legal requirements of the licence.

[amigakit]

Sure.  We are looking forward to your order.

[amigakit]

@cgutjahr

I agree, YAM will always be freely distributable.  That is the nature of the licence which we adhere to.

Last October we found a timer problem in YAM afer many hours of hunting down the bug.  We promptly reported the code fix in the YAM repo bug reports. Recently we have found and fixed two more bugs in RecipientString GoActive and GoInactive method.   These code changes will be fed back to the YAM repo after the weekend when we are back in office.   Going forward, we will always feed back bugs and improvements to the main repo for the benefit of the main YAM sources.

[amigakit]

@cgutjahr

If you look at the screenshots, you will see that this project is already named as "YAM 2.10 [A600GS/m68k]" 

This is to inform the user that it is a separate project.

[amigakit]

I am sorry, I disagree with you.   There are no restrictions in the licence preventing us to use the YAM name and no trademark notices.  If you can point out information to the contrary, I will of course review it.  Our users expect it to be called YAM.  However, we have distinguished it in the splash window by the clarification that this a different version [A600/M68K].  We can add an A600GS logo to the YAM logo image if that helps?

AmigaKit Ltd adopted development of YAM for it's computer platforms after the YAM Development Team announced in April 2022 that they had discontinued development.

You are not reading this carefully enough. What are AmigaKit Ltd's computer platforms?  Well in this immediate case they are A600GS and A1200NG. 

YAM Development has been discontinued and it has been some years since it has been updated in beta/nightly build.  Therefore we have to adopt the code for the A600GS/A1200NG computer systems.  Realistically who else is going to develop YAM for our platforms?   Development costs money and it would be wonderful if the mainline YAM was not discontinued and still being developed.  In that scenario, we would not need to put resources into a dedicated version for our own platforms. 

[amigakit]

@cgutjahr

The name YAM belongs to the people who have been maintaining YAM

Does filing bug reports and source code fixes count as maintenance?

Depending on that: YAM (like the other projects) is an open source project. If you like, you are welcome to create a fork of it and start developing immediately.

  Quoted from Amiga News (24/04/2022)

So you didn't rename it.

It has YAM prominently in the name and splash screen graphics in addition to [A600/M68K] and the version number etc.

This is Nonsense. Why would you and your "team" (hi Andy!) make bugreports in the official YAM bug tracker if "Development has been discontinued"? Why would you "feed code changes back to the YAM repo after the weekend"?

Because that is a decision that has been taken with every open source project we have been working on.  We gave back code to AmiBerry, AROS and YAM.   Anyone else in future who wants to fork the discontinued YAM project can benefit from the bugs that took many hours to find and fix.   Anyone who is fed up with the bugs we found can compile their own private copy too.

And, again: Futaura - the guy you thanked for "helping" you to add AmiSSL 5 support to YAM in this very thread - is making new releases.

Futaura made a nightly/beta build in 2022 - not a new public release.  We incorporated his code into our YAM A600GS public release.  He was very helpful with pointing me to the beta code using AmiSSL last September- it saved us a lot of time having to implement it ourselves.    I informed him by reply that we encountered a Timer bug which took us a week to hunt down.  When it was resolved Futaura was also informed that a bug report (and solution) was filed in the hope he knew of any developers still working on YAM.   

call it SystemV54Mail

Thanks for the marketing suggestion, I think YAM sounds better.