We are planing on taking the majority of these legitimate, open source, 'abandonded' projects and putting them up in cold storage in a git repo on googlesource.com
Will it keep existing deep links published in books and research papers from breaking? What prevents Google from setting the whole site into read-only mode as-is? Keep it working as it does now and disable changes.
Was that a rhetorical question--how could any third party possibly prevent deep links from breaking?
What is the criteria for "legitimate"? A project useful for me may not be "notable" enough for most to consider "legitimate".
Presumably, not abusing Google Code as a hosting site for pirated content.
Or for personal data. I've seen some people using Google Code as a pseudo-Dropbox. Clever, but ultimately not what the service was intended for.
Thanks for this, Chris.
Could you publish a list of projects w/descriptions? That would be great for others (gitlab?) who might want to host / cherry-pick / curate the collection a bit more than that.
Re:Bidding farewell to Google Code
by amiraliakbari on Friday March 13, 2015 @02:50AM
(#9195917)
I suggest letting developers to specify projects they find useful to be included in this cold storage.
Someone needs to do an Internet Archive style project on all these repositories, put them up on Github, and make sure that they are indexed properly by search engines (i.e. intro pages become README.md, wikis are migrated, etc.).
If someone wants to make an actual serious effort on this, feel free to contact me.
[deleted]
Re:Bidding farewell to Google Code
by nothrabannosir on Thursday March 12, 2015 @01:23PM
(#9192286)
Not at all, that's 100% the point of most open source licenses. Which are compulsory for a project on GC.
E.g. MIT:
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to
deal in the Software without restriction, including without limitation the
rights to use, copy, modify, merge, publish, distribute, sublicense, and/or
sell copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. 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.
Specifically, note "Permission is granted" and "distribute".Comply with those terms (i.e. include that piece of text when you redistribute) and you satisfy MIT.
GPL, &c, they all have similar clauses. In fact, MIT goes much further. I could take all those projects, mirror them, and charge people insane amounts of money for it.
If you can't even rehost on Github, what good would copyleft be?
Not really.
Unlike a lot of other hosting services, Google code required you to pick an open source license for the project.
Even if there are no headers on source, you have a good argument that they were proclaiming to the world it was licensed a certain way, ...
(now, third party code they may have included is a different issue, you can't get rights to that through someone else's claims, but ...)
Re:Bidding farewell to Google Code
by jamiesonbecker on Thursday March 12, 2015 @09:44PM
(#9195257)
Agreed. and that's what the DMCA was ostensibly intended for anyway. Someone who claims copyright could always make that claim in the normal fashion.
Re:Bidding farewell to Google Code
by AnkhMorporkian on Thursday March 12, 2015 @12:55PM
(#9192074)
Perhaps archive.org will take it upon themselves to archive all the projects.
Re:Bidding farewell to Google Code
by ocdtrekkie on Thursday March 12, 2015 @01:02PM
(#9192132)
This is the one thing I'm a bit worried about. I've downloaded several Google Code projects this year so far alone.
Re:Bidding farewell to Google Code
by habitmelon on Thursday March 12, 2015 @12:59PM
(#9192102)
Find those useful projects and post them on Bitbucket or GitHub
What will happen, if those projects are not migrated because their developers have simply forgotten about them?