Hello, looking to make a Rust library soon, I intend to license it as free, open source, and no attribution needed, can I? Are there any things I must include? From what I read, Rust is dual licensed under Apache 2.0 and MIT licenses both of which require distributing with those licenses somehow attached, can I just link to Rust legal or what? Have people just been skirting this because I am not seeing this license stuff much in Rust stuff?
I'm not good with licenses, but to me this sounds like the unlicense or MIT-0 should cover your library?
I'm not aware of any reason why you should deal with rustc's licenses at all, unless you somehow intend to distribute it as part of your library, which I find to be highly unlikely.
Yeah, like unlicense or CC0 or MIT0, I know how to license if it is allowed but according to Rust licensing I read all derivative works, which is what this would be I think since it uses Rust specification and std, must reproduce Rust's license in their code I think unless I am reading that wrong or in wrong licensing, am I wrong?
Licenses - Rust Programming Language, can I redistribute with just one or do I need both in like my source code? Is this correct licensing?
Also, it only uses Rust and std, nothing else maybe or maybe not, maybe.
Again, take my post with a grain of salt—I had lectures on OSS and CC licenses in the past, but that's about it and happened surprisingly long ago—but you aren't redistributing rustc or the standard library as part of your crate and I never heard of a programming language (specification) itself requiring you to carry some sort of license for it as part of your project, just because parts of it are written in said language. Your library may need to link the standard library when it is compiled, but you don't carry a copy of std around. All you distribute are the source files you wrote. Your users have to have std on their computer (with a copy of either of the licenses—dual-licensing let's the user choose one of the provided licenses) when they compile your library, which leaves them with the burden to have the license around instead of you.
3 Likes
Okay, I think I was just confused about that MIT thing anyway, whatever "The Software" is which is almost certainly Rust and its stuff not like my code is required to reproduce license, not mine maybe or maybe not, maybe. Thank you, solved maybe or maybe not, maybe.