Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

support license field in abp.yaml file #154

Open
matzew opened this issue Oct 26, 2017 · 3 comments
Open

support license field in abp.yaml file #154

matzew opened this issue Oct 26, 2017 · 3 comments

Comments

@matzew
Copy link
Contributor

matzew commented Oct 26, 2017

It would be nice if the apb.yaml would support (and being valid) a license: field, so that one could do:

version: 1.0
license: Apache 2.0
name: my-cool-apb
...
@matzew
Copy link
Contributor Author

matzew commented Oct 26, 2017

If there is interest, I am happy to help

@rthallisey
Copy link
Contributor

@matzew it's an interesting idea. Do you want to add a licence field because an apb could have a difference licence? Do you mind explaining in more detail how this can be used?

@matzew
Copy link
Contributor Author

matzew commented Oct 26, 2017

I, as a customer 😄, should be able to specify the license of my -apb container, in the metadata. I'd compare this a bit w/ package.json or pom.xml, where you also have option to define the license of your project.

Also, wouldn't it be interesting to see, in the catalog, if the service (and the apb) are under license XYZ?

In middleware (Red Hat) we recently added LICENSE.XML to a bunch of projects, that list all licenses of their dependencies. So if your offering (e.g. feedhenry/mcp-standalone), has a "dependency" to a bunch of APBs, we could use that metadata also to list the license of the -apb.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants