| Table of Contents |
|---|
What is the
...
You requests should be acknowledged by the EWC team within 1 to 2 business days.
What is the usual time of inactivity after which my submission is considered stale?
...
Check for pull requests that may indicate the new metadata is undergoing review. If none if found, reach out to the Item maintainer to clarify if they are planning to feature the new version on the EWC Community Hub dashboard. If the response is negative or no reply reaches you between the response time covered by the stated support level, you may choose to either:
- Simply consume Consume the Item directly from its source
...
If you chose the latter action, the EWC team will assess whether the item is considered orphan and is a good candidate for EWC adoption, or rather it has reach the end of life and should be delisted from the catalog.
Can I contribute
...
with my Item but without offering support?
Yes, specify in the Item metadata during submissionno support commitment is expected for Items contributed by community members. Upon submission, include in your Item metadata should the following attribute:
| Code Block | ||
|---|---|---|
| ||
supportLevel: Community-shared |
This signals to EWC Users that updates will be done on a best-effort approach, without fixed release cycles, or based on the goodwill of other community members (see The varying levels of support are thoroughly documented, so that community members get full transparency upfront and the correct expectations can be set given the contributors' commitment or lack thereof (see Prepare Your Item - Deciding on a Support Level).
...
For Items hosted on GitHub or GitLab you can simply star their repository. In any other case, you may share your endorsements over the EWC discussion platform to boost visibility.
Why should I
...
accept open source
...
contributions
...
only from trusted individuals/organizations?
We advise you to always review contributions thoroughly, conditioning their acceptance not only to quality but also based on whether or not they come from individuals/organizations you know and trust. Keep in mind that, with advent of agentic and generative AI, the topic of dubious issue flagging and code review fatigue has become a serious problem for open-source community in general. Have full certainty that nor the EWC or its community members are entitled to force anything change upon your contributions, and you are free to dismiss any PR you deem untraceable or ill-intended.
...