News for hackers. Stuff that matters.
Re:Why we’re changing to the AGPL license by joerichey on Tuesday October 13, 2020 @04:18PM (#24769863)
So the issue isn't in-work hours vs off-work hours (as that line is fuzzy), but who owns the copyright.

The above link [1] is for the automatic process where Google still owns the copyright (hence no AGPL or non-Commercial stuff). This works for 99% of stuff and is easy.

There's a second process called IARC [2] which lets the employee retain the copyright. It's not automatic but allows for AGPL, non-commercial, or proprietary contributions.

We also have a few AGPL projects that were whitelisted due to COVID-19 [3].

[1]: https://opensource.google/docs/patching/ [2]: https://opensource.google/docs/iarc/ [3]: https://opensource.google/docs/patching/#no-review

Re:Why we’re changing to the AGPL license by corobo on Wednesday October 14, 2020 @12:53PM (#24778790)
> The IARC process is only open to full time employees in good standing.

I wonder who Google considers to be in bad standing while also not fired. Flight risks? Maybe people who want to work on side projects?

Still pretty greasy