Welcome! This repository will be tracking the planning for digital and in-person Reactor events.
Reactors hold events both in-person and digitally. As of Summer 2020, all events are currently being help digitally. This is a combination of Global Live Twitch Streams and Local Live Teams Events. To better partner with the rest of the Azure Developer and Cloud Advocacy teams, we are aligning our topics to the Azure Developer Marketing Calendar.
In this README, you can find the following regarding events:
We have published an overall schedule of events.
Great! We often have openings for speakers! We do require 8-weeks advance notice of all new events to be able to market them properly. We manage our schedule via GitHub issues, so you can see our list of sessions where we are actively seeking help.
Our calendar is rarely set in stone, so we are always open to suggestions. If you have a topic which you think we should cover or see a session you'd like to deliver, please feel free to either comment on an issue or file one of your own!
Part of the mission of the Reactors is to create lasting content for developers to be able to refer back and continue their learning journeys. The customer facing content will reside on a number of Microsoft platforms, depending on the goal of that piece of content. This repository will track the development of new content regardless of its target platform destination.
Microsoft Learn is a learning platform that consists mainly of tutorial-like content. This is an ideal platform for Reactor content that is:
The goals of publishing content to Microsoft Learn are to:
Module or Learning Path Title | Duration | Reactor TPM and Author | Date Published | Technologies Referenced | Live Learn Link |
---|
This process, from the Reactor point of view, is still being defined. While reference material that will generally support Reactor events is of interested, we are also dedicated to creating content and experiences on the Microsoft Learn platform that is more interactive and could be used during instructor-led events. The best option at the moment is to create a new Learn Module Tracking Issue and follow the steps there!
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.opensource.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., status check, 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 opencode@microsoft.com 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.