Merge pull request #350 from cyz/cyz-patch-1

updating contoso real estate workshop

CODE_OF_CONDUCT.md

@@ -1,9 +1,9 @@
-# Microsoft Open Source Code of Conduct
-
-This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/).
-
-Resources:
-
-- [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/)
-- [Microsoft Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/)
-- Contact [opencode@microsoft.com](mailto:opencode@microsoft.com) with questions or concerns
+# Microsoft Open Source Code of Conduct
+
+This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/).
+
+Resources:
+
+- [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/)
+- [Microsoft Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/)
+- Contact [opencode@microsoft.com](mailto:opencode@microsoft.com) with questions or concerns

LICENSE

@@ -1,21 +1,21 @@
-    MIT License
-
-    Copyright (c) Microsoft Corporation.
-
-    Permission is hereby granted, free of charge, to any person obtaining a copy
-    of this software and associated documentation files (the "Software"), to deal
-    in the Software without restriction, including without limitation the rights
-    to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-    copies of the Software, and to permit persons to whom the Software is
-    furnished to do so, subject to the following conditions:
-
-    The above copyright notice and this permission notice shall be included in all
-    copies or substantial portions of the Software.
-
-    THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-    IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-    FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-    AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-    LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-    OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-    SOFTWARE
+    MIT License
+
+    Copyright (c) Microsoft Corporation.
+
+    Permission is hereby granted, free of charge, to any person obtaining a copy
+    of this software and associated documentation files (the "Software"), to deal
+    in the Software without restriction, including without limitation the rights
+    to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+    copies of the Software, and to permit persons to whom the Software is
+    furnished to do so, subject to the following conditions:
+
+    The above copyright notice and this permission notice shall be included in all
+    copies or substantial portions of the Software.
+
+    THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+    IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+    FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+    AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+    LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+    OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+    SOFTWARE

SECURITY.md

@@ -1,41 +1,41 @@
-<!-- BEGIN MICROSOFT SECURITY.MD V0.0.3 BLOCK -->
-
-## Security
-
-Microsoft takes the security of our software products and services seriously, which includes all source code repositories managed through our GitHub organizations, which include [Microsoft](https://github.com/Microsoft), [Azure](https://github.com/Azure), [DotNet](https://github.com/dotnet), [AspNet](https://github.com/aspnet), [Xamarin](https://github.com/xamarin), and [our GitHub organizations](https://opensource.microsoft.com/).
-
-If you believe you have found a security vulnerability in any Microsoft-owned repository that meets Microsoft's [Microsoft's definition of a security vulnerability](https://docs.microsoft.com/previous-versions/tn-archive/cc751383(v=technet.10)) of a security vulnerability, please report it to us as described below.
-
-## Reporting Security Issues
-
-**Please do not report security vulnerabilities through public GitHub issues.**
-
-Instead, please report them to the Microsoft Security Response Center (MSRC) at [https://msrc.microsoft.com/create-report](https://msrc.microsoft.com/create-report).
-
-If you prefer to submit without logging in, send email to [secure@microsoft.com](mailto:secure@microsoft.com).  If possible, encrypt your message with our PGP key; please download it from the the [Microsoft Security Response Center PGP Key page](https://www.microsoft.com/msrc/pgp-key-msrc).
-
-You should receive a response within 24 hours. If for some reason you do not, please follow up via email to ensure we received your original message. Additional information can be found at [microsoft.com/msrc](https://www.microsoft.com/msrc).
-
-Please include the requested information listed below (as much as you can provide) to help us better understand the nature and scope of the possible issue:
-
-  * Type of issue (e.g. buffer overflow, SQL injection, cross-site scripting, etc.)
-  * Full paths of source file(s) related to the manifestation of the issue
-  * The location of the affected source code (tag/branch/commit or direct URL)
-  * Any special configuration required to reproduce the issue
-  * Step-by-step instructions to reproduce the issue
-  * Proof-of-concept or exploit code (if possible)
-  * Impact of the issue, including how an attacker might exploit the issue
-
-This information will help us triage your report more quickly.
-
-If you are reporting for a bug bounty, more complete reports can contribute to a higher bounty award. Please visit our [Microsoft Bug Bounty Program](https://microsoft.com/msrc/bounty) page for more details about our active programs.
-
-## Preferred Languages
-
-We prefer all communications to be in English.
-
-## Policy
-
-Microsoft follows the principle of [Coordinated Vulnerability Disclosure](https://www.microsoft.com/msrc/cvd).
-
-<!-- END MICROSOFT SECURITY.MD BLOCK -->
+<!-- BEGIN MICROSOFT SECURITY.MD V0.0.3 BLOCK -->
+
+## Security
+
+Microsoft takes the security of our software products and services seriously, which includes all source code repositories managed through our GitHub organizations, which include [Microsoft](https://github.com/Microsoft), [Azure](https://github.com/Azure), [DotNet](https://github.com/dotnet), [AspNet](https://github.com/aspnet), [Xamarin](https://github.com/xamarin), and [our GitHub organizations](https://opensource.microsoft.com/).
+
+If you believe you have found a security vulnerability in any Microsoft-owned repository that meets Microsoft's [Microsoft's definition of a security vulnerability](https://docs.microsoft.com/previous-versions/tn-archive/cc751383(v=technet.10)) of a security vulnerability, please report it to us as described below.
+
+## Reporting Security Issues
+
+**Please do not report security vulnerabilities through public GitHub issues.**
+
+Instead, please report them to the Microsoft Security Response Center (MSRC) at [https://msrc.microsoft.com/create-report](https://msrc.microsoft.com/create-report).
+
+If you prefer to submit without logging in, send email to [secure@microsoft.com](mailto:secure@microsoft.com).  If possible, encrypt your message with our PGP key; please download it from the the [Microsoft Security Response Center PGP Key page](https://www.microsoft.com/msrc/pgp-key-msrc).
+
+You should receive a response within 24 hours. If for some reason you do not, please follow up via email to ensure we received your original message. Additional information can be found at [microsoft.com/msrc](https://www.microsoft.com/msrc).
+
+Please include the requested information listed below (as much as you can provide) to help us better understand the nature and scope of the possible issue:
+
+  * Type of issue (e.g. buffer overflow, SQL injection, cross-site scripting, etc.)
+  * Full paths of source file(s) related to the manifestation of the issue
+  * The location of the affected source code (tag/branch/commit or direct URL)
+  * Any special configuration required to reproduce the issue
+  * Step-by-step instructions to reproduce the issue
+  * Proof-of-concept or exploit code (if possible)
+  * Impact of the issue, including how an attacker might exploit the issue
+
+This information will help us triage your report more quickly.
+
+If you are reporting for a bug bounty, more complete reports can contribute to a higher bounty award. Please visit our [Microsoft Bug Bounty Program](https://microsoft.com/msrc/bounty) page for more details about our active programs.
+
+## Preferred Languages
+
+We prefer all communications to be in English.
+
+## Policy
+
+Microsoft follows the principle of [Coordinated Vulnerability Disclosure](https://www.microsoft.com/msrc/cvd).
+
+<!-- END MICROSOFT SECURITY.MD BLOCK -->

devops-devtools/contoso-real-estate/README.md

@@ -1,17 +1,18 @@
-# Community Event-In-A-Box
-
-The event organization guide is a step-by-step guide to help you organize a successful event. It includes tips on how to find speakers, how to promote your event, and more.
-
-You will also find a list of presentations and workshops that you can use to present at your event. These presentations and workshops are based on the **Contoso Real Estate** project. This is a great opportunity to share knowledge about cloud-native applications within your community!
-
-## 📚 Event organization
-Organizing an event is always an adventure, and to assist you, we have created a guide with tips and suggestions to help you organize a successful event.
-
-### Get Started
-
-| Resource      | Description |
-| ----------- | ----------- |
-| **[Event Checklist](event-organization/README.md)**      | A quick guide for community leaders, with tips on speakers, promotion, and more. |
-| **Code of Conduct**   | A CoC is important to ensure that all participants feel safe and comfortable during the event. Be inspired by the [Reactor Code of Conduct](https://developer.microsoft.com/reactor/CodeOfConduct/).       |
-| **[Creative](event-organization/Creative)**   | Assets for promotion on social media, YouTube and Meetup      |
-| **Content**   | [Presentation](content/presentation) and [workshop](content) to build an API with Azure Functions and Deploy the `portal` project using Azure Static Web App CLI      |
+# Community Event-In-A-Box
+
+The event organization guide is a step-by-step guide to help you organize a successful event. It includes tips on how to find speakers, how to promote your event, and more.
+
+You will also find a list of presentations and workshops that you can use to present at your event. These presentations and workshops are based on the **Contoso Real Estate** project. This is a great opportunity to share knowledge about cloud-native applications within your community!
+
+## 📚 Event organization
+Organizing an event is always an adventure, and to assist you, we have created a guide with tips and suggestions to help you organize a successful event.
+
+### Get Started
+
+| Resource      | Description |
+| ----------- | ----------- |
+| **[Event Checklist](event-organization/README.md)**      | A quick guide for community leaders, with tips on speakers, promotion, and more. |
+| **Code of Conduct**   | A CoC is important to ensure that all participants feel safe and comfortable during the event. Be inspired by the [Reactor Code of Conduct](https://developer.microsoft.com/reactor/CodeOfConduct/).       |
+| **[Creative](event-organization/Creative)**   | Assets for promotion on social media, YouTube and Meetup      |
+| **[Presentations](content/presentations)**   | <ul><li>Opening session: Intro do Hack Together (`file: intro-hack-together`)</li><li>Build your front-end and deploy to Azure (`file: intro-contoso-real-state-codespaces`)</li></ul>      |
+| **[Workshop](content)**   | This workshop is a step-by-step to:<ul> <li>Analyze the portal project</li><li>Undestand the Azure Static Web App CLI</li><li>Deploy on Azure Static Web App </li>    |

devops-devtools/contoso-real-estate/event-organization/README.md

@@ -1,38 +1,38 @@
-# Event Guide
-
-A quick guide for community leaders, with tips on speaker sourcing, event promotion, and more.
-
-## Start organizing your event
-
-### Basic definition:
-- Type of content: presentations or workshop
-- Ideal format for your community: online, hybrid or in-person
-- Date and time
-- Duration: 2-3 hours
-     - If you opt for an online event, consider breaking the event into 30-45 minute sessions.
-     - For in-person event, consider a 15-minute break for participants to network.
-- Theme: all events should be related to the **Contoso Real Estate** project and its content packs. You can choose to focus on one or more themes from the project's content pack.
-- Prerequisites: If you decide host an event with a workshop, consider the prerequisites for your attendees. For example, if you are going to host a workshop on Azure Functions, you can ask your attendees to create an Azure account before the event.
-
-### Promotion
-- Use our templates to create assets and promote your event. In the [Creative](/Creative) folder, you will find the downloadable templates:
-     - Event cover for Meetup
-     - Card for speakers
-     - Thumbnail for YouTube
-     - Power Point template
-- Create the registration link for your event, using [Meetup](https://www.meetup.com/pt-BR/), Microsoft Forms or another platform of your choice.
-- Remember to include a code of conduct in your event. A CoC is important to ensure that all participants feel safe and comfortable during the event. Be inspired by the [Reactor Code of Conduct](https://developer.microsoft.com/en-us/reactor/CodeOfConduct/).
-- Connect with local communities, universities, schools, to promote registration for your event.
-- 5 and 2 days prior to the event, send a reminder email to your attendees list and encourage them to share the event with their friends and co-workers.
-- On the day of the event, send a final reminder with link to access the online event or tips to find the location (if in-person).
-
-### Finding speakers
-If you want to find speakers for your event, you can search for members of Microsoft's community programs:
-
-- [Find an MVP (Most Valuable Professional)](https://mvp.microsoft.com/pt-br/MvpSearch)
-- [Find an MSLA (Microsoft Learn Student Ambassador)](https://studentambassadors.microsoft.com/pt-BR/search?target=Profile)
-
-Tip: in your invite, talk about the **Enterprise-grade Reference Architecture for JavaScript** project and share the content you want the speaker to present.
-
-## Content
-In this repository you will find presentations and workshops that you can use in your event. Navigate to the [content](/content) folder to find the content packs for each project.
+# Event Guide
+
+A quick guide for community leaders, with tips on speaker sourcing, event promotion, and more.
+
+## Start organizing your event
+
+### Basic definition:
+- Type of content: presentations or workshop
+- Ideal format for your community: online, hybrid or in-person
+- Date and time
+- Duration: 2-3 hours
+     - If you opt for an online event, consider breaking the event into 30-45 minute sessions.
+     - For in-person event, consider a 15-minute break for participants to network.
+- Theme: all events should be related to the **Contoso Real Estate** project and its content packs. You can choose to focus on one or more themes from the project's content pack.
+- Prerequisites: If you decide host an event with a workshop, consider the prerequisites for your attendees. For example, if you are going to host a workshop on Azure Functions, you can ask your attendees to create an Azure account before the event.
+
+### Promotion
+- Use our templates to create assets and promote your event. In the [Creative](/Creative) folder, you will find the downloadable templates:
+     - Event cover for Meetup
+     - Card for speakers
+     - Thumbnail for YouTube
+     - Power Point template
+- Create the registration link for your event, using [Meetup](https://www.meetup.com/pt-BR/), Microsoft Forms or another platform of your choice.
+- Remember to include a code of conduct in your event. A CoC is important to ensure that all participants feel safe and comfortable during the event. Be inspired by the [Reactor Code of Conduct](https://developer.microsoft.com/en-us/reactor/CodeOfConduct/).
+- Connect with local communities, universities, schools, to promote registration for your event.
+- 5 and 2 days prior to the event, send a reminder email to your attendees list and encourage them to share the event with their friends and co-workers.
+- On the day of the event, send a final reminder with link to access the online event or tips to find the location (if in-person).
+
+### Finding speakers
+If you want to find speakers for your event, you can search for members of Microsoft's community programs:
+
+- [Find an MVP (Most Valuable Professional)](https://mvp.microsoft.com/pt-br/MvpSearch)
+- [Find an MSLA (Microsoft Learn Student Ambassador)](https://studentambassadors.microsoft.com/pt-BR/search?target=Profile)
+
+Tip: in your invite, talk about the **Enterprise-grade Reference Architecture for JavaScript** project and share the content you want the speaker to present.
+
+## Content
+In this repository you will find presentations and workshops that you can use in your event. Navigate to the [content](/content) folder to find the content packs for each project.

online-event-resources/emerging-tech/Bots/Bots101/index.js

@@ -1,62 +1,62 @@
-const fetch = require('node-fetch');
-const restify = require('restify');
-
-const server = restify.createServer();
-server.listen(process.env.PORT || process.env.port || 3978, () => {
-    console.log('server up!!');
-});
-
-const botbuilder = require('botbuilder');
-const { BotAdapter } = require('botbuilder');
-const adapter = new botbuilder.BotFrameworkAdapter();
-
-adapter.onTurnError = (context, error) => { console.log(error); };
-
-// it's all about one route
-server.post('/api/messages', (req, res) => {
-    adapter.processActivity(req, res, async (context) => {
-        // find what the user said
-        switch (context.activity.type) {
-            case 'message':
-                await handleMessage(context);
-                break;
-            case 'conversationUpdate':
-                // was a member added?
-                await welcomeMessage(context);
-                break;
-        }
-    });
-});
-
-async function welcomeMessage(context) {
-    if (context.activity.membersAdded) {
-        await context.sendActivity('I can search GitHub to find users for you.');
-        await context.sendActivity('Just tell me what you want to search for!');
-    }
-}
-
-async function handleMessage(context) {
-    await context.sendActivity({
-        type: 'typing'
-    });
-
-    const text = context.activity.text;
-    const encodedText = encodeURIComponent(text);
-    const response = await fetch('https://api.github.com/search/users?q=' + encodedText);
-    const json = await response.json();
-
-    await context.sendActivity(`I found ${json.total_count} users.`);
-
-    const firstUser = json.items[0];
-    await context.sendActivity(`The first person is named ${firstUser.login}`);
-
-    const card = botbuilder.CardFactory.heroCard(
-        firstUser.login,
-        [{ url: firstUser.avatar_url }]
-    );
-
-    await context.sendActivity({
-        type: 'message',
-        attachments: [card]
-    });
-}
+const fetch = require('node-fetch');
+const restify = require('restify');
+
+const server = restify.createServer();
+server.listen(process.env.PORT || process.env.port || 3978, () => {
+    console.log('server up!!');
+});
+
+const botbuilder = require('botbuilder');
+const { BotAdapter } = require('botbuilder');
+const adapter = new botbuilder.BotFrameworkAdapter();
+
+adapter.onTurnError = (context, error) => { console.log(error); };
+
+// it's all about one route
+server.post('/api/messages', (req, res) => {
+    adapter.processActivity(req, res, async (context) => {
+        // find what the user said
+        switch (context.activity.type) {
+            case 'message':
+                await handleMessage(context);
+                break;
+            case 'conversationUpdate':
+                // was a member added?
+                await welcomeMessage(context);
+                break;
+        }
+    });
+});
+
+async function welcomeMessage(context) {
+    if (context.activity.membersAdded) {
+        await context.sendActivity('I can search GitHub to find users for you.');
+        await context.sendActivity('Just tell me what you want to search for!');
+    }
+}
+
+async function handleMessage(context) {
+    await context.sendActivity({
+        type: 'typing'
+    });
+
+    const text = context.activity.text;
+    const encodedText = encodeURIComponent(text);
+    const response = await fetch('https://api.github.com/search/users?q=' + encodedText);
+    const json = await response.json();
+
+    await context.sendActivity(`I found ${json.total_count} users.`);
+
+    const firstUser = json.items[0];
+    await context.sendActivity(`The first person is named ${firstUser.login}`);
+
+    const card = botbuilder.CardFactory.heroCard(
+        firstUser.login,
+        [{ url: firstUser.avatar_url }]
+    );
+
+    await context.sendActivity({
+        type: 'message',
+        attachments: [card]
+    });
+}

online-event-resources/emerging-tech/Bots/Bots101/package.json

@@ -1,13 +1,13 @@
-{
-    "dependencies": {
-        "botbuilder": "^4.13.5",
-        "dotenv": "^8.2.0",
-        "restify": "^8.5.1"
-    },
-    "devDependencies": {
-        "nodemon": "^2.0.6"
-    },
-    "scripts": {
-        "start-watch": "nodemon index.js"
-    }
-}
+{
+    "dependencies": {
+        "botbuilder": "^4.13.5",
+        "dotenv": "^8.2.0",
+        "restify": "^8.5.1"
+    },
+    "devDependencies": {
+        "nodemon": "^2.0.6"
+    },
+    "scripts": {
+        "start-watch": "nodemon index.js"
+    }
+}

personal-business-development/Imagine-Cup|Ponder-Plan-Pitch/README.md

@@ -1,94 +0,0 @@
-# Imagine Cup  - Ponder Plan Pitch
-
-## **Resources**
-[Slide Deck](https://github.com/microsoft/Reactors/raw/main/personal-business-development/Imagine-Cup%7CPonder-Plan-Pitch/Imagine%20Cup%20-%20Ponder%20Plan%20Pitch.pptx)
-
-**Learn more about...**
-- [Azure Cognitive Services](https://azure.microsoft.com/en-us/products/cognitive-services/#overview)
-- [Azure IoT](https://azure.microsoft.com/en-us/products/cognitive-services/#overview)
-- **Everything**, with module on [Microsoft Learn](https://learn.microsoft.com/en-us/training/)
-
-<br>
-
-## **Activities**
-### **Activity 1 - Whole Group Brainstorm**
-- What issues exist in the categoris of healthcare, environment, educaiton, and lifestyle
-
-<br>
-
-### **Activity 2 - Small group Design Thining activity**
-**For you chosen focus issue ask these question:**
-- ***Who* is your stakeholder or user** 
-
-    Get specific about who you are talking about!
-
-    **Consider:**
-    - Demographics
-    - location
-    - any specific circumstance that lead to them being amongst the issue.
-
-<br>
-
-- **What - Identify what their life looks like, what parts are hard.** – 
-
-    Don't change their whoel life, focus on specific areas:
-    - Describe the users life
-    - What tasks the user do in a day/week/month
-    - Why is it difficult at the moment?
-
-<br>
-
-- **Why – Is there a reason things are challenging**
-
-    What get’s in their way?
-        - Are their physical difficulties
-        - A lack of data/information
-        - Are their systemic barriers that slow them down.
-
-<br>
-
-
-- ***How* Can we remove the barriers or work around them?**
-
-    Come at it from the problem side, not solution first. What do they need?
-
-    What do they need access to?
-
-    - People? 
-    - Expertise?
-    - Resources?
-    - Automation?
-
-
-<br>
-
-### **Activity 3 - Find tech solutions**
-
-Utilising the resources from above, brainstorm potential solutions to the issue that use Azure.
-
-Consider hosting, utilising Azure APIs, IoT, and more. 
-
-<br>
-
-### **Activity 4 - Make a Pitch**
-
-Create a narative around the issue you identified, the people involved, and the tech vission you have. 
-
-**Remember these aspects:**
-
-- People - who are we helping, what is their problem?
-- Making a difference - How are we helping, is this a new way to do it? 
-- Vision & Growth - How does technology let us do this? 
-
-<br>
-
-### **What next?**
-
-- [Sign up for Imagine Cup](https://aka.ms/Imaginecuprego1)
-- [Get Imagine Cup resources](https://aka.ms/Imagine-Cup)
-- Join IC Discord – find teammates, ask questions
-
-
-
-
-