[master] remove info about community calls (hyperledger-archives#4450)

Signed-off-by: Dave Kelsey <d_kelsey@uk.ibm.com>

CONTRIBUTING.md

@@ -24,7 +24,7 @@ If you find a bug in the source code, an error in any documentation, or would li
 
 ## Raising a Composer Improvement Proposal
 
-If you have a suggestion for a Composer Improvement Proposal (CIP), for a feature that is not yet present and you would like to have, please raise an issue using a [CIP template](./contrib-notes/cip-template.md) and tag the issue with the label `improvement proposal`. We endevour to have all CIP items discussed on community calls, so expect to have an invite once raised!
+If you have a suggestion for a Composer Improvement Proposal (CIP), for a feature that is not yet present and you would like to have, please raise an issue using a [CIP template](./contrib-notes/cip-template.md) and tag the issue with the label `improvement proposal`.
 
 ## Getting Started
 

contrib-notes/coding-guidelines.md

@@ -82,7 +82,6 @@ When you start working on new issue, please do the following:
 - Use the [mailing list](https://lists.hyperledger.org/mailman/listinfo/hyperledger-composer) to notify the community that you are planning to start _feature_ work and notify that the design has been placed in the GitHub issue
   - this is to ensure that there is a persistent record of what is happening
 - Say hello, on the composer-dev channel on RocketChat
-- At noteable points please join the weekly community call to share what you have done.
 
 
 ### Good Coding Practices Using ESLint

packages/composer-website/jekylldocs/support/support-index.md

@@ -34,10 +34,3 @@ Check out the code, feel free to get involved.
 
 <a href="https://github.com/hyperledger/composer" class="support-button primary">GitHub</a>
 <br><br>
-
-### Community Call
-
-Join our weekly open community calls.
-
-<a href="https://github.com/hyperledger/composer/wiki/" class="support-button primary">Learn how</a>
-<br><br>