news.volyx.in

Before GitHub (lucumr.pocoo.org)

680 points by mlex · 77 days ago · 237 comments on HN

Article summary

The article discusses the author's experience with open-source software before and after GitHub, highlighting the changes in the open-source landscape. The author reminisces about using Trac and Subversion, and later moving to GitHub, which became a central hub for open-source projects. However, the author notes that GitHub's decline and potential loss of trust may lead to a decentralized future for open-source software. The author argues that a public, well-funded archive for open-source software is necessary to preserve the history and context of projects.

Main themes

  • Open-source software history
  • GitHub's impact
  • Decentralization
  • Archival and preservation
  • Community and trust

What commenters say

  • The pre-GitHub era of open-source software was more decentralized and required more effort to set up and maintain projects, but also allowed for more autonomy and control.
  • GitHub's archival work has been beneficial, but it has also led to a reliance on a centralized platform and a lack of archival skills among developers.
  • A decentralized approach to open-source software, such as using GitTorrent, could provide a more resilient and community-driven alternative to centralized platforms like GitHub.
  • The use of centralized platforms like GitHub has led to a loss of skills and knowledge about how to maintain and preserve open-source projects, making it difficult to transition to alternative platforms.
  • The importance of preserving open-source software history and context is crucial, and a public, well-funded archive is necessary to achieve this goal.
  • The decline of GitHub may lead to a shift towards more decentralized and community-driven platforms, which could ultimately be beneficial for the open-source community.
  • The concentration of power and control in centralized platforms like GitHub can stifle innovation and limit the potential of open-source software.
  • The need for a decentralized and community-driven approach to open-source software is not necessarily at odds with the benefits of centralized platforms like GitHub, and a hybrid approach may be the most effective way forward.