eclipse-thingweb / eclipse-thingweb/node-wot
[question] Naming convention for devices built with node-wot
- Dominant language
- TypeScript
- Stars
- 192
- Forks
- 100
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 6
Description
This is mostly to gather opinions:
We have a couple of devices built with node-wot that are for now on GitHub but we will publish them on npm soon. In a similar way to Node-RED packages always named `nodered-contrib-mypackage` (example https://www.npmjs.com/package/node-red-contrib-io-key), should we also set up a naming convention for node-wot? Here is one simple infrared sensor example: https://github.com/tum-esi/wot-sys/tree/master/Devices/nodewot-infrared-sensor-dobot
I have some ideas below but would like to hear the opinions of others:
1. `@node-wot/contrib/mypackage`: Not sure since `/contrib` after `@node-wot` makes me think that it is part of the node-wot main package and maintained by node-wot developers, which should not be the case
2. `@node-wot-contrib/mypackage`
3. `@node-wot-contrib-mypackage`
4. `node-wot-contrib-mypackage`: I find this one to be the closest to the way Node-RED does, since an `@node-wot` associates it with node-wot developers.
Looking forward to ideas/opinions :)
Contributor guide
Assessment
This issue has not been assessed yet.