Feynman Zhou

@yizha1 Similar to my comments in https://github.com/notaryproject/notation/issues/304#issuecomment-1293593766, I suggest updating `Sign success` to `Sign succeeded`. This is more commonly used. Another question, Notation has supported two signature envelope formats (JWS...

Hi @binbin-li , I assume you are requesting to add `username/password` options to the following commands, right? - notation sign - notation verify - notation push - notation pull -...

@binbin-li Got you. The current implementation support specifying `username` & `password` for each command option, we can merge https://github.com/notaryproject/notation/pull/293 to make the spec consistent with implementation in alpha.3. From an...

cc @notaryproject/notation-code-reviewers

@yizha1 It looks better than before. I suggest updating `Verify success` to `Verify succeeded` and also updating `Verify failure` to `signature verification failed`. I have a few questions: 1. `enforcement...

Hi @SteveLasker @yizha1 @shizhMSFT @iamsamirzon I can start to work on this issue to add more examples to the CLI help doc in [these source files](https://github.com/notaryproject/notation/tree/main/cmd/notation) and format for arguments.

> Should be likely updated here: https://github.com/notaryproject/notation/blob/main/specs/notation-config.md @dtzar @yizha1 @notaryproject/notation-release-managers To avoid duplicate content maintenance work between the website and the code repo, I will migrate all user guides from...

@dtzar @yizha1 See https://github.com/notaryproject/notaryproject.dev/pull/80

> thanks @xmulligan , we are happy to have a meeting with @FeynmanZhou , and I'll let you known if there's any process. I am willing to help @pacoxu and...

/assign @zheng1