-
Notifications
You must be signed in to change notification settings - Fork 145
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
Update NOTICE.txt to include link to certifi source #1679
Conversation
@@ -1,2 +1,4 @@ | |||
connectors-py | |||
Elastic Python connectors |
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.
Not sure whether this is our official product name.
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.
This should be just the name of the repository, following our open-source guidelines (so connectors-python
). I subtly remember this discussion with @gtback but don't remember where it was
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.
According to the NOTICE.txt
requirement for single-licence repo, it should be the product name:
{Product Name}
Copyright 2012-2018 Elasticsearch B.V.
One example: https://github.com/elastic/elasticsearch-ruby/blob/main/NOTICE
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.
Ha didn't know, makes sense!
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.
It doesn't make a huge difference what goes there, but I would generally lean towards what we call the product , not the name of the repo, in the case that those two things are different. I think this is fine.
@@ -1,2 +1,4 @@ | |||
connectors-py | |||
Elastic Python connectors | |||
Copyright 2022 Elasticsearch B.V. |
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.
Should this be
Copyright 2022 Elasticsearch B.V. | |
Copyright 2022-2023 Elasticsearch B.V. |
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.
Probably just 2023?
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 didn't find any doc about this, but my understanding is it's a range from when the software was first developed to the current year. cc @elastic/open-source-wg
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.
Looks good, left a couple small nits.
@@ -1,2 +1,4 @@ | |||
connectors-py | |||
Elastic Python connectors |
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.
This should be just the name of the repository, following our open-source guidelines (so connectors-python
). I subtly remember this discussion with @gtback but don't remember where it was
@@ -1,2 +1,4 @@ | |||
connectors-py | |||
Elastic Python connectors | |||
Copyright 2022 Elasticsearch B.V. |
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.
Probably just 2023?
@gtback confirmed:
|
Connector service uses a transitive library certifi, which is under Mozilla Public License 2.0 (MPL 2.0). MPL 2.0 is in yellow list:
This PR adds the link to certifi source in NOTICE.txt
Checklists
Pre-Review Checklist
v7.13.2
,v7.14.0
,v8.0.0
)