...
Unless your Item has dependencies linked to GPL terms of use, or on the contrary, they are constrained by a proprietary license, you, as the Item owner, are free to choose a suitable open-source license under which to feature Items. For reference, EWC -supported Items typically release under MIT or Apache 2.0 license.
...
Whether an Item is deployable or not depends mainly on the Item Technology. Find the full list of currently supported ones , please refer to (see EWC Community Hub's home page ).
Item is not Deployable
No additional action required.
...
For a complete Item Metadata example including full compatibility with the ewccli checkout "ECMWF Data Flavour" Item, published on GitHub.
Putting
...
it All Together
Besides the information highlighted in the previous sections, Item usage information is recommended to increase the quality of your submission. To help both contributor and reviewers to categorize this information
...
Before formally submitting an initial version of your Item, or to request the indexing of a followup version, we kindly ask you to compile all relevant Item Metadata in a single editable file. The EWC uses YAML format to structure the Item metadatafill in the Item Metadata structure the EWC Community Hub uses (YAML format). Take as example the metadata of the "ECMWF Data Flavour" Item, published on GitHub:
(EWCWF Data Flavour Item's Metadata Excerpt)
...
| Info |
|---|
A contact (email or URL) is required for successful submission. |
.
...
When compiling When preparing metadata for your own Item, we recommend you copy the aforementioned content of said example YAML contents and adapt the attribute values according to your case.values accordingly.
("EWCWF Data Flavour" Item, published on GitHub)
Detailed information on all the supported metadata attributes, both required and optional, is also publicly available. The current version of the Items schema definition is hosted on GitHub, at https://github.com/ewcloud/ewc-community-hub/blob/main/schemas/items/v1alpha1.json.
...