From 62a4c215e84e8e8defe83d95e0178c7e1a518111 Mon Sep 17 00:00:00 2001 From: Derpy Date: Sun, 9 Dec 2018 15:22:47 +0000 Subject: [PATCH 1/4] Include rust It's growing............ --- community.md | 1 + 1 file changed, 1 insertion(+) diff --git a/community.md b/community.md index 12db4c8..0f6385a 100644 --- a/community.md +++ b/community.md @@ -19,5 +19,6 @@ Some communities have strong preferences for particular licenses. If you want to * [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) +* [Rust](https://www.rust-lang.org/) [Crates](https://crates.io/) overwhelmingly uses a dual [MIT](/licenses/mit/)/[Apache License 2.0](/licenses/apache-2.0/). 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](/). From 7998240287fce3d63bc0d483fb39f2f9945e4451 Mon Sep 17 00:00:00 2001 From: Mike Linksvayer Date: Sun, 9 Dec 2018 14:49:10 -0500 Subject: [PATCH 2/4] link to evidence of community license practice matching other items --- community.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/community.md b/community.md index 0f6385a..d9dc74b 100644 --- a/community.md +++ b/community.md @@ -19,6 +19,6 @@ Some communities have strong preferences for particular licenses. If you want to * [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) -* [Rust](https://www.rust-lang.org/) [Crates](https://crates.io/) overwhelmingly uses a dual [MIT](/licenses/mit/)/[Apache License 2.0](/licenses/apache-2.0/). +* [Rust](https://rust-lang-nursery.github.io/api-guidelines/necessities.html#crate-and-its-dependencies-have-a-permissive-license-c-permissive) crates are overwhelmingly licensed under both [MIT](/licenses/mit/) and [Apache License 2.0](/licenses/apache-2.0/). 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](/). From 7cfdeb1256d473110c5281f7fbc547cd64cdd44f Mon Sep 17 00:00:00 2001 From: Mike Linksvayer Date: Sun, 9 Dec 2018 14:49:52 -0500 Subject: [PATCH 3/4] no period matching other items --- community.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/community.md b/community.md index d9dc74b..17971fe 100644 --- a/community.md +++ b/community.md @@ -19,6 +19,6 @@ Some communities have strong preferences for particular licenses. If you want to * [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) -* [Rust](https://rust-lang-nursery.github.io/api-guidelines/necessities.html#crate-and-its-dependencies-have-a-permissive-license-c-permissive) crates are overwhelmingly licensed under both [MIT](/licenses/mit/) and [Apache License 2.0](/licenses/apache-2.0/). +* [Rust](https://rust-lang-nursery.github.io/api-guidelines/necessities.html#crate-and-its-dependencies-have-a-permissive-license-c-permissive) crates are overwhelmingly licensed under both [MIT](/licenses/mit/) and [Apache License 2.0](/licenses/apache-2.0/) 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](/). From 56faa501cfa3612ccb2da995ec9d690f5b1fd027 Mon Sep 17 00:00:00 2001 From: Mike Linksvayer Date: Sun, 9 Dec 2018 14:51:39 -0500 Subject: [PATCH 4/4] alphasort --- community.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/community.md b/community.md index 17971fe..c1dbe82 100644 --- a/community.md +++ b/community.md @@ -18,7 +18,7 @@ Some communities have strong preferences for particular licenses. If you want to * [GNU](https://www.gnu.org/licenses/license-recommendations.html) recommends [GNU GPLv3](/licenses/gpl-3.0/) for most programs * [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) * [Rust](https://rust-lang-nursery.github.io/api-guidelines/necessities.html#crate-and-its-dependencies-have-a-permissive-license-c-permissive) crates are overwhelmingly licensed under both [MIT](/licenses/mit/) and [Apache License 2.0](/licenses/apache-2.0/) +* [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, 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](/).