New package: Signatures v0.1.0

[JuliaRegistrator]

• Registering package: Signatures
• Repository: https://github.com/PeaceFounder/CryptoSignatures.jl
• Created by: @Akels
• Version: v0.1.0
• Commit: b61c26603bdd20055ee9d7390dbe84e7b4070208
• Reviewed by: @Akels
• Reference: PeaceFounder/CryptoSignatures.jl@b61c266#commitcomment-35770978

[github-actions]

Your new package pull request does not meet the following guidelines for auto-merging:

• The following dependencies do not have a compat entry that has an upper bound: Nettle, Paillier

Note that the guidelines are only required for the pull request to be merged automatically. However, it is strongly recommended to follow them, since otherwise the pull request needs to be manually reviewed and merged by a human.

---

If you want to prevent this pull request from being auto-merged, simply leave a comment. If you want to post a comment without blocking auto-merging, you must include the text [noblock] in your comment.

[fredrikekre]

Maybe ElectronicSignatures is a less generic and more descriptibe name? Just a suggestion.

Also, if you add the compatibiltiiy bounds this PR will be merged automatically.

[noblock]

[JanisErdmanis]

The name is indeed generic. Currently, I can think of two examples which user might think about what Signatures does:

• some processing with type signatures
• the electronic signatures from cryptography

On the other hand, I think the second option does dominate. Also, the library intends to cover the case of ring signatures which does not pop out in google easily when searches for electronic signatures.

[DilumAluthge]

How about:

• DigitalSignatures
• ElectronicSignatures
• CryptoSignatures
• CryptographicSignatures

Personally I like DigitalSignatures the best.

That being said, I don't mind Signatures as a name.

[noblock]

[JanisErdmanis]

I like DigitalSignatures and CryptoSingatures. I think I will change the name.

[github-actions]

Your new package pull request does not meet the following guidelines for auto-merging:

• Repo URL does not end with /name.jl.git, where name is the package name
• The following dependencies do not have a compat entry that has an upper bound: Nettle, Paillier

Note that the guidelines are only required for the pull request to be merged automatically. However, it is strongly recommended to follow them, since otherwise the pull request needs to be manually reviewed and merged by a human.

---

If you want to prevent this pull request from being auto-merged, simply leave a comment. If you want to post a comment without blocking auto-merging, you must include the text [noblock] in your comment.

[JanisErdmanis]

I just changed the name and updated pull request. Do I need to worry about:

Repo URL does not end with /name.jl.git, where name is the package name

[DilumAluthge]

This is due to a bug in Registrator.jl: JuliaRegistries/Registrator.jl#236

I will close this pull request. Can you re-trigger Registrator? This will open a new pull request with the correct pull request title corresponding to your new package name.

Also, if you can add compat entries (with upper bounds) for Nettle and Paillier, then your PR will be automerged.

[JanisErdmanis]

But I don't know the future. How can I add upper bounds?