Hi general@incubator, The distribution guidelines [1] say packages published to NPM should be named `apache-<package>`, however, at KIE, we have a somewhat big set of packages that are published under these scopes: - @kie-tools/* - @kie-tools-core/* - @kie-tools-scripts/*
There are also some VS Code Extensions (which can't have a scope): - yard-vscode-extension - swf-vscode-extension - pmml-vscode-extension - dmn-vscode-extension - bpmn-vscode-extension - vscode-extension-kogito-bundle - vscode-extension-kie-ba-bundle - vscode-extension-dashbuilder-editor And a one-off package that is later then transformed into a Maven WebJar [2] (which can't have a scope either) - sonataflow-deployment-webapp Those do not conform with the guidelines, but have been published under these scopes/names for quite some time now, before KIE became a podling. My question is: Are we required to rename everything prior to releasing? Or are we able to pass a vote with the current package names? Asking because that's a substantial amount of work prior to releasing, and also because renaming everything would mean consumers would have to manually "migrate" to the new package names. Thanks a lot in advance! Regards, Tiago Bento [1] https://incubator.apache.org/guides/distribution.html#npm [2] https://www.webjars.org/ --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
