Open source
Public is not open source until there is a licence
An open source licence lets anyone use, study, change and share the code.
Millions of projects on GitHub are open source. What does that really mean? It is not enough for the code to be public. With no licence, the author keeps every right. You can read the code, and that is all. Add an open source licence, and everything changes. Anyone may use the code, study it, change it, and share it. Well known licences such as M I T, Apache and G P L each set a few conditions, like keeping the copyright notice.
Open source · Going deeper
Why open source
More reviewers, shared costs, and transparency.
Contributing
Fork, change, then ask with a pull request
Fork the repository, commit on your copy, open a pull request to upstream.
How do you improve a project when you are not allowed to push to it? You fork it. A fork is your own copy of the repository, under your account, still linked to the original. On your fork, you create a branch and make your commits. Nobody needs to give you permission. Then you open a pull request from your fork back to the original. The maintainers review it, and if they agree, they merge it. That is how strangers build software together.
Contributing · Going deeper
About forks
Upstream, sync fork, and when to use a template instead.
Check yourself
You cannot push to octo-org/tool. What is step 1?
InnerSource
Open source habits, inside the company walls
InnerSource opens code to the whole company, not to the world.
Companies have borrowed the open source way of working, and given it a name. Traditionally, code is closed. Only the owning team can see it and change it. With inner source, the repository is open to everyone in the company. Any employee can read it, report a problem, and send a pull request, and the owning team still decides. Open source goes one circle further, to anyone in the world. Inner source is the middle circle: open inside, private outside.
InnerSource · Going deeper
InnerSource in practice
Discoverable, documented, and reviewed by owners.
Discovery
Topics and a clear description get a repository found
A description and topics place a repository in search and Explore.
An open source project only helps people who can find it. Start with the basics: a clear name, a one line description, a read me and a licence. Then add topics. Topics are tags, such as C S V, or the language the project uses. Together they decide where the repository appears: in search results, on the page for each topic, and in Explore and Trending, where GitHub shows popular and fast growing projects.
Discovery · Going deeper
Follow, star, watch, fork, sponsor
Follow people. Star and watch repositories.
Check yourself
Which action fits?
Sponsors and Marketplace
Fund the people. Add the tools
Sponsors pays maintainers. Marketplace offers apps and actions.
Two more parts of the community are worth knowing. GitHub Sponsors lets you pay the people who maintain the open source you depend on. A person or a company can sponsor a maintainer or a project, monthly or once, and the maintainer shows a sponsor button on their profile. GitHub Marketplace is a catalog of tools that plug into GitHub: apps that integrate with your repositories, and actions for your workflows. Some are free and some are paid.
Sponsors and Marketplace · Going deeper
Clue words for the GitHub community
InnerSource, fork, Sponsors, Marketplace and topics.
Check yourself
Where should this team look?
Lesson complete
You finished “The GitHub community”
Answer the questions along the way to see your score here.