Re:Dear GitHub
by anarchy8 on Thursday January 14, 2016 @04:50PM
(#10904818)
I feel like there is a great opportunity right now for anyone to make a Github replacement. Sounds like a lot of these features are sorely needed at the moment. Why has Github been complacent?
[ Parent
| on HN ]
> I feel like there is a great opportunity right now for anyone to make a Github replacement.
There is GitLab, which is good and is FOSS in addition.
I'm maintaining a GitLab instance for my team at work and it's been really great for us. I am pretty disappointed that the CE version doesn't include GitLab Pages, though, as that was the one feature I missed most from GitHub and GitLab Enterprise is outside of our budget at this time.
At a previous company, we did this in GitLab with a simple post receive hook that just checked out the gh_pages (or gl_pages) branch on a webserver configured w/ rewrite to serve at a proper path. We even were able to do one better and allow PHP since it was self hosted and we trusted the committers.
The hosted version at Gitlab.com is running EE, so it'll be just like Github.com is.
I understand, but that's just not an option for us. I don't resent them at all, they've every right to decide which features are restricted to EE licenses, but I can lament it all the same.
Re:Dear GitHub
by jobvandervoort on Thursday January 14, 2016 @05:06PM
(#10904997)
Thanks, good to hear.
As people can use GitLab Pages on GitLab.com for free, we felt the ability to host your own static pages was more interesting for larger teams, hence our decision to bring it to GitLab Enterprise Edition.
By their very nature, git repos are one of the easiest things to migrate. Simply point at a new remote and push, and that's really it. It means that, unlike many other services, I could see GitHub being completely abandoned almost over night. If something better came along.
Re:Dear GitHub
by autoreleasepool on Thursday January 14, 2016 @05:16PM
(#10905103)
Agreed. This is the point of git. There is no centralized repository.
You would lose the issues.
Re:Dear GitHub
by albertoleal on Thursday January 14, 2016 @05:12PM
(#10905062)
There are lot of tools to migrate them. Example, github.com/babel/babel has migrated their issues to phabricator.babeljs.io
True, but thanks to the API and their relatively simple structure it's reasonably easy to at least copy their contents as well. Linking them correctly to user accounts on a new platform is probably the biggest issue.
Re:Dear GitHub
by johnmaguire2013 on Thursday January 14, 2016 @05:49PM
(#10905383)
Users with public SSH keys would be easy: https://github.com/JohnMaguire.keys
When a new user signs up, ask them for their existing Github username and to upload an SSH key that matches.
I am pretty sure that a potential competitor will use GitHub's APIs to import issues as well.
Re:Dear GitHub
by duncan_bayne on Thursday January 14, 2016 @08:58PM
(#10906551)
+1
Re:Dear GitHub
by twothamendment on Thursday January 14, 2016 @05:12PM
(#10905060)
You say that like it is a bad thing...
Re:Dear GitHub
by rhinoceraptor on Thursday January 14, 2016 @04:57PM
(#10904894)
The same reason YouTube is so popular. Neither GitHub or YouTube are big because of their technology, it's their community that keeps people there.
It's a huge tax on attention and contributions if a project decides not to use GitHub. There are many GitHub replacements but none of them have the community of GitHub.
Playing devil's advocate - in their respective heydays, SourceForge and Google Code both seeemed unassailable. They had large, active communities that hosted the most popular OSS projects.
Could the same thing happen to GitHub?
But it requires feature expansion on the scale of github, and a perpetual decline and ignorance of the community on the parts of the current host for years for that kind of transition to happen naturally.
That, and github has centralized development to a degree that sourceforge or gcode in 2008 could only dream of. It not only obsoleted other hosting solutions but also brought millions of developers into these kinds of development ecosystems whom used to just use forums or their own personal websites to host their projects.
For a very large percentage of young developers I work with, "Git" and "GitHub" are synonyms. GitHub has made themselves literally synonymous with version control to a large number of people. That's a lot of social momentum that a competitor has to overcome. In light of that, it's not that surprising at all that GitHub has become complacent.
Because those features are not ones from the people paying money to Github?
Most of these features are ones that only affect public projects. You're not customers of Github, you're the product. Or rather, the advertising.
Because Github succeeded in being the Git repo host. I think you're on track with saying their complacency is an opportunity and I wouldn't doubt to see a Github killer born this year.
Re:Dear GitHub
by fweespeech on Thursday January 14, 2016 @05:29PM
(#10905224)
> I feel like there is a great opportunity right now for anyone to make a Github replacement. Sounds like a lot of these features are sorely needed at the moment. Why has Github been complacent?
Network effects strong enough to slow the growth of any competitor long enough for GitHub to adapt.
That will be extremely challenging. GitHub has a huge community with a lot of heavy weight projects behind it. Sure you can add a few features on top of whatever you build, but GitHub has the ability to copy whatever seems popular very quickly.
They've pretty much been profitable since the start unlike other start-ups who may be more eager to please users/customers.
Why not bitbucket?
Bitbucket's UX and integrations are worse than Github.
That's almost entirely subjective. YMMV.
Bitbucket requires payment for larger numbers of collaborators. Github requires payment for private repositories. Open source requires unlimited collaborators, and no one wants to pay.
Public (Open Source) repositories on Bitbucket do not have a limit to the number of contributors.
Most people on GitHub do not suffer these issues, simply put. It's only really the popular open source projects, which represents a small minority but are loud and vocal.