⚠️ Deprecation & Archiving Notice ⚠️

Thank you for your support and contributions to ostc-docs.

This repository is now deprecated and will be archived soon.

• No further development, maintenance, or updates will be provided.
• Bug fixes, security patches, and feature enhancements are no longer planned.
• After archiving, this repository will remain available in read-only mode for reference.

We encourage users to explore alternative solutions, as this project will no longer be actively maintained.

For any questions, please refer to the existing documentation or community discussions.

---

ostc-docs

Documentation for the Open Source Technology Center (OSTC) team.

Please note that this is a public repository, and I'd like to keep it public so other public repositories can refer to sections of this repository. This avoids duplication of documentation, which helps avoids repository documentation becoming stale over time.

Experience dictates that this repository is useful for multiple groups. To maintain this, the very first section, Infrastructure Information, is dedicated to OSTC-specific information. All other sections are intended to be generally useful for everyone.

Please keep this in mind when adding documentation to this repository.

---

New to git? See Guidelines for development, which has useful links on how to use git.

---

1. Infrastructure Information
   1. Useful Network Resources
   2. Build Hosts
   3. Build System Dependencies
   4. Development Hosts
   5. Migrating from TFS
   6. Set up Hyper-V DNS configuration
   7. Installing git on UNIX/Linux
   8. Setting up Mac OS/X systems
2. Setup Instructions for Code Contributors
   1. Setting up SSH public/private keys
   2. Setting up git environment
   3. Guidelines for development
   4. Setting up a machine for build purposes
   5. Setting up PBUILD hosts
3. Workflow for Code Contributors
   1. Branching Strategy
   2. Workflow for Development
4. Administrative Information
   1. Tagging Releases
   2. Creating a Hotfix Release

---

Code of Conduct

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.