We face the challenge that we have to release an npm package and a PyPI package at the same time for this add-on (and for lots of other Plone add-ons in the future).
Here are our options:
Namespaces
JS: @kitconcept/volto-form-builder
PY: kitconcept.voltoformbuilder
JS: @plone/volto-form-builder
PY: plone.volto-form-builder
JS: @collective/volto-form-builder
PY: collective.voltoformbuilder
Pro
We keep the current Plone Python package convention
We keep namespaces which allows a clean separation and avoids naming collisions
Cons
The name of the packages differ and make it hard to remember
With Prefix
volto-form-builder
volto-form-builder
plone-form-builder
plone-form-builder
Pro
the name of both packages are identical, this makes it easy to
Cons
possible name conflicts -> unlikely if we use "volto" or "plone" as prefix
package name and Python import differ (volto-form-builder vs voltoformbuilder) -> Django does this as well
We face the challenge that we have to release an npm package and a PyPI package at the same time for this add-on (and for lots of other Plone add-ons in the future).
Here are our options:
Namespaces
JS: @kitconcept/volto-form-builder
PY: kitconcept.voltoformbuilder
JS: @plone/volto-form-builder
PY: plone.volto-form-builder
JS: @collective/volto-form-builder
PY: collective.voltoformbuilder
Pro
Cons
With Prefix
volto-form-builder
volto-form-builder
plone-form-builder
plone-form-builder
Pro
Cons