14 ms·

I think the social effects of GitHub are very strong. It's the de facto arena for open source collaboration. By using it, a project signals that they choose the

by mbrock 11y ago

I think the social effects of GitHub are very strong. It's the de facto arena for open source collaboration. By using it, a project signals that they choose the most widely used community, and thus encourage participation. It's familiar. Everybody has an account. There's built in GitHub support in package managers, even, so the namespace of "githubuser/project" is valuable. Personally I'm not interested in another clone of GitHub.com. Let's try another model entirely. Something more distributed and federated. That way lies diversity and immunity to lock-in. Let's collaborate in an open fashion using open protocols and decentralized hosting.

dudul 11y ago
Agreed. I also see very little value in simply cloning GitHubg, that's one of my problems with GitLab. I like it, it's open source and the perfs get better, but at the end of the day, it is a clone of GitHub. Not much innovation. I would love to say a player take some risk and try to present a new model and new way to leverage Git.
- mwcampbell 11y ago
  How about a Git repository management application designed specifically for Sandstorm (https://sandstorm.io/ https://sandstorm.io/)? Maybe call it Gitgrains.
- sytse 11y ago
  What kind of innovation would you like to see? We already added protected branches, integrated CI and many other features. Our current plans are on https://about.gitlab.com/direction/ https://about.gitlab.com/direction/
  - freeadvice 11y ago
    > What kind of innovation would you like to see "I would love to see a player take some risk and try to present a new model and new way to leverage Git." I may be wrong but doesn't gitolite predate GitLab and didn't that have branch protection? Plus Perforce, ClearCase and other enterprise SCM had this concept for decades. Don't take this response in the wrong way, as I would love for GitLab to succeed, but GitLab is definitely not leading or creating features that Atlassian and GitHub are eager to copy. Innovating is doing things that others have not thought off and for the innovation to be marketable, it has to be useful. I truly want GitLab to be successful, but it's currently stuck in the "Samsung is a ripoff of Apple" stage. In order for GitLab to break this stigma, they really need to focus on something that makes GitHub and Atlassian really need to copy them. From the directions page, I really don't see anything that I would consider to be innovative. The only two points from the directions page that I can somewhat say GitLab could be innovative, would be the analytics and that's because analytics is so abstract/vague. If GitLab could leverage it's continuous build information and reliably tell management how well an employee is performing and/or how buggy their software is going to be, then that would be innovative. If GitLab could develop some formula based on the information that they are able to capture, and accurately predict how things will be, would definitely be something GitHub and Atlassian would want to copy. Along with IBM, Microsoft, etc. Adding continuous integration isn't really that big of a deal considering how well Travis and others integrate with GitHub. Right now, GitHub is the pretty girl, with glaring short comings, but guys put up with her because she is really pretty. Atlassian is the businessman that can get things done and doesn't charge that much. GitLab is the geeky kid that nobody is really taking seriously. There is no denying that geeky kid is useful, but people really only go with it because it melds with their open source ideology and/or because it's the cheapest solution. GitLab needs to find a way to break this current perception. They can do one of three things: - Become the new pretty "it girl" - Become a serious business man - Be both If you can be both, you would definitely be the innovative one. But right now, GitLab is that gawky geeky kid and that perception needs to change. And the worst mistake you can make is believing you are the pretty girl, because other geeks are saying you are pretty. Or believing you are that serious business man, because other cheap business man are saying you are the best. Like I said, I really want GitLab to succeed, and in order for it to succeed, it really needs to be the one that comes up with the innovations. Asking others for what to innovate, is not innovating.
PieterH 11y ago
:-)
danieldk 11y ago
Any suggestions? Git over IPFS?
- mbrock 11y ago
  It's an interesting topic but I don't have much to offer. IPFS seems neat as an object store. Sign your commits and throw them into IPFS and you're good? Given a persistent distributed object store, it seems less obvious how to publish projects, refs, and pull requests. If you hear about "Rails", you want to be able to find the actual consensus Rails repository master branch in a trusted way. Some semantic data on https://rails.org/ https://rails.org/ maybe? Then the namespace for repositories is just the DNS namespace... But that's just one way of getting the data; any source you can verify should be fine. So a signed message by a trusted Rails maintainer published somewhere. I was imagining a kind of NNTP reflog with PGP signatures....

by mbrock 11y ago

dudul 11y ago

Agreed. I also see very little value in simply cloning GitHubg, that's one of my problems with GitLab. I like it, it's open source and the perfs get better, but at the end of the day, it is a clone of GitHub. Not much innovation. I would love to say a player take some risk and try to present a new model and new way to leverage Git.

mwcampbell 11y ago
How about a Git repository management application designed specifically for Sandstorm (https://sandstorm.io/ https://sandstorm.io/)? Maybe call it Gitgrains.
sytse 11y ago
What kind of innovation would you like to see? We already added protected branches, integrated CI and many other features. Our current plans are on https://about.gitlab.com/direction/ https://about.gitlab.com/direction/
- freeadvice 11y ago
  > What kind of innovation would you like to see "I would love to see a player take some risk and try to present a new model and new way to leverage Git." I may be wrong but doesn't gitolite predate GitLab and didn't that have branch protection? Plus Perforce, ClearCase and other enterprise SCM had this concept for decades. Don't take this response in the wrong way, as I would love for GitLab to succeed, but GitLab is definitely not leading or creating features that Atlassian and GitHub are eager to copy. Innovating is doing things that others have not thought off and for the innovation to be marketable, it has to be useful. I truly want GitLab to be successful, but it's currently stuck in the "Samsung is a ripoff of Apple" stage. In order for GitLab to break this stigma, they really need to focus on something that makes GitHub and Atlassian really need to copy them. From the directions page, I really don't see anything that I would consider to be innovative. The only two points from the directions page that I can somewhat say GitLab could be innovative, would be the analytics and that's because analytics is so abstract/vague. If GitLab could leverage it's continuous build information and reliably tell management how well an employee is performing and/or how buggy their software is going to be, then that would be innovative. If GitLab could develop some formula based on the information that they are able to capture, and accurately predict how things will be, would definitely be something GitHub and Atlassian would want to copy. Along with IBM, Microsoft, etc. Adding continuous integration isn't really that big of a deal considering how well Travis and others integrate with GitHub. Right now, GitHub is the pretty girl, with glaring short comings, but guys put up with her because she is really pretty. Atlassian is the businessman that can get things done and doesn't charge that much. GitLab is the geeky kid that nobody is really taking seriously. There is no denying that geeky kid is useful, but people really only go with it because it melds with their open source ideology and/or because it's the cheapest solution. GitLab needs to find a way to break this current perception. They can do one of three things: - Become the new pretty "it girl" - Become a serious business man - Be both If you can be both, you would definitely be the innovative one. But right now, GitLab is that gawky geeky kid and that perception needs to change. And the worst mistake you can make is believing you are the pretty girl, because other geeks are saying you are pretty. Or believing you are that serious business man, because other cheap business man are saying you are the best. Like I said, I really want GitLab to succeed, and in order for it to succeed, it really needs to be the one that comes up with the innovations. Asking others for what to innovate, is not innovating.

PieterH 11y ago

:-)

danieldk 11y ago

Any suggestions? Git over IPFS?

mbrock 11y ago
It's an interesting topic but I don't have much to offer. IPFS seems neat as an object store. Sign your commits and throw them into IPFS and you're good? Given a persistent distributed object store, it seems less obvious how to publish projects, refs, and pull requests. If you hear about "Rails", you want to be able to find the actual consensus Rails repository master branch in a trusted way. Some semantic data on https://rails.org/ https://rails.org/ maybe? Then the namespace for repositories is just the DNS namespace... But that's just one way of getting the data; any source you can verify should be fine. So a signed message by a trusted Rails maintainer published somewhere. I was imagining a kind of NNTP reflog with PGP signatures....