Skip to content

Commit

Permalink
Merge pull request #551 from mandy-chessell/dev-dojo
Browse files Browse the repository at this point in the history
Update slack url (#488) and metadata instances
  • Loading branch information
mandy-chessell authored Oct 24, 2022
2 parents e5201ec + 222237f commit c85c52b
Show file tree
Hide file tree
Showing 21 changed files with 103 additions and 30 deletions.
2 changes: 1 addition & 1 deletion site/docs/concepts/endpoint.md
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@ URL and port number (if needed) for the server where the asset is located
(or at least accessible by the connector). For file-based resources, this is typically the name of the file.
* **protocol** - The communication protocol that the connection should use to connect to the server.
* **encryptionMethod** - Describes the encryption method to use (if any). This is an open value allowing
information needed by the connector user to retrieve all of the information they need to work with
information needed by the connector user to retrieve all the information they need to work with
the endpoint.
* **additionalProperties** - Any additional properties that the connector need to know in order to
access the Asset.
Expand Down
4 changes: 2 additions & 2 deletions site/docs/concepts/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -219,7 +219,7 @@
- [Metadata Access Store](/concepts/metadata-access-store)
- [Metadata Archives](/concepts/open-metadata-archive)
- [Metadata Catalog](/services/omas/asset-catalog/overview)
- [Metadata Collection Id](/concepts/metadata-collection-id)
- [Metadata Collection](/concepts/metadata-collection)
- [Metadata Discovery](/features/discovery-and-stewardship/overview)
- [Metadata Highway](/services/omrs)
- [Metadata Instances](/concepts/open-metadata-instances)
Expand Down Expand Up @@ -259,7 +259,7 @@
- [Open Metadata Exchange Rule](/concepts/open-metadata-exchange-rule)
- [Open Metadata Instances](/concepts/open-metadata-instances)
- [Open Metadata Labs](/education/open-metadata-labs/overview)
- [Open Metadata Repository](/concepts/metadata-repository)
- [Open Metadata Repository](/concepts/open-metadata-repository)
- [Open Metadata Repository Cohort](/concepts/cohort-member)
- [Open Metadata Repository Services](/services/omrs)
- [Open Metadata Type Definitions (TypeDefs)](/concepts/open-metadata-type-definitions)
Expand Down
4 changes: 2 additions & 2 deletions site/docs/concepts/metadata-collection-id.md
Original file line number Diff line number Diff line change
@@ -1,9 +1,9 @@
<!-- SPDX-License-Identifier: CC-BY-4.0 -->
<!-- Copyright Contributors to the ODPi Egeria project. -->

# Metadata Collection Identifier
# Local Metadata Collection Identifier

Every metadata repository has a unique identifier called the *local-metadata-collection-id*. This identifier is assigned automatically during the configuration of the local repository but can be overridden through administrative commands.
Every [cohort member](/concepts/cohort-member) with a [metadata repository](/concepts/open-metadata-repository) has a unique identifier called the *local-metadata-collection-id*. This identifier is assigned automatically during the configuration of its local repository but can be overridden through administrative commands.

Figure 1 shows the local metadata collection id of `1b96495f-82d3-4224-9fdd-31bcb84c224c` in the server configuration. A new local metadata collection id is assigned when the local repository is set up.

Expand Down
12 changes: 12 additions & 0 deletions site/docs/concepts/metadata-collection.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,12 @@
<!-- SPDX-License-Identifier: CC-BY-4.0 -->
<!-- Copyright Contributors to the ODPi Egeria project. -->

# Metadata collection

--8<-- "snippets/metadata-collection-intro.md"

!!! education "Further information"
* Discovering a server's [local metadata collection id](/concepts/metadata-collection-id).


--8<-- "snippets/abbr.md"
2 changes: 1 addition & 1 deletion site/docs/concepts/metadata-repository.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@

# Metadata Repository

A metadata repository is a store for metadata. The metadata within it is called a *[metadata collection](metadata-collection-id.md)*. It is accessed either directly through a [metadata access store](metadata-access-store.md) or indirectly through a [repository proxy](repository-proxy.md).
A metadata repository is a store for metadata. A metadata repository that supports the open metadata standards is called an [*open metadata repository*](/concepts/open-metadata-repository).



Expand Down
2 changes: 1 addition & 1 deletion site/docs/concepts/open-metadata-archive-intro.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ The open metadata archive has three types that are used to signal how the archiv

- A *content pack* contains standard metadata that is generally useful. It may come from the Egeria community or third parties. It can be loaded into many repositories, whether these repositories are connected or not via [cohorts](/concepts/cohort-member). This is a useful way to distribute [open metadata types](/types) or definitions for a standard.
- A *metadata export* contains a collection of metadata elements that have been extracted from a specific open metadata repository to load into another. It is used to transfer metadata between repositories that are not connected via [cohorts](/concepts/cohort-member).
- A *repository backup* contains a collection of metadata elements that have been extracted from a specific open metadata repository to server as a backup. This archive is expected to be loaded back into the same repository. This can be done at any time. If the repository contains more recent content, the older content in the archive is ignored.
- A *repository backup* contains a collection of metadata elements that is intended to act as a backup for a server. It typically contains metadata instances from the server's [local metadata collection](/concepts/metadata-collection). This archive is expected to be loaded back into the same repository. This can be done at any time. If the repository contains more recent content, the older content in the archive is ignored.


--8<-- "snippets/abbr.md"
4 changes: 4 additions & 0 deletions site/docs/concepts/open-metadata-instances.md
Original file line number Diff line number Diff line change
Expand Up @@ -90,4 +90,8 @@ The [*Relationship*](https://odpi.github.io/egeria/org/odpi/openmetadata/reposit

The [*Classification*](https://odpi.github.io/egeria/org/odpi/openmetadata/repositoryservices/connectors/stores/metadatacollectionstore/properties/instances/Classification.html) is the structure for a classification introduced in the EntitySummary.

### InstanceProperties

The [*InstanceProperties*](https://odpi.github.io/egeria/org/odpi/openmetadata/repositoryservices/connectors/stores/metadatacollectionstore/properties/instances/InstanceProperties.html) store the effective dates of the element, along with the attributes defined by its [type](#instancetype)

--8<-- "snippets/abbr.md"
27 changes: 27 additions & 0 deletions site/docs/concepts/open-metadata-repository.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,27 @@
<!-- SPDX-License-Identifier: CC-BY-4.0 -->
<!-- Copyright Contributors to the Egeria project. -->

# Open Metadata Repository

A metadata repository is a store of metadata. A metadata repository that supports the open metadata standards is called an *open metadata repository*. There are two types of open metadata repository:

* *Native open metadata repository*: A native open metadata repository is one that stores [open metadata elements](/concepts/open-metadata-instances) natively. They can typically store any type of open metadata element. It is configured in a [metadata access store](/concepts/metadata-access-store).

* *Adapter open metadata repository*: An adapter open metadata repository supports an open metadata repository API, but translates calls to this API into calls to the native API of a third party metadata repository. It is configured in a [repository proxy](/concepts/repository-proxy).


Open metadata repositories contain one local [metadata collection](/concepts/metadata-collection) that is used for maintaining its own metadata. The identifier for this collection is [configured in the server's configuration document](/concepts/metadata-collection-id).

An open metadata repository may also store metadata elements from other metadata collections, if it is able to preserve the metadata collection id that the metadata element belongs to and honor the maintenance rules associated with its [metadata collection type](/concepts/metadata-collection). All native open metadata repositories can store multiple metadata collection. You need to check the implementation of an adapter open metadata repository to verify its capability.

The value of being able to store metadata elements from other collections is:

* To be able to cache metadata elements from other members of the open metadata ecosystem. These metadata elements are called *reference copies*.
* To be able to manage [external source metadata collections](/concepts/metadata-collection).
* To be able to store metadata from [open metadata archives](/concepts/open-metadata-archive).

Open metadata repositories are responsible for replicating metadata from their local metadata collection to other members of the connected cohorts.

--8<-- "snippets/abbr.md"


Original file line number Diff line number Diff line change
Expand Up @@ -64,11 +64,11 @@ As you work through this Dojo you may find problems with our documentation - per

### Slack

Another useful resource to help you as you work through these Dojo sessions - whether it is problems, questions, or about topics unrelated to the Dojo, you can [join :material-dock-window:](https://slack.lfai.foundation){ target=slack } our LF AI & Data Slack workspace. Once you've done so, look at the channels beginning **#egeria**-.
Another useful resource to help you as you work through these Dojo sessions - whether it is problems, questions, or about topics unrelated to the Dojo, you can [join :material-dock-window:](https://slack.lfaidata.foundation){ target=slack } our LF AI & Data Slack workspace. Once you've done so, look at the channels beginning **#egeria**-.

**#egeria-dojo** has been set-up to support this learning activity.
**#egeria-dojo** has been set up to support this learning activity.

If you're happy to use Slack, go there now and get connected to your tutors and fellow attendees to say hello & discuss any problems.
If you're happy to use Slack, go there now and get connected to your tutors and fellow attendees to say hello and discuss any problems.

### Meetings & calendars

Expand Down
6 changes: 5 additions & 1 deletion site/docs/features/metadata-provenance/overview.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,10 @@ The open metadata ecosystem draws together metadata from many sources. Metadata

## Metadata Collections

Inside the [native open metadata repository](/concepts/open-metadata-repository) found in a [Metadata Access Store](/concepts/metadata-access-store), metadata is organized into *Metadata Collections*. It has one *local metadata collection* which it uses to store the metadata elements that it *homes*. Each metadata element has one home metadata collection. Typically, this is the place where it was first created. The metadata element can only be updated in its home metadata collection.

The native open metadata repository can also store metadata elements from other metadata collections. These metadata elements are called *reference copies*, and they are read-only.

The metadata that a specific technology instance creates and maintains is referred to as a *metadata collection*. For example, in figure 1, there are (at least) three metadata collections. There is one in the database server on the left, (at least) one in the open metadata ecosystem and one in the downstream database server on the right.

![Figure 1](metadata-provenance-examples.svg)
Expand All @@ -23,7 +27,7 @@ Metadata inside the open metadata ecosystem is broken down into small elements c

## Metadata Collection Identifiers

In open metadata, each metadata collection has a unique identifier, called the *metadata collection id* and an optional *metadata collection name*. When a metadata instance from the collection is shared within the broader open metadata ecosystem, it includes the metadata collection id and metadata collection name in its header. This identifies the *home* metadata collection of the metadata instance.
In open metadata, each metadata collection has a unique identifier, called the *metadata collection id* and an optional *metadata collection name*. When a metadata instance from the metadata collection is shared within the broader open metadata ecosystem, it includes the metadata collection id and metadata collection name in its header. This identifies the *home* metadata collection of the metadata instance.

The metadata instance header also includes a category name that describes how the metadata was introduced into the open metadata ecosystem. This category name is called the *Instance Provenance Type* by the [Open Metadata Repository Services (OMRS)](/services/omrs) and *Element Origin* by the [Open Connector Framework (OCF)](/frameworks/ocf/overview) and most of the [Open Metadata Access Services (OMASs)](/services/omas). We will use *Element Origin* for the rest of this description since it is the most commonly used name.

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -327,7 +327,7 @@ Note that in the case of Java clients, these are system properties, and do not u

### Other clients

Similar principles to those documented for Java should apply. If you need further assistance, please contact the team on [Slack :material-slack:](https://lfaifoundation.slack.com/archives/C01F40J2XA8){ target=slack }. A pull request (or issue) with contributed documentation is also very welcome!
Similar principles to those documented for Java should apply. If you need further assistance, please contact the team on [Slack :material-slack:](https://slack.lfaidata.foundation){ target=slack }. A pull request (or issue) with contributed documentation is also very welcome!

### Example to launch Egeria

Expand Down
2 changes: 1 addition & 1 deletion site/docs/guides/community.md
Original file line number Diff line number Diff line change
Expand Up @@ -22,7 +22,7 @@ We have a variety of weekly and bi-weekly meetings to which all are welcome:

### Asynchronous dialog

Egeria uses the [LF AI & Data Slack community :material-slack:](https://lfaifoundation.slack.com/archives/C01F40J2XA8){ target=slack } to provide an ongoing dialogue between members. This creates a recorded discussion of design decisions and discussions that complement the project meetings.
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.

Expand Down
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
<mxfile host="Electron" modified="2022-10-22T10:40:17.139Z" agent="5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) draw.io/20.3.0 Chrome/104.0.5112.114 Electron/20.1.3 Safari/537.36" etag="4KZTUZ_u9gKHB2p20T9R" version="20.3.0" type="device" pages="3"><diagram id="suQpp1NyaX_zTb47WVW7" name="existing-business-flow">3VnbUtswEP2aPNKJLTuXR0gIdKa0TOlM4amj2BtbVLFcWSYJX1/JluJrAxRyDTPEu7qfo7MrOR00mi+vOI7DG+YD7dhdf9lB445tW1a3J7+UZ5V7+n2UOwJOfF2pcNyRZ9DOrvamxIekUlEwRgWJq06PRRF4ouLDnLNFtdqM0eqoMQ6g4bjzMG16fxJfhLl3YPcL/zWQIDQjW71hXjLHprJeSRJiny1KLnTZQSPOmMif5ssRUAWewSVvN/lH6XpiHCLxmga36P7zn/NHMblmk7Phg/croN0zS9OTiJVZMfgSAG0yLkIWsAjTy8J7wVka+aC67UqrqPOFsVg6Lel8BCFWmk2cCiZdoZhTXSpnzFf3qv0n2zX2g+4vM8bLirXSVnPNGoaEpdyDTQvVhAnMAxAbKpoeFQylITSmV8DmIGckK3CgWJCn6j7BersF63oFI/JBk/IGguzBXghaEpHz03e1+VAqKthRxqpM1X3ZyCj95L5AaiI5EedKq9LhUZwkxDPuCaFmTrvgHh0U92beT5imeqg7GZiSxo6o8r0IiYC7GGeYLGRYrnI7k5COGGU8a4t8DINZjjdnv6FU0vMGMJ2pEhO5NtLwBFzAciNsprSvQ6LOCcjYiyLCWiZshqXo2utuC+kjVJlVVVlP7pbNOsusW+BEYgb83RHVEHRsEdUa7pXrEtEm+72Za/ulkLoDVk1wOhBWzbxLsfI7JIC5FzboPvgA6QwHBxYg7f2KphoguxtFUzlORCyC2lninfowl5AjO0usN2GhjxscpTPsiZSTKFBjRr78PyZyn5NpKgiLjk85Vr+qHLdFOeu75W6UY+9DOVs/U3/89tZNbxmRc1kT6tpVQh1UIyoXom5V42o9jXfQhxq6uWZJTASmzXP42+Qxc9Vfqzyyj2rBIlHy558tyAahGsqOu++E4zRw/8Z94E3Q5RJFFWdMSRCpfS8BUQfdCwUE8TA91wVz4vu5ziAhz3iadaWUFqttlC3Fvei4Y9WXlFaSq8xqUKWzyxbiljNsxi23BX97a/i7Dfy/wkItkzM/9USmbI/EcJp8OMiu5pHBK09g2yOk9yIhPiQeJ3Fr5j4JVlAtGaBeCyvOTllpvqIZURIpGDt2jyrIp1w+BerpBydtWeMkqHHqAaxFMG0BrJ7OP4wZ1LwQjoHKgwgnLW/QToKDujxcc0cvcdDfpTpQ89KhX2DWpQFLL8RRcKLZRKaP2vGqKY42Yv5DHNIsflLKD8HFD3Po8i8=</diagram><diagram id="Wf0IVIaQwe-nAOgTDeOM" name="new-business-flow">7Vvrc6o4FP9r/Hh3IOGhH3vt607bWaftzLb7LUKU7CJxQqx6//pNJCiQ1GoVsHXbmZacPIDz+J2Tc0IH9ieLG4am0QMNcdwBVrjowMsOALZteeKfpCwziu/DjDBmJFSDNoQn8hsroqWoMxLitDSQUxpzMi0TA5okOOAlGmKMzsvDRjQu33WKxlgjPAUo1ql/kZBHGbUL/A39FpNxlN/Z9npZzwTlg9WbpBEK6bxAglcd2GeU8uxqsujjWDIv58vda/TsPPg3y4H1Qkbhok8WTz+yxa73mbJ+BYYTftylQbb0G4pnil+3NJ0SjmL1znyZM5LRWRJiuZjVgT/nEeH4aYoC2TsXqiNoEZ/EomWLyxGJ4z6NKVvNhSNX/gp6yhn9Fxd6vNWPnEETXqBnP4L+hhknQpwXMRknoo9Teau1LOTNdmSPYqNcEC8KyqHYdYPpBHO2FENUL+gpySvVt13Vnm8USbxBRouKSmSpgUgp73i99kZA4kLJyCyvQTgYDZxf7B6+YP/afbjvTu9/QEeTCw6FvqsmZTyiY5qg+GpD/VmW3GbMPZW8XLHwH8z5UhkvmnFaliZeEP4ip//hu6r5Wui6XKilV41l3kjECxdnyfZrsXMzb9XKJ6YcMX4hTV8QEprgnHZNJLNWY/YTeUpnLMBbxilIEzcZY76N/cpeJM+3ahDDMeLkrYxBh2jDtscuWO8lDThlqaYke5rraASCwGSuoTf0XK9Gm4MeLNtcT7e5nFQ0Obcui7M0XjZqcJ+yt73M7duYkpo6oES8yFqhHKtbUihoVzQle1I1q6Is68f4vP7Yp6M/1o76U9KejTLtAtdBjNKUBBXE3t9JF9XMyFagq9m2AKduLYOwrGWOcHlNapkexz2JCFj3A4cEcSHC3ZHRK3hBFw9HTYVlNiyHZQDqLsIGBh/h1RaVfb2gzC4buWf7H5j5qjXAjAiWYXaw7zDy0d3Rd/htRWHGp2k3JC/i+xrtzcKvR1q1O/DKLgzCZh2403IECA63bnCaPnxXc8+32Cdi767max9xihELIk1RvqaDdbugbHFW2w7W+yoQu0vuovmN2jYnejIRdK8cQbvWbhG0YDZaFoZN5YD0/ftUvInrVrKm24fnmb33hld3m5Xx4iJ73qN6KF8DpAeUzEYo4DNGkrFkThKKv5dEAAsZzjihyTeBKmiV00UuMKRo7SahqtsGVO3ov3NEs/dAtM+jzjY0+dDnNxRcuqCyb98xuNQN3/0gAZBxpr40k6WBwJ8sxIZUsLAsXtYepEorgRCx3NppNZcJCcNMUXFKfqPhaimpHApsxbruz457KdcSuplmampr8KAcYm1g4DslGQBfBwPXgAWgLiywbU0oHeChicTWZJjKf484IFMsxgQRJYEhY/N9xeValTDTkOpfV9KakZeeRntmGPGJfHPgxVIQQyauxvLqVzKibIKM3vT7Sq0aEa09aUFqXYPQqsB6PKHpVbB+TBLJWl1mz4yg+KyMrLKXWwdDH2BifeJyNHFd4lh4cEbOCv0gMO8sioLxGwU/Pa9xFc4ChW/ZFqJqThfhGw1QsDwjudm9XlluBvwzFahrMyjYTvVhk8QApSzGuvOA0x3vJD+31y/3E/iH6ZG8Pv1hfkSx/0SSk7DXijY0eF6hnVy1SR2+QrI6f+4Cqg/EbVcBrVUIbg/KBmE7dLFvygb1PB8ir7FsEChjszFxnW/Um6kM6071AaN0xrBk+znFO45bCUQ9dye/WVu8A/2W/ebR3eaxIc/bEfLAaSFeKxnYOuVqTtv6jRb7d1aGoyduDzub0crxu1M21tM6O5M/dvHgWiR4Ivaa1l1C5/HqOb9ndOK0Hp04enB4dkUDJ8975FLptlw0cPR85pmGjC6oiMbw/U2jIaOj5y4HjIazQG6mSuWAaqLMmD1TR3QF1Kaz+Kwka/fKmwHo65sB4wmjY3zmET0y/mpdD/s96+F2fgv+vrt7zT/z+L/ys61eVzmIafBfR6r8iObmu8qsRL75OhVe/Qc=</diagram><diagram id="BLJhXTUBH7IGwTq-7cBH" name="layers-of-operation">5ZbBbpwwEIafBqk9VAJ7YZMrZJNspUpRiRSpNwcGsGoYZEyAPn3txSwQLonURpEWDoz/GQ94vjHg0Kjs7ySrix+YgnCIm/YOvXEI8Tw30BejDKOy39NRyCVPbdAsxPwPWNG1astTaFaBClEoXq/FBKsKErXSmJTYrcMyFOu71iyHjRAnTGzVJ56qYlSvyH7W74HnxXRnL7gePSWbgu1KmoKl2C0kenBoJBHVaJV9BMIUb6pLFu4P9Q14ft/T2+DX9/vhGH4bk92+Z8p5CRIq9W9TkzH1CxOtrddPaLCViUY2LloNUyUltlUKJpvr0LAruIK4Zonxdrp3tFaoUuiRp81zscwg40JEKFCeEtHMN6cJUhJ/w8ITnA4zAyu10MdD62+shK3YC0gF/aIPbGXuAEtQctAh1ksCC9l2Ob2y427uGTq1dLHol2kes22an1PPKLRhabyDDN2QOVYZSt2VHCuHBEI/QPgstZUbK27rWpgFRQXj1YXD87bwPP8j4e028MK24RU0Goz7IFFvr8bssNcUvxwfdUA8NArK5utFQdyRzwbR30B8AKw1i0vCQvzrFRay+38vRj2cv6Yn3+KfhB7+Ag==</diagram></mxfile>
2 changes: 1 addition & 1 deletion site/docs/release-notes/2-6.md
Original file line number Diff line number Diff line change
Expand Up @@ -120,7 +120,7 @@ Open Metadata and Governance vision, strategy and content.

# Further Help and Support

As part of the Linux AI & Data Foundation, our slack channels have moved to the [LF AI & Data Slack workspace](https://slack.lfai.foundation/){ target=lf }, and our mailing lists can now be found at https://lists.lfaidata.foundation/groups
As part of the Linux AI & Data Foundation, our Slack channels have moved to the [LF AI & Data Slack workspace](https://slack.lfaidata.foundation){ target=lf }, and our mailing lists can now be found at https://lists.lfaidata.foundation/groups

Continue to use these resources, along with GitHub to report bugs or ask questions.

Expand Down
2 changes: 1 addition & 1 deletion site/docs/release-notes/2-7.md
Original file line number Diff line number Diff line change
Expand Up @@ -47,7 +47,7 @@ Open Metadata and Governance vision, strategy and content.

# Further Help and Support

As part of the Linux AI & Data Foundation, our slack channels have moved to the [LF AI & Data Slack workspace](https://slack.lfai.foundation/), and our mailing lists can now be found at https://lists.lfaidata.foundation/groups
As part of the Linux AI & Data Foundation, our Slack channels have moved to the [LF AI & Data Slack workspace](https://slack.lfaidata.foundation), and our mailing lists can now be found at https://lists.lfaidata.foundation/groups

Continue to use these resources, along with GitHub to report bugs or ask questions.

Expand Down
2 changes: 1 addition & 1 deletion site/docs/release-notes/2-8.md
Original file line number Diff line number Diff line change
Expand Up @@ -142,7 +142,7 @@ Open Metadata and Governance vision, strategy and content.

# Further Help and Support

As part of the Linux AI & Data Foundation, our slack channels have moved to the [LF AI & Data Slack workspace](https://slack.lfai.foundation/){ target=lf }, and our mailing lists can now be found at https://lists.lfaidata.foundation/groups
As part of the Linux AI & Data Foundation, our Slack channels have moved to the [LF AI & Data Slack workspace](https://slack.lfaidata.foundation){ target=lf }, and our mailing lists can now be found at https://lists.lfaidata.foundation/groups

Continue to use these resources, along with GitHub to report bugs or ask questions.

Expand Down
Loading

0 comments on commit c85c52b

Please sign in to comment.