Please add LICENSE file

[gunnarx]

trafficstars

Each source file has a header (good) indicating the copyright and license information, with a MIT style license text.

It is also customary to add a file named COPYING, or LICENSE (my preference), at the root of the directory

Please add the LICENSE file as soon as you can, and then @jeremiah ought to be able to give you a reference to some GENIVI "best practices" if there are any additional things to do.

[jeremiah]

Thanks Gunnar. In general we'd like a pretty standard 'README.md' in Markdown with information on how to install the software, copyright and license, as well as how to contribute and contact the maintainer. That covers the best practices. We've been a little lax about this but in 2018 we're going to tighten our policies somewhat so we'll likely spam you a little until we've met expected practice. No worries though, this is easy and lightweight and I'm happy to provide what you need.

[jeremiah]

Hi @aavulac -- anything I can do to help move these issues forward or identify a maintainer for this code?

[aavulac]

+Hao.

thanks, Chandra.

On Mar 2, 2018, at 8:52 AM, Jeremiah C. Foster <[email protected]mailto:[email protected]> wrote:

Hi @aavulachttps://github.com/aavulac -- anything I can do to help move these issues forward or identify a maintainer for this code?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/GENIVI/navigation-next/issues/1#issuecomment-369980529, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ASo0AJvS2Ma3sMAm52WJPb98whGKORfeks5taXi8gaJpZM4Rd3W3.

[gunnarx]

@aavulac (Chandra) - what does your comment mean?

Will "+Hao" give a notice to Hao? I mean in GitHub you normally have to write @, right? I guess I am not really understanding your method here - maybe you sent this via email, and also copied the text into here?

• Why did you copy the whole email into here. The text "You are receiving this because you were mentioned. " is not relevant for the conversation.
• Also, does Hao have a GitHub account?

[gunnarx]

Hello again

Also, does Hao have a GitHub account?

You didn't answer, but I can now see the answer through #4 that the account is @hsuntcs

The other comment was just a reaction on a way of communicating that felt unfamiliar to me. (Clear GitHub comments that are to the point, and using @ references is more familiar).

What is the progress on the request of this issue -- what help if any do you need? By the way, this topic is still assigned to aavulac. Based on the above comment, should it be reassigned to hsuntcs ?

[shayneoneill]

You really need to do this. Code on github without a clearly identified license is actually dangerous.

For an end user who uses it, if he misidentifies his rights he could get in terrible legal trouble. For the code owner, not specifying rights could end up meaning losing those rights, due to whats implied by uploading o github (and implications are as potent as explicit instructions if the implication is strong enough)

And depending on which juristiction you are in which of those is true is something lawyers will get paid a lot of money to fight over.

And both parties will end up poorer for it, well except the lawyers, of course.

[jeremiah]

There are license headers in many files so I don't know how dangerous this is, but having an overall declaration of license and copyright for the project is certainly a best practice.

For end users I believe it is pretty much caveat emptor given that there are statements that the code is provided as-is, declaiming all responsibility.

Lastly, I suppose that a good lawyer might have a case, but there will be little gained by any lawsuit because the point of this repo is a good faith effort to provide open source code as a demonstrator, not as an end user product. In short, what this project needs is a maintainer.