Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Dear GitHub

github.com

Post reply on HN
Print view View original

261–270 of 491 posts

Re: Dear GitHub

#261

Post by patrickaljord »

zzzeek wrote: post #141

We need world class, modern, distributed bug tracking now. If you google around for this technology, a lot of nice ideas, many using git itself as transport, were poking around, and around 2009 they started falling silent. Why? Because GitHub started up and everyone just buzzed over to it like so many moths to a flame, having learned nothing from places like Sourceforge about what happens when 90% of the open source…

> If issue tracking and code reviews were based on a common, distributed system like git itself

There you go: https://github.com/google/git-appraise

Re: Dear GitHub

#262

Post by Matachines »

ajsharp wrote: post #256

I get that these are super frustrating issues for these people ( cough guys) that maintain these repos, but there's something telling about it that it's all JS people. That last cute lil paragraph really sums it up for me: > Hopefully none of these are a surprise to you as we’ve told you them before. We’ve waited years now for progress on any of them. If GitHub were open source itself, we would be implementing these…

Interestingly most of these people are older than the millennial category

Re: Dear GitHub

#263

Post by hendry »

whyever wrote: post #260
hendry wrote: post #168

Earlier quoted context omitted.

Suckless have discussed this several times and have fallen back to an email mailing list. http://lists.suckless.org/dev/1201/index.html#msg10574 Last one proposed by someone: http://lists.suckless.org/dev/1504/26210.html

The problem with mailing lists is that patches and bug reports get forgotten.

Well that's a problem with the developers.

Amount of times I've posted a bug on a mailing list and a core developer doesn't care to respond is unbelievable. Here is a recent one: http://lists.alpinelinux.org/alpine-user/0042.html

Re: Dear GitHub

#264

Post by ajsharp »

Matachines wrote: post #262
ajsharp wrote: post #256

I get that these are super frustrating issues for these people ( cough guys) that maintain these repos, but there's something telling about it that it's all JS people. That last cute lil paragraph really sums it up for me: > Hopefully none of these are a surprise to you as we’ve told you them before. We’ve waited years now for progress on any of them. If GitHub were open source itself, we would be implementing these…

Interestingly most of these people are older than the millennial category

Fooled me ;)

Re: Dear GitHub

#265

Post by joeblau »

anarchy8 wrote: post #6

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?

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.

Re: Dear GitHub

#266

Post by clinta »

simoncion wrote: post #248
peterfpf wrote: post #243

Earlier quoted context omitted.

I normally put a big "[DEPRECATED]" notice at the beginning of the README. This normally doesn't go unnoticed. Another good example is harthur's "[UNMAINTAINED]" [1] [1] https://github.com/harthur/brain

> I normally put a big "[DEPRECATED]" notice at the beginning of the README. Aye. Some folks in the discussion linked to by krschultz complain that "People sometimes don't read the README and -thus- don't notice deprecation warnings.". To them I ask: "What makes you think that those sorts of people will notice anything less than an overlay that prevents them from interacting with the Github UI for that particular rep…

One concern would be around tools that fetch from github automatically. go get for example would need some sort of structured metadata if it wanted to surface an error to a user that a library is deprecated.

Re: Dear GitHub

#267

Post by ywecur »

scrollaway wrote: post #207
dragonsh wrote: post #126

Earlier quoted context omitted.

Recently even Python language planned to move its repositories to github.com for network effect, instead of helping projects like kallithea SCM and trac by partnering with software conservancy or gnu. Python should learn a lesson when they decided to move their repository to closed source system like github. But obviously as people use Facebook, developers use github for the same reason, network effect. I hope they c…

> instead of helping projects This isn't how it works. You don't help projects by pretending the football-stadium-sized issues with them don't exist and using them despite their flaws. Trac is an awful, awful piece of software. It's awful to set up, to use, to maintain, to gather feedback from, it's awful for just about everything. If in some very weird parallel universe it gathered even 1% of the following that Gith…

Gitlab is FOSS and does everything Github does (arguably) better.

The only reason one would use Github is for network effect.

Personaly i believe the ethical trade off to be too great, and I believe FOSS supporters should agree with me.

Re: Dear GitHub

#268

Post by ywecur »

Osiris wrote: post #173

The author mentions that if GitHub was open source, they would implement these features themselves. Gitlab[1] is an open source repository manager that supports local installs as well as public hosting at gitlab.com. If author appreciates open source, perhaps they should put their efforts into improving an existing open source option rather than relying on a proprietary solution. [1] https://gitlab.com/gitlab-org/git…

Absolutely agree!

I cannot fathom why people are still actively supporting GitHub.

Even if you ignore the ethical reasons, which if you are an open source developer really should suffice, GitLab is better and more customizable in every way.

Supporting it benefits yourself and all of the FOSS community.

Re: Dear GitHub

#269

Post by patrickaljord »

ajsharp wrote: post #256

I get that these are super frustrating issues for these people ( cough guys) that maintain these repos, but there's something telling about it that it's all JS people. That last cute lil paragraph really sums it up for me: > Hopefully none of these are a surprise to you as we’ve told you them before. We’ve waited years now for progress on any of them. If GitHub were open source itself, we would be implementing these…

I agree that the "we’re very good at that!" was not needed. But the rest of the letter is ok to me, not particularly entitled. It is after all an open letter, open letters are designed to pressure people into something. In this case, these people have been asking for changes for years nicely and privately and have been ignored. They are just pressuring them as any customers would do. One may ignore the history of git, but its very existence came to be because a million dollar company called BitKeeper started ignoring its open source customers because they didn't owe them anything. Look what happened to them. Who even remembers BitKeeper? Maybe github should take these millennials hippy contributors more seriously if it doesn't want to end the same way.

https://en.wikipedia.org/wiki/Git_(software)#History

Re: Dear GitHub

#270

Post by ywecur »

zzzeek wrote: post #141

We need world class, modern, distributed bug tracking now. If you google around for this technology, a lot of nice ideas, many using git itself as transport, were poking around, and around 2009 they started falling silent. Why? Because GitHub started up and everyone just buzzed over to it like so many moths to a flame, having learned nothing from places like Sourceforge about what happens when 90% of the open source…

You mean like GitLab?
Post reply on HN