Update CONTRIBUTING.md

Co-authored-by: Fabrizio Ferri-Benedetti <[email protected]>

CONTRIBUTING.md

@@ -277,7 +277,8 @@ This last section includes guidelines and some common practices used by approver
 * A PR by non-maintainers should **never** update git sub modules. This happens by accident from time to time. Let the PR author know that they should not worry about it, we will fix this before merging, but in the future they should make sure that they work from an up-to-date fork.
 * If the contributor is having trouble signing the CLA or used the wrong email by mistake in one of their commits, ask them to fix the issue or rebase the pull request. Worst case scenario, close and re-open the PR to trigger a new CLA check.
 * Words unknown to cspell should be added to the cspell ignore list per page by PR authors. Only approvers and maintainers will add commonly used terms to the global list.
-
+* When an approver or maintainer won't be available to contribute for an extended period of time (more than a few days or a week) or won't be available in that period of time, they should communicate this using the [#otel-comms](https://cloud-native.slack.com/archives/C02UN96HZH6) channel and updating the GitHub status.
+* ```
 [.nvmrc]: .nvmrc
 [clone]:
   https://docs.github.com/en/repositories/creating-and-managing-repositories/cloning-a-repository