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

Before GitHub

lucumr.pocoo.org

Post reply on HN
Print view View original

11–20 of 255 posts

Re: Before GitHub

#11

Post by mbreese »

simonw wrote: post #2

I absolutely loved Trac. Getting a Trac setup as step 1 in starting a new open source project was just an unbelievable amount of friction. Fun fact: Django is still running on Trac today, and has been for more than 20 years now: https://code.djangoproject.com/timeline (I was not involved in setting that one up, though it's possible I helped get the private Trac that pre-dated it running, I honestly can't remember!)

Trac was great.

But, my first issue tracker was bugzilla. Setting that up was a bit of a pain, and it didn’t integrate well with anything, but it was very satisfying to see “Zarro Boogs”.

Re: Before GitHub

#12

Post by [deleted] »

simonw wrote: post #2

I absolutely loved Trac. Getting a Trac setup as step 1 in starting a new open source project was just an unbelievable amount of friction. Fun fact: Django is still running on Trac today, and has been for more than 20 years now: https://code.djangoproject.com/timeline (I was not involved in setting that one up, though it's possible I helped get the private Trac that pre-dated it running, I honestly can't remember!)

[deleted]

Re: Before GitHub

#14

Post by ctoth »

I remember this old thing called Bugs Everywhere -- it was a bug/issue tracker which actually lived inside your hg repository. I wonder if we could standardize on something like that? or git notes with an issues ref? or something magical like that?

Then it's BYOR -- bring your own renderer. Trivial CLI bugtrackers, agentic nonsense, pretty web stuff, whatever and the data lives in the repo.

Re: Before GitHub

#15

Post by flaburgan »

What we need is gitlab to finally integrate ActiviyPub so we can fork, comment, open merge request on all gitlab instances from our personal instance. Git is already decentralized, this isn't that hard to do.

Re: Before GitHub

#16

Post by weiliddat »

Reading this and mitchellh's post I was curious about code archival services, and found a few projects.

GitHub has their own: https://archiveprogram.github.com/

Software Heritage is a non-profit funded by UNESCO: https://www.softwareheritage.org/2019/08/05/saving-and-refer...

Although they're mostly the code / commit history, not so much surrounding metadata like issues, PRs, discussions, wiki, etc.

Re: Before GitHub

#17

Post by lloydatkinson »

ctoth wrote: post #14

I remember this old thing called Bugs Everywhere -- it was a bug/issue tracker which actually lived inside your hg repository. I wonder if we could standardize on something like that? or git notes with an issues ref? or something magical like that? Then it's BYOR -- bring your own renderer. Trivial CLI bugtrackers, agentic nonsense, pretty web stuff, whatever and the data lives in the repo.

I've often wondered why no one has built an issue tracker with Git notes, or if one exists, why it's not widespread.

Re: Before GitHub

#18

Post by saghm »

dijit wrote: post #5
simonw wrote: post #2

I absolutely loved Trac. Getting a Trac setup as step 1 in starting a new open source project was just an unbelievable amount of friction. Fun fact: Django is still running on Trac today, and has been for more than 20 years now: https://code.djangoproject.com/timeline (I was not involved in setting that one up, though it's possible I helped get the private Trac that pre-dated it running, I honestly can't remember!)

Weirdly, I also have fond memories of Trac despite absolutely despising it at the time for “doing too much and excelling at nothing as a result”. I guess that award goes to Gitlab now, which I will probably also remember fondly.

I like Gitlab fine by ignoring pretty much everything it does other than host the source code and let me view READMEs in the browser (and for work, also merge requests). In general the more I have to use anything other than those, the more frustrated I get, which was also how I felt about Github in the past. I'm not sure I've ever had a non-frustrating experience when trying to set up a CI pipeline on any platform, so I guess Gitlab's CI isn't any better or worse than others in that regard. There are an awful lot of tabs on the left any time I look for something through those menus though, most of which I don't know what they do and I would probably not be happy to have to learn.

Re: Before GitHub

#20

Post by bsimpson »

I think I was one of the first people to try Flask. I learned Python so I could take advantage of AppEngine for free and easy modern hosting, which put me in the right spot when Flask launched. I've long been an admirer of Armin's, and recognized his domain before I clicked the link. As he points out, in those days, you didn't default to GitHub.

His post is a response to Mitchell's, from just a few hours ago. I'm impressed with how quickly he wrote a long-form, high-quality, well-reasoned post.

Post reply on HN