GitHub Copilot 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.
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 choose the Sessions + Workshop format, 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.
- 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, including a 15-minute buffer at the start for setup and adjustments.
- 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.
The event agenda includes two sessions 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.
Use the following event naming convention:
GitHub Copilot Dev Days [City Name]
This helps identify your event as part of the global initiative.
- Create an event registration page with complete event details (see the registration page draft in the marketing folder).
- Confirm which participant information is required by the venue and include it in your registration form.
- Use the official templates to create banners for the registration page and social media channels.
All templates are available in the
/marketingfolder.
Your registration page should clearly include: event description, agenda, date, time, location, banner, and the standardized event name.
Tip
We highly recommend using Luma (free) to create your registration page, as your event will be included in our Luma calendar.
You may also use other platforms such as Meetup or any tool your community already uses.
Note
We recommend including an event code of conduct to help create a welcoming and respectful environment for all participants.
Why do I need a code of conduct? Learn more about its importance and benefits in the Open Source Guide
- Send event reminders and any prerequisites to registered participants.
- 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.
- 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.
- 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.