Skip to content

Commit

Permalink
Update information about the community calls.
Browse files Browse the repository at this point in the history
Signed-off-by: Mandy Chessell <mandy.e.chessell@gmail.com>
  • Loading branch information
mandy-chessell committed Sep 1, 2023
1 parent 5ec6d11 commit ad9ad35
Show file tree
Hide file tree
Showing 2 changed files with 5 additions and 14 deletions.
17 changes: 4 additions & 13 deletions site/docs/guides/community.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,25 +9,18 @@ This project welcomes contributors from any organization or background, provided

### Live discussions

We have a variety of weekly and bi-weekly meetings to which all are welcome. These calls run January to June, September to November. July, August and December are popular vacation times, and so we stop the calls while the attendance is low.
We have weekly community meeting to which all are welcome. We cover demos, releases, meetups and other activities going on in the community ([agenda and minutes :material-dock-window:](https://wiki.lfaidata.foundation/display/EG/Community+Meetings){ target=wiki }). These calls run January to June, September to November. July, August and December are popular vacation times, and so we stop the calls while the attendance is low.

<iframe src="https://calendar.google.com/calendar/embed?height=600&amp;wkst=1&amp;bgcolor=%23ffffff&amp;ctz=Europe%2FLondon&amp;src=YjVxaGRyNXFkYmZscDhkbHA3MGxtb2RtMHNmdmlocWxAaW1wb3J0LmNhbGVuZGFyLmdvb2dsZS5jb20&amp;color=%234285F4&amp;showCalendars=0&amp;showPrint=0&amp;title=Egeria%20Calendar" style="border-width:0" width="800" height="600" frameborder="0" scrolling="no"></iframe>

| Call | Purpose |
|---|---|
| Developers call | Discussion on code development (not minuted) |
| Community call | Demos, meetups and other activities going on in the community ([agenda and minutes :material-dock-window:](https://github.com/odpi/data-governance/wiki){ target=wiki }) |
| TSC call | Strategy, planning and decision-making with the [Technical Steering Committee (TSC)](https://wiki.lfaidata.foundation/display/EG/Egeria+Technical+Steering+Committee+%28TSC%29+Home) |


### Asynchronous dialog

Egeria uses the [LF AI & Data Slack community :material-slack:](https://slack.lfaidata.foundation){ target=slack } to provide an ongoing dialogue between members. This creates a recorded discussion of design decisions and discussions that complement the project meetings.

Follow the link above and register with the LF AI & Data Slack service using your email address. Once signed in you can see all the active Slack channels.

!!! tip "The main Slack channel for the Egeria project is called `#egeria-discussion`"
Additional channels are added from time to time as new workgroups and discussion topics are established. For Egeria these channel names will begin with `#egeria`. You can also view Slack channels from other LF AI & Data projects.
We use `#egeria-announce` for meetings and release announcements. Additional channels are added from time to time as new workgroups and discussion topics are established. For Egeria these channel names will begin with `#egeria`. You can also view Slack channels from other LF AI & Data projects.

??? question "More information about Slack?"
Slack is an instant messaging tool that allows multiple conversations to occur amongst the community members at any one time. Each conversation is called a *channel*. Channels can be set up for a specific event or have a long-term existence.
Expand All @@ -38,9 +31,7 @@ The community tends to use the [mailing list :material-dock-window:](https://lis

### Other websites and resources

- [Webinars :material-github:](../../education/webinar-program/overview){ target=gh } - virtual events covering topics of interest.
- [Workshops :material-github:](https://github.com/odpi/data-governance/tree/main/workshops){ target=gh } - face-to-face workshops promoting discussion and education on Egeria
- [Presentations :material-github:](https://github.com/odpi/data-governance/tree/main/presentations){ target=gh } - presentations given at conferences and private gatherings
From time to time we screen webinars that are open to all. The aim of these webinars is to create in depth videos of a particular topic of interest. Past webinars are described on the [webinars page](/education/webinar-program/overview).

## Git repositories

Expand All @@ -61,7 +52,7 @@ Every contribution is signed to say that the contributor has the rights to make

## Creating a Linux Foundation account

The Linux Foundation provide build and distribution facilities. You need an account to access some of the reports from the build.
The Linux Foundation provide build and distribution facilities. You need an account to access some build reports.

This is the link to create a [Linux Foundation account :material-dock-window:](https://identity.linuxfoundation.org){ target=lf }. Note the username and password you selected.

Expand Down
2 changes: 1 addition & 1 deletion site/docs/release-notes/august-2023.md
Original file line number Diff line number Diff line change
Expand Up @@ -71,7 +71,7 @@ Each directory in the assembly includes a README.md file to explain its contents

## Improved use of Apache Kafka (4.2)

Except when the `no-topics` option is specified, the configuration document helper methods add a connection for both the [InTopic](/concepts/in-topic) and the [OutTopic](/concepts/out-topic) to each Open Metadata Access Service (OMAS) configuration irrespective of whether the particular OMAS supports these topics. This has no impact at runtime because the OMASs simply do not start topics they do not use. However, from a set-up point of view, it is misleading - and can result in an organization thinking they need to set up (and may be pay for) topics that are not use.
Except when the `no-topics` option is specified, the configuration document helper methods add a connection for both the [InTopic](/concepts/in-topic) and the [OutTopic](/concepts/out-topic) to each Open Metadata Access Service (OMAS) configuration irrespective of whether the particular OMAS supports these topics. This has no impact at runtime because the OMASs simply do not start topics they do not use. However, from a set-up point of view, it is misleading - and can result in an organization thinking they need to set up (and may be pay for) topics that are not used.

This release adds knowledge of whether an OMAS supports the inTopic and/or OutTopic to the [AccessServiceDescroption](https://github.com/odpi/egeria/blob/main/open-metadata-implementation/admin-services/admin-services-api/src/main/java/org/odpi/openmetadata/adminservices/configuration/registration/AccessServiceDescription.java) class. This information is used by the configuration helper methods when setting up the access service configuration. For example, this is the list of topics for `cocoMDS1` at release 4.2:

Expand Down

0 comments on commit ad9ad35

Please sign in to comment.