-
Notifications
You must be signed in to change notification settings - Fork 0
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
Initial github setup #1
Conversation
jlordiales
commented
Nov 10, 2023
- Added initial markdown files
- Added protobuf spec and generated Go types
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Given this is a third party, do we need to commit this to our own project?
I'm wondering if we could treat this as a library dependency instead
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not aware of a way to include proto files as a library dependency
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I had more the idea of doing what we do with the schemas in general. Having a dedicated place to just compile to different languages, in our case, go, and we import that library
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So we separate the host library from the underlying proto generation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
that feels like a lot of overhead considering the spec here is stable and won't change
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm mostly concerned of having code that belongs to a different org embedded here.
It's not about design, it's more about correctness of licences.
Are you better informed on the legalities here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
https://chat.openai.com/share/c11ac26a-7686-42ce-b579-428c651fdbd2
I think we should be fine
// * Copyright (c) 2015, 2018 Cirrus Link Solutions and others | ||
// * | ||
// * This program and the accompanying materials are made available under the | ||
// * terms of the Eclipse Public License 2.0 which is available at |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't know how this works. Can you commit to our Apache licensed software a different one?