7 ms·
> They are also not on github, which makes collaboration that much harder. This is now vim-emacs level zealotry. There are workflows which gasp do not mesh wel
by chx 12y ago
> They are also not on github, which makes collaboration that much harder.
This is now vim-emacs level zealotry. There are workflows which gasp do not mesh well with github. github issues/PRs have almost no metadata and absolutely none that the issue submitter can set.
- CognitiveLens 12y agozealotry? It's one comment in an article dealing almost entirely with other issues. Github has become the de-facto place to put code that you want others to work with, and it is a platform built to surface such projects and make them accessible in a consistent way. It's not the only such tool, but it is really familiar to a lot of people, and that makes collaboration slightly easier for those who are familiar with it.
- raverbashing 12y ago"Github has become the de-facto place to put code" Maybe in some districts of SF and SV, but apart from that, NO I love Github and I think that it is way better than most of "industry standarts" but amazingly, some people still use self hosted solutions, because they need it.
- CognitiveLens 12y agofull quote: "Github has become the de-facto place to put code that you want others to work with". Maybe I should clarify: "others" == "people who don't know or directly work with you" Self-hosted solutions do not make collaboration simpler (in an OSS context), which is the reasonable, non-zealous claim made by the article.
- raverbashing 12y agoFor the strict issue of sharing code with others (open to everybody), sure, Github is the best solution But this is not what the article was talking about, it was talking about collaboration with other file formats, so jumping to say Github is good (on what we already know it's good and does not correspond to the discussion) is a stretch
- eropple 12y agoI can't find a way to stretch the definition, for the kind of open-source projects he is very clearly discussing, that isn't some sort of reductivist #NotAllSourceRepositories or something.
- freshhawk 12y agoThe author made "being on github" a hard requirement. I think it might have been made as a kind of shorthand for "on github or something equivalent" but you can't blame someone for taking the author at their word when they state it so plainly. And that stated sentiment is pretty insane.
- mfisher87 12y ago>"Github has become the de-facto place to put code that you want others to work with," I think maybe you meant to use a more general term like "source control" here. Because that's so wrong to say github is de-facto for collaboration. There are proprietary projects with their own source control everywhere and "not using github" is no concern for any of them. Source control came around long before source control front-ends, surprisingly. And, again, probably surprisingly, not everyone needs a front-end to actually work.
- angersock 12y agoLet's not mince words. Where else is that code being written, and what is it's volume of code compared to Github? SourceForge? CPAN? The OpenBSD CVS? Bitbucket? Google Code (lol)? I'd be genuinely surprised if you could show me a place with more repositories right now than Github--I'd love to see such a vibrant ecosystem!
- raverbashing 12y agoNo Linux distribution uses github. Same for FreeBSD/OpenBSD The Linux Kernel is there but development is not done there, it's merely a mirror. Gnome (https://git.gnome.org/browse/ https://git.gnome.org/browse/), KDE, XFCE (http://git.xfce.org/ http://git.xfce.org/) are not there. Nginx? Uses Mercurial http://nginx.org/en/download.html http://nginx.org/en/download.html Apache? Not there as well Gcc? LLvm? http://llvm.org/docs/GettingStarted.html#checkout http://llvm.org/docs/GettingStarted.html#checkout But the latest fad.js is in github so that's what people use, right?
- angersock 12y agoSo, you've listed like 5-10 projects, scattered across several services. Big projects which are important, don't get me wrong--but still outnumbered by the huge number of your "fad.js" projects. So, thanks for making my point I guess?
- ef4 12y ago> There are workflows which gasp do not mesh well with github. If we're discussing open source collaboration, it is hugely beneficial to NOT have your own unique workflow and instead adopt one that a large community of people are already using. In the time it takes to read your special "how to submit a patch" document, I could have already been done if you were using a de-facto standard workflow like Github's. This has a material impact on how much contribution you can expect to get from others. This is yet another case of Worse is Better. Ubiquity trumps perfection. I have heard it argued that making contributions harder to submit is somehow a good idea, because it keeps lower quality contributors out. This is very much mistaken, and even someone as cantankerous as Linus is on the record saying that encouraging more patches, even annoyingly naive ones, is in the long-term interest of the project.
- hueving 12y ago>I have heard it argued that making contributions harder to submit is somehow a good idea, because it keeps lower quality contributors out. This is very much mistaken, and even someone as cantankerous as Linus is on the record saying that encouraging more patches, even annoyingly naive ones, is in the long-term interest of the project. Yet Linux is not being developed on Github. Clearly the missing data in the github workflow is so detrimental that it's not worth the extra developers it might attract.
- ef4 12y ago> Clearly the missing data in the github workflow is so detrimental that it's not worth the extra developers it might attract. There is historical path dependence. Linux has changed workflows before, but each time it was controversial. I can see where it wouldn't be worth igniting a holy war. The more interesting question is what new projects should do. Even Linus puts new things (https://github.com/torvalds/subsurface https://github.com/torvalds/subsurface) on Github.
- freshhawk 12y agoI noticed that as well, I was hoping it was ignorant shorthand for "has a public repository, bug tracker and website". Also, it's worse than vim-emacs zealotry, those at least have the benefit of being extremely powerful expert level tools. Those frequently, and maybe rightfully inspire some zealotry. That same attitude towards popular, least common denominator tools is better called fanboyism than zealotry.