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

For example, because I don't want people to have to sign a CLA to contribute patches to my weekend side projects? That's incredibly dev hostile.


Unless it's changed recently, projects released under patching (again, not releasing) don't require a signed cla (edit: just checked and they don't). They're not Google owned, Google just maintains ownership of your contributions.

And if you look at the releasing guidelines, they only make sense for code developed in google3 and later released. You can't actually follow the releasing process for code developed on non-google hardware, your only option is to follow the patching or iarc methods, and patching is trivially easy and doesn't require anyone to sign a cla.




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

Search: