Recommendations for the "non-technical" stuff (license, contributing, code of conduct, etc)

[nastevens]

Assuming that open source projects are going to be a large target of the crate-ci effort, it would be extremely useful to me if there was an easy checklist of the "non-technical" stuff that is useful in an repo. The following is a non-exhaustive list of things that fit into that category:

• License information
  • A template for a "default", i.e. Apache-2.0/MIT, would be useful
• Contributing guidelines
  • A template here modeled after Rust's own guidelines would be useful
• Project code of conduct
  • Template again off of Rust's CoC
• Templates for submitting issues, if appropriate
• Important Cargo.toml keywords

Like I said, this is not meant to be exhaustive but to drive discussion if these things are useful and if so, what to cover.

[epage]

I could see documenting some of these things here just as a place to do it but I assume there will be a set of maintainership guidelines that are going to be created to be a home for these.

Templates for submitting issues, if appropriate

Since this project is about streamlining maintenance, Issue and PR templates would make definitely be in scope.

[epage]

License stuff is documented at https://rust-lang-nursery.github.io/api-guidelines/necessities.html#c-permissive