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

Important open source projects should not use GitHub (2020)

unixdigest.com

Post reply on HN
Print view View original

41–50 of 77 posts

Re: Important open source projects should not use GitHub (2020)

#41

Post by decide1000 »

Double_a_92 wrote: post #38
coldtea wrote: post #37

Earlier quoted context omitted.

> Also why does their website have to look so damn ugly? Because it was made by coders. Old school coders. Backend coders. > I know that's not what really matters for a git server, but I just can't take such a project seriously. "Who knows what else they didn't really care about?" in the back of my head... Yes, a nice looking website, that epitome of project maturity and quality /s (as if there's a shortage of barely…

I wouldn't mind a simple or even boring website... But sometimes they are actively ugly.

I like the design of notabug

Re: Important open source projects should not use GitHub (2020)

#42

Post by guappa »

nottorp wrote: post #39

To quote Joel Spolski, has anyone using a distributed VCS lost any significant amount of code? If github annoys you you can concievably create a new repo elsewhere, change origin locally, push. The real question is how long until they annoy you. And how easy it would be to set up an automatic mirror beforehand.

You can't migrate the bug reports.

Re: Important open source projects should not use GitHub (2020)

#43

Post by loloquwowndueo »

guappa wrote: post #42
nottorp wrote: post #39

To quote Joel Spolski, has anyone using a distributed VCS lost any significant amount of code? If github annoys you you can concievably create a new repo elsewhere, change origin locally, push. The real question is how long until they annoy you. And how easy it would be to set up an automatic mirror beforehand.

You can't migrate the bug reports.

Run a periodic script that slurps bug data via the API and updates a file in the repo with this information. If GitHub goes away you at least have a local copy of the raw data no more than a day old or so.

GitHub json data is horrible but not intractable to work with.

Re: Important open source projects should not use GitHub (2020)

#44

Post by notarobot123 »

konimex wrote: post #16
miloc_c wrote: post #8

Linus Torvalds (Git was originally created by him) seems to be actively contributing in GitHub for the Linux kernel repository (also created by him): https://github.com/torvalds/linux Anyone has seen his position on this topic?

> Anyone has seen his position on this topic? Well, he's not a fan of GitHub pull request as per the last decade. https://github.com/torvalds/linux/pull/17#issuecomment-56546...

> So sure, you may think I hate github. I don't. I hate very specific parts of github that I think are done badly.

> But other parts are done really really well.

> I think github does a stellar job at the actual hosting part. I really do. There is no question in my mind that github is one of the absolute best places to host a project. It's fast, it's efficient, it works, and it's available to anybody.

> That's wonderful. I think github is absolutely lovely in many respects.

> And that then makes me really annoyed at the places where I think github does a subpar job: pull requests and committing changes using the web interface.

Re: Important open source projects should not use GitHub (2020)

#45

Post by sylware »

Capitain Obvious.

More than ever since github broke for good noscript/basic (x)html support under the guidance of... msft not that long ago (I am a noscript/basic (x)html user).

This will attract the fire of msft "trolls" (AIs or humans)... strap on for impact...

Re: Important open source projects should not use GitHub (2020)

#47

Post by decide1000 »

The reason I don't use Github is Microsoft's hatred stance on open source.

Anyone remember Microsoft calling Linux a "cancer"? Or Microsoft threatening open source developers for violating 200 patents? Or their official stand where they whould threaten and fear Linux devs? The secretly funded lawsuits against Linux? They even threatened lawsuits at companies for just using Linux.

This company is rotten by the executive level.

Re: Important open source projects should not use GitHub (2020)

#48

Post by zaphodias »

notarobot123 wrote: post #46

One thing that I haven't quite understood is why more projects don't host their own git services on their own project website. Are there any specific challenges or is it just because of the maintenance overhead?

Maintenance overhead, plus:

- convenience (everyone already has a GitHub account and is familiar with the platform) - discussions platform (issues, prs, discussions) - CI (GitHub Actions)

It's already there, and it's free for the most part. Why would I bother hosting my own?

Re: Important open source projects should not use GitHub (2020)

#49

Post by nottorp »

guappa wrote: post #42
nottorp wrote: post #39

To quote Joel Spolski, has anyone using a distributed VCS lost any significant amount of code? If github annoys you you can concievably create a new repo elsewhere, change origin locally, push. The real question is how long until they annoy you. And how easy it would be to set up an automatic mirror beforehand.

You can't migrate the bug reports.

Maybe you shouldn't use features that contribute to lock in indeed.

Re: Important open source projects should not use GitHub (2020)

#50

Post by nottorp »

dale_glass wrote: post #11

I don't believe there's any major harm in using Github for most projects. Maintaining my own servers and chasing ideological purity doesn't improve my project. Any time I dedicate to setting up infrastructure is time I'm not dedicating to making the code better. The nature of Git means Microsoft can't really do much harm. Every developer and contributor has a copy of the repo, should the worst happen setting up home…

> I don't believe there's any major harm in using Github for most projects.

Actually there was one mentioned in a different post. You're at the mercy of Microsoft (and random US sanctions) not only for your project, where you have a copy of the source and are the canonical source for further updates, but also for your dependencies.

Post reply on HN