Skip to content

Commit

Permalink
docs: Remove community calls
Browse files Browse the repository at this point in the history
Closes: #929
Signed-off-by: Michael Gasch <mgasch@vmware.com>
  • Loading branch information
Michael Gasch authored and embano1 committed Jul 19, 2022
1 parent 3341a87 commit 06a1112
Show file tree
Hide file tree
Showing 2 changed files with 0 additions and 25 deletions.
14 changes: 0 additions & 14 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -29,8 +29,6 @@ Follow](https://img.shields.io/twitter/follow/embano1?style=social)](https://twi
- [Overview](#overview)
- [Architecture](#architecture)
- [Getting in touch](#getting-in-touch)
- [Community Calls](#community-calls)
- [Other Channels](#other-channels)
- [Contributing](#contributing)
- [License](#license)

Expand Down Expand Up @@ -123,18 +121,6 @@ page](https://vmweventbroker.io/kb/architecture).

## Getting in touch

### Community Calls

Public VEBA community meetings are held every **last Tuesday** in the month at
**8AM Pacific Time (US)**.

- **Zoom:** <https://via.vmw.com/veba-ama>
- **Note:** The meeting is **password protected** to mitigate abuse. Please join the VEBA Slack [channel](https://vmwarecode.slack.com/archives/CQLT9B5AA) to receive the Zoom password or contact us in case of issues.
- **Notes**: <https://via.vmw.com/veba-notes>
- **Recording Playlist**: [VEBA Community Calls](https://youtube.com/playlist?list=PLnopqt07fPn3hspeQvarWuFH3IiwkMpDJ)

### Other Channels

Feel free to reach out to [Team #VEBA](https://vmweventbroker.io/#team-veba) and
the community via:
- Email us at [dl-veba@vmware.com](mailto:dl-veba@vmware.com)
Expand Down
11 changes: 0 additions & 11 deletions docs/site/community.md
Original file line number Diff line number Diff line change
Expand Up @@ -54,16 +54,6 @@ links:

The VMware Event Broker Appliance team welcomes contributions from the community and this page presents the guidelines for contributing to VMware Event Broker Appliance.

## Community Calls

Public VEBA community meetings are held every **last Tuesday** in the month at
**8AM Pacific Time (US)**.

- **Zoom:** <https://via.vmw.com/veba-ama>{:target="_blank"}
- **Note:** The meeting is **password protected** to mitigate abuse. Please join the VEBA Slack [channel](https://vmwarecode.slack.com/archives/CQLT9B5AA){:target="_blank"} to receive the Zoom password or contact us in case of issues.
- **Notes**: <https://via.vmw.com/veba-notes>{:target="_blank"}
- **Recording Playlist**: [VEBA Community Calls](https://youtube.com/playlist?list=PLnopqt07fPn3hspeQvarWuFH3IiwkMpDJ){:target="_blank"}

## Contributing

Following the guidelines helps to make the contribution process easy,
Expand Down Expand Up @@ -115,7 +105,6 @@ the following requirements:
- The change is clearly documented and follows Git commit best practices (see
below)


### Format of the Commit Message

We follow the conventions described in [How to Write a Git Commit
Expand Down

0 comments on commit 06a1112

Please sign in to comment.