all important frontmatter 🙃

[michaelkirk]

The idea is that some of the policy issues could eventually be PR's to this document.

Feel free to workshop the copy.

Note, I intentionally used the terms "guidelines" and "expectations" as opposed to something like "policy", thinking it might more effectively communicate the spirit of what I think we're doing. I think ultimately we will (and should) include some things which MUST/MUST NOT, be done but if we can do so while also achieving the more subtle art of communicating that we expect people to do the right thing, even if it's not spelled out... so much the better IMO.

Also "expectation" concisely covers "rules" and "best practices"

If there's concern that this isn't "firm" enough, we could do something more like:

---

Guidelines Requirements for GeoRust Projects

What is a GeoRust project?

GeoRust is a community working to deliver high quality geospatial software using Rust, a programming language focused on performance, reliability, and productivity.

We want to write down some of the expectations rules and best practices for projects within the GeoRust organization. This document is incomplete by nature. We will work to amend it in a way that strikes a good balance between addressing pressing concerns while remaining clear and concise enough that we can expect people to actually read it.

[urschrei]

I like "guidelines", at least for now. If there's a divergence in consensus and expectations as this process continues, we can revisit it to be more prescriptive.