So in #131, we said:

So this repo is getting merged into rust-lang/rust eventually

It's not clear if that's happening or not; but either way, it will still be distributed with Rust, and in general, it's always better to make stuff work offline if possible.

And looking at this comment from nostarch, I realized if we print a link to this repo on paper, we should not then get rid of this repo 😳

I kind of like that this is a separate repo because:

• You don't have to wade through all of rustc's source code to just work on the book
• Potentially less intimidating to contributors
• Can use different conventions for, say, issue labels

I kind of don't like that this is a separate repo because:

• Patches to the book don't get "counted" as "rust" contribs, even though doc contribs should be valued as much as code contribs
• We'd have to do extra work to change the build process of rustc to pull from this repo

I mean, I guess we could just change this repo to have nothing but a README explaining how to find and contribute to the book in rust-lang/rust...

But I think we should know what our plan is before chapter 1 gets finalized.