Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Bidding farewell to Google Code

google-opensource.blogspot.com

Post reply on HN
Print view View original

321–330 of 428 posts

Re: Bidding farewell to Google Code

#321

Post by ta0967 »

lukaslalinsky wrote: post #282
javajosh wrote: post #164

Earlier quoted context omitted.

I'm genuinely curious, what do you like better about bitbucket?

I migrated all my projects to Bitbucket when GitHub decided they do not want to host release downloads (they reversed the decision after that). I also use other Atlassian products and I trust the company to maintain the product, much more than I trust GitHub. Bitbucket has much better review tools - hierarchical comments, approve button, side-by-side diff (GitHub has added that recently). You can see commit log as a…

GitHub decided they do not want to host release downloads (they reversed the decision after that)

AFAICT they haven't, at least i don't see any way to upload release tarballs. they certainly let anybody download tarballs generated for any annotated tag. but those tarballs are not immutable! once in a while, these tarballs start coming down with different hashes, presumably as github changes the code which generates those tarballs. that makes them less than ideal as package sources.

Re: Bidding farewell to Google Code

#322

Post by NeutronBoy »

dchichkov wrote: post #292
enjo wrote: post #235

Earlier quoted context omitted.

On what planet is shutting down a service, with months and months of notice, evil? I get it, we all hate Google on HN (for reasons unclear to me) but this is ridiculous. If these projects are truly important than donate some time and move them over yourself. To demand that google invest time and resources into the migration of these migrations or to keeping this running forever is just silly. Hell tools like https://…

Shutting down Google Code is equivalent to destroying a storage full of handwritten articles, some of which exist only in a single copy and some of which are incredibly valuable. Why valuable? For example computer science researchers had been using Google Code to host supplement code for their research publications for years now. These repositories are not maintained by these researchers any more, yet the code some t…

If the code is that valuable, then perhaps they should put some time into maintaining the code, moving it to another provider, or convincing somebody to pay for hosting.

Re: Bidding farewell to Google Code

#323

Post by pbhjpbhj »

pdknsk wrote: post #31

Does this mean Chromium is also moving away from Google Code? I'm curious how Google plans to migrate almost 500,000 bug reports. I'm expecting Google to purchase GitHub next in order to improve its deficiencies. In particular code search, which is really poor. Google Code search is good, so Google can then apply its search expertise "in-house". https://code.google.com/p/chromium/codesearch Maybe it's just habitual,…

>I'm expecting Google to purchase GitHub next //

So basically this is our 5 year warning on GitHub closing down !?

Re: Bidding farewell to Google Code

#324

Post by asfaltboy »

enjo wrote: post #235
aikah wrote: post #208

Earlier quoted context omitted.

> I work on Google Code, and we will be putting a service in place to redirect deep links to project homepages, issues, etc. to their new locations. And this is an opt in service, nothing is automated. They could ,AT LEAST, partner with Github or someone else to have the whole thing automated... Seriously... the really want to put 0 money in that stuff,they don't give a damn. There are seriously good projects that wi…

On what planet is shutting down a service, with months and months of notice, evil? I get it, we all hate Google on HN (for reasons unclear to me) but this is ridiculous. If these projects are truly important than donate some time and move them over yourself. To demand that google invest time and resources into the migration of these migrations or to keeping this running forever is just silly. Hell tools like https://…

I like how that project is hosted on Google code

Re: Bidding farewell to Google Code

#325

Post by sytse »

ta0967 wrote: post #306
sytse wrote: post #234

Earlier quoted context omitted.

Thanks mlinksva!

i just spotted "GitLab is build to handle very large repositories." there. someone should proof-read it all i guess. :)

Thanks, fixed with https://gitlab.com/gitlab-com/www-gitlab-com/commit/5ef9196b... Hopefully many eyes will make all spelling errors shallow :)

Re: Bidding farewell to Google Code

#326

Post by skj »

asfaltboy wrote: post #324
enjo wrote: post #235

Earlier quoted context omitted.

On what planet is shutting down a service, with months and months of notice, evil? I get it, we all hate Google on HN (for reasons unclear to me) but this is ridiculous. If these projects are truly important than donate some time and move them over yourself. To demand that google invest time and resources into the migration of these migrations or to keeping this running forever is just silly. Hell tools like https://…

I like how that project is hosted on Google code

It's not a googlecode-hosted project: there is no /p/ in the middle, and you can't see its source (not that there'd be much to see). It's a tool made by the googlecode team to help migrate.

Re: Bidding farewell to Google Code

#327

Post by epriest »

nadams wrote: post #294

I predicted this a long time ago and I've moved my projects off. I would recommend migrating to self hosting to prevent an issue like this in the future. It's not too much of a hassle if you only have a couple of projects but when you have 10+ migrating to another source code hosting service is a real pain. If you are looking for a good list of what's out there check out this stackexchange post: http://softwarerecs.s…

What are you missing from Phabricator?

https://secure.phabricator.com/book/phabcontrib/article/feat...

Re: Bidding farewell to Google Code

#328

Post by walterbell »

oldmanjay wrote: post #278
jayvanguard wrote: post #264

Earlier quoted context omitted.

> On what planet is shutting down a service, with months and months of notice, evil? The current planet? Open source projects have a lifetime of years so five months is not that long in the scheme of things. People put there code on there and participated (providing Google content that they were able to use and drive traffic) with the expectation that it would be there for the long term.

This is a rather watery definition of evil. It is fairly close to saying a restaurant is evil for not keeping a menu item you like.

Would it be ok for Google to delete Usenet archives?

Or a library to burn down its own buildings? Or Google to delete all scans of old books?

History matters, because citations to "old" research/code may become more valuable with new requirements and research. Surely a company that "organizes the world's information" needs no explanation of these topics.

Re: Bidding farewell to Google Code

#329

Post by jszymborski »

sytse wrote: post #275
boundlessdreamz wrote: post #218

Earlier quoted context omitted.

I think that's because you are promoting the Gitlab Enterprise edition. It is very easy to miss the third blurb which promotes the free repos. Compare this to bitbucket.org front page (Free private repos are upfront). Github.com frontpage is not as clear but they don't need to I think what Gitlab.com needs is a template like this - Free Private Repos - Host it on Gitlab.com - Need to host it on your servers? Get our…

Thanks for the great feedback! I've changed the homepage according to your feedback in https://gitlab.com/gitlab-com/www-gitlab-com/commit/3a09175f... https://about.gitlab.com/gitlab-com/ mentions that it runs the enterprise edition in the middle box The pricing page is a hard one, we'll look into that. Any idea how we can make the three blurbs on the homepage feel more like different products?

This is a HUGE improvement :D

Re: Bidding farewell to Google Code

#330

Post by jamiesonbecker »

NeutronBoy wrote: post #322
dchichkov wrote: post #292

Earlier quoted context omitted.

Shutting down Google Code is equivalent to destroying a storage full of handwritten articles, some of which exist only in a single copy and some of which are incredibly valuable. Why valuable? For example computer science researchers had been using Google Code to host supplement code for their research publications for years now. These repositories are not maintained by these researchers any more, yet the code some t…

If the code is that valuable, then perhaps they should put some time into maintaining the code, moving it to another provider, or convincing somebody to pay for hosting.

It may not be valuable to the author. That does not mean it's not valuable to some future searcher.
Post reply on HN