If you maintain an open-source project in the range of 10k-200k lines of code, add an ARCHITECTURE document next to README and CONTRIBUTING. Keep it short: every recurring contributor will have to read it. Only specify things that are unlikely to frequently change. Don’t try to keep it synchronized with code. Instead, revisit it a couple of times a year.

This site adds additional context to GitHub Issue labels. The intention here is to be descriptive regarding the Open Source development process, not prescriptive. In other words it is an attempt to document how developer generally apply these labels, and not attempt to impose some kind of standard.

GitHub Next investigates the future of software development.

We are a team of researchers and engineers at GitHub, exploring things beyond the adjacent possible. We prototype tools and technologies that will change our craft. We identify new approaches to building healthy, productive software engineering teams.

Open source content management for your Git workflow

It drives me a li’l crazy when people don’t even take one glance at the “files changed” tab in GitHub.

This is what forges hath wrought compared to patches.

Our industry teaches a lot of people that there is nothing they cannot learn, and we have a critical mass of arrogant people in tech and on GitHub. It’s incredibly toxic and I never want to maintain a real repository this large on GitHub, paid or not.

The developer community remains the heart of GitHub, and we’re committed to respecting the privacy of developers using our product.

A curated list of Artificial Intelligence Top Tools - mahseema/awesome-ai-tools

🎉 Personal GNU Emacs configuration. Contribute to rememberYou/.emacs.d development by creating an account on GitHub.