Add security doc link to README (#2487)

Move contributing doc within Getting Involved link.

Depends on #2461

CONTRIBUTING.md

@@ -1,27 +1,37 @@
 # Contributing Guide
 
-We'd love your help!
+We'd love your help! Please join our weekly [SIG
+meeting](https://github.com/open-telemetry/community#special-interest-groups).
 
 ## How to structure PRs to get expedient reviews?
 
-We recommend that any PR (unless it is trivial) to be smaller than 500 lines (excluding go mod/sum changes) in order to help reviewers to do a thorough and reasonably fast reviews.
+We recommend that any PR (unless it is trivial) to be smaller than 500 lines
+(excluding go mod/sum changes) in order to help reviewers to do a thorough and
+reasonably fast reviews.
 
 ### When adding a new component
 
-Consider submitting different PRs for (more details about adding new components [here](#adding-new-components)) :
+Consider submitting different PRs for (more details about adding new components
+[here](#adding-new-components)) :
 
 * First PR should include the overall structure of the new component:
-  * Readme, configuration, and factory implementation usually using the helper factory structs.
-  * This PR is usually trivial to review, so the size limit does not apply to it.
-* Second PR should include the concrete implementation of the component.
-If the size of this PR is larger than the recommended size consider splitting it in multiple PRs.
-* Last PR should enable the new component and add it to the `otelcontribcol` binary by updating the `components.go` file.
-The component must be enabled only after sufficient testing, and there is enough confidence in the stability and quality of the component.
+  * Readme, configuration, and factory implementation usually using the helper
+    factory structs.
+  * This PR is usually trivial to review, so the size limit does not apply to
+    it.
+* Second PR should include the concrete implementation of the component. If the
+  size of this PR is larger than the recommended size consider splitting it in
+  multiple PRs.
+* Last PR should enable the new component and add it to the `otelcontribcol`
+  binary by updating the `components.go` file. The component must be enabled
+  only after sufficient testing, and there is enough confidence in the
+  stability and quality of the component.
 
 ### Refactoring Work
 
-Any refactoring work must be split in its own PR that does not include any behavior changes.
-It is important to do this to avoid hidden changes in large and trivial refactoring PRs.
+Any refactoring work must be split in its own PR that does not include any
+behavior changes. It is important to do this to avoid hidden changes in large
+and trivial refactoring PRs.
 
 ## Report a bug or requesting feature
 
@@ -74,7 +84,8 @@ Verify that the upstream exists:
 
 `git remote -v`
 
-To update your fork, fetch the upstream repo's branches and commits, then merge your `main` with upstream's `main`:
+To update your fork, fetch the upstream repo's branches and commits, then merge
+your `main` with upstream's `main`:
 
 ```
 git fetch upstream
@@ -120,7 +131,8 @@ $ make install-tools # Only first time.
 $ make
 ```
 
-*Note:* the default build target requires tools that are installed at `$(go env GOPATH)/bin`, ensure that `$(go env GOPATH)/bin` is included in your `PATH`.
+*Note:* the default build target requires tools that are installed at `$(go env
+GOPATH)/bin`, ensure that `$(go env GOPATH)/bin` is included in your `PATH`.
 
 ## Creating a PR
 

README.md

@@ -4,7 +4,7 @@
   <strong>
     <a href="https://opentelemetry.io/docs/collector/getting-started/">Getting Started<a/>
     &nbsp;&nbsp;&bull;&nbsp;&nbsp;
-    <a href="https://github.com/open-telemetry/community#special-interest-groups">Getting Involved<a/>
+    <a href="CONTRIBUTING.md">Getting Involved<a/>
     &nbsp;&nbsp;&bull;&nbsp;&nbsp;
     <a href="https://gitter.im/open-telemetry/opentelemetry-service">Getting In Touch<a/>
   </strong>
@@ -28,8 +28,6 @@
 
 <p align="center">
   <strong>
-    <a href="CONTRIBUTING.md">Contributing<a/>
-    &nbsp;&nbsp;&bull;&nbsp;&nbsp;
     <a href="docs/vision.md">Vision<a/>
     &nbsp;&nbsp;&bull;&nbsp;&nbsp;
     <a href="docs/design.md">Design<a/>
@@ -38,6 +36,8 @@
     &nbsp;&nbsp;&bull;&nbsp;&nbsp;
     <a href="docs/performance.md">Performance<a/>
     &nbsp;&nbsp;&bull;&nbsp;&nbsp;
+    <a href="docs/security.md">Security<a/>
+    &nbsp;&nbsp;&bull;&nbsp;&nbsp;
     <a href="docs/roadmap.md">Roadmap<a/>
   </strong>
 </p>