Documenting Rust license bundling

[mbhall88]

As is recommended on conda-forge I wonder if we can document somewhere the recommeded license bundling for Rust projects?

[mbhall88]

And maybe even a recommended build invocation conda-forge/conda-forge.github.io#2191

[mbhall88]

As an additional, somewhat related tope, it could also be worth create subteams for languages as is done on conda-forge. So if someone is stuck with an R, or Go, or Rust etc. recipe they can ping some bioconda members who are designated "pros" at recipes for that language?

[aliciaaevans]

We actually do have teams for the build-system, lib, haskell, osx, perl, python, r, and rust. I'm not sure if those would be more or less effective at getting a response versus pinging the core team, but it does look like there are some additional Bioconda members who have volunteered for them.

[mbhall88]

Oh cool! I didn't know that. And LOL, I'm in one of the teams 😅 🤦 my cognitive decline has clearly started early.

I wonder if it could be worth linking to that teams page in the PR/issue boilerplate so people know they can ping those teams if they're stuck on a language-specific problem?

And given my refound knowledge of these teams, I'll ping @bioconda/rust for input on the overarching theme of this issue.