←back to thread

Mozilla Firefox – Official GitHub repo

(github.com)
848 points thefilmore | 1 comments | 13 May 25 05:23 UTC | HN request time: 0.199s | source
Show context
bandrami ◴[13 May 25 06:03 UTC] No.43969975[source]▶
Pretty cool that Linus Torvalds invented a completely distributed version control system and 20 years later we all use it to store our code in a single place.
replies(29): >>43969999 #>>43970002 #>>43970008 #>>43970018 #>>43970019 #>>43970028 #>>43970031 #>>43970032 #>>43970036 #>>43970037 #>>43970142 #>>43970154 #>>43970198 #>>43970282 #>>43970314 #>>43970343 #>>43970418 #>>43970419 #>>43970431 #>>43970434 #>>43970451 #>>43970472 #>>43970541 #>>43970904 #>>43971268 #>>43971299 #>>43971387 #>>43971586 #>>43988717 #
SCdF ◴[13 May 25 06:11 UTC] No.43970018[source]▶
I get what you're saying, but tbf hosting on github doesn't (yet!) box you out of just moving back to that system. It's still just git. It's still distributed, in the sense that if github goes down you could still generate patches and email them around, and then push back to github when it's back.

Everything surrounding code: issues, CICD, etc, is obviously another story. But it's not a story that is answered by distributed git either. (though I would love a good issue tracking system that is done entirely inside git)

replies(9): >>43970039 #>>43970120 #>>43970143 #>>43970151 #>>43970180 #>>43970299 #>>43970301 #>>43970480 #>>43970514 #
rablackburn ◴[13 May 25 07:04 UTC] No.43970301[source]▶
>> I would love a good issue tracking system that is done entirely inside git

You might like git-bug:

https://github.com/git-bug/git-bug

replies(1): >>43971681 #
sublinear ◴[13 May 25 11:21 UTC] No.43971681[source]▶
Why bury this in the documentation if it's the sole feature its users would care about? https://github.com/git-bug/git-bug/blob/master/doc/design/da...

This should be one of the very first links in the readme.

replies(2): >>43980638 #>>43980718 #
1. rablackburn ◴[14 May 25 03:56 UTC] No.43980638[source]▶
>> ...if it's the sole feature its users would care about?

The tag-line covers it pretty well I thought?

"git-bug is a standalone, distributed, offline-first issue management tool that embeds issues, comments, and more as objects in a git repository (not files!), enabling you to push and pull them to one or more remotes."

That tells you what the feature is - if you need/want a more technical overview you can still get from the `README` to `entity data model` in two clicks (Documentation > Data model).