diff options
| author | CoprDistGit <infra@openeuler.org> | 2023-04-12 06:57:33 +0000 |
|---|---|---|
| committer | CoprDistGit <infra@openeuler.org> | 2023-04-12 06:57:33 +0000 |
| commit | 13b4a61ed5474ac3dd3cc2857e0f5d507f3fbd7e (patch) | |
| tree | 8e7e11f5995135165140a3fe850787b6037bbdf7 | |
| parent | 5e450986306ef276e3d7a6afd6dbc3df274d28fd (diff) | |
automatic import of python-kedro-telemetryopeneuler20.03
| -rw-r--r-- | .gitignore | 1 | ||||
| -rw-r--r-- | python-kedro-telemetry.spec | 314 | ||||
| -rw-r--r-- | sources | 1 |
3 files changed, 316 insertions, 0 deletions
@@ -0,0 +1 @@ +/kedro-telemetry-0.2.4.tar.gz diff --git a/python-kedro-telemetry.spec b/python-kedro-telemetry.spec new file mode 100644 index 0000000..7c1072a --- /dev/null +++ b/python-kedro-telemetry.spec @@ -0,0 +1,314 @@ +%global _empty_manifest_terminate_build 0 +Name: python-kedro-telemetry +Version: 0.2.4 +Release: 1 +Summary: Kedro-Telemetry +License: Apache Software License (Apache 2.0) +URL: https://github.com/kedro-org/kedro-plugins/tree/main/kedro-telemetry +Source0: https://mirrors.nju.edu.cn/pypi/web/packages/65/7a/4f8f96df64cb13d81586e901f8dfed33d97d0125e79562fe64e13e20b0ad/kedro-telemetry-0.2.4.tar.gz +BuildArch: noarch + +Requires: python3-kedro +Requires: python3-requests + +%description +# Kedro-Telemetry + +[](https://pypi.org/project/kedro-telemetry/) +[](https://pypi.org/project/kedro-telemetry/) +[](https://opensource.org/licenses/Apache-2.0) +[](https://github.com/ambv/black) + +## Introduction + +To find out how Kedro's features are used, the [Kedro team](https://github.com/kedro-org/kedro) have created an opt-in Kedro-Telemetry [plugin](https://kedro.readthedocs.io/en/stable/07_extend_kedro/04_plugins.html) to gather anonymised (before being sent across the internet) and aggregated usage analytics. + +The data it gathers will help drive future development of Kedro because we can understand how the product is being used. + +## Why is my data being collected? + +Telemetry data is made available to [project maintainers of the Kedro Project](https://kedro.readthedocs.io/en/stable/faq/faq.html#who-maintains-kedro). The purpose of providing this information is to provide metrics to the maintainers on how Kedro is used. This data helps inform future product development because we can better understand if certain features are having traction with our users. We want to make sure that Kedro is as streamlined as possible and it is difficult to do this without usage analytics. + + +## What about my personal data? + +The Kedro Project’s telemetry has been reviewed and approved under the [Telemetry Data Collection and Usage Policy](https://lfprojects.org/policies/telemetry-data-policy/) of LF Projects, LLC. + + +## What data is being collected? + +We process your hashed hostname and hashed computer username, which both is pseudonymized information that indirectly relates to you personally. Besides the hashed host and username, we collect the following project-related information. Again, we rely on your consent to do so: + +|Description|Example Input|What we receive| +|-|-|-| +|CLI command (masked arguments)|`kedro run --pipeline=ds --env=test`|`kedro run --pipeline ***** --env *****`| +|_(Hashed)_ Package name|my-project|1c7cd944c28cd888904f3efc2345198507...| +|_(Hashed)_ Project name|my_project|a6392d359362dc9827cf8688c9d634520e...| +|`kedro` project version|0.17.6|0.17.6| +|`kedro-telemetry` version|0.1.2|0.1.2| +|Python version|3.8.10 (default, Jun 2 2021, 10:49:15)|3.8.10 (default, Jun 2 2021, 10:49:15)| +|Operating system used|darwin|darwin| + +## How do I consent to the use of Kedro-Telemetry? + +Kedro-Telemetry is a Python plugin. To install it: + +```console +pip install kedro-telemetry +``` + +> _Note:_ If you are using an official [Kedro project template](https://kedro.readthedocs.io/en/stable/02_get_started/06_starters.html) then `kedro-telemetry` is included in the [project-level `requirements.txt`](https://kedro.readthedocs.io/en/stable/04_kedro_project_setup/01_dependencies.html#kedro-install) of the starter. `kedro-telemetry` is activated after you have a created a new project with a [Kedro project template](https://kedro.readthedocs.io/en/stable/02_get_started/06_starters.html) and have run `kedro install` from the terminal. + +When you next run the Kedro CLI you will be asked for consent to share usage analytics data for the purposes explained in the privacy notice, and a `.telemetry` YAML file will be created in the project root directory. The variable `consent` will be set according to your choice in the file, e.g. if you consent: + +```yaml +consent: true +``` + +>*Note:* The `.telemetry` file should not be committed to `git` or packaged in deployment. In `kedro>=0.17.4` the file is git-ignored. + +## How do I withdraw consent? + +To withdraw consent, you can change the `consent` variable to `false` in `.telemetry` YAML by editing the file in the following way: + +```yaml +consent: false +``` + +Or you can uninstall the plugin: + +```console +pip uninstall kedro-telemetry +``` + +## What happens when I withdraw consent? + +Data will only be collected if consent is given. Otherwise, if consent was explicitly denied or withdrawn, the message below will be printed out on every Kedro CLI invocation. If you explicitly deny consent from the beginning, no data will be collected. If you withdraw consent later, the processing of data will be stopped from that moment on. + +``` +Kedro-Telemetry is installed, but you have opted out of sharing usage analytics so none will be collected. +``` + +## How is the data collected + +Kedro-Telemetry uses [`pluggy`](https://pypi.org/project/pluggy/) hooks and [`requests`](https://pypi.org/project/requests/) to send data to [Heap Analytics](https://heap.io/). Project maintainers have access to the data and can create dashboards that show adoption and feature usage. + + +%package -n python3-kedro-telemetry +Summary: Kedro-Telemetry +Provides: python-kedro-telemetry +BuildRequires: python3-devel +BuildRequires: python3-setuptools +BuildRequires: python3-pip +%description -n python3-kedro-telemetry +# Kedro-Telemetry + +[](https://pypi.org/project/kedro-telemetry/) +[](https://pypi.org/project/kedro-telemetry/) +[](https://opensource.org/licenses/Apache-2.0) +[](https://github.com/ambv/black) + +## Introduction + +To find out how Kedro's features are used, the [Kedro team](https://github.com/kedro-org/kedro) have created an opt-in Kedro-Telemetry [plugin](https://kedro.readthedocs.io/en/stable/07_extend_kedro/04_plugins.html) to gather anonymised (before being sent across the internet) and aggregated usage analytics. + +The data it gathers will help drive future development of Kedro because we can understand how the product is being used. + +## Why is my data being collected? + +Telemetry data is made available to [project maintainers of the Kedro Project](https://kedro.readthedocs.io/en/stable/faq/faq.html#who-maintains-kedro). The purpose of providing this information is to provide metrics to the maintainers on how Kedro is used. This data helps inform future product development because we can better understand if certain features are having traction with our users. We want to make sure that Kedro is as streamlined as possible and it is difficult to do this without usage analytics. + + +## What about my personal data? + +The Kedro Project’s telemetry has been reviewed and approved under the [Telemetry Data Collection and Usage Policy](https://lfprojects.org/policies/telemetry-data-policy/) of LF Projects, LLC. + + +## What data is being collected? + +We process your hashed hostname and hashed computer username, which both is pseudonymized information that indirectly relates to you personally. Besides the hashed host and username, we collect the following project-related information. Again, we rely on your consent to do so: + +|Description|Example Input|What we receive| +|-|-|-| +|CLI command (masked arguments)|`kedro run --pipeline=ds --env=test`|`kedro run --pipeline ***** --env *****`| +|_(Hashed)_ Package name|my-project|1c7cd944c28cd888904f3efc2345198507...| +|_(Hashed)_ Project name|my_project|a6392d359362dc9827cf8688c9d634520e...| +|`kedro` project version|0.17.6|0.17.6| +|`kedro-telemetry` version|0.1.2|0.1.2| +|Python version|3.8.10 (default, Jun 2 2021, 10:49:15)|3.8.10 (default, Jun 2 2021, 10:49:15)| +|Operating system used|darwin|darwin| + +## How do I consent to the use of Kedro-Telemetry? + +Kedro-Telemetry is a Python plugin. To install it: + +```console +pip install kedro-telemetry +``` + +> _Note:_ If you are using an official [Kedro project template](https://kedro.readthedocs.io/en/stable/02_get_started/06_starters.html) then `kedro-telemetry` is included in the [project-level `requirements.txt`](https://kedro.readthedocs.io/en/stable/04_kedro_project_setup/01_dependencies.html#kedro-install) of the starter. `kedro-telemetry` is activated after you have a created a new project with a [Kedro project template](https://kedro.readthedocs.io/en/stable/02_get_started/06_starters.html) and have run `kedro install` from the terminal. + +When you next run the Kedro CLI you will be asked for consent to share usage analytics data for the purposes explained in the privacy notice, and a `.telemetry` YAML file will be created in the project root directory. The variable `consent` will be set according to your choice in the file, e.g. if you consent: + +```yaml +consent: true +``` + +>*Note:* The `.telemetry` file should not be committed to `git` or packaged in deployment. In `kedro>=0.17.4` the file is git-ignored. + +## How do I withdraw consent? + +To withdraw consent, you can change the `consent` variable to `false` in `.telemetry` YAML by editing the file in the following way: + +```yaml +consent: false +``` + +Or you can uninstall the plugin: + +```console +pip uninstall kedro-telemetry +``` + +## What happens when I withdraw consent? + +Data will only be collected if consent is given. Otherwise, if consent was explicitly denied or withdrawn, the message below will be printed out on every Kedro CLI invocation. If you explicitly deny consent from the beginning, no data will be collected. If you withdraw consent later, the processing of data will be stopped from that moment on. + +``` +Kedro-Telemetry is installed, but you have opted out of sharing usage analytics so none will be collected. +``` + +## How is the data collected + +Kedro-Telemetry uses [`pluggy`](https://pypi.org/project/pluggy/) hooks and [`requests`](https://pypi.org/project/requests/) to send data to [Heap Analytics](https://heap.io/). Project maintainers have access to the data and can create dashboards that show adoption and feature usage. + + +%package help +Summary: Development documents and examples for kedro-telemetry +Provides: python3-kedro-telemetry-doc +%description help +# Kedro-Telemetry + +[](https://pypi.org/project/kedro-telemetry/) +[](https://pypi.org/project/kedro-telemetry/) +[](https://opensource.org/licenses/Apache-2.0) +[](https://github.com/ambv/black) + +## Introduction + +To find out how Kedro's features are used, the [Kedro team](https://github.com/kedro-org/kedro) have created an opt-in Kedro-Telemetry [plugin](https://kedro.readthedocs.io/en/stable/07_extend_kedro/04_plugins.html) to gather anonymised (before being sent across the internet) and aggregated usage analytics. + +The data it gathers will help drive future development of Kedro because we can understand how the product is being used. + +## Why is my data being collected? + +Telemetry data is made available to [project maintainers of the Kedro Project](https://kedro.readthedocs.io/en/stable/faq/faq.html#who-maintains-kedro). The purpose of providing this information is to provide metrics to the maintainers on how Kedro is used. This data helps inform future product development because we can better understand if certain features are having traction with our users. We want to make sure that Kedro is as streamlined as possible and it is difficult to do this without usage analytics. + + +## What about my personal data? + +The Kedro Project’s telemetry has been reviewed and approved under the [Telemetry Data Collection and Usage Policy](https://lfprojects.org/policies/telemetry-data-policy/) of LF Projects, LLC. + + +## What data is being collected? + +We process your hashed hostname and hashed computer username, which both is pseudonymized information that indirectly relates to you personally. Besides the hashed host and username, we collect the following project-related information. Again, we rely on your consent to do so: + +|Description|Example Input|What we receive| +|-|-|-| +|CLI command (masked arguments)|`kedro run --pipeline=ds --env=test`|`kedro run --pipeline ***** --env *****`| +|_(Hashed)_ Package name|my-project|1c7cd944c28cd888904f3efc2345198507...| +|_(Hashed)_ Project name|my_project|a6392d359362dc9827cf8688c9d634520e...| +|`kedro` project version|0.17.6|0.17.6| +|`kedro-telemetry` version|0.1.2|0.1.2| +|Python version|3.8.10 (default, Jun 2 2021, 10:49:15)|3.8.10 (default, Jun 2 2021, 10:49:15)| +|Operating system used|darwin|darwin| + +## How do I consent to the use of Kedro-Telemetry? + +Kedro-Telemetry is a Python plugin. To install it: + +```console +pip install kedro-telemetry +``` + +> _Note:_ If you are using an official [Kedro project template](https://kedro.readthedocs.io/en/stable/02_get_started/06_starters.html) then `kedro-telemetry` is included in the [project-level `requirements.txt`](https://kedro.readthedocs.io/en/stable/04_kedro_project_setup/01_dependencies.html#kedro-install) of the starter. `kedro-telemetry` is activated after you have a created a new project with a [Kedro project template](https://kedro.readthedocs.io/en/stable/02_get_started/06_starters.html) and have run `kedro install` from the terminal. + +When you next run the Kedro CLI you will be asked for consent to share usage analytics data for the purposes explained in the privacy notice, and a `.telemetry` YAML file will be created in the project root directory. The variable `consent` will be set according to your choice in the file, e.g. if you consent: + +```yaml +consent: true +``` + +>*Note:* The `.telemetry` file should not be committed to `git` or packaged in deployment. In `kedro>=0.17.4` the file is git-ignored. + +## How do I withdraw consent? + +To withdraw consent, you can change the `consent` variable to `false` in `.telemetry` YAML by editing the file in the following way: + +```yaml +consent: false +``` + +Or you can uninstall the plugin: + +```console +pip uninstall kedro-telemetry +``` + +## What happens when I withdraw consent? + +Data will only be collected if consent is given. Otherwise, if consent was explicitly denied or withdrawn, the message below will be printed out on every Kedro CLI invocation. If you explicitly deny consent from the beginning, no data will be collected. If you withdraw consent later, the processing of data will be stopped from that moment on. + +``` +Kedro-Telemetry is installed, but you have opted out of sharing usage analytics so none will be collected. +``` + +## How is the data collected + +Kedro-Telemetry uses [`pluggy`](https://pypi.org/project/pluggy/) hooks and [`requests`](https://pypi.org/project/requests/) to send data to [Heap Analytics](https://heap.io/). Project maintainers have access to the data and can create dashboards that show adoption and feature usage. + + +%prep +%autosetup -n kedro-telemetry-0.2.4 + +%build +%py3_build + +%install +%py3_install +install -d -m755 %{buildroot}/%{_pkgdocdir} +if [ -d doc ]; then cp -arf doc %{buildroot}/%{_pkgdocdir}; fi +if [ -d docs ]; then cp -arf docs %{buildroot}/%{_pkgdocdir}; fi +if [ -d example ]; then cp -arf example %{buildroot}/%{_pkgdocdir}; fi +if [ -d examples ]; then cp -arf examples %{buildroot}/%{_pkgdocdir}; fi +pushd %{buildroot} +if [ -d usr/lib ]; then + find usr/lib -type f -printf "/%h/%f\n" >> filelist.lst +fi +if [ -d usr/lib64 ]; then + find usr/lib64 -type f -printf "/%h/%f\n" >> filelist.lst +fi +if [ -d usr/bin ]; then + find usr/bin -type f -printf "/%h/%f\n" >> filelist.lst +fi +if [ -d usr/sbin ]; then + find usr/sbin -type f -printf "/%h/%f\n" >> filelist.lst +fi +touch doclist.lst +if [ -d usr/share/man ]; then + find usr/share/man -type f -printf "/%h/%f.gz\n" >> doclist.lst +fi +popd +mv %{buildroot}/filelist.lst . +mv %{buildroot}/doclist.lst . + +%files -n python3-kedro-telemetry -f filelist.lst +%dir %{python3_sitelib}/* + +%files help -f doclist.lst +%{_docdir}/* + +%changelog +* Wed Apr 12 2023 Python_Bot <Python_Bot@openeuler.org> - 0.2.4-1 +- Package Spec generated @@ -0,0 +1 @@ +c335c738011ebf67fa0d916fe483e518 kedro-telemetry-0.2.4.tar.gz |