3 years ago
A separate portal for template discussions. This could be implemented in different ways as mentioned below.
1 Replies
3 years ago
Firstly, I'll explain the use cases:
-
Bug reports
-
Troubleshooting
-
General setup help
-
Feature requests
-
Deployment issues
Implementation:
The implementation can be divided into important and optional features.
-
(imp) Discussions linked to each template on the template page with clear status messages to show if the template has reported bugs, deployment issues, or it's good for plug and play.
-
A central place to see all discussions on templates a user owns. This might be redundant since each template has its own discussions linked anyways.
-
A notification system/mailing list for anything negative reported on templates you own.
-
(imp) Automatically report to the template owner if deployments from their template crash. (unless this is a privacy issue). Note that this might cause false positives as deployments could crash due to faulty ENV variables.