[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Team book licensing and editorial process



On Sun, Jan 12, 2025 at 10:07:37PM +0800, Blair Noctis wrote:
> Hi team,
> 
> Seeing the book is catching up (https://rust-team.pages.debian.net/book/ if you didn't know), I'd like to ask you to help formalize some aspects of it.

Awesome! I'm really happy to see this.

> == Licensing
> 
> Content of the book is not entirely new: the policy section is copied over from the [wiki], mainly written by Josh Triplett and Ximin Luo (thus sending to you); the packaging process (for single crates) from readme.rst in the debcargo-conf repo, mainly written by Ximin Luo and Sylvestre Ledru (thus sending to you); the rust_hacks.md document also in the dc-c repo, mainly by Matthias Geiger (thus sending to you); with occasional contributions from a few others.
> 
> There was, however, no clear licensing on any of them, AFAICT. They seem to have been written and shared on a "being useful" ground. I took them into the book for the same purpose. Now that we have a concentrated documentation effort, I'd like to ask for your opinions and permissions on a proper license of the book. I'd suggest CC-BY-SA-4.0 since it's documentation, not code (albeit some small examples in it).

I would express a mild preference for picking something Rust-compatible;
it's remarkable how often it ends up being useful to copy freely between
code and documentation. For instance, consider the value of being able
to copy a passage from the book into the code as a comment.

Given that, I'd suggest `MIT OR Apache-2.0`, like debcargo and most Rust
code.

- Josh Triplett


Reply to: