Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
28 commits
Select commit Hold shift + click to select a range
94a698e
Start review of legal article
bkeepers Aug 11, 2016
607e2a1
Merge remote-tracking branch 'origin/gh-pages' into review-legal
bkeepers Aug 13, 2016
6251982
source+license
mlinksva Aug 15, 2016
56e6166
Merge branch 'review-legal' of github.com:github/open-source-handbook…
mlinksva Aug 15, 2016
d303ce4
comply with->covered by TOS, slightly more intuitive links
mlinksva Aug 15, 2016
1d146fa
rm superfluous at best jargon
mlinksva Aug 15, 2016
eee2d92
rm individual license mentions
mlinksva Aug 15, 2016
01096e9
you are not a project, a file does not actively solicit
mlinksva Aug 15, 2016
18757d4
write->establish coc...
mlinksva Aug 15, 2016
36b9bd0
less stale link, essential link
mlinksva Aug 15, 2016
7655d8e
pertinent link, rm not final finally
mlinksva Aug 15, 2016
ec8f0fe
wording
mlinksva Aug 15, 2016
b9501e8
Merge remote-tracking branch 'origin/gh-pages' into review-legal
bkeepers Aug 15, 2016
aa27772
Fix merge conflict
bkeepers Aug 15, 2016
6441d5a
Fix link
bkeepers Aug 15, 2016
5ffcb80
Fix lint warnings
bkeepers Aug 15, 2016
daad3f0
CLA section edits
mlinksva Aug 16, 2016
b79ca97
fix internal link
mlinksva Aug 16, 2016
0c62362
fix warnings
mlinksva Aug 16, 2016
efd9713
@aitchabee feedback https://github.com/github/open-source-handbook/pu…
mlinksva Aug 16, 2016
9040bba
rewrite "which license" section
mlinksva Aug 16, 2016
e3cea09
fix dupe blank lines warning
mlinksva Aug 16, 2016
3353b21
legal team considerations
mlinksva Aug 17, 2016
31ed010
fix internal links
mlinksva Aug 17, 2016
ad10f92
Merge remote-tracking branch 'origin/gh-pages' into review-legal
mlinksva Aug 17, 2016
a612752
Merge remote-tracking branch 'origin/gh-pages' into review-legal
mlinksva Aug 17, 2016
f4560c8
make legal.md friendlier sounding
Aug 18, 2016
7de78c1
edit contributor agreement section
Aug 18, 2016
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions getting-started/branding.md
Original file line number Diff line number Diff line change
Expand Up @@ -15,9 +15,9 @@ Pick a name that is easy to remember and, ideally, gives some idea of what the p

Consider clarity above all. Puns are fun, but remember that some jokes might not translate to other cultures or people with different experiences from you. For example, some of your users might be employees; you don’t want to make them uncomfortable when they have to explain your project’s name to coworkers!

## Avoiding namespace conflicts
## Avoiding name conflicts

Make sure that your project’s name doesn’t infringe upon any trademarks. A company might ask you to take down your project later on, or even take legal action against you. It’s just not worth the risk. You can check for U.S. trademark conflicts [here](http://www.uspto.gov).
Make sure that your project’s name doesn’t infringe upon any trademarks. A company might ask you to take down your project later on, or even take legal action against you. It’s just not worth the risk. You can check for U.S. trademark conflicts [here](http://www.uspto.gov/trademarks-application-process/search-trademark-database). If you’re at a company, this is one of the things your [legal team can help you with](../legal/#what-does-my-companys-legal-team-need-to-know).

You’ll also want to look for open source projects with a similar name, especially if you share the same language or ecosystem. If your name overlaps with a popular existing project, you will confuse your audience and make it less likely that anyone will use what you’ve created. You can check for similar project names [here](http://ivantomic.com/projects/ospnc/).

Expand Down
8 changes: 4 additions & 4 deletions getting-started/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,17 +9,17 @@ So you’re interested in making your project open source? Congratulations! 🎉

Before we get into the details of running and managing an open source project, let’s talk about what open sourcing a project actually means.

## Public projects on GitHub are not open source
## Public projects on GitHub without a license are not open source

When you publish a project on GitHub, you have the option to make the repository **private** or **public**. A public repository is not automatically open source unless you pick a license that grants a certain set of rights to people who might interact with your project.

Open source licenses grant permission to everyone to use, modify, and share licensed software for any purpose, subject to certain conditions, depending on the license.

Public repositories on GitHub [comply with GitHub’s Terms of Service](https://help.github.com/articles/open-source-licensing/), which gives other people the right to view and fork your repository. But if you want others to use, copy, modify, or contribute back to your project, you need to include an open source license. For example, someone cannot legally use your GitHub project in their code, even if it’s public, unless you explicitly give them the right to do so. (You can learn more about the legal side of open source [here](legal/).)
Public repositories on GitHub are covered by [GitHub’s Terms of Service](https://help.github.com/articles/github-terms-of-service/#f-copyright-and-content-ownership), which gives other people the right to view and fork your repository. But if you want others to use, copy, modify, or contribute back to your project, you need to [include an open source license](https://help.github.com/articles/open-source-licensing/). For example, someone cannot legally use any part of your GitHub project in their code, even if it’s public, unless you explicitly give them the right to do so. (You can learn more about the legal side of open source [here](legal/).)

## Open source is more than just a license
## Open source is more than just source code with a license

Open source is defined by its legal protections and freedoms. In terms of culture, open sourcing a project has come to mean much more.
Open source is [defined by](https://opensource.org/osd) source code with legal protections and freedoms. In terms of culture, open sourcing a project has come to mean much more.

There are many reasons why a person or organization might want to open source a project. Some examples are:

Expand Down
Loading