> What GitHub Gave Us<p>To me one of the clear things that GitHub gave us was a structure around a person rather than a project. To me it felt liberating to quickly create a repository attached to my name than it was to go through the (what felt to me) very serious process of coming up with a project name and reserving it on sourceforge just to get a cvs or svn repository (along with website, mailing lists, issue tracking(?), etc, etc...). It felt like the mental load of "oh this is just a quick thing" was a lot easier with github.<p>> It gave projects issue trackers, pull requests, release pages, wikis, organization pages, API access, webhooks, and later CI.<p>Although it didn't give us this all at once. I still remember when we created a new user account in order to simulate an organisation, before they existed. I distinctly recall discussing with friends if we wanted to set up a bug tracker software for our project with the assumption that "GitHub will probably release one in a few months anyway". In the end we just kept a text file committed in the repository. Issues were announced a few months later.
I enjoy speculating on what could come from revisiting the first principles with our new tech stack.<p>The Fediverse makes it much easier to broadcast updates in a truly decentralized fashion. Maybe this can be the discovery layer instead of requiring a centralized social network in GitHub?<p>Git itself has many of the primitives needed, but issue tracking and CI/CD seem the main pieces still lacking. Seems likely that issues can be solved satisfactorily both natively in git, or in the fediverse. I bet that agents can pass branches/patches amongst themselves just fine, maybe native git (pulling from each others’ remotes on a crontab, or sharing patches by listserv) is actually completely viable now.<p>I also wonder if agents will cause a shift from forking and contributing back upstream, to more like horizontal gene transfer where people or tight teams broadcast their repos and other projects borrow/steal whatever may be useful. You see this with the Claws where maintainers are simply swamped with contributions and no way to verify whether they are correct/positive. (Things like “first time install on a Mac mini breaks at step 7, due to some iMessage issue” are fiendishly difficult to automate”)
>To me it felt liberating to quickly create a repository attached to my name<p>If I remember correctly, it was also one of the few places sticking to the now-standard passing of the parameters via path rather than the '?' URL query part.<p>It might not seem like much now, but then the ease and simple beauty of having just github.com/user/repo - not only for web access but also cloning - was definitely some freshness factor.
Definitely not. That's been a thing for at least as long as mod_rewrite has existed (and I'm sure there's prior art). It was common long before GitHub.
That was just a byproduct of how Rails did routing based on the URL
[flagged]
[flagged]
Huh? The usual pattern is that experiments belong to a user and then they graduate to having their own org iff they grow enough maintainers for that to make sense. How is that toxic or self-centered? It's just like "here's a place to do low-stakes experiments in public view". It's not particularly about ego or selfishness or whatever.
“Organizations” didn't exist until GitHub was already popular and entrenched, and it got popular and entrenched by centering the person developing the code instead of the code that was being developed: <a href="https://github.blog/news-insights/introducing-organizations/" rel="nofollow">https://github.blog/news-insights/introducing-organizations/</a><p>And they weren't free until 2020: <a href="https://docs.github.com/en/get-started/learning-about-github/faq-about-changes-to-githubs-plans" rel="nofollow">https://docs.github.com/en/get-started/learning-about-github...</a>
[flagged]
Good grief. Now the YouTube Shorts crowd is showing up here too.
Very strange take. A lot of software is built on trust and the people behind it. Hence why the social aspect of Github was so important to a lot of open source software.
Hey, thank you for staying polite while expressing disagreement. That's much appreciated.<p>To the risk it might seem surprising, I actually completely agree that trust is essential to software creation and and use.<p>Actually I would more broadly frame it as, no trust, no viable sustainable society, no technical/cultural artifact.<p>But trust and societies can be realized without individualism as underlying chief paradigm.<p>That doesn't mean total negation of individual though. One alternative, among others yet different approches, can be state as a metaphor of individual like a cell in a social body. Thus the term metastasis, as when a cell starts to degenerate in self centric behavior at the expense of the health of the body as a whole. On the other hand, no cell, no body.
I don't think it was important. It just came at a time when sourceforge was being heavily enshittified.
The most insane response I've ever read here, so far.
What a weird take on what GP said...
Bruh.
[flagged]
I am still so salty that Git won out for the average project over Fossil. Sure Git has some performance advantages for massive codebases like the Linux Kernel, but the vast majority of projects will never run into performance limits from their VCS. Fossil’s internal tools (wiki, forum, tickets<issues>, etc) are just so useful to have versioned with your code in one file.<p>I use Fossil for all my freelance work and it so easily allows me to get right back into the context of a project, niche details and agreements had with a client, etc. No need to pollute the codebase or gather together a million emails or notetaking software just to get back up to speed.<p>It can still change, I hate the notion that because Git is so culturally embedded we couldn’t ever switch. Fossil makes it super easy to switch and the workflow is actually easier coming from Git.
A key feature of github is you could bug report on many projects without registering an account for each one, this is not true of fossil. if fossil is to be taken seriously, then it needs a distributed auto id system, oauth or the like, without storing another user and another password.
Funny timing — I've been working on a hosted Fossil service to scratch this exact itch. The integrated wiki+forum+tickets+code is killer for small teams, but most people who'd pick Fossil don't actually want to babysit a server. So we host it.<p>Two things I keep coming back to:
(1) The "opinionated / small-teams only" critique others have raised in this thread is real, and I think Fossil should own it instead of fighting it. The 5,000-engineer monorepo market is a solved problem (Git won). Fossil should own the 1-50 person bracket — where having issues, wiki, forum, and code in one self-contained, syncable SQLite file is a huge unfair advantage.<p>(2) AI agents are a brand-new reason to look at Fossil that didn't exist when Git won. Every repo is a queryable SQLite file. An agent reads tickets + wiki + code + history with one SELECT — not 47 GraphQL calls and a rate limit. RAG and MCP setups against the repo become trivial.<p>We're stuck on the name (fossilforge vs fossilhub).
If you have an opinion: <a href="https://fossilhub.io" rel="nofollow">https://fossilhub.io</a> | <a href="https://fossilforge.io" rel="nofollow">https://fossilforge.io</a> — vote, get early access.<p>The self-hosted side is already shipping at fossilrepo.io if you'd rather run your own.<p>---
Disclosure: founder, so grain of salt accordingly.
Fossil is very easy to self host. If you already have a web server it needs maybe 10 or 15 lines of server config. If you want to avoid start up you need something to autostart/restart the server process. If you point it at a directory you can add a new repo simply by adding a Fossil file to the directory.<p>You can even run it on shared hosting as a CGI (never done it myself).<p>The only thing that took some setup was sending email notifications.<p>> The "opinionated / small-teams only" critique others have raised in this thread is real, and I think Fossil should own it instead of fighting it.<p>I agree I use Fossil for multiple personal and small projects. Anywhere I can, really. It is very simple and everything is distributed.
You should continue with a name which is related to fossils, fossillab.io, boneyard.dev and so on…
"countryclub.com" - ie, a bunch of fossils :)
fossilised.dev .. maybe british spelling.<p>palaeontology.dev ... too awkward.<p>museum.dev has a sort of "this is dead" ring to it.<p>Ironically what fossils are stored in within a museum is referred to as a "repository"..<p>Well, there's only 2 hard problems in computer science right?
The best know hosted Fossil service is <a href="https://chiselapp.com/" rel="nofollow">https://chiselapp.com/</a>
Yeah, museum sounds like dead and rot… However on my small site [1] that’s the name of the fossil repos page<p>[1]: <a href="https://hdrz.cc/museum" rel="nofollow">https://hdrz.cc/museum</a>
> what fossils are stored in within a museum is referred to as a "repository"<p>I own a cute domain for that: repositoryum.com. I had the plans for it, but it's one of those that never came to a realization.
boneyard.dev evokes something dead but that name kinda goes hard
Maybe something fossil-adjacent:<p>- amber.dev<p>- quarry.sh<p>You’ll probably need to play with gTLDs to find something that works.<p>Can also echo “scm” from fossil’s domain:<p>- amberscm.dev<p>Along with useX.com, Xhq.com, etc., patterns.<p>Of the two you have listed, I’d choose fossilforge, but would vote for an alternative TLD since .io has an expected meaning coming from GitHub.
Or, hear me out, we learn to host our own shit again and stop giving all our data to $megacorp after the inevitable buyout.
I trust more a megacorp to survive more than 5 years than a personal host, I can't tell you how many times I've gone to a personal server where something I used was hosted and its dead.
there's a host your own version thats available now <a href="https://fossilrepo.dev" rel="nofollow">https://fossilrepo.dev</a> live server (demo) in fossilrepo.io which is a modern wrapper UI. There's also the standard <a href="https://fossil-scm.org/" rel="nofollow">https://fossil-scm.org/</a> which you can also host yourself on a $5/mo server on Hertzner or the like.
You can (and people did) do same kind of tooling based off git protocol and storage. Hell, even one for distributed code reviews.<p>It just... never was something majority <i>actually</i> want so they didn't really get any traction.<p>Issues wise you also get few nasty cases where you really do <i>not</i> want to keep it with project, like having clients send a bunch of screenshots or even videos of triggering some bugs can grow storage pretty quickly... and while extra few GBs on a file server isn't a big deal, keeping it with code repo just so someone can look at tickets locally is PITA, and you quickly get into "let's not use it, it just makes everything complicated and everyone repo bloated".<p>Someone could probably implement most of fossil features using git as backing store without all that much problems, the wiki/issues/whatever else features would just be separate, parallel branch hierarchy
Those screenshots and videos are taking up space SOMEWHERE, whether it be your inbox or your filesystem, why not have them as unversioned artifacts in your db? (Fossil supports this). Of course if you have multiple people working on it and many assets, other solutions would be better (shared cloud drives, etc). But for my use case of a storing textual information only (and perhaps a demo video, which many Git users often keep a video in their source and link it in the readme), Fossil works great to keep all my stuff together in the same context.<p>I explicitly dislike the idea of using Git as the backing store. Forget the fact that Git is not native on Windows and is immensely bloated; the actual .git folder is a mess for backup systems when working locally compared to a single database file.
> Those screenshots and videos are taking up space SOMEWHERE,<p>Sure but there is a big difference between being stored once (modulo backups) on a central server, and every developer needing to download all the resources for every issue and the entire wiki in order to work on the code at all. It works fine for sqlite, because they only have a handful of developers, so it's not a big deal for them each to have their own local copy of everything. But having to download GBs of issue and wiki data in order to make a pull request (however that would work with fossil) or otherwise contribute is a significant barrier to entry.
I feel like part of that was timing. IIRC, when git was already stable and usable as a daily-driver, Fossil was still sometimes requiring that you completely recreate your repo when updating to a new version.<p>Git certainly had (and perhaps still has) worse user experience, but it worked and felt production-ready, with, of course, one of the largest open source projects in the world using it, and that made all the difference, perception-wise.
Part of the problem is that fossil is <i>very</i> opinionated. It's great if your development flow is similar to that of the sqlite team. But it is very difficult to get it to work for other workflows. And in particular, fossil is designed for use by small teams and isn't really designed to be used by large organizations. This is even explicitly mentioned in the "Fossil versus Git" page (<a href="https://fossil-scm.org/home/doc/trunk/www/fossil-v-git.wiki" rel="nofollow">https://fossil-scm.org/home/doc/trunk/www/fossil-v-git.wiki</a>)
> It can still change, I hate the notion that because Git is so culturally embedded we couldn’t ever switch. Fossil makes it super easy to switch and the workflow is actually easier coming from Git.<p>I was exposed to Mercurial before Git and I stubbornly tried to advocate for it over Git for a while. BitBucket, at the time, gave Github a good run for their money and had great Mercurial support and was what I preferred.<p>I'm not really sure VCS were ever differentiated for there to be a wide world of them. They all solved the same set of problems so similarly that it felt, to me, that there had to be one winner. Right now most of the competition is in the Git Porcelain space.<p>N.B. I actually have a soft spot for darcs, which was my first actual DVCS. I just loved it so much more than svn and refused to use svn in college and used darcs to actually manage my projects and push them to svn after.
I'm still using Mercurial whenever I can (including work!). The Tortoisehg GUI is good for doing reviews, and the command line is comfortable.<p>I grew up on CVS and then Subversion. Played with Bazaar a little, mainly because it could use an SFTP location as the back-end.<p>And I still avoid Git if I can help it. I would/do figure it out when I have to, but it never feels comfortable. Such is my avoidance that I'm dabbling with Jujutsu although I'll still need to really sit down and read through it some more to grok the way it works.
My first distributed VCS was Tom Lord's Arch. I may have started early, but it took me a <i>long</i> time to understand distributed version control, thanks in no small part to Tom Lord, lol. GNU.
You might like pijul if you like darcs
If it got proper tooling this would be true—but the community will need to build it. Darcs has more out of the box & more existing ecosystems to work with. Pijul is barebones by design, ready to be scripted, there’s just not much out there.
> I use Fossil for all my freelance work and it so easily allows me to get right back into the context of a project, niche details and agreements had with a client, etc. No need to pollute the codebase or gather together a million emails or notetaking software just to get back up to speed.<p>Hmm that's interesting to hear. I'm starting up a very small business this year (one guy selling shit at a craft fair booth) and I'm using plaintext accounting files in a Git repo for it. I wonder if Fossil could keep me from re-inventing some note taking and record keeping approaches. I'll have to look into what it can do.
When I tried Fossil it had things weirdly separated.<p>I was expecting when I make a commit, I would have the facility to specify what issues it addressed and it would close them for me automatically. It seemed there is so much opportunity there to "close the loop" when the issue tracker, etc and integrated in your VCS, but it wasn't taken.
This is a current architectural limitation, manifests (defining check-ins) and tickets are different types of artifacts and you cannot combine the card types into the same artifact. Changing this would likely break backwards compatibility with previous Fossil versions and I'd expect resistance. It may still be worth bringing up on the Fossil forum if you desire the feature.<p>Personally speaking though, I don't want things automagically closed GitHub-style based on parsing a check-in comment. An issue ought to be closed with intention.
> I don't want things automagically closed GitHub-style based on parsing a check-in comment.<p>Sure, I get that. I was just disappointed that none of the project management stuff seemed terribly integrated in any way from my brief review. It seemed like opportunities there that were not taken.
You can link the commit with the ticket by including its hash in the commit message, and then mark the ticket as fixed. See here:<p><a href="https://stackoverflow.com/questions/5761669/how-to-fix-a-ticket-with-a-commit-in-fossil" rel="nofollow">https://stackoverflow.com/questions/5761669/how-to-fix-a-tic...</a>
I wanted to host our company wiki in Fossil, but there is no way to import it because Fossil completely separates versioned project docs and the built-in Wiki function. Our git-based wiki could be imported into Fossil as "docs" but would not receive the nice formatting, GUI editor or dedicated page that the Wiki function does. There is also no benefit to manually converting it all to Fossil Wiki as some of our wiki editors work on raw markdown.md files and commit changes by git which is not possible with the Fossil Wiki; everyone would be forced to use the online editor only, whereas currently we have a choice of markdown or Gitea's editor.
For me it was Mercurial, but yeah, being done by Linus and adopted in the Linux kernel was the killer feature for Git's adoption.<p>If Git was created by a random dude, it would never taken off.
Now is a great time for somebody to buy fossilhub.com and create a new community.
I know someone[0] who is working on exactly this right now: <a href="https://fossilrepo.io/" rel="nofollow">https://fossilrepo.io/</a><p>I don't think he's got public sign ups turned on yet. Maybe hit him up on the Twitter for more info.<p>[0] - <a href="https://x.com/ragelink" rel="nofollow">https://x.com/ragelink</a>
There's also "Chisel - Fossil SCM Hosting".<p>"This service is completely free and run because a service like it should exist."<p><a href="https://chiselapp.com/" rel="nofollow">https://chiselapp.com/</a><p>"All public repositories":<p><a href="https://chiselapp.com/repositories/" rel="nofollow">https://chiselapp.com/repositories/</a><p>I don't know if it has all the GitHub features people may be looking for.<p>Chisel runs on Flint, "The ISC licensed codebase behind <a href="http://chiselapp.com" rel="nofollow">http://chiselapp.com</a>.":<p><a href="https://chiselapp.com/user/rkeene/repository/flint/index" rel="nofollow">https://chiselapp.com/user/rkeene/repository/flint/index</a><p>EDIT: Add "...should exist." sentence from the homepage.
I already saw fossilhub.io mentioned in this thread, actually.
I wonder what tradeoffs make Git faster for large repository. Though for a long time that excluded large blobs.
None, it just received the help of the vast majority of well-payed SWE to make it that way
Git has format dedicated for storing snapshots of trees and diffing them, fossil just uses SQLite and few tricks to keep size small
Of tree, or of sub-DAG?<p>"Just use SQLite" feels like missing the forest for the tree (the pun being coincidence here). That is, certainly any database out there already use all kinds of very efficient structures to walk graphs under the wood.<p>Maybe Git has a more bespoke approach to its specific goal of source code as main topic to deal with, and finner layer of abstractions. Which could also explain the clumsy leaky interface it presents.
I think this shows that you do not consider all build-up options here. Let me explain that.<p>Could something like github be made with fossil, aka fossilhub?<p>I believe the answer is ... in theory yes, in practice no. So this already means, if correct, the comparison between git and fossil is incorrect here. Fossilhub would not have dominated; git + github on the other hand did. Again, in theory a fossilhub could win over people to use it (and fossil), but people will compare it to github (back when github was still great) and become quite critical when fossilhub does not offer the same or similar set of functionality. At the least the core functionality - great issues + discussions, easy committing and changing of code and so forth.<p>Perhaps with enough resources, fossilhub could have conquered the world, but for whatever the reason, it did not, and I think this is in part due to the design. GitHub changed how people interact with repositories. They even made it easy to e. g. add files and change them online, at a later point in time. For instance in one project I am a co-maintainer and I rarely have to use the commandline; I can simply edit via the browser as it is. I don't think fossilhub would have done the same - actually, there is not even a fossilhub, so how would you want to compare git to fossil? It's not just the commandline code. Git has github; while it is a separate project, what does fossil have that people know and use?<p>> It can still change, I hate the notion that because Git is so culturally embedded we couldn’t ever switch.<p>We all have our dreams. All desert to become forests or agriculture may be a great idea. Effecting this is hard - but best luck to you betting on fossil here. I don't see it happening. Git raised the barrier here, even if only indirectly via github.
> But maybe the most underappreciated thing GitHub did was archival work: GitHub became a library. It became an index of a huge part of the software commons because even abandoned projects remained findable.<p>I think this is a bad thing actually. Having something that's centralized but helpful-99%-of-the-time atrophies our collective archival skills. If <i>everything</i> had to be seeded by someone to keep it alive, everyone would be better at holding on to their copies of the things they really cared about instead of being able to assume they can just check it out again when they want to.<p>There should be no single place that something can be taken down. When a project on GitHub gets DMCAed it takes everyones' forks with it too. Just look at what happened when Nintendo took down the popular Switch emulators in 2024, where archival/continuation efforts consisted of people figuring out who had the latest revision checked out and sharing it. That was only possible because they were very popular project: <a href="https://news.ycombinator.com/item?id=40254602">https://news.ycombinator.com/item?id=40254602</a><p>Aside: I really love the Splatoon-ish header/footer animation on this site! Very unintrusive, adds a lot to the vibe, and also quickly gets out of your way as soon as you scroll down. I'm totally going to rip this off lol
> Having something that's centralized but helpful-99%-of-the-time atrophies our collective archival skills.<p>Also it feels like "if it's not on GitHub, it doesn't exist", which is a bad thing. Feels like too many developers don't know that code can be stored somewhere else.
Archival is easy but copyright and IP law gets in the way. If we removed obstacles to making information accessible, it would lead to less concentration of power.
I don't agree with this. Github has existed for years and one of the reasons developers trust it is that they never monetized their "archival" work yet (TBD with all the new Copilot features).<p>The alternative would be many sites, each one of them with their own DMCA rules.<p>What would be the better alternative?
Yeah first thing I do when I come across a repo I like is to clone it. I've seen a few reverse engineering projects disappear before my eyes.
> I definitely cringed when Zig moved to Codeberg!<p>If anything Codeberg’s legal structure (being a non-profit) and vision makes it a lot more aligned with the objectives of free and open source projects than GitHub in the long run (which has always been the case but it’s just abundantly clearer today).<p>I think “for-profit corporations providing high quality public services for free” was a <i>zero interest-rate phenomenon</i> and never sustainable.
><i>For a while, leaving GitHub felt like a symbolic move mostly made by smaller projects or by people with strong views about software freedom. I definitely cringed when Zig moved to Codeberg! But I now see people with real weight and signal talking about leaving GitHub. The most obvious one is Mitchell Hashimoto, who announced that Ghostty will move.</i><p>I didn't understand this. I perceive the Zig project and Mitchell Hashimoto / Ghostty to be at similar levels of "weight and signal." Especially because Ghostty is written in Zig.<p>It feels kind of like saying, "Oh, I didn't take this seriously when it was just Fabrice Bellard, but now that an actual influential person like Guido van Rossum is doing it, it's real."
It’s because the more visible people are, the stronger they have a pull on others. It’s not so much about person A vs person B but about what likelihood am I attributing to an individual or project to pull others along. For me projects moving off GitHub prior to Zig didn’t have that yet and even Zig itself didn’t feel that meaningful to me.<p>But you might think about it differently.
I agree with you. But I do see one crucial difference between the Zig and Ghostty announcements, namely that Ghostty did it purely for service degradation reasons while Zig did also mention ideological reasons such as GitHub’s relationship with ICE and their push for AI. Those were, naturally, much discussed points on HN. I can’t help but wonder if that contributed to the “cringing”.
> Regardless of whether GitHub is here to stay or projects find new homes, what I would like to see is some public, boring, well-funded archive for Open Source software. Something with the power of an endowment or public funding to keep it afloat. Something whose job is not to win the developer productivity market but just to make sure that the most important things we create do not disappear.<p>There is already such an organization in Europe:<p><a href="https://www.softwareheritage.org/" rel="nofollow">https://www.softwareheritage.org/</a><p>Underfunded relative to the task, and the (accelerating) speed of free software production.
They are getting access to a supercomputer soon, and will be scanning all their archive for licensing information (using scancode and ort), security information, and other metadata.
The top sponsors are quite telling: US tech companies and hyperscalers, Abu Dhabi, French Government and some french universities.
Codeberg?
The problem is GitHub spends on the order of $100m/year on providing free CI. Nobody else can compete with that. It's <i>possible</i> they could make it shit enough that a large number of projects will say "screw this we'll just pay for CI", but people really like free (and easy!) things so I think we are a <i>long</i> way from that point.
"Nobody else can compete with that"<p>My laptop is on all the time, make a WASM slave and thousands of developers can give their CPU/Memory/Disk for build slaves.<p>Like bitcoin mining, there could be some competition between 3 parallel builds to pick the winner if the output is the same.
> make a WASM slave and thousands of developers can give their CPU/Memory/Disk for build slaves<p>WASM isn't a magic bullet for sandboxing. CI environments assume a full Linux. So you need to either ran a VM (with the attack surface that implies) or a write an x86 emulator in WASM (which would be very slow).<p>You also need anti-abuse to stop bitcoin miners from using your system. GitHub probably have full-time employees working on it.<p>> Like bitcoin mining, there could be some competition between 3 parallel builds to pick the winner if the output is the same.<p>It's a lot more complicated because many builds are not deterministic, you need to store artefacts, build secrets, etc.<p>Companies like golem.network or iex.ec have been working on this problem for a decade and they are still not easy to use.
And yet, GitHub Actions are notoriously broken, and serious customers are self-hosting their runners.<p>Codeberg does have <i>some</i> free CI runners, although I’m not sure what capacity they currently have, and how well it would work out if everybody decides to switch from GitHub today. They do encourage you to pick the smallest runner that works for you, and keep the workflows lean: <a href="https://codeberg.org/actions/meta" rel="nofollow">https://codeberg.org/actions/meta</a><p>Or you can self-host your own runners too, of course.<p>Edit: there’s one caveat – Forgejo Actions are Linux only. If you need Windows or macOS runners, this won’t work for you. But... you could have a readonly GitHub mirror (which you should probably do if you want people to discover your project), and use the GitHub Actions runners for free :-)
I absolutely loved Trac. Getting a Trac setup as step 1 in starting a new open source project was just an <i>unbelievable amount</i> of friction.<p>Fun fact: Django is still running on Trac today, and has been for more than 20 years now: <a href="https://code.djangoproject.com/timeline" rel="nofollow">https://code.djangoproject.com/timeline</a><p>(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.<p>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”.
Bugzilla was relatively painless to setup but it already had a bit of the Jira going on - in that it had SO MANY OPTIONS!<p>I remember being interested in MantisBT and a few others (Launchpad for BZR?) mainly because it seemed they made a bunch of decisions for me.
It's a bit fuzzy, but what I remember was getting it running was painless -- but there was a ton of effort in getting it configured.<p>In retrospect, it was probably the flexibility of projects like Bugzilla that heralded the "opinionated" approaches to software that followed. In many ways software also follows the patterns of the language they are written in . Bugzilla was written in Perl, so of course there is more than one way to do anything.<p>I had forgotten about Mantis, but that was the first tracker that the non-programmers in our group were comfortable using. It is a bit funny how quickly we all migrated to Github as a larger community as it became the default for just about everything.
Bugzilla was too big/complex for pretty much every company I ever worked in :D<p>Trac was perfection. Self-hosted and just the right amount of features.
I've switched to GitHub from Trac because of spam. Despite using Akismet and bayesian filters, on a small instance, there were still several spam tickets if you didn't require an account (for the details, <a href="https://vincent.bernat.ch/en/blog/2011-migrating-to-github" rel="nofollow">https://vincent.bernat.ch/en/blog/2011-migrating-to-github</a>). I am a bit amazed that Trac still exists and is maintained today.
Trac is in many ways what motivated me to build out an app in Python rather than in PHP for redistribution. It had a great plugin system!
I liked bitbucket, it did its job, it didn’t break for me and I preferred mercurial.<p>Employers used GH so I switched but even now I use GH as a dumb git endpoint and do all my build/deploy with docker and shell scripts so switching for me is extremely cheap.<p>For work stuff I’ll use whatever I’m paid to use if I don’t get to make the call just as it was back in the svn days.
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”.<p>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.
> 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.<p>Honestly, Gitlab's CI is one of its killer features.<p>I <i>really</i> enjoy Gitlab CI.<p>But, nearly everything else (kubernetes management, AST, AI "DUO", work items, milestones, snippets, workspaces, "operations", "security dashboards", "value stream managements", "service desk") - ugh, awful.<p>I guess some of the artifact repository stuff is nice, but like; their terraform repository is probably the worst of all choices, all the downsides of the HTTP state backend and no upside..<p>It's so hit and miss; but! the CI is actually good..
I don't hate using Gitlab CI once it's set up; I just hate "put shell scripts in YAML to define how this should work". The least annoying experiences I've had with them are when every entry is literally just a single line that invokes an external script; shell scripting is already annoying enough without having to also spend the time to understand a YAML schema for what order they get invoked in and what environmental variables are in scope (not to mention what the implicit inputs are; a few months ago I tried to add a task to run some check on the commit message for an MR, and I found that even on repositories where the merge commit option is disabled in favor of squashing or fast-forwarding, the top commit message is still a merge commit).
> I guess that award goes to Gitlab now<p>Painfully true - I remember a company I was at replacing GitHub and a bunch of other tools with GitLab because it was better to pay for one tool that does it all. Kind of.
Similar (904 comments): <a href="https://news.ycombinator.com/item?id=47939579">https://news.ycombinator.com/item?id=47939579</a>
Reading this and mitchellh's post I was curious about code archival services, and found a few projects.<p>GitHub has their own: <a href="https://archiveprogram.github.com/" rel="nofollow">https://archiveprogram.github.com/</a><p>Software Heritage is a non-profit funded by
UNESCO: <a href="https://www.softwareheritage.org/2019/08/05/saving-and-referencing-research-software-in-software-heritage/" rel="nofollow">https://www.softwareheritage.org/2019/08/05/saving-and-refer...</a><p>Although they're mostly the code / commit history, not so much surrounding metadata like issues, PRs, discussions, wiki, etc.
I use a self hosted Gitea instance and it's very simple. I was also surprised when Zig moved to Codeberg and had a big blog post about it, but now over time I start to see the reasons materialize in reality.
This got me thinking about code.google.com, I can't believe Google dropped the ball that hard.
Has Google ever done a good job with anything, other than search? I don't want to count YouTube since they bought it, but least they haven't ruined it...
…have you met Google?
Man what a blast from the past. I was on that team before it got shut down.
To add salt to the wound: <a href="https://killedbygoogle.com/" rel="nofollow">https://killedbygoogle.com/</a>
Memories...
It's fun to read stuff like this and then reflect on the journeys of the projects I've been involved with. Most of my open source work has been done with self-hosted infra. My main example is Xfce: back when I started with them in 2004, we had a SVN server, using (I think) CVSweb's then-new SVN support for the web interface, and... maybe that was it?<p>My memory is telling me that I set up Bugzilla at some point after I joined the core team, though that may have been someone else. When git started becoming a big deal, I spearheaded converting our big SVN repo into many git repositories, and set up the cgit web interface for it. We were still using Bugzilla at that point.<p>I left the project in 2009 or 2010 or so (I'd joined a small startup and didn't have much time for OSS, sadly), and rejoined in 2022. In the intervening years they'd stood up a GitLab instance with CI runners, and had migrated everything from Bugzilla to GitLab issues.<p>It's still a very small team (handful of active people), and the infra is mostly managed by one person. It's all very doable, even for small teams. We're very lucky that our infra is generously donated/sponsored, though we also probably get just enough in regular donations that we could pay for it ourselves if we had to. I really appreciate that we're not dependent on Github/Microsoft for anything. Seriously, if you told me 20 years ago that <i>Microsoft</i> of all companies was going to own the largest OSS code forge in the world, I would have thrown up. It still doesn't sit well with me.
An important part to me that gets overlooked is shared logins. Rust runs the tests of all known Rust projects in a tool called `crater`. I was analyzing a run identifying projects relying on internals of Cargo and opening issues. When making 200 issues by hand, it is a big help when the process is low friction: I had credentials for the site and allowing blank templates. Any time I came across a self-hosted instance, I usually ended up giving up.
This is something federation could help with: you would be able to use your account on, say, Codeberg to make issues on all self-hosted instances. Sadly, it’s still not in a great shape: <a href="https://forgefed.org/" rel="nofollow">https://forgefed.org/</a><p>(As a fallback, why not email the maintainers instead?)
If it wasn't for GitHub self-hosting and open-source development would be much more difficult. Like the article says open-source development was obviously still happening but it was a smaller space. I appreciate how many apps I've interacted with because of GitHub like OpenGOAL, IINA, and Ghostty along with the services running on my servers at home like Immich, Glance, Filebrowser, and audiobookshelf. I even used GitHub myself for some private repos, but I've since migrated them to a self-hosted Forgejo container.
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.<p>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.
That’s because most of this post was hanging around as a draft. I originally wrote it after Zig left but I didn’t finish or publish it.
<i>> His post is a response to Mitchell's, from just a few hours ago.</i><p>Is there a link to Mitchell's post somewhere? I can't find one in the article.
<a href="https://mitchellh.com/writing/ghostty-leaving-github" rel="nofollow">https://mitchellh.com/writing/ghostty-leaving-github</a>
<a href="https://news.ycombinator.com/item?id=47939579">https://news.ycombinator.com/item?id=47939579</a>
I'm going to throw out a really naive solution<p>Tangled supports hosting your own knots. Why wouldn't the current GitHub CEO choose to support self-hosted "databases". GH infra can protect you from all the traffic (ssh and http spam), while you keep the social aspect.<p>I don't need ~100 extra features, I need a reliable platform. If that means I need to self-host the storage, runners, etc. fine.
> We Need an Archive<p>This archival project already exists, it is funded by France computer science research agency Inria, by Europe, and maybe by the UN through UNESCO if I'm not mistaken, but I really think it should still receive much more attention and funding to really pursue its goal: <i>Software Heritage</i>.<p><a href="https://www.softwareheritage.org/" rel="nofollow">https://www.softwareheritage.org/</a>
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.
> But if projects move to something more akin to self-hosted forges, to their own self-hosted Mercurial or cgit servers, we run the risk of losing things that we don’t want to lose. The code might be distributed in theory, but the social context often is not. Issues, reviews, design discussions, release notes, security advisories, and old tarballs are fragile.<p>Thankfully, this doesn’t have to be the case – Forgejo imports pretty much everything mentioned. (1) Whether you decide to move to Codeberg or host your own instance, you won’t have to lose the context.<p>But I definitely agree we should also have a metadata archive of some sort, for both GitHub, Codeberg, and self-hosted projects.<p>(1): Not sure about code reviews, and you don’t get the security advisories, though I’m sure it can be replicated with a CI workflow somehow?
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?<p>Then it's BYOR -- bring your own renderer. Trivial CLI bugtrackers, agentic nonsense, pretty web stuff, whatever and the data lives in the repo.
SF was exe + source code as zip file. And an admin that made all the decisions and had to for a project,<p>I do not agree with details, because it was for me before and after git.<p>So the hidden denominator here is and still is git, which sparked a tooling frenzy with reversing flow by being online server first (it wasn’t named cloud back then).<p>So even today, all splinters are doing something around git. That hasn’t changed.<p>What I really miss is the some sort of standardization that GitHub provided for a brief period of time. Projects would get no love aka stars when you couldn’t easily be used even for the experts. Some convenience as well as tooling evolved, devops became a thing.<p>I think of the future of a concept called cocooning. The JavaScript expert of today would be puzzled to write code on a notepad in a html file, because it has become so meta, being TypeScript essentially.<p>There is so much tooling going on that especially Python before AI already felt like I would miss something out if I would code more than 100 lines and that there must be libraries that abstract this all away and instead of coding I should google better.<p>AI is one thing, but the cluttered tech stacks aren’t really sparking any interest or joy in me, I think it is the not invented here syndrome or because I can story.<p>I miss the die hard coders, who stick to a tech stack which simply worked, not optimizing for weird use cases which are contrived at worst and rarely needed at best.<p>This became evident with the decline of data sheets, because Grunt, Gulp etc. as build tools were great but slow. We JavaScript devs couldn’t any longer joke about the compile times of the Backend dudes. And besides that, build times costs you focus, money, cpu time. But this was the main currency.<p>With AI I stopped trying out lots of tools because they feel like a weekend project by some dude who blasted his Claude budget.<p>Over are the fork and commit wars. Until AI battles itself this hard for quality source code I will stick to GitHub.
"We Need an Archive"<p>Before we had FTP, which made easy to mirror stuff with "lftp mirror -p".<p>HTML is not good for archiving.<p>We have to rethink those protocols so that mirroring is made easy, and "git clone" is not an answer sorry.
Smaller, decentralised forges actually make lots of sense from a digital sovereignty point of view. Over reliance on a single instance like GitHub is not healthy in the long run. The issue they would have to solve is federation.
Yeah, federation is really the sticky bit. It's very frustrating for people to have to create yet another account in order to file an issue or submit a pull request.<p>And on top of that, spam is a huge issue. We've progressively further and further locked down new accounts on gitlab.xfce.org because the spam situation has just gotten so bad. We actually don't allow new "native" account creation at this point, and ask people to come to our Matrix channel to ask for an account. We do allow SSO from Github and gitlab.com, but some spam still sneaks through that way too.<p>I have my own personal Gitea instance that just doesn't allow outside users at all. I'd love to move all my personal projects to it, but at some point I would actually like to try to start a community around one or two of them, and I don't want to have to deal with spam.
We already had federation for decentralized forges: Email<p>But that wasn't hip enough so everyone moved to GitHub.
Oh we have a neat solution for that. Just give us your government issued id! I'm joking of course.<p>Thank you for maintaining Xfce! It's the best de around.
I really like the idea of distributed forges, but am not familiar with viable solutions for federation. Are there good options available right now? Or at least a not-terrible option?<p>(Edit: Turns out there’s a very obvious and widely used option. <i>git format-patch</i> + <i>git send-email</i> is used to develop major open source software such as Linux, GCC, and Git itself.)
We used bitbucket for years in our academic research group because GH didn't allow private repos. But otherwise it was better to use, so when they allowed that, we made the switch.
And not a single mention of GitLab. I remember it was a pretty serious contender, sometimes leader, strange that author doesn't mention it.
SVN (subversion) was working excellent for my team, about 20 yrs back. I never saw sufficient justification for the complexity brought in by Git.<p>But as I say, New tech invades the world and makes the perfectly working old tech as incompatible, just by changing the world around it. So git became a necessity imposed.
There was a big hype around it (you probably remember it), and around distributed version control, if you weren't using a DVCS you were suddenly seen as an inferior computer programmer and hence your employment opportunities were diminishing. That perspective when it comes to almost all-things programming-related has only accelerated ("if you're not quick to adapt to agentic AI you will lose your cushy job!"), with the recent AI craze the latest example of that.
I was hoping that by now we would have an up and coming DVCS replacement that functioned as a "github in a box" (pretty sure fossil has been described as that, but it's too much on the cathedral side). Being able to mirror an entire project though version control would significantly help with mirroring if we go back to a decentralized world. Maybe going back to decentralized project hosting is just another pendulum swing similar to how compute moved to the cloud...
I think github is at a point that its too hard to ignore just like google is even though we might not like what they are doing now but we were the one made them this big.
I really worry about a bunch of people going over to codeberg. Site's already super slow, but apparently it's quite nice when self-hosted<p>Anyone who is able to just plop a forgejo instance on their own machines... please do that if possible!
Can a small project do this and (cheaply) be robust to getting slashdotted?<p>Which is often the dream for a small project.<p>Probably yes, Codeberg are very transparent about their infra details and they don't seem wild:<p><a href="https://codeberg.org/Codeberg-Infrastructure/meta" rel="nofollow">https://codeberg.org/Codeberg-Infrastructure/meta</a>
My first was this monster:<p><a href="https://en.wikipedia.org/wiki/Microsoft_Visual_SourceSafe" rel="nofollow">https://en.wikipedia.org/wiki/Microsoft_Visual_SourceSafe</a>
I remember that. I've been writing code since the 70's, and have lost count of the number of source code management systems I have been forced to learn. Early on they were over engineered, and a pain in the ass to learn. Then they'd go "out of fashion" and the next pain-in-the-ass over engineered nonsense was forced and learned. I resisted git FOR FUCKING EVER because i was so tired of relearning how to do the same fucking thing slightly different in some other convoluted over engineered system. But it looked like Git was going to be the forever winner, so I finally gave in and learned git through and through. Fuck now its dying!?
<i>"Hey can you check that file back in?"</i>
<i>Things Fall Apart</i><p>Turning and turning in the widening gyre<p>The falcon cannot hear the falconer;<p>Things fall apart; the centre cannot hold;<p>Mere anarchy is loosed upon the world,<p>The blood-dimmed tide is loosed, and everywhere<p>The ceremony of innocence is drowned
If it wasn’t for SourceForge I’m not sure my life would’ve ended up where it is! They use to promote projects they liked and ended up putting Waterfox on their front page a few times. Really sad when they started blasting people with ads and swapping out installers with adware for popular projects.
By that time I moved to Microsoft’s CodePlex, if anyone else remembers that? Felt like I was the only one using it at the time! I remember the connection speeds to it were atrocious, but appreciated they’d share ad revenue from the downloads of a projects page which was nice. I remember it was actually super expensive to offer downloads [for binaries] back then, using these code hosting websites was the only way to do it for “free”
former CodePlex Product Manager here! I wondered if anyone would mention CodePlex in this discussion :)
I also remember SourceForge fondly, before the ad infested thing.<p>Specially, I remember not "getting" Github at some point. Bitbucket had mercurial support, sourceforge had SVN, and all the Cool projects lived in SF (I'm talking mid/late 2000s).<p>The first time I navigated into a github project and just saw the code three I was puzzled. (SF was centered on <i>the project/product</i> while GH focused on the code.
What is GitHub’s decline? I’ve used it extensively since 2011 ish (to lazy to look up when) it’s only gotten better. What’s the issue?
Great through-history write-up! Thank you.<p>> That is one of the great ironies of modern Open Source. The distributed version control system won, and then the world standardized on one enormous centralized service for hosting it.<p>Cycles everywhere indeed. Perhaps we should -><p>> GitHub wrote a remarkable chapter of Open Source, and if that chapter is ending, the next one should learn from it and also from what came before.<p>Indeed! Try to learn from the inevitable iterations to make the next instance at least that slightly better.<p>... Where the stuff meets the metastuff it seems all works under very similar forces.
My thinking is step-by-step - it works on the individual level, and it scales up.<p>Day to day is step by step and a step today funds the step tomorrow.
GitHub sooner or later will be only source of training data for the AI engine
This “slowly dying” effect is what happens to every company that gets acquired by big monster slug companies like Microsoft.<p>What Microsoft acquisitions still have any of their original spark left in them? Or Oracle? Or IBM? Or Google? Etc…<p>Hell, some Microsoft originals from
inside the company like Xbox have even lost their edge.<p>Money is great and I’m sure I’d take the big check, too, but I’m surprised more tech founders don’t think of their legacy in this way when they decide to sell out.<p>It’s considered a grand accomplishment to essentially lead the wonderful thing you created to its slow demise and hand it over to apathetic quarterly earnings zombies.
I was posting on Planet Source Code before SourceForge existed.
Radicle is a good answer, coupled with a reborn Usenet, maybe Nostr. We have like never before the ability to communicate and cooperate yet most fails to understand and implement that.<p>Nearly any of us could run an XMPP/Matrix server and federate with friends or Nostr/{0xchat,whitenoise}, all with audio, video, text, file exchange etc, yet less than 1% do that.<p>Simply people, techies as well, have forgot the meaning of personal ownership and therefore are owned by someone else.
IMHO the problem is always the same. Social networks (and I consider Github as one in this discussion) tend toward centralization and hence monopolization. But monopolization tends towards enshittification. It happens again and again. There's a new cool player, it grows, it's not the cool player anymore. Rinse and repeat.<p>Unfortunately I don't have a clever solution (to the social aspect of the problem).
If everyone moves off GH, it'll just go back to normal again?
we let one company accidentally become the library of Alexandria for open source, and now we're shocked it's on fire - maybe don't do that again
Maybe something like <a href="https://fossil-scm.org/home/doc/trunk/www/index.wiki" rel="nofollow">https://fossil-scm.org/home/doc/trunk/www/index.wiki</a> is worth another look. Although Forgejo is probably an easier switch from GitHub. If their federation ideas play out well, that could be a good outcome from all this
> That is why I find what is happening to GitHub today so sad and so disappointing. I do not look at it as just the folks at Microsoft making product decisions I dislike. GitHub was part of the social infrastructure of Open Source for a very long time.<p>Well ... sad or not sad ...<p>I remember I was very displeased when Microslop, 'xcuse me, Microsoft assimilated GitHub. But for some time it worked quite ok-ish, to some extent. Only more recently are things suddenly breaking down. I am not sure why they break down right now, but I suspect it has a lot to do with the new AI-focus Microslop pushes onto everything. The AI permeates everything like a virus and contages things (I just tried to create a new word from contagious ...). It seems as if this is the real new corporate identity. As Microslop proceeds to dive deeper into AI (they have no alternative anymore, they already sold their soul to AI), they forget that GitHub used to be about people, first and foremost. Steve Ballmer also had this with his fake antics aka "Developers developer developers" many years ago in 1999 (<a href="https://www.youtube.com/watch?v=8fcSviC7cRM" rel="nofollow">https://www.youtube.com/watch?v=8fcSviC7cRM</a> - at the least Ballmer was entertaining, the current slop-CEO is boring to no ends).<p>> So when I think about GitHub’s decline, I also think about what came before it, and what might come after it.<p>Well - the decline happens largely because Microslop totally struggles. They could have decoupled departments and what not, but they decided the corporate strategy is AI-only now. And this creates a ton of downstream problems. So in many ways the current CEO is to be held responsible; he is in charge since 2014 after all. Fatigue kicks in. I am not saying a single person alone is responsible for failure, but it is clear that whatever the reasons for problems, this comes from Microslop first and foremost. The GitHub team contributes to this decline as well (services no longer working suddenly) but it really is induced from top, aka the overall corporate strategy here. And I also don't see Microslop being able to change course - they overcommitted already, so now the decline is indeed unstoppable.<p>> GitHub changed how Open Source feels, and later npm and other systems changed how dependencies feel. Put them together and you get a world in which publishing code is almost frictionless<p>Frictionless is a strange word. I retired from rubygems.org when shopify flooded the zone with ... corporate agenda. The final straw was the 100k download limit ("past that point we disallow you from removing old code you published to rubygems.org", which meant that people would download old code and assume that I would maintain that, which clearly was a lie, so thanks for that RubyCentral ... a year after that they went amok and mass-fired numerous devs; the whole story is a bit more complicated than that, but I can now wisely nod my head, since I retired about a year from that before that mass-fire devs event unfolding). I think if you have a source code hosting service in place, no matter what it is, you need to think about making publishing code super-easy at all times, including the UI. GitHub did this, sort of; I notice this when I compare it to gitlab. Perhaps gitlab has more features, but using it is soooooo much more annoying compared to GitHub. Codeberg lacks features on the other hand. Offering a good service here is actually difficult. It almost seems as if there are no clever UI designers anymore.<p>> My first Open Source projects lived on infrastructure I ran myself. There was a Trac installation, Subversion repositories<p>Well. I hated using Trac. Reporting issues is of course possible, but it feels so much more cumbersome than github issues. What could help would be to kind of make semi-universal IDs, e. g. I register once, but then I could use the same account on many different issue trackers. Right now I need to register for each instance and that is just tedious. I keep a password file (don't tell anyone) and I noticed that, say, after about 100 different websites and names and password, it just becomes unmanageable. Yes, I could use software to help me with that, but I decided that I simply no longer want to have a gazillion accounts. I almost never register for phpBB webforums (though discourse appears to be killing phpBB anyway).<p>> You could find forks, and old issues and discussions all stayed online.<p>That is true in general, but I would like to remind the blog author here that when the xz backdoors utils were found, Microslop took down the whole repository INCLUDING discussions. I remember that because I also discussed this on the xz utils github issue; and next day when I looked for more discussions, the whole thing was gone. Microslop censored here. Lateron the repository was back again, some days later, but if I recall correctly the whole discussion section was also gone. Microslop did not like the discussion; perhaps it was the author too, but the initial removal was from Microslop. So why was that bad? The whole discussion contained valuable information for people who were not yet familiar with this. Thus, Microslop deprived people of that information. Since then I am very wary about "trusting" Microslop or any private actor here when it comes to censorship. So I would not trust the "discussions stay online" claim here.
[dead]
[flagged]
> Before GitHub, Open Source was a much smaller world.<p>Not that much smaller right-before GitHub and right-after it became available.<p>> but in the number of projects most of us could realistically depend on.<p>Most FOSS I realistically depend on I don't obtain from GitHub actually.<p>> There were well-known projects, maintained over long periods of time by a comparatively small number of people.<p>There were even more not-well-known projects, maintained for less time, by a larger number of people. They just weren't that many of them in one place.<p>> You knew the names.<p>You absolutely did not know the names. Post author is just thinking of the names they knew as though those were everybody.<p>> reputation mattered in a very direct way.<p>And now it doesn't?<p>> We took pride (and got frustrated) when the Debian folks came and told us our licensing stuff was murky or the copyright headers were not up to snuff, because they packaged things up.<p>RedHat was just as popular a distribution; and most users used Windows (like they do today); and the BSD distributions were a thing (although we didn't have Apple's BSD, i.e. MacOS)<p>Bottom line: Inaccurate description of history.
> You absolutely did not know the names. Post author is just thinking of the names they knew as though those were everybody.<p>I absolutely knew the names of the people I interacted with and whose projects I used. I even went to conferences with some of them. When I worked on my first web portal for Ubuntu we had a total of about ~4 dependencies and all was vendored. I knew the person who packaged my Python libraries for Debian.<p>You might call it an inaccurate description of history but it is very much <i>my</i> experience.
back in the day, I work in a web hosting company.<p>I know every name on mysql devel team.<p>The only reason i subscribe that mail list is: i reported some bugs and need to follows the release.<p>Signal to noise ratio on those mailing list was high. I can't say the same for github or discord
> I know every name on mysql devel team.<p>That's one project. You did not know every name, or most names, in FOSS generally. Today as well - a project which uses GitHub still needs a mailing list, web forum, chat channel (Matrix/IRC/discord/Telegram/whatever) to discuss and coordinate, and that hasn't changed.<p>As for whether signal to noise ratio on mailing lists was high - that really depends on the list. I don't see that much noise on GitHub repositories, to be honest - it's not easy to post noise that many people will see, so there's not much motivation for it.
I'm working pretty hard on building what comes after Github, but I'm going full-tilt boogie and trying to also work out what comes after Git.<p>I'd love to have a longer conversation with you about how we can seed a better system, because on the off chance I'm successful I have a once-in-a-generation opportunity to fix past mistakes.