diff --git a/assets/css/application.scss b/assets/css/application.scss index 8ced3ad..3a8b5ae 100644 --- a/assets/css/application.scss +++ b/assets/css/application.scss @@ -125,6 +125,10 @@ strong { width: 220px; } +.situations .existing { + margin-top: 16px; +} + .situations .whatever { margin-top: 16px; } @@ -143,9 +147,9 @@ strong { display: inline-block; } -.three-arrows { background-position: 0 0; width: 72px; height: 57px; } -.lightbulb { background-position: 0 -57px; width: 43px; height: 72px; } -.circular { background-position: 0 -129px; width: 72px; height: 69px; } +.three-arrows { background-position: 0 0; width: 72px; height: 56px; } +.community { background-position: 0 -57px; width: 72px; height: 56px; } +.circular { background-position: 0 -115px; width: 72px; height: 68px; } .license-overview { @@ -438,12 +442,12 @@ strong { only screen and (-o-min-device-pixel-ratio: 200/100), only screen and (min-device-pixel-ratio: 2.0) { .three-arrows, - .lightbulb, + .community, .circular { background-image: url(../img/home-sprite@2x.png); - -webkit-background-size: 72px 198px; - -moz-background-size: 72px 198px; - background-size: 72px 198px; + -webkit-background-size: 72px 182px; + -moz-background-size: 72px 182px; + background-size: 72px 182px; } .license-sprite { diff --git a/assets/img/home-sprite.png b/assets/img/home-sprite.png index f9390ea..64e489f 100644 Binary files a/assets/img/home-sprite.png and b/assets/img/home-sprite.png differ diff --git a/assets/img/home-sprite@2x.png b/assets/img/home-sprite@2x.png index eaf6d51..1107696 100644 Binary files a/assets/img/home-sprite@2x.png and b/assets/img/home-sprite@2x.png differ diff --git a/existing.md b/community.md similarity index 50% rename from existing.md rename to community.md index d4387b6..12db4c8 100644 --- a/existing.md +++ b/community.md @@ -1,6 +1,7 @@ --- layout: default -permalink: /existing/ +permalink: /community/ +redirect_from: /existing/ title: Existing projects and communities --- @@ -8,12 +9,15 @@ If you're contributing to or extending an existing project, it's almost always e Depending on how you're building on an existing project and what its license is, using the existing project's license for your own might not just be the easiest thing to do, but a condition on which your permission to build on the existing project rests: see the "same license" condition of [some licenses](/licenses/). -Some communities have strong preferences for particular licenses. If you want to participate in one of these, it will be easier to use the preferred license even if you're starting a brand new project with no existing dependencies. A few examples: +Some communities have strong preferences for particular licenses. If you want to participate in one of these, it will be easier to use the preferred license even if you're starting a brand new project with no existing dependencies. Examples: {: .bullets} * [Apache](https://www.apache.org/licenses/) requires [Apache License 2.0](/licenses/apache-2.0/) +* [Cloud Native Computing Foundation](https://github.com/cncf/toc/blob/master/process/project_proposals.adoc) dictates [Apache License 2.0](/licenses/apache-2.0/) by default * [GNU](https://www.gnu.org/licenses/license-recommendations.html) recommends [GNU GPLv3](/licenses/gpl-3.0/) for most programs -* [OpenBSD](https://www.openbsd.org/policy.html) prefers [ISC](/licenses/isc/) +* [NPM packages](https://libraries.io/search?platforms=NPM) overwhelmingly use the [MIT](/licenses/mit/) or the very similar [ISC](/licenses/isc) licenses +* [OpenBSD](https://www.openbsd.org/policy.html) prefers the [ISC License](/licenses/isc/) +* [WordPress](https://wordpress.org/about/license/) plugins and themes must be [GNU GPLv2](/licenses/gpl-2.0/) (or later) -Communities come in all shapes and sizes. The examples above are *very* well established. If the community you see your project as a part of doesn't have set-in-stone licensing traditions, or you don't see your project as part of any particular community, that's just fine: [make your own choice of an open source license](/). +Communities come in all shapes and sizes, and more than one might be pertinent (e.g., [your company](https://opensource.guide/legal/#what-does-my-companys-legal-team-need-to-know)). The examples above are *very* well established. If the community you see your project as a part of doesn't have set-in-stone licensing traditions, or you don't see your project as part of any particular community, that's just fine: [make your own choice of an open source license](/). diff --git a/index.html b/index.html index a11992e..cb1c493 100644 --- a/index.html +++ b/index.html @@ -6,43 +6,45 @@ title: Choose an open source license permalink: / --- +

An open source license protects contributors and users. Businesses and savvy developers won’t touch a project without this protection.

+

{ Which of the following best describes your situation? }