Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

But the OSS license already absolves them of responsibility. This might just be to set the tone that security fixes won't be prioritized to the standard that they used to be.


You seem really confident that an OSS license would protect them from liability… what is that confidence based on?


It's a straightforward MIT license: https://github.com/calcom/cal.diy/blob/main/LICENSE

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


Just because a license says you are not liable for anything doesn't mean a court will always uphold that.


if the license can't shield them, do you think that a blog post might?


This is good , switching from viral license to more corporate friendly licensig




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: