The project names are not very constistent. E.g.
org.openhab.io.mqttembeddedbroker is named openHAB Add-ons :: Bundles :: IO :: MQTT Broker Moquette while org.openhab.io.homekit is named openHAB Add-ons :: Bundles :: Homekit and not openHAB Add-ons :: Bundles :: IO :: Homekitorg.openhab.extensionservice.marketplace is named openHAB Add-ons :: Extension Service :: Eclipse IoT Marketplace why is org.openhab.transform.exec named openHAB Add-ons :: Bundles :: Exec Transformation Service and not openHAB Add-ons :: Transformation Service :: ExecMy suggestion would be:
@openhab/2-x-add-ons-maintainers, WDYT?
I agree with your suggestions.
It would be nice if the projects in openhab-core and openhab-webui also use the same naming strategy. The openhab-core project has "Bundles" added to the respective project names. The openhab-webui doesn't but it does have bundles. Was this done intentionally @maggu2810 ?
The openHAB WebUI repository has not been migrated by me.
IMHO all repos should use the same scheme for directories, group IDs, artifact IDs, bundle names, etc.
So what would you prefer?
openHAB Add-ons :: Transformation Service :: ExecopenHAB Add-ons :: Bundles :: Transformation Service :: ExecopenHAB Add-ons :: Bundles :: Transformation Service ExecopenHAB Add-ons :: Bundles :: Exec Transformation ServiceI would vote for 2. We should also discuss what features should be named. We have similar "problems" there:
openhab-binding-airvisualnode - org.openhab.binding.airvisualnode (ok from my POV)openhab-misc-market - org.openhab.extensionservice.marketopenhab-misc-homekit - org.openhab.io.homekit openhab-io-javasound - org.openhab.io.javasoundopenhab-transport-modbus - org.openhab.transport.modbusopenhab-transformation-exec - org.openhab.transformation.execI would vote for 2 for the bundle name, too.
2
Most helpful comment
I would vote for 2 for the bundle name, too.