Skip to content

chore: add LICENSE and transfer PyPI ownership#20

Open
cusell-google wants to merge 5 commits intoUniversal-Commerce-Protocol:mainfrom
cusell-google:main
Open

chore: add LICENSE and transfer PyPI ownership#20
cusell-google wants to merge 5 commits intoUniversal-Commerce-Protocol:mainfrom
cusell-google:main

Conversation

@cusell-google
Copy link
Copy Markdown
Contributor

This PR adds a LICENSE and handles the transition of the PyPI package ownership as a temporary approach until we find a generic group or alias.

@gemini-code-assist
Copy link
Copy Markdown

Summary of Changes

Hello, I'm Gemini Code Assist1! 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 establishing proper licensing and updating package metadata for the UCP Python SDK. It ensures that the project explicitly states its Apache 2.0 license and prepares the package for better distribution and identification on PyPI by enriching its configuration with relevant classifiers and updating the primary author for ownership transfer purposes.

Highlights

  • License Addition: A LICENSE file has been added to the repository, specifying the Apache License, Version 2.0, and updating the copyright information to '2026 UCP Authors'.
  • PyPI Package Metadata Update: The pyproject.toml file has been updated to reference the newly added LICENSE file and include a comprehensive set of classifiers for better package discoverability on PyPI.
  • Ownership Transfer: The author in pyproject.toml has been updated from 'Florin Iucha' to 'Enric Cusell', facilitating the temporary transfer of PyPI package ownership as described in the PR description.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

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.

Footnotes

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

Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request adds a license file and updates the pyproject.toml with new metadata, including classifiers and a change of authorship. While the updates to pyproject.toml are beneficial, there is a significant issue in the LICENSE file. The copyright year has been set to 2026, a future date, which is legally incorrect and should be updated to the current year.

@cusell-google cusell-google marked this pull request as draft March 24, 2026 13:49
pyproject.toml Outdated
license = {file = "LICENSE"}
authors = [
{ name = "Florin Iucha", email = "fiucha@google.com" }
{ name = "Enric Cusell", email = "cusell@google.com" }
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Nit: could we get at least 1 more person for coverage?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

keeping Florin and adding myself. I'll update it further with another contributor.

@cusell-google cusell-google changed the title Add LICENSE to the UCP python sdk and transfer ownership chore: add LICENSE and transfer PyPI ownership Mar 24, 2026
@cusell-google cusell-google marked this pull request as ready for review March 24, 2026 13:52
@ptiper ptiper requested a review from amithanda March 24, 2026 13:59
@cusell-google
Copy link
Copy Markdown
Contributor Author

Merged which had conflicts, updated with 2 authors: Federico D'Amato and Enric Cusell.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants