GH-433: [License] Adding Apache 2.0 License and Copyrights to each file on the repo

[vibhatha]

This PR includes a script to include the License and Copyrights for the source files.

This PR closes #433

[gemini-code-assist]

Summary of Changes

Hello @vibhatha, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request focuses on adding and managing Apache 2.0 license headers across the OpenGIN repository. It introduces two new Python scripts to automate the process of adding license headers and managing them for different components. The PR also updates the .gitignore file to exclude the scripts' cache directory.

Highlights

• License Headers: This PR adds Apache 2.0 license headers to all relevant files in the repository.
• New Script: add_license_headers.py: Introduces a new Python script to automate the addition of license headers to files based on their extensions.
• New Script: manage_licenses.py: Introduces a management script to manage license headers for different OpenGIN components.
• .gitignore Update: The .gitignore file is updated to ignore the pycache directory within the scripts directory.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request adds Apache 2.0 license headers to numerous files across the repository and introduces two Python scripts, add_license_headers.py and manage_licenses.py, to automate this process. My review focuses on these new scripts. I've suggested improvements to make them more robust and user-friendly, such as enhancing the license detection logic, fixing a minor output typo, and making the script for managing licenses less dependent on the directory it's run from.

[vibhatha]

/gemini review

[gemini-code-assist]

Code Review

This pull request adds the Apache 2.0 license and copyright headers to numerous files across the repository, which is a great step for project clarity and compliance. It also introduces two new Python scripts, add_license_headers.py and manage_licenses.py, to automate this process. My review focuses on these new scripts, and I've provided some suggestions to improve their robustness and adherence to best practices, such as refining exception handling, improving the license detection logic, and making path resolution more reliable.