Automating the world one-liner at a time…
With the recent changes in v2 to increase the visibility of the cmdlet design guidelines, we want to make sure we have a solid set of verbs on the approved verb list before we ship v2. We've already talked with a number of partners and customers and have made some recent changes to the verb list. In addition, we'd love to have feedback from our community on any holes you perceive we have in our current list of approved verbs.
To provide some context, here are the things we think about when deciding whether to add a new verb:
When suggesting a new verb, it's most helpful if you can include the following information in your suggestion:
For example, we recently approved Open and Close as new verbs in v2. Our internal discussions boiled down to the following:
Here is our current list of approved verbs:
Thanks,Dan HarmanProgram ManagerWindows PowerShell
Verb name: watch
Description: used to watch process in action and potentially alert if a certain even triggers
List of at least 5 significantly different applicable domains: file, account, process, copy, move, search, merge
List of at least 3 alternative verbs from the approved list: Test, Measure, Show
Pair with: unknown
How about Upgrade as this is a common lifecycle concept for administrators and the other terms (namely update and install) have different connotations that will potentially cause confusion.
Proposed upgrade verb in template format:
Verb name = Upgrade
Description = Upgrade is used to perform major version or minor patch level changes to a product, operating system, data, or files. Upgrade may not be reversible (See downgrade) depending on the inherit upgrade abilities and structure of the item being upgraded.
Category = Lifecycle
Domains = SQL Server, SharePoint, other server applications or even file types.
Alt verbs = Set, Update, Install
Reciprocal verb would be Downgrade
What about Encode/Decode (as in Encrypt/Decrypt or Base64, or BarCodes or Morse Code) ... what verb pair on there you would stand in for that?
We felt that the Convert verbs cover those scenarios well. The .NET Framework even follows this by hanging the Base64 methods on the Convert class.
Lee Holmes [MSFT]
Windows PowerShell Development