Conversation
|
@richard-cox what do we need to move this forward? I see there are a couple of mentions to Troy but I don't remember exactly what we needed from him (at this moment I can't remember the context of all the mentions 😅 ) |
| ### What are the requirements for adding a project to this repository? | ||
|
|
||
| ## Requirements | ||
| TODO: Confirm with Troy - verified partner |
There was a problem hiding this comment.
Do we need to run through the SUSE verified partner process for owners of extensions that we ship in this repo?
| TODO: Confirm with Troy - verified partner | ||
|
|
||
| * Charts must be Helm 3 compatible. | ||
| TODO: Confirm with Troy - how supply and track business contact (if not included below)? |
There was a problem hiding this comment.
If we don't require them to become suse verified partners how to we track contact details?
| * Compatibility annotations. For more information see [here](https://extensions.rancher.io/extensions/next/extensions-configuration#configurable-annotations) | ||
| * Be compatible with at least the current version of Rancher | ||
|
|
||
| TODO: require description, home url, maintainers in package.json |
There was a problem hiding this comment.
Ad specific requirements
| - Impact on security, scaling and performance | ||
| - Code Review | ||
| - UX Review | ||
| - Documentation and test approach TODO: Confirm, do we include these? |
There was a problem hiding this comment.
To discuss, do we need to add more detail here, elsewhere or at all?
|
@aalves08 added some PR comments that should help clarify the TODOs. Unfortunately, from my side, this won't get any TLC for a few months |
I know... I know... Don't worry. What you've written is already amazing 🙇 I'll try to move this forward in between my priority work. Thanks! 🙏 |
2 participants
Initial contribution process