The Windows Calculator app is a modern Windows app written in C++ that ships pre-installed with Windows. This repository contains in-progress and archived spec documents for new features in Microsoft/calculator.
Documents in this repo are used for features in development and are not intended to be up-to-date developer or user documentation. For product issues, bugs, and feature requests please go to Microsoft/calculator.
We welcome your contributions to the project, and we thank you for your interest in making Calculator better! We follow a user-centered process for developing features.
- DO provide feedback on active pull requests, which represent new features that are being reviewed
- DO provide feedback on spec documents in the
activefolder, which represent new features that are being worked on - DO NOT provide feedback on spec documents in the
archivefolder since those features have already been released - DO NOT submit pull requests that create new specs for ideas that do not have an associated approved feature pitch tracked in Microsoft/calculator. To propose a new feature, please follow the Calculator contribution process
-
Ensure that your pitch has been approved and moved into planning. When features enter this stage, a new working branch in this repo will be created:
feature/<feature> -
Create a new directory for your spec under the
activedirectory:/active/<feature> -
Write your spec following the spec template, leveraging relative links when referencing images or other assets in the directory
-
When your spec is ready for review, open a new pull request to merge your spec into the
masterbranch -
Once all feedback has been addressed and your spec has been merged into
master, your feature will move into implementation. -
After your feature ships, move your spec from
activetoarchive
Once there is a high-fidelity design which addresses the goals described in the original pitch, the Microsoft product team will review the spec and ensure all items on this checklist are addressed:
- Is there a high-fidelity design which gives reviewers a clear idea of how the feature will look and function when implemented?
- Has the plan been shared with the community and have others been given an opportunity to provide suggestions?
- Are Fluent design principles followed? If we do something which deviates from the guidelines, do we have a good reason?
- Does the design include provisions for all users and all cultures?
- Is it technically feasible to build this feature? Take a look at the "before committing" checklist and identify any issues which are likely to be blockers.
This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.microsoft.com.
When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.
Microsoft and any contributors grant you a license to the Microsoft documentation and other content in this repository under the Creative Commons Attribution 4.0 International Public License, see the LICENSE file, and grant you a license to any code in the repository under the MIT License, see the LICENSE-CODE file.
Microsoft, Windows, Microsoft Azure and/or other Microsoft products and services referenced in the documentation may be either trademarks or registered trademarks of Microsoft in the United States and/or other countries. The licenses for this project do not grant you rights to use any Microsoft names, logos, or trademarks. Microsoft's general trademark guidelines can be found at http://go.microsoft.com/fwlink/?LinkID=254653.
Privacy information can be found at https://privacy.microsoft.com/en-us/
Microsoft and any contributors reserve all other rights, whether under their respective copyrights, patents, or trademarks, whether by implication, estoppel or otherwise.