3 ms·

Any way to see this without a Google account?

Maxious 12y ago
Subject: All past Keyczar contributors PLEASE READ Shawn Willden: It turns out that the Googlers on this project haven't done our legal due diligence as we should, and as a result, Keyczar is in danger of being pulled completely, just when I was thinking that we had a chance to revive it and move it to Github (thanks entirely to Devin's offer and interest). To avoid having it taken down, and to get it moved to Github, we need to get Contributor Licensing Agreements signed by everyone who has contributed. The agreement doesn't give your IP to Google or restrict your use of it... well, I probably shouldn't try to interpret it for you. The agreements for individual and corporate contributors are here: https://cla.developers.google.com https://cla.developers.google.com Obviously, in the future we'll need CLAs from anyone who contributes. Thanks, and sorry about this. Steve Weis: Keyczar was released under an Apache 2.0 license and I received approval from open source and legal teams in 2008. Why is there suddenly a need to retroactively get a Google CLA? What happens if you're unable to get everyone to agree? Regardless, these are all the internal contributors I recall before it was released: Me Arkajit Dey Ben Laurie Neil Daswani Marius Schilder Sarvar Patel Loren Kornfelder Manuel Marquez Garrido Rafael Castro Laura Krotowski This specifies who worked on what: https://code.google.com/p/keyczar/wiki/Contributors https://code.google.com/p/keyczar/wiki/Contributors Two early external contributors were: Sébastien Martini Martin Clausen Everyone else should be in the commit history.
Tiksi 12y ago
Here's a screenshot of it: http://paste.click/JSYZBj http://paste.click/JSYZBj And here's a copy of the text: http://paste.click/GdAeQx http://paste.click/GdAeQx (Not sure if copying this is an issue, if it is let me know and I'll take it down)
blfr 12y ago
It loads fine without logging in.
- icebraining 12y ago
  Google has a weird state between logged in and logged out. I believe it happens when your session has expired, but the cookies are still being sent. You're constantly asked to login again to access completely open pages.

Subject: All past Keyczar contributors PLEASE READ Shawn Willden: It turns out that the Googlers on this project haven't done our legal due diligence as we should, and as a result, Keyczar is in danger of being pulled completely, just when I was thinking that we had a chance to revive it and move it to Github (thanks entirely to Devin's offer and interest). To avoid having it taken down, and to get it moved to Github, we need to get Contributor Licensing Agreements signed by everyone who has contributed. The agreement doesn't give your IP to Google or restrict your use of it... well, I probably shouldn't try to interpret it for you. The agreements for individual and corporate contributors are here: https://cla.developers.google.com https://cla.developers.google.com Obviously, in the future we'll need CLAs from anyone who contributes. Thanks, and sorry about this. Steve Weis: Keyczar was released under an Apache 2.0 license and I received approval from open source and legal teams in 2008. Why is there suddenly a need to retroactively get a Google CLA? What happens if you're unable to get everyone to agree? Regardless, these are all the internal contributors I recall before it was released: Me Arkajit Dey Ben Laurie Neil Daswani Marius Schilder Sarvar Patel Loren Kornfelder Manuel Marquez Garrido Rafael Castro Laura Krotowski This specifies who worked on what: https://code.google.com/p/keyczar/wiki/Contributors https://code.google.com/p/keyczar/wiki/Contributors Two early external contributors were: Sébastien Martini Martin Clausen Everyone else should be in the commit history.

Tiksi 12y ago

Here's a screenshot of it: http://paste.click/JSYZBj http://paste.click/JSYZBj And here's a copy of the text: http://paste.click/GdAeQx http://paste.click/GdAeQx (Not sure if copying this is an issue, if it is let me know and I'll take it down)

blfr 12y ago

It loads fine without logging in.

icebraining 12y ago
Google has a weird state between logged in and logged out. I believe it happens when your session has expired, but the cookies are still being sent. You're constantly asked to login again to access completely open pages.