Live data from Hacker News

Bidding farewell to Google Code

google-opensource.blogspot.com

211–220 of 428 posts

Re: Bidding farewell to Google Code

#211
post #199

Earlier quoted context omitted.

We did not move anybody. People imported their repo's themselves. Another project that moved is F-droid https://gitlab.com/u/fdroid that was before the acquisition.

Gitorious has a header that informs people to migrate to Gitlab.

Yes, we certainly strongly suggest it to people. Just wanted to make sure everyone understands that the move is initiated by people themselves, we didn't move anyone.

Re: Bidding farewell to Google Code

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

We use GitLab internally, and it's an amazing piece of software. It's open source, easy to setup and is pretty robust. I would love to see the option to move from Google code to GitLab.

We do too, it would be nice if someone can contribute an importer.

Re: Bidding farewell to Google Code

#213

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…

Well if we're using "Responsiveness of the UI" as the metric, then I would argue that http://fossil-scm.org/ beats both GitLab and GitHub. Fossil is easily self hosted (just run one small executible file). And it is really fast, because it is written in C with sqlite and is simple and minimalistic. It is not git based, but is a simpler DVCS. Dynamically generated pages on my home computer take less than .001 ms to display. It has all the features most small developers need, with a builtin lightweight wiki, issue tracker, and code tree. Your self-hosted website is available even if you don't have an internet connection, or you can use free hosting service like http://chiselapp.com/. Of course it looses in terms of size of community. But popularity does not determine quality.

You will likely loose arguments on public forums if you make statements like "absolutely no objective reason to ..." because someone just needs one reason to disprove. Here goes: GitLab has a functioning interface for managing git projects and lets anyone selfhost the community edition. Therefore there is an objective reason to put a project on GitLab. QED.

Re: Bidding farewell to Google Code

#216

Earlier quoted context omitted.

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

Well if we're using "Responsiveness of the UI" as the metric, then I would argue that http://fossil-scm.org/ beats both GitLab and GitHub. Fossil is easily self hosted (just run one small executible file). And it is really fast, because it is written in C with sqlite and is simple and minimalistic. It is not git based, but is a simpler DVCS. Dynamically generated pages on my home computer take less than .001 ms to di…

> Well if we're using "Responsiveness of the UI" as the metric, then I would argue that http://fossil-scm.org/ beats both GitLab and GitHub.

Which is why I really don't think (and that was my original point) that a Google announcement of shutting down Google Code should act as some sort of advertisement for $code-hosting-site/project. Github and Bitbucket deserve the mention because those projects are well established.

Re: Bidding farewell to Google Code

#218
post #170

Earlier quoted context omitted.

Ah for whatever reason I didn't see that at all.

No problem, it is not that obvious, any suggestions how to make it more findable without messing up the other options are welcome.

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 open source edition

- Need enterprise support/features? Get our enterprise edition and host it on your servers

Btw do you offer enterprise features on gitlab.com? It was not very clear

Also your pricing page needs to be clear about the different versions. There are at least 3 different Gitlab products (free gitlab.com, gitlab ce, gitlab ee) but the information is easy to miss.

In your homepage, the three blurbs (download and install.., pricing for spport.., signup for gitlab.com..) feel like 3 product features rather than 3 different products.

Re: Bidding farewell to Google Code

#219

Earlier quoted context omitted.

> I expect an innovator to move on from failures That's great if you are an investor or employee, but if you are a user it kind of sucks. Google just needs to be up front about it (and maybe they are): We make no commitment to supporting this application or maintaining it as is. We might make radical changes, we might shut it down. If we do shut it down, we'll warn you at least 9 months ahead of time. I'm not going t…

I gotta be frank here: If you expect anyone in the tech world, Google or otherwise, to support a non-paid product past the point it's obviously declining in user base (IE obvious to not just internal users, but to external ones), for more than a few years, you are just not going to use anyone's products ;) Google code is mostly irrelevant to this calculus, because it was not ever meant to make money for anyone, but i…

The problem is that Google represented itself as an altruistic supporter of open-source. People trusted it because it deliberately cultivated the impression of being more responsible than the default 'duh capitalism' mentality it now represents.

Google is suffering the reputational damage it deserves - not because it is now behaving any differently from other corporations but because it has betrayed the promise that it would.

Re: Bidding farewell to Google Code

#220
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,…

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.
Post reply on HN