GitHub 宣佈將在 2024 移除對 Subversion 支援
source link: https://blog.gslin.org/archives/2023/01/22/11034/github-%e5%ae%a3%e4%bd%88%e5%b0%87%e5%9c%a8-2024-%e7%a7%bb%e9%99%a4%e5%b0%8d-subversion-%e6%94%af%e6%8f%b4/
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
GitHub 宣佈將在 2024 移除對 Subversion 支援
GitHub 從 2010 年的愚人節時宣佈支援 Subversion：「Announcing SVN Support」，雖然是愚人節的功能，但這個功能是會動的。
而這個功能出現十多年後，可以預期用的人愈來愈少。前幾天 GitHub 宣佈將在大約一年後的 2024/01/08 停止支援 Subversion：「Sunsetting Subversion support」。
然後在 Hacker News 上的討論「GitHub Sunsetting Subversion Support (github.blog)」則是直接讓 Scott Chacon (GitHub co-founder，同時也是第一篇公告文的作者 + 這個功能的兇手之一) 出來解釋當初搞出這個東西的前因與後果，還有一些感想。
裡面有提到這個功能當初推出來的時候是個好玩的性質，但意外的在上線後發現也讓一些老系統可以比較容易轉移：也就是讓 developer 可以先開始用 Git，但 CI 類的工具可以先不用改。
As one of the GitHub cofounders and the brainchild of this particular feature, I want to let everyone know that this is maybe the funniest thing I've ever done.
We released this feature and published the announcing blog post, on April Fool's Day, 2010. I remember demoing it to the other GitHub guys and saying how funny it would be if we made this an April Fool's day post as though it was a big stupid joke but then it actually completely worked on every repository we had and we all thought it would be great. Until nobody believed us. Which in hindsight we should have seen coming, since that was the joke, but nobody actually tried it. Then people tried it and it worked and they thought it was a trick or something.
It was really helpful for people migrating from legacy SVN based systems to us (CI and stuff) but I'm surprised to some degree that it's still running 13 years later when nobody is really facing that issue anymore. And I'm still undecided if the joke was worth the massive confusion it caused. But if I'm pressed, I would say that I would 100% release it on April Fool's Day again.
不過想要拔掉這個功能的起因不知道是什麼，技術債不知道有多少...
Related
WebKit 專案將從 Subversion 搬到 GitHub 上
在 Hacker News 首頁上看到 WebKit 專案宣佈從本來的 Subversion 搬到 GitHub 上：「WebKit on GitHub!」，新的專案位置在 WebKit/WebKit 這邊。對應的討論在「WebKit Migrates from Subversion to GitHub (webkit.org)」這邊。 但 issue tracking system 的部份目前看起來還是繼續用 WebKit Bugzilla，沒有開 GitHub 的 issue 功能，但至少是從 Subversion 換成 Git 了。 在 Hacker News 上的討論意外看到已經是歷史的 SVK (試著在 Subversion 上面堆一些功能)，而且還聊到了一些 tricky 的技巧： Funny story: my first task…
September 1, 2022In "Computer"
在 Gmail 裡面展開 GitHub 信件連結的 Userscript
從以前用 Subversion 就有習慣用 e-mail 收 diff log (內建的 hook 就有這個功能)。後來有了 Gmail 就更方便了，畢竟搜尋是 Google 的強項，另外一方面 Gmail 也是目前少數可以完全用鍵盤操作的 e-mail client。 現在用 Git 與 GitHub 平台讓這件事情麻煩不少，得透過 webhook + API 自己包出來，目前折衷的方法是收 GitHub 的通知信 (但是沒有 diff log)，然後寫個 Userscript，在按下 i 之後會把 GitHub 通知信裡的連結全部點開：「open-github-links-in-gmail」。 寫的很簡單... 最花時間反而是因為 hotkey 都被吃掉了，要測出哪個鍵還沒被用掉。
May 14, 2019In "Browser"
GitHub 對 Open Source Community 請願的回應
大約一個多月前 (2016 年一月 15 日)，一群用 GitHub 發展 Open Source 軟體的人對 GitHub 提出請願，要求重視 Open Source Community 在 GitHub 平台上遇到的問題：「An open letter to GitHub from the maintainers of open source projects」。 這個請願在卡了將近一個月後，陸陸續續有相當多要搬出 GitHub 的討論，像是 eslint 就直接在 GitHub 開了 issue，討論搬出 GitHub 會遇到的問題以及可能的解決方法：「Investigate switching away from GitHub」。 在二月 13 日的時候，GitHub 透過 pull request 發出回應說「我們在處理了」，但也沒講正在處理什麼，看起來就是個很…
February 18, 2016In "Computer"
Leave a Reply
Your email address will not be published. Required fields are marked *
Comment *
Name *
Email *
Website
Notify me of follow-up comments by email.
Notify me of new posts by email.
To respond on your own website, enter the URL of your response which should contain a link to this post's permalink URL. Your response will then appear (possibly after moderation) on this page. Want to update or remove your response? Update or delete your post and re-enter your post's URL again. (Learn More)
Post navigation
Recommend
About Joyk
Aggregate valuable and interesting links.
Joyk means Joy of geeK