Monorepo or Multirepo? Role-Based Repositories
Roles in open source projects
home > resources > briefing notes > Roles in open source projects
Repositories Are Human/Agent Knowledge Factories
Repositories aren’t where code lives anymore—they’re where **knowledge is manufactured**. And increasingly, it’s not humans doing the work—it’s agents, with humans supervising the factory.…
What is an atproto repository? - The Book of Eli
One repo with multiple ways to sync
Open Source Saturation
In Supporting Open Source Software I discussed the critical need for better support for contributors to open source projects. Now, Quo Vadi...
GitHub - github/balanced-employee-ip-agreement: GitHub's employee intellectual property agreement, open sourced and reusable
GitHub's employee intellectual property agreement, open sourced and reusable - github/balanced-employee-ip-agreement
Code Repository - Git Source Control | Harness
Host Git repositories in Harness, manage pull requests, and connect every commit to secure CI/CD workflows with source-to-deploy traceability.
A Taxonomy for Open Source Software
I’m working on a structured taxonomy for classifying open source projects across multiple dimensions: domain, role, technology, audience, layer, and function.
Schema 5.5 now available: adding CRediT, new record types for blogs and posters, and more - Crossref
Research is rarely limited to a single contributor performing a single role. Behind every research output are people contributing in various ways: software development, data analyses, methodology design, and much more. Often, the same person contributes in several of these ways. Until now, Crossref metadata could only capture part of that picture, but this is changing with Schema 5.5.
repomirror/repomirror.md at main · repomirrorhq/repomirror
Contribute to repomirrorhq/repomirror development by creating an account on GitHub.
Git at any scale · Cursor
Hosting Git repositories at scale is a nightmare. When Linus Torvalds designed the first version of the information manager from hell (that's actually the tagline for Git, look it up), he had a very specific use case in mind: his own. He wanted to replace BitKeeper, the distributed version control system that was being used to develop the Linux Kernel. Of course, the replacement had to be distributed too. The Kernel is an unusual software project; it is extremely decentralized, with many different maintainers for its many different subsystems. A distributed version control system is a natural fit for this workflow.
I’m Now a Full-Time Professional Open Source Maintainer
It works! I am now a full-time independent open-source maintainer. I'm announcing my first cohort of six clients, and sharing some details of how the model works.
Capabilities
There are three kinds of capabilities in Peergos: Mirror, Read and Write.