AI & Machine Learning
Event Team Structure
Design the standing organizing team of a recurring technical event - the structure that persists between editions. Covers legal-entity posture (none, fiscal sponsorship, own non-profit), decision-rights shape (board-plus-organizers split, domain-lead federation, consensus committee), the role taxonomy, succession and bus-factor planning, burnout guardrails, organizer conflict of interest, a voluntary peer network of independent local communities, and the volunteer-to-paid-staff hiring gate. Use whenever the user mentions structuring or governing an organizing team, forming an association or non-profit for an event, splitting decision rights, organizer succession or rotation, organizer burnout, finding co-organizers, organizers doing business through the event, several independent meetups cooperating as a network, or hiring the first paid staff - even if they never say "team structure". Do NOT use for day-of staffing - use samber/dev-event-organizer-skills@event-volunteers instead.
- Publisher / source
- samber/dev-event-organizer-skills (found on skills.sh)
- Upstream record
- samber/dev-event-organizer-skills
- Version
- Version 3
- Published
- Publication review
- Approved for publication
- Content fingerprint
67cf0dee06da3763f17976118b8a70a6a2beaf2ef3e9ce998bcab32ec3f25c90