diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md new file mode 100644 index 0000000..680b638 --- /dev/null +++ b/CODE_OF_CONDUCT.md @@ -0,0 +1,76 @@ +# Contributor Covenant Code of Conduct + +This Code of Conduct addresses our standards and expectations for conduct within this repository. + +## Our Pledge + +In the interest of fostering an open and welcoming environment, we as +contributors and maintainers pledge to making participation in our project and +our community a harassment-free experience for everyone, regardless of age, body +size, disability, ethnicity, gender identity and expression, level of experience, +nationality, personal appearance, race, religion, or sexual identity and +orientation. + +## Our Standards + +Examples of behavior that contributes to creating a positive environment +include: + +* Using welcoming and inclusive language +* Being respectful of differing viewpoints and experiences +* Gracefully accepting constructive criticism +* Focusing on what is best for the community +* Showing empathy towards other community members + +Examples of unacceptable behavior by participants include: + +* The use of sexualized language or imagery and unwelcome sexual attention or +advances +* Trolling, insulting/derogatory comments, and personal or political attacks +* Public or private harassment +* Publishing others' private information, such as a physical or electronic + address, without explicit permission +* Other conduct which could reasonably be considered inappropriate in a + professional setting + +## Our Responsibilities + +Project maintainers are responsible for clarifying the standards of acceptable +behavior and are expected to take appropriate and fair corrective action in +response to any instances of unacceptable behavior. + +Project maintainers have the right and responsibility to remove, edit, or +reject comments, commits, code, wiki edits, issues, and other contributions +that are not aligned to this Code of Conduct, or to ban temporarily or +permanently any contributor for other behaviors that they deem inappropriate, +threatening, offensive, or harmful. + +## Scope + +This Code of Conduct applies both within project spaces and in public spaces +when an individual is representing the project or its community. Examples of +representing a project or community include using an official project e-mail +address, posting via an official social media account, or acting as an appointed +representative at an online or offline event. Representation of a project may be +further defined and clarified by project maintainers. + +## Enforcement + +Instances of abusive, harassing, or otherwise unacceptable behavior may be +reported by contacting the project team at . All +complaints will be reviewed and investigated and will result in a response that +is deemed necessary and appropriate to the circumstances. The project team is +obligated to maintain confidentiality with regard to the reporter of an incident. +Further details of specific enforcement policies may be posted separately. + +Project maintainers who do not follow or enforce the Code of Conduct in good +faith may face temporary or permanent repercussions as determined by other +members of the project's leadership. + +## Attribution + +This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, +available at [http://contributor-covenant.org/version/1/4][version] + +[homepage]: http://contributor-covenant.org +[version]: http://contributor-covenant.org/version/1/4/ diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md new file mode 100644 index 0000000..59cc0e4 --- /dev/null +++ b/CONTRIBUTING.md @@ -0,0 +1,36 @@ +## Contributing + +[fork]: https://github.com/github/dev-days/fork +[pr]: https://github.com/github/dev-days/compare + +Hi there! We're thrilled that you'd like to contribute to this project. Your help is essential for keeping it great. + +Contributions to this project are [released](https://help.github.com/articles/github-terms-of-service/#6-contributions-under-repository-license) to the public under the [project's open source license](LICENSE). + +Please note that this project is released with a [Contributor Code of Conduct](CODE_OF_CONDUCT.md). By participating in this project you agree to abide by its terms. + +## How to contribute + +If you've found a **bug** or have a **specific change request**, please open a **GitHub Issue** so it can be tracked and triaged properly. + +### Community expectations + +Please help keep this space welcoming and useful: +- Follow the repository's [Code of Conduct](/CODE_OF_CONDUCT.md) +- Be respectful and constructive +- Stay on topic and relevant to this repository +- Search existing issues before opening a new one +- Avoid spam or unrelated promotional content + +### Security note + +Do **not** report security vulnerabilities in Issues or Pull Requests. +Please follow the process outlined in `SECURITY.md` for responsible disclosure. + +Thanks for helping make Dev Days a great experience for organizers and developers worldwide! + +## Resources + +- [How to Contribute to Open Source](https://opensource.guide/how-to-contribute/) +- [Using Pull Requests](https://help.github.com/articles/about-pull-requests/) +- [GitHub Help](https://help.github.com) diff --git a/EVENT_CODE_OF_CONDUCT.md b/EVENT_CODE_OF_CONDUCT.md new file mode 100644 index 0000000..72e4306 --- /dev/null +++ b/EVENT_CODE_OF_CONDUCT.md @@ -0,0 +1,47 @@ +# GitHub Event Code of Conduct + +This Code of Conduct addresses our standards and expectations for conduct at Dev Days events. + +## Code of Conduct + +By attending a GitHub event, including any of the events or activities organized by GitHub in association with the GitHub event (collectively the "Event"), you represent that you have read, understand, and agree to the following GitHub Event Code of Conduct (hereinafter "Code of Conduct"). This Code of Conduct applies to all attendees, speakers, exhibitors, sponsors, organizers, staff, and volunteers (collectively "Event Participants") at the Event. + +GitHub values the participation of all Event Participants and aims to create an event where all Event Participants have an enjoyable and fulfilling experience. Accordingly, all Event Participants are expected to show respect and courtesy to other Event Participants throughout the Event. + +GitHub is dedicated to providing a positive and harassment-free experience for everyone, regardless of age, gender, gender identity and expression, sexual orientation, disability, personal appearance, body size, ethnicity, race, religion, nationality, or level of experience. + +We do not tolerate harassment of Event Participants in any form, nor do we tolerate any behavior that would reasonably lead to an Event Participant being made to feel unsafe, insecure, or frightened for their physical or emotional well-being. All communication and behavior should be appropriate for a professional setting including people of many different backgrounds. + +Examples of encouraged behavior that contributes to a positive environment include: + +- Using welcoming and inclusive language +- Being respectful of differing viewpoints and experiences +- Gracefully accepting constructive criticism +- Focusing on what is best for everyone at the Event +- Showing empathy towards others and Event Participants + +Unacceptable behavior includes, but is not limited to: + +- The use of sexualized language or imagery +- Inappropriate physical contact, sexual attention, or advances +- Trolling, insulting or derogatory comments or behavior +- Personal or political attacks toward Event Participants +- Sustained disruption of talks or any other events or activities organized by GitHub in association with the Event +- Intimidation, stalking, following, or harassing of Event Participants +- Photography or recording of Event Participants without their consent +- Harassment of any kind, even in a joking or ironic manner +- Conduct which could reasonably be considered inappropriate in a professional setting +- Each Event Participant is entirely responsible for their own actions. + +Thank you for helping to make this a welcoming, friendly space for all. + +## Reporting an incident + +If you are being harassed, notice that someone else is being harassed, have any other concerns, or if you believe an Event Participant is not acting in a way compliant with this Code of Conduct, please speak directly with a venue security officer or GitHub employee for urgent help, or email us at events@github.com for non-urgent issues. For life threatening situations, please dial emergency services immediately. + +GitHub employees will be happy to help Event Participants contact security or local law enforcement, escort to safety, or otherwise assist those experiencing harassment to feel safe for the duration of the Event. + +## Credit +Portions of this Code of Conduct are based on the example anti-harassment policy from the Geek Feminism wiki, created by the Ada Initiative and other volunteers, under a Creative Commons Zero license. + +See the full Code of Conduct in the [GitHub Documentation](https://docs.github.com/site-policy/github-terms/github-event-code-of-conduct). diff --git a/LICENSE b/LICENSE new file mode 100644 index 0000000..5017bd4 --- /dev/null +++ b/LICENSE @@ -0,0 +1,21 @@ + MIT License + + Copyright GitHub, Inc. + + 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 diff --git a/README.md b/README.md index e456548..bcacd39 100644 --- a/README.md +++ b/README.md @@ -1,69 +1,58 @@ -# GitHub Copilot Dev Days +# Dev Days -Landing page for **GitHub Copilot Dev Days** β€” a collection of hands-on workshops to master GitHub Copilot across every IDE, language, and workflow. +> 🚨 **To run an official Dev Days event and receive program support, you must fill out the [event request form](https://gh.io/dev-days-2026) and receive approval from the Dev Days team**. +> +> This repository contains the technical content, promotional materials, and organizer instruction for Dev Days event organizers. -πŸ”— **Live site:** [github.github.com/dev-days](https://github.github.com/dev-days/) +**Dev Days** is a global, in-person user group initiative taking place from **September 1st to October 31st 2026**. The series brings together developers, enthusiasts, and local tech communities to explore the power of GitHub Copilot through practical, hands-on experiences. -## Workshops +Open to all developers, the events are led by local tech communities and designed to be highly practical. Each session runs for approximately **2-3 hours** and focuses on real-world workflows, hands-on activities, and workshops centered on AI-assisted coding with GitHub Copilot. -> NOTE: The links below point to the old repository. +## πŸ™οΈ Find or Host an event in your city -### VS Code β€” Agent Lab (Social Bingo) +Find an event near you on our [Luma calendar](https://gh.io/dev-days/calendar). -| Workshop | Stack | Duration | -|----------|-------|----------| -| [Agent Lab β€” Python](https://copilot-dev-days.github.io/agent-lab-python/) | Python + FastAPI + HTMX | ~1 hr | -| [Agent Lab β€” TypeScript](https://copilot-dev-days.github.io/agent-lab-typescript/) | TypeScript + Vite + React | ~1 hr | -| [Agent Lab β€” Java](https://copilot-dev-days.github.io/agent-lab-java/) | Java 21 + Spring Boot | ~1 hr | -| [Agent Lab β€” .NET](https://copilot-dev-days.github.io/agent-lab-dotnet/) | .NET 10 + Blazor | ~1 hr | +If you're a community leader and want to host a Dev Days event, this repository includes everything you need to plan, organize, and promote your event successfully. -### VS Code β€” Specialized +Want to organize a Dev Days event in your city? Fill in our [event request form](https://gh.io/dev-days-2026). +> Filling out the form does not guarantee your event will be accepted. Please await confirmation from our team before planning your event. -| Workshop | Stack | Duration | -|----------|-------|----------| -| [Mona Mayhem β€” VS Code (Beginner)](https://copilot-dev-days.github.io/mona-mayhem/?track=vscode) | VS Code + Astro + TypeScript | ~60 min | -| [App Modernization](https://copilot-dev-days.github.io/appmod-workshop-java/) | Java + Spring Boot Modernization | ~60 min | +--- -### Terminal +### πŸ—“οΈ Event formats -| Workshop | Stack | Duration | -|----------|-------|----------| -| [Mona Mayhem β€” CLI (Beginner)](https://copilot-dev-days.github.io/mona-mayhem/?track=cli) | Terminal + Copilot CLI | ~60 min | -| [Copilot CLI Workshop](https://copilot-dev-days.github.io/tailspin-toys-workshop/) | Terminal + AI-Powered Development | ~90 min | +**Dev Days** are flexible - please tailor the format to fit your community! We recommend using one of the following **two formats**, depending on your community's experience, audience, **and available infrastructure**. -### IDEs +**1️⃣ Sessions-only format:** Focused on technical talks and demos around GitHub Copilot. -| Workshop | Stack | Duration | -|----------|-------|----------| -| [Copilot for Visual Studio](https://copilot-dev-days.github.io/visual-studio-lab/) | Visual Studio + .NET 10 + Blazor | ~120 min | -| [Copilot for JetBrains](https://copilot-dev-days.github.io/jetbrains-workshop/) | IntelliJ IDEA + Spring PetClinic | ~60 min | -| [Copilot for Xcode](https://copilot-dev-days.github.io/xcode-workshop/) | Xcode + SwiftUI | ~60 min | +**2️⃣ Sessions + Workshop format:** Combines technical sessions with a hands-on workshop for deeper, practical learning. -## Prerequisites +Both formats are designed to be interactive and hands-on, encouraging participants to learn by doing. -- GitHub Account -- GitHub Copilot License -- Git installed -- Your IDE of choice +--- -## Development +### πŸ“š Resources available -This is a static site hosted on GitHub Pages. To run locally, serve the files with any static file server: + **πŸ‘‰ Send attendees to [github.github.com/dev-days](https://github.github.com/dev-days/)** β€” the central site where all Dev Days hands-on workshops are published. The site displays every available workshop option so attendees can easily find and follow the lab for your event. -```sh -# Example using Python -python3 -m http.server +| Topic | Description | Resources | +| :----------------------------------------- | :------------------------------------------------------------------ | :--------------------------------------- | +| πŸ“ [**Organization Guide**](organization) | Practical guidance to plan and run your event from start to finish. | Event checklist, registration page draft | +| πŸ“ [**Content - Organizer View**](content) | Technical content for sessions and workshops. | Presentation slides, hands-on labs | +| πŸ“ [**Content - Attendee View**](https://github.github.com/dev-days/) | Technical content for sessions and workshops. | Hands-on labs | +| πŸ“ [**Marketing**](marketing) | Materials and templates to help you promote your event. | Social media templates, event covers | -# Example using Node.js -npx serve -``` +## ❓ Questions +Head to the [Issues](https://github.com/github/dev-days/issues) area in this repo to ask questions. -## Links +If you were already approved to organize an event, you will be added to a **Slack channel**. Here you can ask event-specific questions. -- [GitHub Organization](https://github.com/copilot-dev-days) -- [Copilot Docs](https://docs.github.com/en/copilot) -- [Awesome Copilot](https://github.com/github/awesome-copilot) +For more information about contributing to this repository, please read our [contributing guide](CONTRIBUTING.md). ---- +## Trademarks -Built with πŸ’œ by the GitHub Copilot Team +This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft +trademarks or logos is subject to and must follow +[Microsoft's Trademark & Brand Guidelines](https://www.microsoft.com/en-us/legal/intellectualproperty/trademarks/usage/general). +Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. +Any use of third-party trademarks or logos are subject to those third-party's policies. diff --git a/SECURITY.md b/SECURITY.md new file mode 100644 index 0000000..67a9cbf --- /dev/null +++ b/SECURITY.md @@ -0,0 +1,31 @@ +Thanks for helping make GitHub safe for everyone. + +# Security + +GitHub takes the security of our software products and services seriously, including all of the open source code repositories managed through our GitHub organizations, such as [GitHub](https://github.com/GitHub). + +Even though [open source repositories are outside of the scope of our bug bounty program](https://bounty.github.com/index.html#scope) and therefore not eligible for bounty rewards, we will ensure that your finding gets passed along to the appropriate maintainers for remediation. + +## Reporting Security Issues + +If you believe you have found a security vulnerability in any GitHub-owned repository, please report it to us through coordinated disclosure. + +**Please do not report security vulnerabilities through public GitHub issues, discussions, or pull requests.** + +Instead, please send an email to opensource-security[@]github.com. + +Please include as much of the information listed below as you can to help us better understand and resolve the issue: + + * The type of issue (e.g., buffer overflow, SQL injection, or cross-site scripting) + * 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. + +## Policy + +See [GitHub's Safe Harbor Policy](https://docs.github.com/en/site-policy/security-policies/github-bug-bounty-program-legal-safe-harbor#1-safe-harbor-terms) diff --git a/SUPPORT.md b/SUPPORT.md new file mode 100644 index 0000000..d22e312 --- /dev/null +++ b/SUPPORT.md @@ -0,0 +1,14 @@ +# Support + +## How to file issues and get help + +This project uses GitHub issues to track bugs and feature requests. Please search the existing issues before filing new issues to avoid duplicates. For new issues, file your bug or feature request as a new issue. + +For help or questions about using this project, please create an issue. + +**dev-days** is under active development and maintained by GitHub staff. We will do our best to respond to support, feature requests, and community questions in a timely manner. + + +## GitHub Support Policy + +Support for this project is limited to the resources listed above. diff --git a/content/README.md b/content/README.md new file mode 100644 index 0000000..6137784 --- /dev/null +++ b/content/README.md @@ -0,0 +1,80 @@ +# πŸ“š Content + +This folder contains the **official content** for **Dev Days**, including presentation slides and hands-on labs. + +Dev Days events are flexible, so organizers should feel empowered to adjust the format based on the needs of their audience. + +## πŸ—“οΈ Sample Agenda (Session + Workshop) + +This is a suggested agenda for events following the **Sessions + Workshop** format +(approximately **2-3 hours total**). + +| Order | Session | Type | Estimated Time | Description | +| ----: | ------------------ | ------------ | -------------- | ------------------------------------------------------------------------------------- | +| 01 | **GitHub Copilot app: From issue to merge, in one app** | Session | 30–45 min | The provided slide deck is an overview of the GitHub Copilot app. | +| 02 | **Hands-on Lab** | Hands-on Lab | 60 min | Start using the GitHub Copilot app with guided, practical exercises. | + +> This agenda combines **official content** and **hands-on practice** in a balanced format. + +## πŸ” Prerequisites + +Dev Days events are open to developers of all experience levels. Different events may cover different topics that are more relevant for a subset of developers. + +**For organizers**: + +- Clearly define the topics you plan to cover on your registration page. + +- Include any additional prerequisites relevant to your event. Make sure to inform attendees whether they need to bring their own laptops or if devices will be provided at the venue (common for events hosted at universities). + +**For attendees**: + +- **GitHub Copilot free subscription** at a minimum β€” [Sign up here](https://aka.ms/get-github-copilot-devdays) + +- Download the [GitHub Copilot app](https://gh.io/dev-days/app) + +- Install the [GitHub Copilot CLI](https://docs.github.com/en/copilot/how-tos/copilot-cli/set-up-copilot-cli/install-copilot-cli) + +- Laptop β€” Required for events that include a hands-on workshop. + +## ✨ Dev Days – *Core Content Session* + +The current round of Dev Days focuses on the **GitHub Copilot app**, the only desktop experience for agent-driven development built natively on GitHub. + +Alternatively, if your audience wants to focus on development tools in the Terminal, you may focus on the GitHub Copilot CLI. + +*Every Dev Days session should include at least one of the following two presentations.* + +| Name | Type | Time | Description / Concepts Taught | Level | +| ---- | ---- | ---- | ----------------------------- | ----- | +| **⭐Recommended: GitHub Copilot app** | Session | ~30 min | The GitHub Copilot app is the only desktop experience for agent-driven development built natively on GitHub. | Beginner | +| **GitHub Copilot CLI** | Session | ~30 min | GitHub Copilot CLI in the terminal and command-line workflows. | Beginner | + +> Note: While the GitHub Copilot app is available to users on all GitHub plans, workshop exercises will consume AI credits. We recommend keeping an eye on your credit usage before and during your event so you have enough available to fully participate in the hands-on activities. + +## πŸ“š Content Tracks - Workshops + +> πŸ”Ž **Highlight** +> All workshop content is available at **[github.github.com/dev-days](https://github.github.com/dev-days/)**. This is the best link to share with attendees β€” it displays every available workshop option for Dev Days events so participants can navigate directly to the lab for your event. + +There are two workshop topic options. The recommended option focuses on the GitHub Copilot app. Alternatively, you may use one of the workshops focused on the GitHub Copilot CLI. + +Each track includes the **Dev Days – Core Content Session** and one of the **hands-on workshops**. + +### ⭐ GitHub Copilot app + +| Name | Type | Time | Description / Concepts Taught | Level | +| ------------- | ------------ | --------- | ----------------------------- | ------------- | +| [**GitHub Copilot app Workshop**](https://github.github.com/dev-days/) | Hands-on Lab | ~1 - 1.5 hr | Your team is adopting AI agents to work through a growing backlog. The Copilot app gives you one place to direct that work β€” picking up issues, running agents, reviewing changes, and merging pull requests. This lesson gets you installed, connected, and comfortable starting a conversation about your project. | Beginner | + +### ⌨️ GitHub Copilot CLI + +| Name | Type | Time | Description / Concepts Taught | Level | +| ------------- | ------------ | --------- | ----------------------------- | ------------- | +| [**GitHub Copilot CLI: Tailspin Toys Workshop**](https://github.github.com/dev-days/) | Hands-on Lab | ~2 hr | Master GitHub Copilot in the terminal with Tailspin Toys. Covers custom instructions, Copilot CLI setup, MCP servers, custom agents, and agent skills for AI-assisted delivery. | Intermediate | +| [**GitHub Copilot CLI: Mona Mayhem Workshop**](https://github.github.com/dev-days/) | Hands-on Lab | ~1 hr | Build a retro arcade contribution-battle game while learning context engineering, Plan Mode, Agent Mode, multi-agent workflows, and design-first development in VS Code. | Intermediate | + +## 🧠 How to use this content + +* Use **sessions** to introduce concepts and workflows +* Use **hands-on labs** for guided, practical learning +* Prefer **one hands-on lab per event** to ensure enough execution time diff --git a/marketing/README.md b/marketing/README.md new file mode 100644 index 0000000..d26ca49 --- /dev/null +++ b/marketing/README.md @@ -0,0 +1,16 @@ +# πŸ“£ Marketing Toolkit + +This marketing toolkit provides everything you need to successfully promote your **Dev Days** event. All materials are professionally designed and ready to customize with your event details. + +## πŸ’œ Series Hashtag + +When posting about your Dev Days event, include our series hashtag in your post: **#DevDays** + +## 🎨 Generate Event Assets + +Use the event [asset generator](https://gh.io/dev-day/assets) to create your event's: +- Luma event page cover +- Speaker banner +- Social promo + +> πŸ’‘ You can also use the **[Registration Page template](draft-registration-page.md)** available in this toolkit to ensure consistent messaging between your event page and promotional assets. \ No newline at end of file diff --git a/marketing/draft-registration-page.md b/marketing/draft-registration-page.md new file mode 100644 index 0000000..8fca5d1 --- /dev/null +++ b/marketing/draft-registration-page.md @@ -0,0 +1,97 @@ +# πŸ“ Registration Page – Dev Days + +This document provides a ready-to-use template for creating your **Dev Days** event registration page. +Customize it with your local event details, such as date, time, location, and agenda. + +--- + +## Before you start + +* 1️⃣ Use the following event name format: + `Dev Days [City Name]` + Example: `Dev Days SΓ£o Paulo` +* 2️⃣ Generate necessary event page and promotional assets using the [asset generator tool](https://gh.io/dev-day/assets) +* 3️⃣ Dev Days are open to all developers. But if you plan to cover a topic that has additional prerequisites or experience suggestions, please state this in your registration page. +* 4️⃣ Clearly state whether participants need to **bring their own laptops** or if computers will be provided by the venue. + +--- + +## **Dev Days [Your City]** + +Join us for a community-led developer event focused on **AI-assisted coding with GitHub Copilot**. +This event brings together developers to explore practical workflows, real-world use cases, and hands-on experiences using GitHub Copilot. + +Whether you are new to GitHub Copilot or already using it, this event will help you better understand how to apply AI-assisted coding techniques in everyday development. + +--- + +## πŸ—“οΈ Event format + +Choose the format that best fits your audience, available infrastructure, and time. This is flexible and you may customize the format. + +### Sessions-only + +* Technical sessions and demos +* Flexible agenda length + +### Sessions + Workshop + +* **Total duration: approximately 3 hours** +* Includes: + + * **1 technical session** + * **1 hands-on workshop (1 hour)** + +> **Important** +> For events including a workshop, make sure the venue supports hands-on activities. +> This may include access to a **computer lab** (for example, at a university) or infrastructure for participants to use their **own laptops**, such as tables, **power outlets**, and a **stable Wi-Fi connection**. + +--- + +## πŸ“… Sample agenda (Sessions + Workshop) + +*[Time]* – **Check-in & Networking** + +*[Time]* – **Welcome & Opening** + +*[Time]* – **Session 1: GitHub Copilot app** *[or similar title]* + +*[Time]* – **Workshop: GitHub Copilot app** + All workshop content is available at **[github.github.com/dev-days](https://github.github.com/dev-days/)**. + +*[Time]* – **Closing & Next Steps** + +--- + +## πŸ“œ Code of Conduct + +We are committed to providing a welcoming and inclusive environment for all participants. +Please review the event **Code of Conduct** before attending. + +πŸ‘‰ [Event Code of Conduct](../EVENT_CODE_OF_CONDUCT.md) + +--- + +## πŸ“ How to get there + +πŸ“Œ **Event location:** +*[Organizer to fill in]* + +πŸš‰ **Public transportation:** +*[Organizer to fill in]* + +πŸ…ΏοΈ **Parking information:** +*[Organizer to fill in]* + +--- + +### βœ… Final check + +Before publishing your registration page, confirm that it includes: + +* Event name following the global standard +* Selected event format +* Clear agenda aligned with the chosen format +* Laptop and infrastructure requirements +* Location and access information +* Code of conduct link diff --git a/organization/README.md b/organization/README.md new file mode 100644 index 0000000..81757c1 --- /dev/null +++ b/organization/README.md @@ -0,0 +1,96 @@ +# πŸŽ‰ Organizer Guide: Dev Days + +Dev Days is a community-driven event created by Microsoft developers for the broader developer community. **The goal is to foster learning, collaboration, and innovation around GitHub Copilot.** + +As an organizer and community leader, you play a crucial role in making this initiative a success. Your leadership helps bring people together, encourages knowledge sharing, and creates an inclusive environment where everyone can grow and contribute. + +--- + +## πŸ“‹ Event Organization Checklist + +To assist you in organizing your event, we've created a practical checklist covering the key aspects to consider when planning. This guide is designed to help you run a successful technical event, ensuring nothing important is overlooked. + +> [!IMPORTANT] +> If you plan to run a **Workshop**, make sure your venue supports hands-on activities. +> This includes either access to a **computer lab** (for example, at a university) or adequate infrastructure for participants to use their **own laptops**, such as tables, **power outlets**, and a **stable Wi-Fi connection**. + +--- + +### πŸ‘₯ 1. Initial Planning + +* [ ] Connect with partners in your community to support event organization. + This may include roles such as check-in, main host, timekeeping, and content delivery (speakers, facilitators, and proctors). +* [ ] Define the **event date and time** (events should take place between **September 1st and October 31st 2026**), including a 15-minute buffer at the start for setup and adjustments. + +--- + +### 🏒 2. Venue and Logistics + +* [ ] Secure an **appropriate venue** (company office, co-working space, or university). + Since the event is hands-on, ensure participants have enough space to work comfortably. +* [ ] Confirm the **venue capacity** (recommended minimum: 30 participants). +* [ ] Validate the **infrastructure** (tables, chairs, stable Wi-Fi, projector or large display, and microphones for larger spaces). +* [ ] Check **accessibility and location details** (public transportation, parking) and plan to include this information on the registration page. +* [ ] Explore sponsorship opportunities to provide **food and drinks** (water, coffee, snacks). + +> [!TIP] +> You can include venue, food, and swag partner logos on the registration page and promotional materials to recognize sponsors and strengthen future collaborations. + +--- + +### 🎀 3. Content: Speakers & Facilitators + +The event agenda includes **one session and one workshop**, which means support from your local community is essential. + +* [ ] Identify and invite **speakers** to lead the sessions. +* [ ] Recruit **facilitators and proctors** to support the workshop and assist participants during hands-on activities. +* [ ] Share content resources with all speakers, facilitators, and proctors in advance. +* [ ] Prepare a **backup plan** in case a speaker or facilitator becomes unavailable. + +--- + +### πŸ“£ 4. Marketing + +Use the following event naming convention: +`Dev Days [City Name]` +This helps identify your event as part of the global initiative. + +* [ ] The Dev Days team will create your registration page on Luma and add you as an event host. This will give you the ability to edit the event information. Update the event page description based on your event details + ([see the registration page draft in the marketing folder](../marketing/draft-registration-page.md)). +* [ ] Confirm which participant information is required by the venue and include it in the Luma registration flow. +* [ ] Use **official event graphics** for the registration page and social media channels. + Generate the necessary assets using the [generator tool](https://gh.io/dev-day/assets). + +**Your registration page should clearly include:** event description, agenda, date, time, location, banner, and the standardized event name. + +> Tip: All registration pages will be hosted on Luma. You may also use other platforms such as Meetup or any tool your community already uses to promote your event. But, official attendee registration should be on Luma. + +--- + +### πŸ“§ 5. Communications + +* [ ] Send **event reminders** and any **prerequisites** to registered participants. +* [ ] Include the workshop site link β€” **[github.github.com/dev-days](https://github.github.com/dev-days/)** β€” in your attendee communications so participants can access the hands-on lab content. +* [ ] Confirm **attendance** a few days before the event. + +> [!TIP] +> For example, send a reminder on Wednesday and a final follow-up on Friday for a Saturday event. + +--- + +### πŸ“… 6. On the Event Day + +* [ ] Arrive early to **set up the venue** and prepare the space. +* [ ] **Test all equipment**, including Wi-Fi, projector, and microphones. +* [ ] Distribute **badges**, if applicable. +* [ ] **Manage time** across sessions and activities. +* [ ] Coordinate **breaks or icebreakers** to maintain engagement. + +--- + +### πŸ“ 7. Post-Event + +* [ ] Thank **speakers, facilitators, and participants**. +* [ ] Collect **participant feedback**. +* [ ] Run a **team debrief** to review what worked well and what can be improved. +* [ ] Share feedback about the **GitHub Copilot workshop experience**, including challenges and suggestions, to help improve future events.