From 2b35c5b03e476a6636868cc215b4f2a67065718a Mon Sep 17 00:00:00 2001 From: Mike Linksvayer Date: Mon, 18 Apr 2016 21:54:10 -0700 Subject: [PATCH 1/3] when contributing existing projects and commmunities page covering licensing for this situation - not linked anywhere yet - partially addresses #239 - tangentially addresses #242, could be extended to address including code from other projects more explicitly - with some additional work (feedback wanted) could be useful to link as another "situation" from the home page --- existing.md | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) create mode 100644 existing.md diff --git a/existing.md b/existing.md new file mode 100644 index 000000000..0a4235403 --- /dev/null +++ b/existing.md @@ -0,0 +1,19 @@ +--- +layout: default +permalink: existing/ +title: Existing projects and communities +--- + +If you're contributing to or extending an existing project, it's almost always easiest to continue using that project's license. Look for a file called `LICENSE` or `COPYING`, or a notice in the project's `README` to find out what that license is. If you can'd finda license, [ask](/no-license/#for-users). + +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 exisiting dependencies. A few examples: + +{: .bullets} + +* [Apache](https://www.apache.org/licenses/) requires [Apache License 2.0](/licenses/apache-2.0/) +* [GNU](https://www.gnu.org/licenses/license-recommendations.html) recommends [GNU GPLv3](/licenses/gpl-3.0/) for most programs +* [OpenBSD](http://www.openbsd.org/policy.html) prefers [ISC](/licenses/isc/) + +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](/). From 8dbeb10909cd6ef268456b45ad18eda5fcffa133 Mon Sep 17 00:00:00 2001 From: Mike Linksvayer Date: Mon, 18 Apr 2016 21:57:56 -0700 Subject: [PATCH 2/3] spel --- existing.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/existing.md b/existing.md index 0a4235403..191152796 100644 --- a/existing.md +++ b/existing.md @@ -4,7 +4,7 @@ permalink: existing/ title: Existing projects and communities --- -If you're contributing to or extending an existing project, it's almost always easiest to continue using that project's license. Look for a file called `LICENSE` or `COPYING`, or a notice in the project's `README` to find out what that license is. If you can'd finda license, [ask](/no-license/#for-users). +If you're contributing to or extending an existing project, it's almost always easiest to continue using that project's license. Look for a file called `LICENSE` or `COPYING`, or a notice in the project's `README` to find out what that license is. If you can't find a license, [ask](/no-license/#for-users). 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/). From a5f28da4fde5eb7238c2a0ebe532155979b4f55d Mon Sep 17 00:00:00 2001 From: Mike Linksvayer Date: Wed, 20 Apr 2016 21:18:03 -0700 Subject: [PATCH 3/3] missing leading / on permalink --- existing.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/existing.md b/existing.md index 191152796..9f2620742 100644 --- a/existing.md +++ b/existing.md @@ -1,6 +1,6 @@ --- layout: default -permalink: existing/ +permalink: /existing/ title: Existing projects and communities ---