winget-cli

Unnamed repository; edit this file 'description' to name the repository.
Log | Files | Refs | README | LICENSE

spec-template.md (1676B)

      1 ---
      2 author: <first-name> <last-name> <github-id>/<email>
      3 created on: <yyyy-mm-dd>
      4 last updated: <yyyy-mm-dd>
      5 issue id: <github issue id>
      6 ---
      7 
      8 # Spec Title
      9 
     10 [comment]: # Link to issue: "For [#1](https://github.com/microsoft/winget-cli/issues/1)"
     11 
     12 ## Abstract
     13 
     14 [comment]: # Outline what this spec describes
     15 
     16 ## Inspiration
     17 
     18 [comment]: # What were the drivers/inspiration behind the creation of this spec.
     19 
     20 ## Solution Design
     21 
     22 [comment]: # Outline the design of the solution. Feel free to include ASCII-art diagrams, etc.
     23 
     24 ## UI/UX Design
     25 
     26 [comment]: # What will this fix/feature look like? How will it affect the end user?
     27 
     28 ## Capabilities
     29 
     30 [comment]: # Discuss how the proposed fixes/features impact the following key considerations:
     31 
     32 ### Accessibility
     33 
     34 [comment]: # How will the proposed change impact accessibility for users of screen readers, assistive input devices, etc.
     35 
     36 ### Security
     37 
     38 [comment]: # How will the proposed change impact security?
     39 
     40 ### Reliability
     41 
     42 [comment]: # Will the proposed change improve reliability? If not, why make the change?
     43 
     44 ### Compatibility
     45 
     46 [comment]: # Will the proposed change break existing code/behaviors? If so, how, and is the breaking change "worth it"?
     47 
     48 ### Performance, Power, and Efficiency
     49 
     50 ## Potential Issues
     51 
     52 [comment]: # What are some of the things that might cause problems with the fixes/features proposed? Consider how the user might be negatively impacted.
     53 
     54 ## Future considerations
     55 
     56 [comment]: # What are some of the things that the fixes/features might unlock in the future? Does the implementation of this spec enable scenarios?
     57 
     58 ## Resources
     59 
     60 [comment]: # Be sure to add links to references, resources, footnotes, etc.