Skip to content
This repository was archived by the owner on Apr 17, 2025. It is now read-only.

Commit 06a1112

Browse files
Michael Gaschembano1
Michael Gasch
authored andcommitted
docs: Remove community calls
Closes: #929 Signed-off-by: Michael Gasch <mgasch@vmware.com>
1 parent 3341a87 commit 06a1112

File tree

2 files changed

+0
-25
lines changed

2 files changed

+0
-25
lines changed

README.md

-14
Original file line numberDiff line numberDiff line change
@@ -29,8 +29,6 @@ Follow](https://img.shields.io/twitter/follow/embano1?style=social)](https://twi
2929
- [Overview](#overview)
3030
- [Architecture](#architecture)
3131
- [Getting in touch](#getting-in-touch)
32-
- [Community Calls](#community-calls)
33-
- [Other Channels](#other-channels)
3432
- [Contributing](#contributing)
3533
- [License](#license)
3634

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

124122
## Getting in touch
125123

126-
### Community Calls
127-
128-
Public VEBA community meetings are held every **last Tuesday** in the month at
129-
**8AM Pacific Time (US)**.
130-
131-
- **Zoom:** <https://via.vmw.com/veba-ama>
132-
- **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.
133-
- **Notes**: <https://via.vmw.com/veba-notes>
134-
- **Recording Playlist**: [VEBA Community Calls](https://youtube.com/playlist?list=PLnopqt07fPn3hspeQvarWuFH3IiwkMpDJ)
135-
136-
### Other Channels
137-
138124
Feel free to reach out to [Team #VEBA](https://vmweventbroker.io/#team-veba) and
139125
the community via:
140126
- Email us at [dl-veba@vmware.com](mailto:dl-veba@vmware.com)

docs/site/community.md

-11
Original file line numberDiff line numberDiff line change
@@ -54,16 +54,6 @@ links:
5454

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

57-
## Community Calls
58-
59-
Public VEBA community meetings are held every **last Tuesday** in the month at
60-
**8AM Pacific Time (US)**.
61-
62-
- **Zoom:** <https://via.vmw.com/veba-ama>{:target="_blank"}
63-
- **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.
64-
- **Notes**: <https://via.vmw.com/veba-notes>{:target="_blank"}
65-
- **Recording Playlist**: [VEBA Community Calls](https://youtube.com/playlist?list=PLnopqt07fPn3hspeQvarWuFH3IiwkMpDJ){:target="_blank"}
66-
6757
## Contributing
6858

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

118-
119108
### Format of the Commit Message
120109

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

0 commit comments

Comments
 (0)