{"thread":{"id":"62189","subject":"git-scm.com is now a static website","startedAt":"2024-09-24T22:07:15Z","lastAt":"2024-10-09T17:33:12Z","messageCount":12,"participants":["Johannes Schindelin","Taylor Blau","brian m. carlson","Jeff King","Junio C Hamano","Toon Claes","Patrick Steinhardt","Scott Chacon","Christian Couder"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"503436","messageId":"c3e372f6-3035-9e6b-f464-f1feceacaa4b@gmx.de","threadId":"62189","inReplyTo":null,"subject":"git-scm.com is now a static website","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2024-09-24T22:07:05Z","receivedAt":"2024-09-24T22:07:15Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi all,\n\nalmost 400 weeks after Matt Burke started the process with\nhttps://github.com/spraints/git-scm.com/commit/60af4ed3bc60 of migrating\nGit's home page away from being a Rails app to being a static website that\nis hosted on GitHub pages instead, today marks the day when Git's home\npage at https://git-scm.com/ has finally moved. Or actually: yesterday\n(because I took so long writing this email that I ended up sending it\nafter midnight).\n\nThis was truly a team effort, and I would like to celebrate everyone who\ncontributed:\n\n- Jeff King for nerdsniping Matt Burke to look into migrating the site to\n  Jekyll,\n\n- Matt Burke for the first spike that identified what would be easy and\n  what would be tricky in said migration,\n\n- Victoria Dye for working with me during the first hackathon and figuring\n  out all the hard parts such as sorting and filtering the GUIs at\n  https://git-scm.com/downloads/guis,\n\n- Bjørn Erik Pedersen for his tireless work on Hugo, a static site\n  generator that is fast enough to handle the amount of content on Git's\n  home page within a reasonable amount of time (unlike Jekyll, sadly),\n\n- Andrei Rybak, Pedro Rijo, Kaartic Sivaraam and Todd Zullinger for\n  testing the site when it was still rough around its edges,\n\n- Oswald Buddenhagen for pointing out that the auto-generated content\n  needs to be tracked separately from the non-generated content,\n\n- Todd Zullinger for suggesting to use an automated link checker,\n\n- Matthias Aßhauer for reviewing (part of) that humongous 242-commits\n  strong PR at https://github.com/git/git-scm.com/pull/1804,\n\n- Liam Bigelow for writing the only client-side Javascript-backed search\n  engine (called Pagefind) capable of dealing with the size of\n  git-scm.com, and particularly for his patience and for his competent &\n  kind assistance when I tried to adapt Pagefind to the needs of Git's\n  home page, so that searching for Git's subcommands will find the\n  corresponding manual pages first,\n\n- Matthias Endler and Thomas Zahner for their extensive work on the link\n  checker Lychee, including their outstanding help with my PR to support\n  the extension-less URLs we want to see on git-scm.com,\n\n- Toon Claes for not only pointing out that the style sheet for the search\n  results needs fixing but also for fixing it right away,\n\n- Taylor Blau and Jeff King for endorsing the work enthusiastically and\n  suggesting to switch over already at the end of the Git Contributor\n  Summit that took place at GitMerge '24.\n\n- Taylor Blau for assisting in the switch, taking care of the DNS\n  adjustments, and in particular for taking care of the rollback when the\n  first attempt at switching failed (due to caching issues) allowing me to\n  catch my train.\n\nYou will note that the site looks pretty similar to the version before,\nand this is of course intentional.\n\nThere are subtle differences, though. For example, the site search is now\nlanguage-dependent. Searching for \"commit\" when on a Spanish version of a\nmanual page will find only matching Spanish pages:\n\nhttps://git-scm.com/search/results?search=commit&language=es\n\nAs with all big efforts, I am under no illusion about everything working\nas intended, I do expect some fall-out to crop up (e.g. external links\nthat might now be broken, even if I tried very hard to avoid that). I hope\nthat the team spirit I described above invites more helping hands in\ngetting those issues found and sorted out.\n\nThere are also new things that have sprung up that are not caused by the\nmigration to Hugo/Pagefind, for example some diagrams no longer shown (see\nhttps://github.com/git/git-scm.com/issues/1862) because the Google Charts\nAPI entered the Google Graveyard. Any takers?\n\nCiao,\nJohannes\n"},{"id":"503443","messageId":"ZvM65LqtFW8f9uqC@nand.local","threadId":"62189","inReplyTo":"c3e372f6-3035-9e6b-f464-f1feceacaa4b@gmx.de","subject":"Re: git-scm.com is now a static website","fromName":"Taylor Blau","fromEmail":"me@ttaylorr.com","sentAt":"2024-09-24T22:19:16Z","receivedAt":"2024-09-24T22:19:19Z","isPatch":false,"sender":{"key":"me@ttaylorr.com","avatar":"https://avatars.githubusercontent.com/u/301000140?v=4"},"body":"On Wed, Sep 25, 2024 at 12:07:05AM +0200, Johannes Schindelin wrote:\n> Hi all,\n>\n> almost 400 weeks after Matt Burke started the process with\n> https://github.com/spraints/git-scm.com/commit/60af4ed3bc60 of migrating\n> Git's home page away from being a Rails app to being a static website that\n> is hosted on GitHub pages instead, today marks the day when Git's home\n> page at https://git-scm.com/ has finally moved. Or actually: yesterday\n> (because I took so long writing this email that I ended up sending it\n> after midnight).\n>\n> This was truly a team effort, and I would like to celebrate everyone who\n> contributed:\n\nI'm really excited to see this change (or really, lack of change,\nbecause the conversion was so seamless and faithful to the original\ndesign).\n\nThank you for sticking with this for all these years and seeing it\nthrough to the finish line. Congratulations to yourself and those below\nfor all of the hard work that went into this!\n\n> - Taylor Blau and Jeff King for endorsing the work enthusiastically and\n>   suggesting to switch over already at the end of the Git Contributor\n>   Summit that took place at GitMerge '24.\n>\n> - Taylor Blau for assisting in the switch, taking care of the DNS\n>   adjustments, and in particular for taking care of the rollback when the\n>   first attempt at switching failed (due to caching issues) allowing me to\n>   catch my train.\n\nI just clicked a few buttons ;-).\n\nAs an aside, I am really glad to be able to spin down our Heroku account\nand for the opportunity to save the project some money. We're spending\nabout ~$60/mo USD on Heroku, and I'm glad to be able to put that money\nto other uses that will benefit the project.\n\nI haven't yet spun down the dynos on Heroku, on the off-chance that we\nneed to quickly get back to the non-static version of the site. But the\nrollout has gone so smoothly that I doubt doing so will be necessary. In\na couple of days I'll go ahead and spin them down, assuming nothing has\nchanged.\n\n> You will note that the site looks pretty similar to the version before,\n> and this is of course intentional.\n>\n> There are subtle differences, though. For example, the site search is now\n> language-dependent. Searching for \"commit\" when on a Spanish version of a\n> manual page will find only matching Spanish pages:\n>\n> https://git-scm.com/search/results?search=commit&language=es\n\nSounds like an improvement to me ;-). Thanks again for all of your hard\nwork, Johannes.\n\nThanks,\nTaylor\n"},{"id":"503446","messageId":"ZvM8-z-0QD9OEs4R@tapette.crustytoothpaste.net","threadId":"62189","inReplyTo":"c3e372f6-3035-9e6b-f464-f1feceacaa4b@gmx.de","subject":"Re: git-scm.com is now a static website","fromName":"brian m. carlson","fromEmail":"sandals@crustytoothpaste.net","sentAt":"2024-09-24T22:28:11Z","receivedAt":"2024-09-24T22:28:13Z","isPatch":false,"sender":{"key":"sandals@crustytoothpaste.net","avatar":"https://avatars.githubusercontent.com/u/497054?v=4"},"body":"On 2024-09-24 at 22:07:05, Johannes Schindelin wrote:\n> Hi all,\n> \n> almost 400 weeks after Matt Burke started the process with\n> https://github.com/spraints/git-scm.com/commit/60af4ed3bc60 of migrating\n> Git's home page away from being a Rails app to being a static website that\n> is hosted on GitHub pages instead, today marks the day when Git's home\n> page at https://git-scm.com/ has finally moved. Or actually: yesterday\n> (because I took so long writing this email that I ended up sending it\n> after midnight).\n\nThis is great news, and I appreciate everyone's contributions here.  As\nI said at the contributor summit, it's fantastic to see that we've\nmanaged to preserve all the links, including the page fragments, which I\nreally appreciate since I've been trying to link the Git FAQ from\neverywhere on the Internet.\n\nThanks again for all your work.\n-- \nbrian m. carlson (they/them or he/him)\nToronto, Ontario, CA\n"},{"id":"503447","messageId":"20240924222924.GC1148242@coredump.intra.peff.net","threadId":"62189","inReplyTo":"c3e372f6-3035-9e6b-f464-f1feceacaa4b@gmx.de","subject":"Re: git-scm.com is now a static website","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2024-09-24T22:29:24Z","receivedAt":"2024-09-24T22:29:26Z","isPatch":false,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Wed, Sep 25, 2024 at 12:07:05AM +0200, Johannes Schindelin wrote:\n\n> almost 400 weeks after Matt Burke started the process with\n> https://github.com/spraints/git-scm.com/commit/60af4ed3bc60 of migrating\n> Git's home page away from being a Rails app to being a static website that\n> is hosted on GitHub pages instead, today marks the day when Git's home\n> page at https://git-scm.com/ has finally moved. Or actually: yesterday\n> (because I took so long writing this email that I ended up sending it\n> after midnight).\n> \n> This was truly a team effort, and I would like to celebrate everyone who\n> contributed:\n\nYay! A big thank _you_ for carrying it all through to completion.\n\nI cowered in fear from the project on multiple occasions. And even when\nyou started working on it, I intentionally avoided getting involved\nbecause I knew what a rabbit hole it could become. So I am doubly happy\nthat it was completed, and without me. :)\n\n> As with all big efforts, I am under no illusion about everything working\n> as intended, I do expect some fall-out to crop up (e.g. external links\n> that might now be broken, even if I tried very hard to avoid that). I hope\n> that the team spirit I described above invites more helping hands in\n> getting those issues found and sorted out.\n\nYeah. One of the reasons I was so enthusiastic about switching is that\nwe'd routinely see small breakages with the old site (failing\ntranslation imports, search index going belly-up, oops we need to move\nto a new version of ruby which subtly breaks all sorts of things, etc).\nPeople will generally open issues in the GitHub repo as they see things,\nand I figured that even with a few rough edges the new site was probably\ngoing to be more reliable than the old one.\n\n-Peff\n"},{"id":"503453","messageId":"xmqq7cb0r4lu.fsf@gitster.g","threadId":"62189","inReplyTo":"c3e372f6-3035-9e6b-f464-f1feceacaa4b@gmx.de","subject":"Re: git-scm.com is now a static website","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2024-09-24T23:53:17Z","receivedAt":"2024-09-24T23:53:20Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:\n\n> almost 400 weeks after Matt Burke started the process with\n> https://github.com/spraints/git-scm.com/commit/60af4ed3bc60 of migrating\n> Git's home page away from being a Rails app to being a static website that\n> is hosted on GitHub pages instead, today marks the day when Git's home\n> page at https://git-scm.com/ has finally moved. Or actually: yesterday\n> (because I took so long writing this email that I ended up sending it\n> after midnight).\n>\n> This was truly a team effort, and I would like to celebrate everyone who\n> contributed:\n\nThanks, everyone.  It is great to see such a long-lived effort come\nto successful completion.\n"},{"id":"503511","messageId":"87o74a4y1n.fsf@iotcl.com","threadId":"62189","inReplyTo":"c3e372f6-3035-9e6b-f464-f1feceacaa4b@gmx.de","subject":"Re: git-scm.com is now a static website","fromName":"Toon Claes","fromEmail":"toon@iotcl.com","sentAt":"2024-09-26T08:30:28Z","receivedAt":"2024-09-26T08:30:50Z","isPatch":false,"sender":{"key":"toon@iotcl.com","avatar":"https://avatars.githubusercontent.com/u/121621?v=4"},"body":"Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:\n\n> This was truly a team effort, and I would like to celebrate everyone who\n> contributed:\n\nAmazing job everyone, it's really impressive!\n\n> - Toon Claes for not only pointing out that the style sheet for the search\n>   results needs fixing but also for fixing it right away,\n\nI only wrote five lines of CSS, but thanks for having me take part.\n\n> You will note that the site looks pretty similar to the version before,\n> and this is of course intentional.\n\nThat's the best thing. Nobody's gonna know...\n\n> There are also new things that have sprung up that are not caused by the\n> migration to Hugo/Pagefind, for example some diagrams no longer shown (see\n> https://github.com/git/git-scm.com/issues/1862) because the Google Charts\n> API entered the Google Graveyard. Any takers?\n\nYeah, serving static images makes a lot more sense. Unfortanately I'm\nnot familiar with d3.js.\n\nBut I will have a look at the GitHub issue tracker if there's anything\nelse I can help out with.\n\n-- \nToon\n"},{"id":"503553","messageId":"ZvVncnF8A-zZLJ-q@pks.im","threadId":"62189","inReplyTo":"c3e372f6-3035-9e6b-f464-f1feceacaa4b@gmx.de","subject":"Re: git-scm.com is now a static website","fromName":"Patrick Steinhardt","fromEmail":"ps@pks.im","sentAt":"2024-09-26T13:53:54Z","receivedAt":"2024-09-26T13:54:03Z","isPatch":false,"sender":{"key":"ps@pks.im","avatar":"https://avatars.githubusercontent.com/u/4056630?v=4"},"body":"On Wed, Sep 25, 2024 at 12:07:05AM +0200, Johannes Schindelin wrote:\n> Hi all,\n> \n> almost 400 weeks after Matt Burke started the process with\n> https://github.com/spraints/git-scm.com/commit/60af4ed3bc60 of migrating\n> Git's home page away from being a Rails app to being a static website that\n> is hosted on GitHub pages instead, today marks the day when Git's home\n> page at https://git-scm.com/ has finally moved. Or actually: yesterday\n> (because I took so long writing this email that I ended up sending it\n> after midnight).\n> \n> This was truly a team effort, and I would like to celebrate everyone who\n> contributed:\n\nThanks to all of you, and you specifically, Johannes! The new website\ncertainly feels pleasingly fast. And other than that I wouldn't really\nbe able to tell that anything changed -- awesome job!\n\nPatrick\n"},{"id":"503653","messageId":"CAP2yMa+PtRADLB2ZL4U3S8X+87Ddz4UZQNMmtEvV5p9nyoq5SA@mail.gmail.com","threadId":"62189","inReplyTo":"c3e372f6-3035-9e6b-f464-f1feceacaa4b@gmx.de","subject":"Re: git-scm.com is now a static website","fromName":"Scott Chacon","fromEmail":"schacon@gmail.com","sentAt":"2024-09-29T08:41:51Z","receivedAt":"2024-09-29T08:42:04Z","isPatch":false,"sender":{"key":"schacon@gmail.com","avatar":"https://gravatar.com/avatar/9b13a8a078e1dcf8588c4eea9554445d51ebed6c41b51f56f4d96738130b05c6?d=mp&s=160"},"body":"Hey,\n\nOn Wed, Sep 25, 2024 at 12:07 AM Johannes Schindelin\n<Johannes.Schindelin@gmx.de> wrote:\n>\n> Hi all,\n>\n> almost 400 weeks after Matt Burke started the process with\n> https://github.com/spraints/git-scm.com/commit/60af4ed3bc60 of migrating\n> Git's home page away from being a Rails app to being a static website that\n> is hosted on GitHub pages instead, today marks the day when Git's home\n> page at https://git-scm.com/ has finally moved. Or actually: yesterday\n> (because I took so long writing this email that I ended up sending it\n> after midnight).\n\nBig thanks to everyone involved in making this happen. As I'm pretty\nsure that nearly everything you've struggled valiantly to replace was\nlargely my Ruby stuff from a decade ago, I appreciate the effort to\nmove to something more stable and maintainable.\n\n> There are also new things that have sprung up that are not caused by the\n> migration to Hugo/Pagefind, for example some diagrams no longer shown (see\n> https://github.com/git/git-scm.com/issues/1862) because the Google Charts\n> API entered the Google Graveyard. Any takers?\n\nSo, I commented on this issue, but maybe this is a good thing to\ndiscuss at the group level. The images on this page were comparing the\nspeed of common operations between Git and _Subversion_. Ugh. Who\ncares now? I wrote all this stuff in the early days because those\namong us old enough to remember the fall of the Berlin Wall were still\nusing systems like Subversion then and I was trying to sell Git's\nvirtues. But now _everybody_ uses Git, there is no reason to sell it\nanymore, especially versus something like Subversion.\n\nThe simple thing would be to solve issues like this by just removing\nthis specific content, but we could also work on a perhaps more\nvaluable project to rethink the website content entirely. Why are\npeople coming to git-scm.com? What information are they looking for?\nHow could we answer those questions most efficiently?\n\nThis is essentially what my first version of git-scm.com was trying to\ndo when I registered the domain and launched the first version 16\nyears ago as an alternative to git.or.cz:\n\nhttps://lore.kernel.org/git/d411cc4a0807251035i7aed2ec9wef7e8f1b3ae4c585@mail.gmail.com/\n\nBut as I said, the answers to these questions are very different today\nthan they were 16 years ago.\n\nThe version I helped launch 12 years ago (essentially the exact same\nsite that exists there today) was trying to do the same thing -\ndetermine what people are coming to the site for and give them that\ninformation as quickly and easily as possible:\n\nhttps://lore.kernel.org/git/CAP2yMaJy=1c3b4F72h6jL_454+0ydEQNXYiC6E-ZeQQgE0PcVA@mail.gmail.com/\n\nI would love to take another crack at this, I'm happy to put some\ndesign resources and further engineering (built off the great work\nJohannes has done here) into the project. It would be great to get\nsome feedback from this group as to what they think would be most\nvaluable for people today.\n\nFor example, I think the book contents and the man-page hosting has\nbeen incredibly valuable. I still use those resources today from\nGoogle searches. I feel like perhaps the Guides section could be\nstructured and presented better - there is some great documentation\nthere. I have been talking to Apress on and off about a third edition,\nperhaps a revamp of that content is also overdue - the last edition of\nthat was published in 2014.\n\nI think the entire \"About\" section should be totally rethought.\n\nPerhaps adding something about different use cases - large files for\ngame development, etc. There is no mention of LFS or partial cloning\nor anything here.\n\nThere is no information currently on any forge or hosting options,\nwhich seems silly. I think at the time I was trying to avoid\n\"advertising\" for GitHub, but it would be nice for people to know all\nthe options for hosting their code, just as we have a client section.\nEven more CLI clients and tools, rather than just GUIs - things like\ngit-absorb, stacked git, etc.\n\nPerhaps more videos - there is so much great content on YouTube we\ncould link to. Right now it's like Linus's talk, my old Google talk\nand 4 Matt McCullough tutorials.\n\nI would love to pull in Git Rev News as a blog on git-scm.com, and/or\nlink to Taylor's regular posts about what's new in the new versions.\nIt's such great content and would be nice to have more visible.\nHonestly, this whole website would be nice to incorporate:\nhttps://git.github.io/rev_news/\n\nIn the end, I'm happy to put some work into this, or perhaps work with\nJohannes and Taylor and Matt and whomever else is maintaining the site\nnow.\n\nScott\n"},{"id":"503669","messageId":"CAP8UFD0uUJ3Ztwy+GDQe_tjf5KnHLyqW-2eDLf+qErF2dFgs-Q@mail.gmail.com","threadId":"62189","inReplyTo":"CAP2yMa+PtRADLB2ZL4U3S8X+87Ddz4UZQNMmtEvV5p9nyoq5SA@mail.gmail.com","subject":"Re: git-scm.com is now a static website","fromName":"Christian Couder","fromEmail":"christian.couder@gmail.com","sentAt":"2024-09-30T07:46:57Z","receivedAt":"2024-09-30T07:47:11Z","isPatch":false,"sender":{"key":"christian.couder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/208954?v=4"},"body":"Hi,\n\nOn Sun, Sep 29, 2024 at 10:42 AM Scott Chacon <schacon@gmail.com> wrote:\n> On Wed, Sep 25, 2024 at 12:07 AM Johannes Schindelin\n> <Johannes.Schindelin@gmx.de> wrote:\n\n> > almost 400 weeks after Matt Burke started the process with\n> > https://github.com/spraints/git-scm.com/commit/60af4ed3bc60 of migrating\n> > Git's home page away from being a Rails app to being a static website that\n> > is hosted on GitHub pages instead, today marks the day when Git's home\n> > page at https://git-scm.com/ has finally moved. Or actually: yesterday\n> > (because I took so long writing this email that I ended up sending it\n> > after midnight).\n\nCongrats and thanks for making it happen!\n\n> The simple thing would be to solve issues like this by just removing\n> this specific content, but we could also work on a perhaps more\n> valuable project to rethink the website content entirely. Why are\n> people coming to git-scm.com? What information are they looking for?\n> How could we answer those questions most efficiently?\n>\n> This is essentially what my first version of git-scm.com was trying to\n> do when I registered the domain and launched the first version 16\n> years ago as an alternative to git.or.cz:\n>\n> https://lore.kernel.org/git/d411cc4a0807251035i7aed2ec9wef7e8f1b3ae4c585@mail.gmail.com/\n>\n> But as I said, the answers to these questions are very different today\n> than they were 16 years ago.\n>\n> The version I helped launch 12 years ago (essentially the exact same\n> site that exists there today) was trying to do the same thing -\n> determine what people are coming to the site for and give them that\n> information as quickly and easily as possible:\n>\n> https://lore.kernel.org/git/CAP2yMaJy=1c3b4F72h6jL_454+0ydEQNXYiC6E-ZeQQgE0PcVA@mail.gmail.com/\n\nThanks for your previous work on the website and for this background\ninformation!\n\n> I would love to take another crack at this, I'm happy to put some\n> design resources and further engineering (built off the great work\n> Johannes has done here) into the project. It would be great to get\n> some feedback from this group as to what they think would be most\n> valuable for people today.\n\nGlad that you are willing to put more effort on the website!\n\n> For example, I think the book contents and the man-page hosting has\n> been incredibly valuable. I still use those resources today from\n> Google searches. I feel like perhaps the Guides section could be\n> structured and presented better - there is some great documentation\n> there. I have been talking to Apress on and off about a third edition,\n> perhaps a revamp of that content is also overdue - the last edition of\n> that was published in 2014.\n>\n> I think the entire \"About\" section should be totally rethought.\n>\n> Perhaps adding something about different use cases - large files for\n> game development, etc. There is no mention of LFS or partial cloning\n> or anything here.\n\nI agree that having content about those topics could help. It would\nperhaps avoid companies and projects around Git duplicating such kind\nof content on their respective websites.\n\n> There is no information currently on any forge or hosting options,\n> which seems silly. I think at the time I was trying to avoid\n> \"advertising\" for GitHub, but it would be nice for people to know all\n> the options for hosting their code, just as we have a client section.\n> Even more CLI clients and tools, rather than just GUIs - things like\n> git-absorb, stacked git, etc.\n\nI think it would be a good idea to improve on this too, but care\nshould be taken to keep a level playing field for all tools, solutions\nand companies.\n\n> Perhaps more videos - there is so much great content on YouTube we\n> could link to. Right now it's like Linus's talk, my old Google talk\n> and 4 Matt McCullough tutorials.\n>\n> I would love to pull in Git Rev News as a blog on git-scm.com, and/or\n> link to Taylor's regular posts about what's new in the new versions.\n> It's such great content and would be nice to have more visible.\n\nAbout Taylor's regular posts on GitHub's website, GitLab decided some\ntime ago to also have their own news about new Git versions:\n\nhttps://about.gitlab.com/blog/2024/07/29/whats-new-in-git-2-46-0/\nhttps://about.gitlab.com/blog/2024/04/30/whats-new-in-git-2-45-0/\nhttps://about.gitlab.com/blog/2024/02/26/gitlabs-contributions-to-git-2-44-0/\nhttps://about.gitlab.com/blog/2024/01/11/the-contributions-we-made-to-the-git-2-43-release/\n\nThat's because when writing for one company's blog, people tend to\noveremphasize what that company contributed, and to emphasize less\nwhat other companies (especially competitors) contributed. I think\nthis is normal and not specific to GitHub by the way.\n\nAnyway if only GitHub's version of what happened would be shown by the\nGit project, it would seem like the Git project would endorse it in\nsome ways which would not be fair.\n\n> Honestly, this whole website would be nice to incorporate:\n> https://git.github.io/rev_news/\n\nI would have hoped it would be the whole https://git.github.io/ (Git\nDeveloper Pages) site instead of just the Git Rev News part of it.\nThere are basically 3 parts to the Git Developer Pages: Git Rev News\nrelated pages, the Hacking Git page and the mentoring program pages,\nand I think it would not make much sense to move only parts of them to\ngit-scm.com as they are all related to trying to encourage people to\nparticipate in Git's development. We could either move them all to\nsubsections of https://git-scm.com/community or perhaps create a high\nlevel https://git-scm.com/developer or\nhttps://git-scm.com/development. One big advantage in deprecating the\nwhole Git Developer Pages site would be to avoid issues with style\nsheets, with layouts on mobile phones, etc on 2 different websites\ninstead of just one. We would need to keep the Git Developer Pages\nsite on for some time and add redirects for most pages of it though.\n\nI have created the following issue to discuss this:\n\nhttps://github.com/git/git.github.io/issues/729\n\nbut I am Ok with discussing it here if people prefer.\n\n> In the end, I'm happy to put some work into this, or perhaps work with\n> Johannes and Taylor and Matt and whomever else is maintaining the site\n> now.\n\nThanks,\nChristian.\n"},{"id":"503737","messageId":"ZvrNmsycmamx2dcR@nand.local","threadId":"62189","inReplyTo":"ZvM65LqtFW8f9uqC@nand.local","subject":"Re: git-scm.com is now a static website","fromName":"Taylor Blau","fromEmail":"me@ttaylorr.com","sentAt":"2024-09-30T16:11:06Z","receivedAt":"2024-09-30T16:11:09Z","isPatch":false,"sender":{"key":"me@ttaylorr.com","avatar":"https://avatars.githubusercontent.com/u/301000140?v=4"},"body":"On Tue, Sep 24, 2024 at 06:19:16PM -0400, Taylor Blau wrote:\n> I haven't yet spun down the dynos on Heroku, on the off-chance that we\n> need to quickly get back to the non-static version of the site. But the\n> rollout has gone so smoothly that I doubt doing so will be necessary. In\n> a couple of days I'll go ahead and spin them down, assuming nothing has\n> changed.\n\nI had a reminder in my personal calendar today to shut down our Heroku\naccount, which is now mostly done.\n\nI de-provisioned all of our add-ons (which were the Heroku Scheduler,\nPostgres, and Bonsai instances), and then deleted the app.\n\nThe only thing that is left is to actually delete the account itself,\nwhich can't be done until our last invoice is cleared, which should\nhappen on sometime later today. Our final invoice is $61.86 USD. Once\nthat is cleared, I'll delete the account entirely.\n\n(As an aside, this is a significant cost-savings for the project. Our\nusual invoices are around $65 USD/mo, but that is taking into account\nthe OSS credits[1] that Heroku provides us, which are worth $40 USD/mo.\nSo the real cost-savings is somewhere around $1,200 USD/yr, which is\nawesome.)\n\nThanks,\nTaylor\n\n[1]: https://lore.kernel.org/git/ZZ7zezSRZfdklS4u@nand.local/\n"},{"id":"504599","messageId":"Zwaqy3oh83tuM3m6@nand.local","threadId":"62189","inReplyTo":"ZvrNmsycmamx2dcR@nand.local","subject":"Re: git-scm.com is now a static website","fromName":"Taylor Blau","fromEmail":"me@ttaylorr.com","sentAt":"2024-10-09T16:09:47Z","receivedAt":"2024-10-09T16:09:49Z","isPatch":false,"sender":{"key":"me@ttaylorr.com","avatar":"https://avatars.githubusercontent.com/u/301000140?v=4"},"body":"On Mon, Sep 30, 2024 at 12:11:06PM -0400, Taylor Blau wrote:\n> The only thing that is left is to actually delete the account itself,\n> which can't be done until our last invoice is cleared, which should\n> happen on sometime later today. Our final invoice is $61.86 USD. Once\n> that is cleared, I'll delete the account entirely.\n\nThis settled yesterday, and I have deleted our Heroku account. The last\ntraces of the old Rails site are now gone for good!\n\nThanks,\nTaylor\n"},{"id":"504613","messageId":"xmqqbjztuqp6.fsf@gitster.g","threadId":"62189","inReplyTo":"Zwaqy3oh83tuM3m6@nand.local","subject":"Re: git-scm.com is now a static website","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2024-10-09T17:33:09Z","receivedAt":"2024-10-09T17:33:12Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Taylor Blau <me@ttaylorr.com> writes:\n\n> On Mon, Sep 30, 2024 at 12:11:06PM -0400, Taylor Blau wrote:\n>> The only thing that is left is to actually delete the account itself,\n>> which can't be done until our last invoice is cleared, which should\n>> happen on sometime later today. Our final invoice is $61.86 USD. Once\n>> that is cleared, I'll delete the account entirely.\n>\n> This settled yesterday, and I have deleted our Heroku account. The last\n> traces of the old Rails site are now gone for good!\n\nHuge thanks to everybody involved in the effort.  Thanks.\n"}]}