-
Notifications
You must be signed in to change notification settings - Fork 86
Add Category Proposal issue template #1033
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Add Category Proposal issue template #1033
Conversation
…ategory proposals
…eligibility requirements and proposal process
jsoriano
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great. @nimarezainia could you please also take a look?
| - Enhancement requests that complain about the lack of this category. | ||
| - Full-story data reporting on average 50+ unique searches for this keyword per month in the integrations UI. | ||
| - Usage of this category for filtering purposes by our industry. | ||
| - [ ] Impact that are we expecting with this category and how we will measure it (success criteria) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure about possible answers to this point. @nimarezainia are we checking some telemetry related to categories?
Co-authored-by: Jaime Soriano Pastor <[email protected]>
💚 Build Succeeded
History
|
| 3. Ecosystem team assesses the request and makes a decision based on data points provided in the GitHub issue | ||
| 4. If we are not able to address and the category doesn’t meet eligibility requirements, we can assume that | ||
| this category is more harmful to the UX than the value it provides, and hence, it must not be added. | ||
| 5. If the decision is in favor of adding the category, the Ecosystem team will prioritize and work on the GitHub issue in | ||
| one of the releases under planning (future releases) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
According to this , should this issue be added the Team:Ecosystem label directly when it is created ? Or should it be added by the user once it has all the data ? @kpollich
What does this PR do?
Adds a new issue template to file categories propsal.
Why is it important?
In order to discuss the change and follow the implementation plan
Checklist
test/packagesthat prove my change is effective.spec/changelog.yml.Related issues
Related #430