As a developer I want to find odh webcomponents through npm packging system to easily incorporate it in my app with a standard packaging system

noi-techpark / odh-web-components

Common repository for all web-components created in line with the opendatahub project

0 stars 2 forks source link

As a developer I want to find odh webcomponents through npm packging system to easily incorporate it in my app with a standard packaging system #6

Open bertolla opened 5 years ago

bertolla commented 5 years ago

Advantages of scoped packages:

no naming issues
only scope members have access
we don’t have to switch the npm registry in order to install and publish the packages

bertolla commented 5 years ago

@ohnewein I would create scoped packages, which means we need an organization which will be used like a namespace by npm. I think we should either go with the org name like...

[ ] noi-ag
[ ] noi-techpark

...or if really needed we could use

[x] opendatahub.bz.it

NPM generally calls that namespace like the organization e.g. https://www.npmjs.com/package/@angular/http

ohnewein commented 5 years ago

I would prefer opendatahub.bz.it being it the project name, like angular is the project name and not the compan(y|ies) behind.

bertolla commented 5 years ago

Created pipeline for releasing existing web components. Waiting for approval of release.

bertolla commented 5 years ago

Can somebody @noi-techpark/ict-automation tell me which license we use for web components in particular for mobility-echarging? Currently in one of the 2 wc is stated MIT but I guess thats not what we want.

rcavaliere commented 5 years ago

@bertolla I would suggest the use the same license used for other web-apps we have developed, according to the license guidelines / overview provided some time ago by @ohnewein