1 | Proposal | Open a ticket (or PULL REQUEST) with metadata relative to the item, specifically: Title: Name for the item
contacts: "CONTACTS (e.g. email, Github issues, etc.)." description: "SHORT DESCRIPTION OF THE ITEM." description_long: "LONG DESCRIPTION OF THE ITEM Description: Providing an overview of the software's purpose, features, and functionality." license: "NAME OF THE LICENSE (e.g. Apache License 2.0)." license_url: "URL : link to github repositoryTO THE LICENSE (e.g. https://github.com/ewcloud/ewc-flavours/blob/main/LICENSE)." logo_url: "URL TO /logos in this repository or another pointer (e.g. http://placehold.it/200)." maintainer: "ORGANIZATION, ORGANIZATIONS OR PERSON (e.g. EWC Team)" name: "NAME OF THE ITEM." repository_url: "URL TO THE PUBCLI REPOSITORY (e.g. https://github.com/ewcloud/ewc-flavours/tree/main)." support_level: "INDICATE the level of assistance and maintenance provided." tag_technology: - "SEE BELOW FOR A COMPLETE LIST" tag_category: - "SEE BELOW FOR A COMPLETE LIST" version: "SOFTWARE VERSION Version Number: indicating the current release of the software, allowing users to track updates, bug fixes, and new features. - License: specifying the terms and conditions under which the item is distributed and used.
- Support level: It indicates the level of assistance and maintenance provided by the EWC contributor.
- Responsible person/organization contacts: EWC contributions contacts to get support or ask questions.
Tags for filters and categories: tags provide different dimensions to browse and filter the content. They can contain (non-exclusively) dimensions such as field (weather / climate / etc.), application (nowcasting / fire monitoring / NWP / etc), type (deployable / documentation / etc). TECHNOLOGY ->
- Ansible Playbooks
- Terraform modules
- Dataset
CATEGORY ->
- Compute
- Storage
- Data Access
|