[ 
https://issues.apache.org/jira/browse/HDDS-424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16611078#comment-16611078
 ] 

Anu Engineer commented on HDDS-424:
-----------------------------------

First and foremost, Bikeshedding feedback:
 # Should we use <noun> <verb> or <verb> <noun>
 # 
||Noun||Verb|| ||Verb||Noun||
|volume |create| |create|volume|
|volume|list| |list|volume|
|volume|update| |update|volume|
|volume|info| |info|volume|
|bucket|create| |create|bucket|
|bucket|update| |update|bucket|
|key|put| |put|key|
|key|get| |get|key|

To me it feels more natural to do <verb> <noun> I am sure it is influenced by 
the languages that I speak, so it is just a linguistic preference. Just wanted 
to flag it.

End of BikeShedding. 

Feel free to ignore this feedback, as I said this not really based on 
quantitative measurements. To me it feels more natural to say <verb> <noun>. 

> Consolidate ozone oz parameters to use GNU convention
> -----------------------------------------------------
>
>                 Key: HDDS-424
>                 URL: https://issues.apache.org/jira/browse/HDDS-424
>             Project: Hadoop Distributed Data Store
>          Issue Type: Bug
>          Components: Ozone CLI
>            Reporter: Elek, Marton
>            Assignee: Elek, Marton
>            Priority: Major
>             Fix For: 0.2.1
>
>         Attachments: HDDS-424-ozone-0.2.001.patch
>
>
> In the common linux commands the convention is
> 1. avoid to use camelCase argument/flags
> 2. use double dash with words (--user) and singla dash with letters (-u) 
> I propose to modify ozone oz with:
> * Adding a second dash for all the word flags
> * Use 'key get', 'key info' instead of -infoKey
> * Define the input/output file name as a second argument instead of 
> --file/-file as it's always required



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to