Update guidelines

.github/PROCESS.md

@@ -4,6 +4,10 @@ This file contains some process notes for FerretDB Inc. engineers and long-term
 If you are a community contributor, feel free to ignore all this!
 We will do all that for you so you can focus on what is really interesting for you.
 
+We encourage diversity between us as different points of view expand our vision and contribute to the project's success.
+
+Keep guides short: we don't create rules; we automate.
+
 ## Pull requests
 
 1. Pull request **title** should be accurate and descriptive as it is used in the generated changelog.
@@ -16,3 +20,8 @@ We will do all that for you so you can focus on what is really interesting for y
    All commits are always squashed on merge by GitHub, so there is no need to squash them manually, amend them, and/or do force pushes.
    Autogenerated GitHub's squash commit's title and body should be manually replaced by PR's title and description; that includes both manual merges and auto-merges.
    Do not leave original commit messages in the squashed commit body.
+
+## Calls "to show and/or to explain"
+
+Please multiply the knowledge shared on calls and 1-1 messages by writing a separate detailed blog-post article (not in the project's source code).
+1-1s are good to check what you might have missed along the way - what seemed to you obvious and to others is not.

CONTRIBUTING.md

@@ -38,6 +38,9 @@ With `task` installed, you may do the following:
    The differences in response are then logged and the FerretDB response is sent back to the client.
 5. Run `mongosh` with `task mongosh`.
    This allows you to run commands against FerretDB.
+6. Change the code.
+7. Run `task fmt` to format source code.
+8. Run `task lint` to run linter checks.
 
 You can see all available `task` tasks with `task -l`.