Elgato_dark/fleet
1
0
Fork 0
mirror of https://github.com/fleetdm/fleet synced 2026-04-21 13:37:30 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 91

Git ops workshop template update (#42729)

Browse source 
Updated GitOps Workshop issue template to replace post workshop happy
hours with dinners.
closes #15135

---------

Co-authored-by: johnjeremiah <jjeremiah@gmail.com>
Co-authored-by: Ashish Kuthiala <53918208+akuthiala@users.noreply.github.com>
This commit is contained in:
Michael Buck 2026-03-31 14:39:14 -05:00 committed by GitHub
parent b95af9a439
commit e35d07c96d
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 6 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

11
handbook/marketing/event-execution.md
View file

@ -131,7 +131,8 @@ We use GitHub labels to organize the difference between overall event issues and
We utilize two general event plans, which act as templates depending on the scale and type of the event:
1. **Conference:** Used for large conferences and events where we have a booth, speaking slots, lead scanning, and other major logistical needs.
2. **Workshop/Happy hour:** Used for our GitOps workshop series (which often includes happy hours). This smaller template can be used for the full workshop or for bespoke, standalone happy hours.
2. **Workshop/Dinner:** Used for our GitOps workshop series (which often includes a post workshop dinner).
3. **Meetups/Happy Hours** ...wip
### **Execution process**
@ -465,7 +466,7 @@ echo "Done."
## How to automate workshop creation
The workshop tracking process uses the same GitHub parent/child issue structure as conferences, but with a smaller, workshop-specific set of tasks. Use this script instead of the conference script when running a GitOps workshop (with or without a happy hour).
The workshop tracking process uses the same GitHub parent/child issue structure as conferences, but with a smaller, workshop-specific set of tasks. Use this script instead of the conference script when running a GitOps workshop.
> If you haven't set up the GitHub CLI yet, follow the **Setup** steps in the [How to automate event creation](#how-to-automate-event-creation) section above before continuing.
@ -682,9 +683,9 @@ Plan the post-workshop networking. This is treated as a separate event to allow
- [ ] Update the $PLANNING_DOC_URL with these details
- Secure venue — find a bar/restaurant within a 5-minute walk of the workshop area
- Confirm menu/tab — decide on Open Bar vs. Fixed Menu and set the budget cap
- IF NEEDED: Create Happy Hour registration page on Eventbrite or Luma and promote separately
- IF NEEDED: Create Dinner registration page on Eventbrite or Luma and promote separately
EOF
create_sub_issue "3. Happy Hour Planning & Promotion"
create_sub_issue "3. Dinner Planning"
# --- Child 4 ---
@ -723,7 +724,7 @@ cat > "$BODY_FILE" << EOF
**Description**
To be completed within 48 hours after the event. Close the loop on leads and technical feedback.
- [ ] Update the $PLANNING_DOC_URL with these details
- Calculate stats — record Registered, Attended, and No-Show rates for both Workshop and Happy Hour
- Calculate stats — record Registered, Attended, and No-Show rates for both Workshop and Dinner
- Log technical issues — document any WiFi drops or firewall blockers for future reference
- CRM upload — upload attendee list to Salesforce/HubSpot
- Send follow-up email with slides and repo links