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

Copyright in README file? #274

Closed
erikbosch opened this issue Apr 28, 2021 · 3 comments
Closed

Copyright in README file? #274

erikbosch opened this issue Apr 28, 2021 · 3 comments

Comments

@erikbosch
Copy link
Collaborator

From a comment in w3c/automotive#379 it seems that the status/ambition of VSS can be misunderstood

It does show a solution of three particular car producers, or I am mistaken?

I guess this depends on that 3 OEMs are listed at the top of the README, and there is nothing that states that this is a joint activity managed by GENIVI (involving W3C as well) aiming for standardization, and not just a contribution from the 3 companies listed. Some thought that came to my mind:

  • Would it make sense to give a general introduction to VSS already in the README, to avoid the missunderstanding?
  • Which organizations shall be listed in the README? Only those that has changed the README, anyone that has contributed anything to the repository or none.
  • Compare with vss-tools where we have no copyright, would it makse sense to align the READMEs?
@gunnarx
Copy link
Contributor

gunnarx commented May 11, 2021

It is somewhat unusual to keep (C) statements in README and the interpretation could in theory be that it applies only to the README text itself, which we think is not the intention here.

Group consensus seems to be that it is not needed to have these statements in README, but companies may want to keep the intended information that companies hold copyright somewhere. We also said, independently of formal copyright, that keeping a section in the README to give credit to companies that have contributed might be useful.

As the overseer of the GENIVI repositories, I'll have to give this some thought and come back.

@danielwilms
Copy link
Collaborator

@danielwilms, check files WRT BMW (C)

@SebastianSchildt
Copy link
Collaborator

Can be closed, fixed in #291

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

4 participants