If I Could Make My Own GitHub
11 hours ago
- #p
- #d
- #g
- #e
- #r
- #a
- #c
- #m
- #o
- #t
- #v
- #i
- #
- #,
- #f
- #s
- #n
- #j
- #l
- The author dreams of creating a new forge in response to dissatisfaction with existing platforms like GitHub, focusing on core issues with modern forges.
- Modern forges (GitHub, GitLab, Gitea) are built on a centralized model, adding features on top of git that shift workflows away from its decentralized design for kernel development.
- Key problems include: delayed feedback loops in pull requests, overly binary approval processes, inflexible PR requirements, lack of support for stacked PRs, bloated feature sets, and heavy hosting units.
- Proposed improvements involve: pre-commit hooks for early feedback, nuanced PR approvals (e.g., weak approvals), customizable review processes, first-class stacked PRs, and focused feature sets that avoid unnecessary tools.
- Suggestions for hosting include smaller, flexible units that can be linked into organizations, lightweight representations of repos locally, efficient synchronization, and signed, offline-capable actions for reliability and control.
- The author advocates for integrating tools (like JJ as VCS) and using modern concepts, highlighting that as monolithic forges decline, there's an opportunity to build a replacement tailored for developers rather than following default options.