Recent

Author Topic: MIT License  (Read 605 times)

paweld

  • Hero Member
  • *****
  • Posts: 996
MIT License
« on: February 26, 2024, 10:55:27 am »
I would like to clarify one thing regarding MIT License, which was raised by @paule32 in the thread: https://forum.lazarus.freepascal.org/index.php/topic,66358.msg508372.html#msg508372         

In order not to litter that thread I am separating it here.
@paweld

Yes, this is right, and a next one Point, that I would talking.
What does anyone of us ?
The License will not be read that will prompt out when we install software.

So, we don't read the tiny words in the long License.

So, I was usung MIT - License on much Projects...

But for me, MIT License (github.com) is a Snow-Ball-System-License:
See:
- you can declare your Work with MIT
- each other can use your Work (and can declare it as own Work)
- than, I someone (Client/Customer) comes from a Fork to you, and claim Money-Back about Damage from Software, you never had develop for (and here, the Snow-Ball-System starts: someone knows someone, that knows someone... etc. and so forth...)

You understand, what I would like to say ?
     
The content of the license includes an exclusion of warranty for the software that is provided:
Code: [Select]
The MIT License (MIT)

Copyright © 2024 <copyright holders>

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated
documentation files (the “Software”), to deal in the Software without restriction, including without limitation
the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software,
and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
   
     
Such an exclusion is also included in many other licenses, not just open source.
Best regards / Pozdrawiam
paweld

paule32

  • Full Member
  • ***
  • Posts: 197
Re: MIT License
« Reply #1 on: February 26, 2024, 01:14:54 pm »
That's right.

But MIT License can use for commercial, too.
And then, I don't believe that the "next" Developer of your Work hold it on the License,
to add the Notice of the Original Work/Developer.

Even, when you make a Fork on github.com - which was the first Author ?
Can you tell me this ?

paweld

  • Hero Member
  • *****
  • Posts: 996
Re: MIT License
« Reply #2 on: February 26, 2024, 01:31:53 pm »
If the seller does not provide the original license, how will the recipient know who the original author is?
In my opinion, such a guess makes no sense, because then it will turn out that it is not worth doing anything at all and making it available.
Best regards / Pozdrawiam
paweld

paule32

  • Full Member
  • ***
  • Posts: 197
Re: MIT License
« Reply #3 on: February 26, 2024, 01:35:40 pm »
It was near 1980, and it flawed a Dispute - who the Inventor of the WalkMen was.

In Original, it was a German Engineer.
He strikes the big Firm SONY - which copied the first Model of him.

 

TinyPortal © 2005-2018