There's a team of engineers at Raven Industries that wanted to work on an open sourced, MIT (or BSD) licensed Rust CAN stack for their innovation sprint project. We got approval from Raven's leadership and legal teams for doing so, under the provision that Raven maintains copyright of the resulting project.

However, those same engineers believe the project will be most successful long-term if we work together with the excellent Open-Agriculture community, which seems especially true as the very same community has expressed significant interest in such a CAN stack [1,2,3,4] over the last few years. This belief is founded on the momentum we have observed from the Open-Agriculture community, as well as a believe in the values of contributing to open-source software.

See also the discussion in [5] for more context.

[1] https://github.com/Open-Agriculture/AgIsoStack-plus-plus/discussions/215 [2] https://github.com/Open-Agriculture/AgIsoStack-plus-plus/discussions/279 [3] https://github.com/Thom-de-Jong/AgIsoStack-rs [4] https://github.com/OpenIsobus/OpenIsobus [5] https://github.com/Open-Agriculture/AgIsoStack-rs/discussions/1

This PR:

• Sets up an empty Cargo project
• Adds README, CODE_OF_CONDUCT, and CONTRIBUTING files heavily influenced by their counterparts inhttps://github.com/Open-Agriculture/AgIsoStack-plus-plus
• Changes the copyright holder to Raven Industries as discussed in https://github.com/Open-Agriculture/AgIsoStack-rs/discussions/1

The PR coverage report step uses a bot to add a comment on the PR associated with this commit. But for it to do so, it requires finding the PR number for the current branch. I found two ways to do so:

1. Change "on: [push]" to "on: [pull_request]" at the top-level workflow.
2. Use the "gh" CLI tool (which is installed by default in every default runs-on: distribution that GitHub provides) to find the PR number for the current branch

I picked option 2, because option 1 means that the workflow is only ever run on the creation of a PR, and not on every push to an existing PR.

But I didn't think about the pipeline that will run on the main branch after merging the PR, in which case there is no PR to submit a code-coverage comment on.

https://github.com/Open-Agriculture/AgIsoStack-rs/actions/runs/5790553309/job/15693817217