Add docs about what is/is not suitable to be added to GitLab UI
To remain maintainable, we have to say "no" to some merge requests. Not all features are suitable to be implemented in the library itself, and would be best done in the application that requires the feature.
This issue is about documenting this in some way, and also making sure GitLab UI's maintainers are aware of this and keep it in mind when reviewing MRs.
Questions
- Would it make sense to partition maintainers to subsets of the codebase? E.g., make Foundations members
CODEOWNERS
ofGlListbox
?
Edited by Mark Florian