event-media-partnerships

Event Media Partnerships You set up reciprocal visibility deals between a technical event and media or community properties that are not themselves events: newsletters, podcasts, online communities (Slack/Discord, developer-ambassador programs), blogs, and media outlets. The exchange is symmetric exposure for exposure: the event gives logo placement and mentions, the partner gives a newsletter blurb, a podcast slot, or a community post. No cash changes hands by default. Organizer guides name this as a distinct tier, not an ad-hoc favor: DevOpsDays organizing guide, "Community Sponsor": "Used for media outlets and other conferences that are interested in cross-promotion with you... usually you will not ask them to provide cash." MLH organizer guide: "Strategic/Media Partners... Community Partners... typically for free." Four boundaries, drawn explicitly because the sourced guides blur at least one of them: Earned coverage is not a partnership. "We ask a publication to cover us" is a one-way ask the event neither controls nor reciprocates - that is samber/dev-event-organizer-skills@event-press-relations (press kit, journalist targeting, accreditation, embargoes). This skill's deals are two-way exchanges the event initiates and structures. MLH's own guide lists both in one breath without separating them - draw the line for the user every time. Another conference is not a media property. The same newsletter-swap mechanics with another event's newsletter belong to samber/dev-event-organizer-skills@cross-event-promotion - settled boundary, both sides. This skill takes the "media outlets" half of DevOpsDays' tier phrase; that sibling takes "other conferences". Cash reclassifies the deal. If a candidate deal mixes cash and barter (a discounted paid tier plus a reciprocal mention), split it: the cash component goes to the sponsor block ( samber/dev-event-organizer-skills@event-sponsor-value-proposition and its siblings), and only the barter component stays here. Never let this skill's simplicity under-charge a sponsor who could pay. The event's own channels are not this skill. Scheduling the event's own thank-you posts and amplification belongs to samber/dev-event-organizer-skills@event-social-media ; a media partnership is inbound amplification from someone else's channel. Like cash sponsorship in this collection, a barter deal buys placement and promotion - never a talk slot, editorial coverage, or program influence. Every target in Measurement is self-set: what a newsletter swap or podcast exchange returns in registrations is whatever this event's own tracked links measure. If you can browse the web, check 2-3 live media-partner pages of comparable conferences before locking a public partner tier. Every ranking below is a default, not a law: it shifts with context and with who executes it. After the interview, re-rank the format menu against what you know about this organizer. Each of the following overturns a default rung: Show more Installs 1.3K Repository samber/dev-even…r-skills GitHub Stars 2 First Seen Sep 13, 2026 Security Audits Gen Agent Trust Hub Pass Socket Pass Snyk Pass