README: adjust contribution notes, acknowledge the non-ORM-ness

1 files changed, 6 insertions, 3 deletions

diff --git a/README.md b/README.md
index 0bc2e9e..d49165d 100644
--- a/README.md
+++ b/README.md
@@ -15,9 +15,10 @@ Please refer to the [package documentation](https://pkg.go.dev/go.xyrillian.de/o
 
 ## How to contribute
 
-The primary repository at <https://git.xyrillian.de/go-oblast> is only writable by the maintainer.
-To contribute, you may use `git format-patch` in the usual manner and send patches to the maintainer's mail address (which can be found in the copyright notice headers on each file).
-Alternatively, if you have a GitHub account, you can submit issues and pull requests at the mirror repository <https://github.com/majewsky/go-oblast>.
+Before sending a patch, please ensure that `make check` does not report any problems, and run `make benchmark` to check the performance impact of your changes.
+
+To contribute to the primary repository at <https://git.xyrillian.de/go-oblast>, please use `git format-patch` in the usual manner and send patches to the maintainer's mail address (which can be found in the copyright notice headers on each file).
+Alternatively, if you are still using GitHub, you can submit issues and pull requests at the mirror repository <https://github.com/majewsky/go-oblast>.
 
 ## Design goals and priorities
 
@@ -39,3 +40,5 @@ Explicit non-goals include:
   Another thing that the author of this library does not believe to be worthwhile in an ORM library.
   In real-world applications, you will need to manage the schema using versioned schema migrations.
   Schemas generated by ORM libraries from type declarations cannot really offer this, especially once you get into stored functions, triggers and so on.
+
+The author realizes that this means that Oblast is technically only an OM library, not an ORM library. Sometimes, optimization means getting rid of on of th lttrs.