...
| Step | Name | Description |
|---|---|---|
| 1 | Proposal | Open a ticket (or PULL REQUEST) with metadata relative to the item, specifically: contacts: "CONTACTS (e.g. email, Github issues, etc.)." description: "SHORT DESCRIPTION OF THE ITEM." description_long: "LONG DESCRIPTION OF THE ITEM's purpose, features, and functionality." license: "NAME OF THE LICENSE (e.g. Apache License 2.0)." license_url: "URL TO THE LICENSE (e.g. https://github.com/ewcloud/ewc- flavoursLICENSE)."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 indicating the current release of the software, allowing users to track updates, bug fixes, and new features. "
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).
|
| 2 | Evaluation by EWC administrator | E&E reviews the proposal and make sure all metadata are included. REVIEW OF THE PULL REQUEST |
| 3 | EWC Community Hub Listing | When the review is successful, E&E will merge the proposal and integrate it in the EWC Community Hub items. → In this way it will appear in the dashboard. PULL REQUEST IS MERGED |
| 4 | Community Engagement |
|
...