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

Update NOTICE.txt to include link to certifi source #1679

Merged
merged 2 commits into from
Sep 27, 2023

Conversation

wangch079
Copy link
Member

@wangch079 wangch079 commented Sep 25, 2023

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:

Incorporation of unmodified source or binaries into Elastic products is permitted, provided that the product's NOTICE file links to a URL providing the MPL-covered source code

This PR adds the link to certifi source in NOTICE.txt

Checklists

Pre-Review Checklist

  • this PR has a meaningful title
  • this PR links to all relevant github issues that it fixes or partially addresses
  • this PR has a thorough description
  • Added a label for each target release version (example: v7.13.2, v7.14.0, v8.0.0)

@@ -1,2 +1,4 @@
connectors-py
Elastic Python connectors
Copy link
Member Author

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.

Copy link
Member

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

Copy link
Member Author

@wangch079 wangch079 Sep 26, 2023

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

Copy link
Member

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!

Copy link
Member

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.
Copy link
Member Author

Choose a reason for hiding this comment

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

Should this be

Suggested change
Copyright 2022 Elasticsearch B.V.
Copyright 2022-2023 Elasticsearch B.V.

Copy link
Member

Choose a reason for hiding this comment

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

Probably just 2023?

Copy link
Member Author

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

Copy link
Member

@artem-shelkovnikov artem-shelkovnikov left a 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
Copy link
Member

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.
Copy link
Member

Choose a reason for hiding this comment

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

Probably just 2023?

@wangch079
Copy link
Member Author

wangch079 commented Sep 26, 2023

Have you checked this with our #open-source team?

@gtback confirmed:

I confirm that the PR you linked to provides appropriate NOTICE of the Source URL. Please make sure that the NOTICE.txt file is included in all distributions of the package (PyPI, Docker images, etc.).

@wangch079 wangch079 merged commit 0ea3995 into main Sep 27, 2023
@wangch079 wangch079 deleted the chenhui/update-NOTICE branch September 27, 2023 07:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants