Austin Gill

Both a Telegram and Discord group were mentioned in https://github.com/Open-Agriculture/AgIsoStack-rs/discussions/25 - what do we want to use? We should mention it in the README.md and CONTRIBUTING.md

Motivated by https://github.com/Open-Agriculture/AgIsoStack-rs/discussions/30#discussioncomment-7513986 It appears we can achieve this through judicious use of `#[warn(missing_docs)]` and the existing use of `-Dwarnings` in the CI/CD pipeline. https://doc.rust-lang.org/rustdoc/write-documentation/what-to-include.html

* [ ] Include README in generated docs * [ ] Include a feature table in the README * [ ] Enable all features in generated documentation * [ ]...

Motivated by https://github.com/Open-Agriculture/AgIsoStack-rs/pull/12#issuecomment-1799028872 Having optional tracing is great, but as the project grows, adding tracing around _everything_ will get quite verbose. We should find a way to let a developer...

There are a few examples (asemic and random-lsystem) that generate random results. * [ ] Probably requires #171 to make asemic writing reproducible. * [ ] random-lsystem not being deterministic...

Closes #172 # Polar conversion ```sh grid -O lines ```  ```sh grid -O lines | transform --from-polar --range2 0 360 ```  Whoops; one too many times. Kinda cool....

Requires the use of a logging facade like we have at work. The C++ build will implement the facade with log4cplus; the Rust bindings will implement it with `tracing` macros.

I simply prefer `tracing` more; and the ability to use spans may be useful