From 62a4c215e84e8e8defe83d95e0178c7e1a518111 Mon Sep 17 00:00:00 2001 From: Derpy Date: Sun, 9 Dec 2018 15:22:47 +0000 Subject: [PATCH] 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](/).