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

Would you donate the google-cloud-* crate names to Google? #343

Open
coryan opened this issue Jan 29, 2025 · 8 comments
Open

Would you donate the google-cloud-* crate names to Google? #343

coryan opened this issue Jan 29, 2025 · 8 comments

Comments

@coryan
Copy link

coryan commented Jan 29, 2025

I am one of the Google engineers working on the Cloud SDK for Rust. We were wondering if you would consider donating the google-cloud-* crate names. That would make the crate names more consistent with the SDKs for other languages.

We already have about 20 generated libraries, and we are planning to work on the more complex services that require hand-crafted clients (e.g. Storage, Spanner, Bigtable, BigQuery) too.

If the answer is yes, we can discuss how to make the transition as easy as possible to existing users.

@yoshidan
Copy link
Owner

yoshidan commented Feb 1, 2025

Hi coryan.
I' m grad to hear that you will finally launch the official SDK.
Many GCP users, including myself, have been waiting for it.
I will gladly donate my `google-cloud-* name.

@coryan
Copy link
Author

coryan commented Feb 1, 2025

Thank you very much. I personally appreciate it.

Do you have any thoughts on how to perform this transfer without disrupting current users too much? Maybe something like this:

  1. Create (if needed) a final release of the current packages.
  2. Create new releases of your packages under new names.
  3. Invite @codyoss and myself to become owners. We will add @googleapis/rust-cloud-sdk later.
  4. Create new releases of the current packages names, with empty contents and instructions on where to find their new home.

Does that sound Okay to you?

@coryan
Copy link
Author

coryan commented Feb 4, 2025

Hey, we looked at it in more detail and there is only one conflicting name (google-cloud-auth) between our current list of crates and what you have published. As such, we will start publishing all the crates that do not conflict with yours.

I think only two are going to be confusing: you have published google-cloud-kms and google-cloud-artifactregistry. Ours would be google-cloud-kms-v1 and google-cloud-artifactregistry-v1 (not published yet).

Please let us know if you think that would cause trouble for you.

@yoshidan
Copy link
Owner

yoshidan commented Feb 4, 2025

Sorry for the late reply.

Does that sound Okay to you?

LGTM.
I have not yet decided on a name for the new create, but plan to run 1, 2, and 3 by the end of this week.

@yoshidan
Copy link
Owner

yoshidan commented Feb 7, 2025

@coryan
@codyoss
I have completed steps 1, 2 and 3.
We have invited you to become an owner of crate on crates.io. Please check your notifications.

@coryan
Copy link
Author

coryan commented Feb 15, 2025

I just noticed we are using google-cloud-longrunning too. Could you transfer this one too? Or maybe you already did and I missed the invitation, in that case: do you mind resending it?

@yoshidan
Copy link
Owner

Now I sent the invitation for google-cloud-longrunning. Please confirm.

@coryan
Copy link
Author

coryan commented Feb 18, 2025

Confirmed, thanks for the quick response.

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

No branches or pull requests

2 participants