291–300 of 428 posts
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.
Bitbucket also has free private repos
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://…
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 times is incredibly valuable, because it allows to reproduce research results. The reason why researchers were using Google Code, is because it was supposed to be as stable as the underlying company. Yet now, in 10 months, these repositories will be destroyed.
What's the median lifetime of free cloud services? It seems to be around 5 years. Someone probably tracks that. With SourceForge putting ads in installers, they're no longer a good option. This leaves GitHub in a monopoly position, which is worrisome. Especially given the terms: "GitHub, in its sole discretion, has the right to suspend or terminate your account and refuse any and all current or future use of the Serv…
If only we had some sort of version control system that didn't rely on a master copy somewhere, a 'distributed' version control system if you will...
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.stackexchange.com/questions/3506/self-ho...
I tried rhodecode - it's very basic but upgrading was always a pain (~1hr/upgrade). And when I did manage to get an upgrade to go through there was always some problem.
Gitlab looks interesting but their community edition is lacking.
The one benefit of indefero/srchub is that it supports SVN, hg and git and private projects. So people can request a project in whatever SCM system they want and it's all managed from the same place. Also it's fairly easy to setup and maintain - no real external dependencies such as rabbitMQ or something. I have read of people even installing it on shared hosting.
I've personally tried http://phabricator.org/ but after installing it - it seemed like it was missing major features that you would assume would be there.
Disclaimer: I am the forker/owner of srchub.
Earlier quoted context omitted.
how do you (google) get away with being such asses? i know a bunch of developers will come to your defense, and say things like it is a free service, but it's not really, because for google, users are the product, and you guys have developed a rep for constantly shutting those users down. switching costs are very real, and people just don't trust you anymore. i don't care about google code in particular, but i hate g…
I might be feeding here, but the lesson is that you can't count on things Google releases to be around very long. Even APIs for popular products, like Google Maps. Just don't expect anything they release to have a long shelf life. It's annoying and it sucks, and it is now laughable when they tag things with phrases like "free code hosting forever" and so on. For them to change, they'd have to either: 1) Support every…
(a) For things (eg. Reader, Google Wallet for Digital Goods) that could be viable businesses in their own right with some modifications, spin them off as small companies.
(b) Open source the project they no longer have interest in. (as was done for Google Wave, which arguably wasn't necessary because the level of interest in Wave at that point was quite low)
In this case (and perhaps they already have this), I would suggest that they allow anyone to discover all the projects on Google Code and export them such that they could be imported into other code hosting sites, allowing everyone else to build a Google Code alternative.
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.
Bitbucket also has free private repos
Earlier quoted context omitted.
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, e…
As can be seen in my blog post and various talks in the subject, the Kallithea community faced two choices: a fork of only the GPLv3'd components, or a lengthy GPL enforcement battle with Rhodecode, who violated the GPL by changing to a non-Free-Software license for code that combined GPL'd software that wasn't copyrighted by Rhodecode.
If Rhodecode would go back to a pure GPLv3 model for its software and develop the software in pubic again, I think the fork could be easily resolved and we could all work together again. Thus, only one simple act of yours would resolve the fork entirely, sebastiank123, will you take that act?
Meanwhile, I'm sure the Free Software user community can make the easy and obvious choice between a community-run, developed-in-public Free Software project that complies with GPLv3 and a for-profit-corporate run, developed-in-private, semi-Open-Source project that has a history of GPLv3 compliance problems.
This is the #1 reason I fear the cloud. When Google shuts a project down, unless you act fast, you lose data.
Would it be rocket science for Google to set up a service which provides:
1. DNS hosting 2. Static page redirects 3. Static page hosting 4. Secure static page hosting (available only to authenticated accounts)
in perpetuity? This would be a read/delete-only service.
When Google Reader shuts down, I could access my data forever. When Google Code shut down, the project archives would stay up as read-only. Etc. No maintenance, and a one-time migration with Google Takeout for each dying service.
Myself and lots of other academics chose google code to host projects that are no longer actively contributed to but still used or of interest to the academic community as building blocks for future research. At the time it seemed like the safest place to leave something. I'll be moving my code and forking a few analytical projects I use appreciate but I hope they would leave the site up in read only or archive mode…
> At the time it seemed like the safest place to leave something. Google is never the safest place to store anything, unless it's your personal data. Google sunsets products constantly.
My point is that Code has been running for quite a while, and at one stage it probably did look like the safest way to keep a project online. Can't blame people for choosing it earlier on.