egeria

https://egeria.odpi.org/Community-Guide.html links to the developer resources page - https://egeria.odpi.org/developer-resources/Developer-Guidelines.html

The project uses the DCO. It is enforced in the PR process. See developer guide https://github.com/odpi/egeria/blob/master/developer-resources/why-the-dco.md

This is defined in the Operations Guide: https://github.com/odpi/egeria/blob/master/Operations-Guide.md

This is the link to the code of conduct: https://github.com/odpi/egeria/blob/master/CODE_OF_CONDUCT.md

This is defined in the Community Guide: https://github.com/odpi/egeria/blob/master/Community-Guide.md

The project has a core team of 10 + contributors who have been with the project since its inception. There is a good span of modules that have multiple contributors who can maintain the code. https://github.com/odpi/egeria/graphs/contributors

The project has a core team of 10 + contributors who have been with the project since its inception. There is a good span of modules that have multiple contributors who can maintain the code. https://github.com/odpi/egeria/graphs/contributors

This is the roadmap: https://egeria.odpi.org/open-metadata-publication/website/roadmap/

This is the link to the documentation: https://egeria.odpi.org/. Key modules have their own design pages. This is an example of the repository serivces: https://egeria.odpi.org/open-metadata-implementation/repository-services/

The project has security defined at multiple levels. The metadata security module shows how this is set up and implemented: https://egeria.odpi.org/open-metadata-implementation/common-services/metadata-security/. There is also information on customising the platform itself which inclides security settings https://egeria.odpi.org/open-metadata-implementation/server-chassis/server-chassis-spring/

The project has tutorials including a 3 day course for new consumers/contributors: https://egeria.odpi.org/open-metadata-resources/open-metadata-tutorials/ This is linked to from the home page.

The project uses GitHub pages to manage its documentation. This means the documentation is located with the code. The developer guide explains the responsiblity to maintain the documentation. There is a steady stream of doc updates in line with new code function. See the file index.md at the top of the git hub repository for Egeria. https://github.com/odpi/egeria. It is the file that creates the home page found at this URL https://egeria.odpi.org/

The project documents new releases and badges on its website: * https://github.com/odpi/egeria * https://egeria.odpi.org/release-notes/

New releases are announced on Slack as soon as they are ready and the LF publicises the release soon after it is available (but not guaranteed to be in 48 hours).

All contributions are visible through the public git repositories

The project repository website is GitHub and the project website is gnerated from GitHub pages. The documentation is primarily text however there are images. These are labelled and include ALT text. There is also a text description accompanying the diagrams.

All of Egeria's diagnostics use our Audit Log Framework (ALF) which is internationalized.
https://egeria.odpi.org/open-metadata-publication/website/diagnostic-guide/

We do not provide translations. However each log message and exception includes an English formatted message along with the parameter values and the message's unique message id. The unique Id points to an externalized message specification which includes a description to the system action and user response. This means a third party agent receiving these messages can translate them into another language if they have created the translated message specification.

This section is not marked complete because Egeria has 2 UIs and there has been no accessibility testing on them.

All messages go through the audit log framework that externalizes messages both for the audit log and for messages in exceptions. Every message has a unique identifier. Values that are inserted in the messages are stored in the exception or audit log record to allow the message to be reformatted in multiple languages. The project uses US-English as the default language.

The only store of passwords and certificates that the project holds is in our configuration documents. These are manged by a plug-in connector. The supplied default connector uses encryption for the whole document.