-
Notifications
You must be signed in to change notification settings - Fork 3
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
Will this work be merged to upstream plonky2 repo? #2
Comments
We are happy to do that, but I don't think the upstream repo will accept. |
Why not ? I think code needs little bit of cleanup and perhaps squash commits which don't have important commit message. Also instead of my_prove() it would be better to use prove_with_cuda() or some other better naming convention. |
I work with @vivekvpandya. We can try to help you work with upstream to get your code in, if you are interested. Btw, would you be willing to change the license to the one upstream uses? Why do you think upstream wouldn't want your code? |
Which upstream repo do you mean? |
The same where your PR was created. |
Yes, we had in mind helping you to contribute your code directly to the main plonky2 repository. Not to add a link in a readme somewhere. We've contributed to plonk2 before, and found them fairly welcoming. |
We can polish code for the merge. This project is actually supported by Side Labs. Do you mind if we add "Side Labs" somewhere for its early supporting. |
I don't mind, but we'd need to check with plonky2 folks what they think. |
@liangping are you guys still planning merging it upstream? |
Yes, but haven't worked on it much recently. We had some people join and leave. |
Thanks for open sourcing this work! Are there any future plans to merge upstream repo?
The text was updated successfully, but these errors were encountered: