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

Migrate jProtoc and Canteen to grpc-ecosystem #231

Open
5 of 17 tasks
rmichela opened this issue Apr 12, 2023 · 2 comments
Open
5 of 17 tasks

Migrate jProtoc and Canteen to grpc-ecosystem #231

rmichela opened this issue Apr 12, 2023 · 2 comments

Comments

@rmichela
Copy link
Collaborator

With the loss of a consistent release sponsor at Salesforce, it's time to move this repo to the grpc-ecosystem org.

Tasks to do:

  • Your project is currently hosted in a public repository.
  • Your project's license is the Apache license 2.0.
  • Your project doesn't depend on third party libraries with copyleft licenses such as AGPL and GPL.
  • Your project has a top-level README.md with the following information:
    • Project overview
    • How gRPC is used
    • A list of external project dependencies such as third-party libraries
    • Build instructions
    • Automated tests and test instructions
  • Ensure that all project contributors have signed Google's Contributor License Agreement, accepting that all license and patent rights are determined by the CLA under the Apache license.
  • Get written signoff from Salesforce
  • Once you've addressed all of the requirements listed above, complete and submit a gRPC Ecosystem Project Addition Request Form.
  • Update Maven coordinates
  • Update Java package names
  • Add an explicit module-info.java for Java >9 users
  • Secure access to new Maven repository at Sonatype
  • Release version 2.x
@lokesh-confluent
Copy link

Hi @rmichela, What's the latest update on the migration of this repo to grpc-ecosystem?

@rmichela
Copy link
Collaborator Author

I'm in contact with Google, and have gotten initial by in from there side. Salesforce is being more complicated because releasing a repo involves the loss of IP rights, so lawyers have to be involved. So, working on it.

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