...
| Name | Summary | Audience | Service Level Agreement (SLA) | Example |
|---|---|---|---|---|
| Community-Shared | Best-Effort / No SLA | For typical users or research groups sharing useful work | None. No guaranteed response, or issue acknowledgement. Contributions and fixes depend entirely on community goodwill. | A GitHub repository with a permissive license but no maintainer commitment |
| Community-Updated | Active / No SLA | For small teams or labs actively using the Item themselves | None. Maintainers monitor issues and PRs. Best-effort responses. Updates are featured occasionally (aligned with their internal usage) | An enriched dataset with pre-calculated metrics on atmospheric phenomena, updated at irregular interval and/or subject to data availability, without any formal commitment |
| Community-Supported | Well-defined SLAs | For organizations willing to stand behind their Items | Documented response channels (email, ticket system, GitHub issues). Defined response time (within hours or up to 7 business days). Regular security patches. Changelog publishing. | A data pipeline template for various streaming analysis algorithms, regularly updated to support new datasets and increase throughput capabilities |
| EWC-Supported | Well-defined SLAs, Partner-Backed | For Items featured by EWC partners (ECMWF, EUMETSAT, etc.) or trusted collaborators | Same as Community-Supported, plus guaranteed compatibility with the EWC hardware and clear escalation path in case of security sensitive issues. | A one-click deployable software stack for self-managed identity/policy/audit (IPA), hardened SSH access point and remote desktop environment hosting |
Defining Deployability
Wether Whether an Item is deployable or not depends mainly on the Item Technology (find . Find the full list of currently supported ones, please refer to EWC Community Hub's home page).
Item is not Deployable
No additional action required.
...