← Back to context

Comment by growse

2 years ago

> B: Be clearly labelled, in its public-facing information, as being offered as-is, without any implied updates or future development.

So if I had a text file in the root of my repo that said:

  THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW.  EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.  THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU.  SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.

Would that be sufficient?

12 comments

growse

Reply
teddyh  2 years ago

That text does not disclaim support, security bugfixes, and future development. On the contrary, all three of those things are probably either heavlily implied or outright stated to be available on the project web site.

  • growse  2 years ago

    You and I are reading "SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION." very differently.

  • infamouscow  2 years ago

    It also doesn't disclaim the author from writing you a check out of the good will of their heart.

    I genuinely don't understand what's so difficult to grasp here.

    • teddyh  2 years ago

      > * It also doesn't disclaim the author from writing you a check out of the good will of their heart.*

      Nobody expects that. But people do reasonably expect a project to recieve updates, security fixes, and new releases.

      3 replies →