Core of kirigami-addons should be a framework
from teams/frameworks-devs/kf6-workboard#59
Kirigami Addons
- mixes production and experimental components, strict API guarantees are a problem for the latter
- split repo into two? with the production part going into KF (kirigami-addons) and the experimental part remaining as is right now (kirigami-labs)
- Plasma currently depends on components that are production-ready
- priorize the components currently needed by Plasma for review and move to KF
The conclusion was that for plasma to have any dependence on it, the components it depends from should be a framework, with that release schedule and the same quality, testing and stability promises.
Some classes are definitely ready, some aren't.
The idea is to have in the repository called kirigami-addons only the classes that are ready (in the beginning very sparse, empty-ish) and having everything else in a kirigami labs repository, which would continue probably having its on-demand release (it then could have in itself have several levels of readyness), with component being moved over when ready, hopefully most/all of them.