News for hackers. Stuff that matters.

A comment on Why we’re changing to the AGPL license. Parent comment

Re:Why we’re changing to the AGPL license by tsss on Tuesday October 13, 2020 @07:44AM (#24764572)
I actually have a library that is Mozilla licensed and gets some contributions from the likes of Google, Uber, Airbnb and so on. Mozilla license is similar to GPL in the sense that it also commands you to publish your code in some situations, so I would expect Google to outlaw this license as well, but so far I haven' received any complaints and I don't think the contributors would go out of their way to get permission from higher-ups at Google. Perhaps they didn't notice what terms the Mozilla license implies.
[ Parent | on HN ]
Re:Why we’re changing to the AGPL license by joerichey on Tuesday October 13, 2020 @08:05AM (#24764735)
At Google, MPL (and other copyleft licenses) are OK for internal use and for external contributions.

I think we have a mirroring system setup to automatically publish any internal changes.

Edit: See https://opensource.google/docs/thirdparty/licenses/#reciproc... for the public info about mirroring.

[ Parent | on HN ]