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

121–130 of 428 posts

Re: Bidding farewell to Google Code

#121

Post by ericfontaine »

the_mitsuhiko wrote: post #108
sytse wrote: post #57

Hi Chris, GitLab CEO here. What do you think about mentioning Gitlab.com as an alternative for people to move to? It has unlimited (private) projects and unlimited collaborators. It is based the open source GitLab project.

I really don't think that blog post is the place to pitch code hosting websites. Github (and to a lesser degree bitbucket) are websites that are exactly in the space where Google Code and before that Sourceforge were. Gitlab is not.

I think it is fair to for GitLab to pitch their service, considering that the google code blogspot post specifically mentioned both GitHub 8 times and Bitbucket 3 times, while GitLab offers similar functionality. It would have been fairer for the blog to not-specifically endorse anything or post a link to https://en.wikipedia.org/wiki/Comparison_of_source_code_soft...

Re: Bidding farewell to Google Code

#122

Post by rogerbinns »

cdibona wrote: post #2

Hi everyone. I wanted to let you know (and I know this isn't a huge surprise) that we will be shutting down the Google Code project hosting system over the next year. Wired did a nice story about Github that touches on the shutdown: http://www.wired.com/2015/03/github-conquered-google-microso... I'll be hanging around answering questions, but the short form of 'why' is that it just isn't used much anymore, ourselves…

Please can you add a way for projects on google code to do a redirect to wherever they have gone. I moved all my projects late 2013, put notices on all pages I could etc, but still searching for the project often shows the google code site first.

https://code.google.com/p/apsw/

Google Code did one thing very well - each project could have one wiki and issue tracker, but any number of source code repos. This is fantastic for projects where there are multiple parts - eg an Android client, an iOS client, multiple server parts etc. Github for example only lets you have one source repository per project, and as a result the wikis and issues are useless since they are almost always filed against the wrong sub-project.

Every startup I have been involved in over the last many years used Google for business (users, groups, office stuff etc), but then for code hosting we were forced to go elsewhere, needing yet another set of user accounts, groups, admin, billing etc. There was a ticket begging to let folks pay for google code, but it never came to pass. All the startups would have gladly paid, especially to avoid dealing with multiple accounts, sites and admin. Some features like the issue tracker were quite good. Heck you could even prioritise issues - something github still didn't have the last time I looked.

Re: Bidding farewell to Google Code

#123

Post by jszymborski »

BinaryIdiot wrote: post #114
sytse wrote: post #57

Hi Chris, GitLab CEO here. What do you think about mentioning Gitlab.com as an alternative for people to move to? It has unlimited (private) projects and unlimited collaborators. It is based the open source GitLab project.

I've used GitLab before as an enterprise type installation and it was okay but I had no idea you offered GitHub like hosting. When I visit your site it looks like there are no free options but Google Code was meant to house open source projects for free just like GitHub and BitBucket. Do you have free hosting for open source? If not then I don't think it makes sense for them to mention your service. Edit: As pointed…

Both open and private repos on GitLab are free :D

Re: Bidding farewell to Google Code

#124

Post by lultimouomo »

Between this and gitorious, I forsee a lot of dead links in the future.

Hasty times we are living; a lot of useful information will be lost in the cloud age as services shut down. Of course, that information wouldn't probably have been available at all if it weren't for those services, but it's still sad.

Re: Bidding farewell to Google Code

#125

Post by richardwhiuk »

raverbashing wrote: post #62
cdibona wrote: post #2

Hi everyone. I wanted to let you know (and I know this isn't a huge surprise) that we will be shutting down the Google Code project hosting system over the next year. Wired did a nice story about Github that touches on the shutdown: http://www.wired.com/2015/03/github-conquered-google-microso... I'll be hanging around answering questions, but the short form of 'why' is that it just isn't used much anymore, ourselves…

From the comments "What will happen to things that are hosted on google code, like jquery and the google font set? Thousand, if not millions of pages link to these directly - will they all be invalidated? "

That's Google CDN, not Google Code, as the follow on comment says

Re: Bidding farewell to Google Code

#126

Post by warbiscuit »

jfroma wrote: 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.

Among others, there's gitlab.com and bitbucket.com (and also mercurial, as an alternative to git itself -- though the two can push/pull between each other's repos with the right plugin).

Re: Bidding farewell to Google Code

#127

Post by DannyBee »

[deleted] wrote: post #89
btown wrote: post #54

Earlier quoted context omitted.

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

[deleted]

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

#128

Post by raverbashing »

richardwhiuk wrote: post #125
raverbashing wrote: post #62

Earlier quoted context omitted.

From the comments "What will happen to things that are hosted on google code, like jquery and the google font set? Thousand, if not millions of pages link to these directly - will they all be invalidated? "

That's Google CDN, not Google Code, as the follow on comment says

Apparently it's called Google APIs or something

https://developers.google.com/speed/libraries/devguide

Re: Bidding farewell to Google Code

#129

Post by tjohns »

rogerbinns wrote: post #122
cdibona wrote: post #2

Hi everyone. I wanted to let you know (and I know this isn't a huge surprise) that we will be shutting down the Google Code project hosting system over the next year. Wired did a nice story about Github that touches on the shutdown: http://www.wired.com/2015/03/github-conquered-google-microso... I'll be hanging around answering questions, but the short form of 'why' is that it just isn't used much anymore, ourselves…

Please can you add a way for projects on google code to do a redirect to wherever they have gone. I moved all my projects late 2013, put notices on all pages I could etc, but still searching for the project often shows the google code site first. https://code.google.com/p/apsw/ Google Code did one thing very well - each project could have one wiki and issue tracker, but any number of source code repos. This is fantas…

Google Code already has an option to flag a project as moved. From your project: Administer > Advanced > Project Moved

For an example of what this looks like: http://code.google.com/p/iosched

Re: Bidding farewell to Google Code

#130

Post by DannyBee »

fafner wrote: post #120
DannyBee wrote: post #29

Earlier quoted context omitted.

"Google Code was, by contrast, always ugly, hard to navigate, and hard to understand." It's really funny to hear this. If you look at press/reviews/OSS forum comments of it around launch time, people thought it had an excellent interface, because it was being compared to sourceforge. Then github came, and by comparison, the interface looked like crap. But you end up with this kind of weird history rewrite where the v…

Google Code was such an improvement over SourceForge. I think the real problem of Google Code was that it took them too long to support git. When GitHub started Google Code was still SVN only and later they only added Mercurial support. This made people look at GitHub and GitHub could shine with some new ideas, like making code contributions extremely easy and placing the code first. Which of course further increased…

" I think the real problem of Google Code was that it took them too long to support git."

Yeah, this is true. Part of it was that it was going to require a ton of work to fit Git's concepts and protocols (remember, git only started supporting smart http in 2010) into the infrastructure we had. It wasn't until the storage backend for code was completely rewritten, and better http support was added to git that it really became feasible.

(Note that Google code has a completely replicated storage backend infrastructure. It's not just a ton of git/mercurial/svn setups)

Post reply on HN