We could release an empty version 0.1 that has Products.CMFPlone as requirement, and for the rest no code, no distribution.
We would pin the version in coredev.buildout 6.0, so it will end up on dist.plone.org for future releases.
Result: we can start telling add-on authors that they can depend on plone.classicui if their add-on is really a Classic UI one.
Downside might be that in CMFPlone or wherever, we cannot check for the presence of the plone.classicui package as a simple way of seeing if we have a Classic UI distribution. But I don't think we need that, and there would be other ways.
Products.CMFPloneas requirement, and for the rest no code, no distribution.coredev.buildout6.0, so it will end up on dist.plone.org for future releases.plone.classicuiif their add-on is really a Classic UI one.plone.classicuipackage as a simple way of seeing if we have a Classic UI distribution. But I don't think we need that, and there would be other ways.Opinions?