Live data from Hacker News

Bidding farewell to Google Code

google-opensource.blogspot.com

261–270 of 428 posts

Re: Bidding farewell to Google Code

#261
post #98

While I agree that Google Code, as it is right now, isn't needed anymore, I believe there is still room for innovation in this space and I wish there were more players than github, pushing the boundaries harder. As a software developer is a tool that we use all day.

Take a look at Kallithea.

Re: Bidding farewell to Google Code

#262
post #243

Earlier quoted context omitted.

Thanks for the concrete examples. GitLab is faster in on some pages. The commit page probably is slower, but not by so much: wget https://gitlab.com/gitlab-org/gitlab-ce/commits/master master.1 [ ] 66.40K 382KB/s in 0.2s wget https://github.com/gitlabhq/gitlabhq/commits/master master.2 100%[=====================>] 183.50K 662KB/s in 0.3s Again, your milage may vary (cache) and I do agree that the commits page of GitH…

> GitLab is faster in on some pages. The commit page probably is slower, but not by so much: For the initial HTTP request maybe and if you're in the US. Gitlab is painfully slow when loaded from a European network connection and you factor in the time it takes to fetch all resources. Cached or uncached. > GitLab doesn't have preview support for as many features as GitHub, but it has many other features GitHub doesn't…

Right now GitLab is hosted in Germany (AWS Frankfurt) and I was testing from the US (Mountain View). But I sometimes see the same delay you mention. We'll move it to the US east coast over the next couple of months.

I think protected branches are really nice for open source projects too, although I agree that most contributions will come from forks. Right now no open source projects use Git Annex but that might change now that it becomes easier to use, probably it is really nice if you have an open source game with huge digital assets.

Re: Bidding farewell to Google Code

#263
post #235
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://…

In actuality, I've found most HN users seem to love Google. To the extent that almost any criticism of Google gets downvoted to death.

Re: Bidding farewell to Google Code

#264
post #235
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://…

> 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.

Re: Bidding farewell to Google Code

#266

Earlier quoted context omitted.

Last error report I created (which is consistently causing tab crashes) was marked as duplicate and merged (without comment) into an issue that is private and inaccessible. All attempts to get additional information have been met with silence.

That sounds like it means it's a security issue. All the browsers do this (the ones with open issue trackers, at least)

Ah, good point. That could very well be it. Of course, the last issue I found was a security hole in google's core data api. Their review team admitted it was an issue, but rejected fixing it or rewarding a bounty, because they decided it was too esoteric. Even though it is literally a huge api key check that just doesn't happen. I've had bad experiences with filing bug reports to google :)

Re: Bidding farewell to Google Code

#268

Earlier quoted context omitted.

Subversion & Mercurial? Then actually just RhodeCode ( https://rhodecode.com ) is the only alternative since it supports Git, Mercurial and Subversion. Disclaimer: I am RhodeCode's co-founder.

Kallithea is partly a fork of our old, legacy version of RhodeCode without all the hard work our engineers spent over the last 12 months in turning an open source project into a real, sophisticated enterprise product. In more than 30,000 engineering hours our team added exclusive Subversion support, 4x better performance and tons of security fixes (all based on enterprise customer feedback), server-side-mergeable pul…

Reply to comment by jordigh:

Wow, there is someone really angry and offensive here and not really telling the truth ...

It is sad to see how often forks go downhill if they were purely based on ideologies and not with the user and general good for the project in mind.

But anyway, we welcome and fully support everyone to fork our old GPL versions, the world does not need less but more source code management systems, especially since we lost now one of the key players in Google Code.

Re: Bidding farewell to Google Code

#269
post #41

Earlier quoted context omitted.

I guess they will be using their own tool to migrate issues: IssueExporterTool "How to export Google Code issue tracker data to other services" https://code.google.com/p/support-tools/wiki/IssueExporterTo...

The problem is that last time I looked at these tools, they all sucked. I migrated code hosting and website for my project to github but left issue tracking on Google Code because the github API doesn't let you do any kind of high fidelity import of issues. I hope GH find a way to do some kind of reasonable issue import soon.

The API doesn't, but if you contact the Github team, they have ways of doing much higher fidelity bug imports if you give them massaged data.

Here is an example of a project we imported from Bugzilla:

https://github.com/translate/pootle/issues?page=47&q=is%3Ais... (all issues below id ~3200 are imported).

Here is the tool I wrote for the occasion:

https://github.com/jleclanche/bugzilla-to-github/

Re: Bidding farewell to Google Code

#270

Earlier quoted context omitted.

> How is this even a failure? Google Code was the best at what it did for several years. Google Code had a few good years, and I am grateful that it happened. However, it did fail to win the software forge battle as the space heated up. It failed to evolve enough to keep up. It failed to keep the mindshare it built in those two initial years as Github and others blew past it over the next six. So call it for what it…

It actually can be considered a success in the style of the original intent of Chrome, Fiber, the Nexus line, and who knows, maybe the upcoming MVNO: to spur innovation and increased investment in a stagnating product area. When Google Code came out Source Forge was horrible, and Github didn't exist. Google Code helped both open source software and the market for code hosting. Now there's a dominant, but so far so gr…

Yeah, it's tempting to take a small bit of credit for the existence of the new generation of project hosting services. Google Code showed that there was room for new players, so it did open the door, but you have to give credit to GitHub for the concept of social coding. I never understood it and it goes against my personal OSS DNA, so I would never have made that leap.

Another way to (very charitably) count Google Code's success is to look at the role it played in Google. One of the largest users of Google Code has always been Google itself. In 2005, Google had released like 8 project tarballs on SF, kind of tentatively. Having Google Code as a home field endorsement allowed that to grow into the thousands. Now, OSS releases seem pretty routine for Google and feel more integrated with the community than ever.

Post reply on HN