-
Notifications
You must be signed in to change notification settings - Fork 0
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
Package name/org #3
Comments
This package is a place holder for adding OpenSSH API (that's the goal and mentioned in the motivation section of the readme). Currently, I don't have time to expose those API, but since it is in the organization, anyone can opt-in for development. |
I'm really not a fan of this kind of land grab approach to package naming. But independent of that, even if this package had a beautiful implementation of the complete OpenSSH API, I don't think JuliaCrypto is the correct org for it, since it's not a low level cryptographic primitive. |
Since this package does not have the implementation it is not registered yet, so its name is free for everyone to use. Originally, @ViralBShah suggested that I should transfer this to this organization, and choose this name. |
Well, I think he's wrong ;). |
Unless there is a more appropriate organization, we can always have it under JuliaDocs. |
I don't mind being wrong. :-) |
As I mentioned on Slack, I don't think JuliaCrypto is the right place for this package as is. JuliaCrypto as an org provides cryptographic primitives which this does not do. I also don't think the package name is great, because it takes the OpenSSH name from a package that might want to expose the SSH capabilities in OpenSSH (though even that shouldn't go into JuliaCrypto). As it is, why not just add these capabilities to the Documenter package itself?
The text was updated successfully, but these errors were encountered: