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

Initial github setup #1

Merged
merged 3 commits into from
Nov 10, 2023
Merged

Initial github setup #1

merged 3 commits into from
Nov 10, 2023

Conversation

jlordiales
Copy link
Collaborator

  • Added initial markdown files
  • Added protobuf spec and generated Go types

@jlordiales jlordiales requested a review from a team November 10, 2023 22:32
Copy link
Collaborator

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

Copy link
Collaborator Author

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

Copy link
Collaborator

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

Copy link
Collaborator

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

Copy link
Collaborator Author

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

Copy link
Collaborator

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?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

// * 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
Copy link
Collaborator

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?

@jlordiales jlordiales merged commit bed3cb2 into main Nov 10, 2023
3 checks passed
@jlordiales jlordiales deleted the gh-setup branch November 10, 2023 23:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants