-
Notifications
You must be signed in to change notification settings - Fork 24
Enhance clarity in FAQ and README #16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
+95
−90
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
c104bee
Update FAQ and README to enhance clarity on event submissions, discou…
katiesavage 0755819
Apply batched suggestions from code review
brunoborges 6e064de
Updated FAQ
katiesavage 6092eb5
Merge branch 'update-faq' of https://github.com/github/dev-days into …
katiesavage File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,179 +1,184 @@ | ||
| # FAQ | ||
| # 🤔 Dev Days FAQs | ||
|
|
||
| ## What are Dev Days? | ||
| ## Latest | ||
|
|
||
| Dev Days is a global series of community-led in-person events focused on product awareness and adoption of GitHub's key products, with a focus on the GitHub Copilot app and Copilot CLI. | ||
| ### Can I submit a new Dev Days event now? | ||
|
|
||
| No. Due to the overwhelming response to the [Dev Days](https://gh.io/dev-days/calendar) program, we have reached capacity and are no longer accepting or approving new event submissions. | ||
|
|
||
|
|
||
| --- | ||
|
|
||
| ## General | ||
|
|
||
| ### What are Dev Days? | ||
|
|
||
| Dev Days is a global series of community-led in-person events focused on product awareness and adoption of GitHub's key products, with the focus on GitHub Copilot app and Copilot CLI. | ||
|
|
||
| **Events run from September 1 through October 31, 2026.** | ||
|
|
||
| ## Who can organize a Dev Days event? | ||
| ### Who can organize a Dev Days event? | ||
|
|
||
| Community leaders, GitHub Stars, MVPs, and other developers can organize Dev Days events. The program activates these community members to host and run events in their local areas. | ||
|
|
||
| ## Where do I go to manage my event? | ||
| ### Where do I go to manage my event? | ||
|
|
||
| The program team will provide you with an event page on the Luma calendar based on the date provided when you signed up to host an event. From there, you can update the page details to make the most sense for your event. | ||
| The program team will provide you an event page on the Luma calendar based on the date provided when you signed up to host an event. From there, you can update the page details to make the most sense for your event. | ||
|
|
||
| ## Can I host multiple Dev Days events? | ||
| ### Can I host multiple Dev Days events? | ||
|
|
||
| Yes, you can host multiple events as long as they are for different audiences, dates, and/or in different cities. | ||
|
|
||
| You will need to fill out one registration form for each event you plan to run. | ||
|
|
||
| ## There is already a Dev Days event in my city. Can I run another event? | ||
| ### There is already a Dev Days event in my city. Can I run another event? | ||
|
|
||
| Yes, you can run an additional event in the same city if the events are sufficiently different. | ||
|
|
||
| Questions to consider: | ||
| Yes, you can run an additional event in the same city if the events are sufficiently different. Questions to consider: | ||
|
|
||
| - Do these events cover the same topics? | ||
| - Do they reach the same audience? For example, you may plan to run an event specifically for your user group or school. | ||
| - Are the event dates too close? | ||
|
|
||
| If the events would be too similar, we suggest reaching out to collaborate with the existing event. If you have any questions about your prospective event, you can reach out to us for guidance. | ||
|
|
||
| ## How do attendees register for Dev Days events? | ||
|
|
||
| Attendees can sign up using the shortlink: https://gh.io/join-dev-days, which will show them the full calendar. | ||
|
|
||
| Registration details are managed through Luma. | ||
| ### How do attendees register for Dev Days events? | ||
|
|
||
| ## Can I charge attendees to come to the event? | ||
| Attendees can sign up using the [Dev Days event calendar](https://gh.io/join-dev-days), which will show them the full calendar. Registration details are managed through Luma. | ||
|
|
||
| No. Dev Days events must be free to attend. You may set a capacity limit to adhere to your venue's capacity limits. | ||
| ### Can I charge attendees to come to the event? | ||
|
|
||
| ## How do I use the Dev Days content? | ||
| No, Dev Days events must be free to attend. You may set a capacity limit to adhere to your venue's capacity limits. | ||
|
|
||
| ### Core Content Session (Slide Deck) | ||
| ### How do I use the Dev Days content? | ||
|
|
||
| https://github.com/github/dev-days/blob/main/content | ||
| **Core Content Session (Slide Deck):** [Dev Days content repository](https://github.com/github/dev-days/blob/main/content) | ||
|
|
||
| You may choose to focus on the GitHub Copilot app or GitHub Copilot CLI for your event. The provided slide decks give a comprehensive, all-in-one resource covering the GitHub Copilot app or CLI. | ||
|
|
||
| All available decks can also be found in the [Dev Days Presentation Decks release](https://github.com/github/dev-days/releases/tag/2026-07-30). | ||
|
|
||
| ### Workshops | ||
| **Workshops** | ||
|
|
||
| In addition to the core talk, we recommend including one workshop: | ||
|
|
||
| - Choose the workshop option that aligns with your selected topic and audience. | ||
| - Workshops are designed to be hands-on and practical, reinforcing the concepts covered in the talk. | ||
| - You do not need to run multiple workshops in a single event, but you can if you want. | ||
|
|
||
| ## What languages is the Dev Days content available in? | ||
| ### What type of promotion will the Dev Days program do for events? | ||
|
|
||
| All content is available in English. | ||
| Your event will be featured on the official Dev Days page, including your registration link. The page is promoted across Microsoft and GitHub social media channels. | ||
|
|
||
| The GitHub Copilot app presentation deck, workshops, and train-the-trainer content are also available in Spanish, Portuguese, Chinese, and Korean. | ||
| ### What Code of Conduct do I and my attendees need to follow during my Dev Days event and within the event repository? | ||
|
|
||
| ## What type of promotion will the Dev Days program do for events? | ||
| We have two Codes of Conduct related to the Dev Days series. Both can be found in the Dev Days repository. | ||
|
|
||
| Your event will be featured on the official Dev Days page, including your registration link. | ||
| - The [Contributor Covenant Code of Conduct](https://github.com/github/dev-days/blob/main/CODE_OF_CONDUCT.md) addresses our standards and expectations for conduct within this repository. | ||
| - The [GitHub Event Code of Conduct](https://github.com/github/dev-days/blob/main/EVENT_CODE_OF_CONDUCT.md) addresses our standards and expectations for conduct at Dev Days events. | ||
|
|
||
| https://gh.io/dev-days/calendar | ||
| Ensure all attendees and organizers are aware of and agree to the Code of Conduct. | ||
|
|
||
| --- | ||
|
|
||
| ## Event Setup & Registration | ||
|
|
||
| ### Should my Dev Days event be public or private? | ||
|
|
||
| All Dev Days events must be marked **Public** on Luma so attendees can discover and register for your event. | ||
|
|
||
| The page is promoted across Microsoft and GitHub social media channels. | ||
| ### How should attendees register for my Dev Days event? | ||
|
|
||
| ## My community group uses a different registration platform (Meetup, Eventbrite, etc.). Can I use this platform for registration instead of Luma? | ||
| All registrations must be managed through your **Luma event page**. Do not use external registration platforms or forms. | ||
|
|
||
| ### My community group uses a different registration platform (Meetup, Eventbrite, etc.). Can I use this platform for registration instead of Luma? | ||
|
|
||
| Your primary registration page should be the one that we provide you on Luma. You may utilize other platforms to further promote the event, but attendees should register on the Luma page. | ||
|
|
||
| ## What Code of Conduct do I and my attendees need to follow during my Dev Days event and within the event repository? | ||
| ### Do I need to include the required registration questions on my Luma page? | ||
|
|
||
| We have two Codes of Conduct related to the Dev Days series. Both can be found in the Dev Days repository. | ||
| Yes. Required registration questions must remain enabled on your Luma registration page. | ||
|
|
||
| - **Contributor Covenant Code of Conduct** | ||
| https://github.com/github/dev-days/blob/main/CODE_OF_CONDUCT.md | ||
| Addresses standards and expectations for conduct within the repository. | ||
| Required registration questions include: | ||
|
|
||
| - **GitHub Event Code of Conduct** | ||
| https://github.com/github/dev-days/blob/main/EVENT_CODE_OF_CONDUCT.md | ||
| Addresses standards and expectations for conduct at Dev Days events. | ||
| - **Required for attendee:** What country are you based in? | ||
| - **Required for attendee:** What is your GitHub username? | ||
| - **Required for attendee:** What is your job title? | ||
| - **Not required for attendee:** What company do you work for? | ||
| - **Not required for attendee:** Yes please, I'd like GitHub and Microsoft to use my information for personalized communications, targeted advertising and campaign effectiveness. See the [GitHub Privacy Statement](https://docs.github.com/en/site-policy/privacy-policies/github-privacy-statement) for more details. | ||
|
|
||
| Ensure all attendees and organizers are aware of and agree to the Code of Conduct. | ||
| ### Can I update my event information after submitting? | ||
|
|
||
| # Coupon & Swag Questions 🛍️ | ||
| Yes. If any event details change, especially the event date, update your Luma page and ensure all information remains accurate. | ||
|
|
||
| ## How do I redeem my Copilot coupon to be able to host an event? | ||
| --- | ||
|
|
||
| The program team will reach out to determine if receiving a Copilot Max coupon makes sense for your event and coordinate any complexities if needed. | ||
| ## Coupon & Swag Qs 🛍️ | ||
|
|
||
| ## What would cause me to not be able to receive a Copilot Max coupon? | ||
| ### How do I redeem my Copilot coupon to be able to host an event? | ||
|
|
||
| - If you are a Microsoft/GitHub FTE, MVP, or GitHub Star, you should already be set up on the appropriate Copilot plans. | ||
| - If you are not associated with any of those groups, we'll review your account to ensure there are no reasons we would be unable to provide a coupon (primarily if another coupon is already associated with your account). | ||
| - If you already have a student or other coupon associated with your account, we recommend using a different account to run the workshop effectively. | ||
| The program team will reach out to determine if receiving a Copilot Max coupon makes sense for your event and coordinate any complexities, if there are any. | ||
|
|
||
| ## What swag is provided for Dev Days events? | ||
| ### What would cause me to not be able to receive a Copilot Max coupon? | ||
|
|
||
| Each event receives a swag kit including: | ||
| - If you are a Microsoft/GitHub FTE, MVP, or GitHub Star, you should already be set up on the appropriate Copilot plans. | ||
| - If you are not associated with any of those groups, we'll review your account to ensure there are no reasons we won't be able to provide a coupon, mainly if you already have another coupon on your account. | ||
| - If you know you already have a student or other coupon associated with your account, we'd recommend utilizing a different account to be able to run the workshop effectively. | ||
|
|
||
| - Copilot plushies (300 per event) | ||
| - CLI and Copilot pins (3,000 total; 10 per event) | ||
| - Sticker packs with both assorted GitHub stickers and Dev Days-specific stickers (300 of each per event) | ||
| ### How do I know if I'm eligible to receive swag? | ||
|
|
||
| ## I'm having issues with my swag package. What do I do? | ||
| Swag eligibility is based on the benefits approved for your event. Refer to your event approval communication for details. | ||
|
|
||
| Please reach out to our swag partner at: | ||
| ### I'm having issues with my swag package I received. What do I do? | ||
|
|
||
| github@succinctive.com | ||
| Please reach out to our swag partner at **github@succinctive.com** or ping the team in the Slack channel. | ||
|
|
||
| Or contact the team through the Slack channel. | ||
| --- | ||
|
|
||
| # Reimbursement Questions 💰 | ||
| ## Reimbursement Qs 💰 | ||
|
|
||
| *F&B support is available and may be requested in the onboarding form.* | ||
|
|
||
| ## Key Requirements | ||
| ### Key requirements | ||
|
|
||
| - You must pay for F&B upfront and submit a receipt for reimbursement. | ||
| - Reimbursements are processed through Plain Sight, a Microsoft vendor. | ||
| - You must pay for F&B upfront and submit a receipt for reimbursement. The reimbursement is processed through Plain Sight, a Microsoft vendor. This is the standard process for all organizers. | ||
| - Include your estimated number of attendees and total F&B cost in your event request. | ||
| - Support is limited to **USD $400 per event**, on a first-come, first-served basis. | ||
| - Expenses submitted without prior approval will not be reimbursed. | ||
| - We will not reimburse expenses without prior approval. Please ensure your event and F&B request has been approved in advance. | ||
|
|
||
| ## How long does it take for my invoice to be paid? | ||
| ### How long does it take for my invoice to be paid? | ||
|
|
||
| You can expect to receive your payment request within 30 days. | ||
| You can expect to receive your payment request within 30 days. On average, payments are typically received within **10 - 15 business days** after the invoice has been submitted, as long as all of the payment information has been received by Plain Sight. | ||
|
|
||
| On average, payments are typically received within 10–15 business days after the invoice has been submitted, provided Plain Sight has received all required payment information. | ||
| ### What currency should I use in my invoice for reimbursement? | ||
|
|
||
| ## What currency should I use in my invoice for reimbursement? | ||
| Feel free to request payment in USD or whatever currency you used to pay for food and beverages. Plain Sight will pay you in your preferred currency, but please be sure to indicate on your invoice which form of currency you're requesting for payment. | ||
|
|
||
| You may request payment in USD or the currency used to pay for food and beverages. | ||
| ### Can the reimbursement be paid out to someone other than the community leader / point of contact? | ||
|
|
||
| Plain Sight will pay you in your preferred currency, but be sure to indicate on your invoice which currency you are requesting. | ||
| Yes. Plain Sight will issue payment to the business or individual listed on your invoice, even if that person is not the point of contact for the event. Just make sure that the payment details are accurately listed on the invoice. | ||
|
|
||
| ## Can the reimbursement be paid out to someone other than the community leader or point of contact? | ||
| ### What happens after I submit my reimbursement request? | ||
|
|
||
| Yes. Please notify the Dev Days team if someone other than the point of contact will be reimbursed. | ||
| For those requesting to be paid via wire transfer, check, or ACH, Plain Sight will reach out via email to notify you once they have reviewed your reimbursement request. They will then send you a link to complete your one-time profile for payment processing. The email link will come from Rho Banking, and the account name will be Get to Work, Inc. d/b/a Plain Sight. | ||
|
|
||
| Plain Sight will issue payment to the business or individual listed on your invoice, even if that person is not the point of contact for the event. Ensure payment details are accurately listed on the invoice. | ||
| When you receive the email from Rho, click the link and insert your payment details. Having you insert the information directly provides Plain Sight with the most accurate verification against your invoice. Once complete, Plain Sight will get the payment sent out. | ||
|
|
||
| ## What happens after I submit my reimbursement request? | ||
| ### How do I check the status of my reimbursement? | ||
|
|
||
| For those requesting payment via wire transfer, check, or ACH: | ||
| For questions or status updates about your reimbursement request, contact **deleon@plainsighthq.com** via email. | ||
|
|
||
| 1. Plain Sight will email you after reviewing your reimbursement request. | ||
| 2. You will receive a link to complete a one-time payment profile. | ||
| 3. The email link will come from **Rho Banking**, and the account name will be **Get to Work, Inc. d/b/a Plain Sight**. | ||
| 4. Complete the form with your payment details. | ||
| 5. Plain Sight will process and send your payment. | ||
| ### What counts as an itemized receipt? | ||
|
|
||
| ## How do I check the status of my reimbursement? | ||
| Please be sure to include receipts in your post-event report that have been provided to you by the vendor(s) after you purchased the food and beverages for the event. These receipts should not be quotes. Receipts should show how much was paid as well as what items were included with your purchase. | ||
|
|
||
| For questions or status updates regarding your reimbursement request, contact: | ||
| --- | ||
|
|
||
| deleon@plainsighthq.com | ||
| ## Surveys & Reporting | ||
|
|
||
| ## What counts as an itemized receipt? | ||
| ### Where can attendees provide feedback after the event? | ||
|
|
||
| Please include receipts provided by the vendor(s) after purchasing food and beverages for the event. | ||
| Attendees can complete the post-event survey here: [Dev Days Attendee Survey](https://gh.io/dev-days/feedback). | ||
|
|
||
| Receipts must: | ||
| ### Is there a survey for event organizers? | ||
|
|
||
| - Be actual receipts, not quotes. | ||
| - Show the amount paid. | ||
| - Include the items purchased. | ||
| Yes. All Dev Days organizers must complete the post-event organizer survey, regardless of whether they request Food & Beverage reimbursement: [Dev Days Organizer Survey](https://gh.io/dev-days/event-report). | ||
|
|
||
| These receipts should be submitted as part of your post-event report. | ||
| Completing the survey is required and helps us improve future Dev Days events. | ||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.