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

391–400 of 428 posts

Re: Bidding farewell to Google Code

#391

Post by Moru »

eveningcoffee wrote: post #179
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…

Have you considered that Google Code hosts amount of code that is related to the research papers and are not actively maintained (many probably since uploading). This wast valuable resource will be gone forever.

Mabe someone will finally get it. You can't trust third-party sites to keep your stuff up. Host it yourself if you want to be sure it's around somewhere. Use free hosting as a backup plan.

Re: Bidding farewell to Google Code

#392

Post by avinassh »

sytse wrote: post #316
sachinag wrote: post #288

Earlier quoted context omitted.

Hey look! You get to put "I heartily recommend people look at Gitlab - Chris DiBona, Google" on your homepage. That you haven't yet is mindboggling.

Totally agree. And even better, we put your quote about Chris his quote on there together with you HN profile :) See https://gitlab.com/gitlab-com/www-gitlab-com/commit/7eb4ced6... and https://gitlab.com/gitlab-com/www-gitlab-com/commit/b9342fd5... (if you'll get in trouble for this please say so here or via sytse@gitlab.com and I'll remove it ASAP)

I think you should wait, get permission from both and put it. You have put Sachin's company name and position also...

Re: Bidding farewell to Google Code

#393

Post by turingbook »

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 think that GitLab should compete directly with GitHub in open source projects hosting area. Free open tier is powerful tools for letting more people know you.

And for the whole community's benefits, we need another choice other than GitHub.

Re: Bidding farewell to Google Code

#394

Post by z1mm32m4n »

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…

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

You can disable the wiki and issues pages on a repository-by-repository basis. If you're looking to solve the issue of issues being filed in the wrong place, you could try to pick the component that is the most central or most front-facing and only leave that wiki or issue tracker enabled. Then you'd just add a simple note in the README of the other repos about where to go to report issues or read documentation. It's definitely not the same, but it is a somewhat elegant workaround.

Re: Bidding farewell to Google Code

#395

Post by avinassh »

the_mitsuhiko wrote: post #186
ericfontaine wrote: post #173

Earlier quoted context omitted.

"There are many other hosting services like gitlab, what would make gitlab different so that it would deserve a pitch there?" Which is why I said the blogpost would be fairer to just post the wikipedia comparison link. I never said that gitlab should "deserve" a pitch on the blog. I did say it was fair for GitLab to pitch their services, as the CEO has done here, but that is different from "deserving" a pitch. It is…

> It is hard to objectively determine what is the better hosting, but based on people's individual preferences, they can subjectively decide for themselves, which the wikipedia article helps out by clearly explaining the differences. It's quite easy to tell actually. Responsiveness of the UI, featureset, availability, size of the community. * Gitlab is measurably slower (it takes about 5 seconds to load the commit pa…

On GitLab I could not search for top repositories by programming language. For a beginner like me, it is very important. I could go to Github and search for top repositories in the language I am learning. I usually find top projects, try to figure out how they work, how a experienced dev does a specific stuff (compared to noob like me) and I ask myself how can I "copy" those traits and improve myself.

On GitLab, if I stumble upon any repo I can't figure which language it uses. On GitHub it is very clear. It even shows percentage of programming language used.

Open Source helps in so much for learning about programming for a noob like me and GitLab no way does that as like GitHub. Thats the one reason I don't use GitLab much, though I have an account. And one more reason why GitHub shines over GitLab for open source projects.

Re: Bidding farewell to Google Code

#397

Post by rquirk »

51Cards wrote: post #79
ocdtrekkie wrote: post #65

I'm not surprised, and yeah, I've assumed code on Google Code is abandoned by default. But, you know, just yet another Google product biting the dust.

While I've been sad to see a lot of Google projects come to and end I think this one is justifiable. I don't know of any active projects still hosted there.

Here are a few: vim, waf, ttrss-reader-fork, gperftools, include-what-you-use, googletest and googlemock. All have had commits in the last few weeks, some in the last day or two.

Re: Bidding farewell to Google Code

#398

Post by vegedor »

sk5t wrote: post #382
wiseleo wrote: post #358

Earlier quoted context omitted.

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?

googlesource.com is not a third party

Re: Bidding farewell to Google Code

#400

Post by 72deluxe »

enneff wrote: post #373
lnanek2 wrote: post #34

Earlier quoted context omitted.

Honestly, I think he was right. Google has a really bad image problem right now where lots of people don't want to get involved with their projects because Google will most likely kill the project just like Reader and Glass. See my couple of wasted Google Glass devices that will never see an Android update again. Do you think I'll ever buy a Google Android product after they wasted $3k of mine? Do you think I'll buy…

If you joined Google's Glass Explorer program (twice?!) expecting anything but a beta-level device with a short shelf life then more fool you. I don't think they could have been any more explicit about the goals of their program.

I think his point stands though, that Google cannot be trusted to keep services going. This will adversely affect their appeal in many minds, including mine. I have used Google since about 1998 (?) and you'd be amazed how many products have come and gone in that time.

Apologies for the rantiness of the post below, it isn't meant aggressively, just more frustration at no apparent direction seen within the Googlesphere.

The removal of features that people use with no warning and non-implementation of features immediately after release is really really annoying. It makes their stated goals ("index everything") meaningless/temporary/untrustworthy, and dissuades me from buying services from them. Freeloaders use their products a lot (I do!) but I would think twice about ever ever ever paying for software from them, or for a service because you have no idea when it'll shut shop. Even products they still produce appear to be completely disjointed (see the Play Books app on Android and the complete disparity found with their web interface...)

Here's a list of annoyances in products they've released to much fanfare, then apparently just not bothered developing anymore:

1. Google+, yes all of it. And I use it! (where is it going now that Gundotra has left?)

2. Maps: My Maps now isn't integrated into the Android app (they spun it off??), Latitude is gone, Google Local is gone but apparently still there (you can read reviews but hidden and secret GUI controls are now the order of the day for working out how to do anything in Google Maps)

3. Google Drive desktop client: will it ever tell me how far it has got in uploading a massive file? The web client does, the desktop one doesn't. Surely that's an OBVIOUS feature in a filesync utility. Don't ask about their promised Linux version. Couldn't they write it in Go or something?

4. Google Hangouts Android client: the forced update from Talk with the removal of features (is someone actually online? a presence feature seen since MSN Messenger that somehow escapes Google's notice)

5. Google Chrome OS: why is it even here? There was much talk of being stiff competition to Windows and OSX but it's like an Etch-A-Sketch toy operating system. I think TinyCore Linux does more?

I'll stop now because it's coming up to lunch time and I'll get indigestion.

I am a big fan of Android, but their incessant removal of features within their core apps and then rereleases of similar-but-ever-so-slightly-different apps ever year at I/O is getting wearisome.

Post reply on HN