Title ===== Plugging into the corporate backplane - hacking sponsorship for open source projects Audience - advanced, beginner, developer, everyone, intermediate ======== Everyone Topic - Open Source in Enterprises ===== Tags openinfra, sponsorship, ==== All ages Speakers: me Primary contact: me Brief description (255 char) ============================ Maybe you've said, "We're big enough, we should be able to help open source projects in some way." Sure, you can contribute or host a meetup, but how do you get your organization to sustainably sponsor projects? Let's talk about that ... Short abstract (600 char) ========================= Have you ever thought, "It would be a good idea for our company/school/org to make sponsoring of open source projects something that we just DO"? Then you hit wall after wall, verbal support but no one with budget will open their checkbook and commit to the ideas? This session covers stories and lessons from a Red Hat community architect who has walked this path several times. Learn to hack the bureacracy, uncover and plug into the corporate backplane, and create something that lives beyond you as champion. Long abstract (10000 char) ========================== Have you ever thought, "It would be a good idea for our company/school/org to make sponsoring of open source projects something that we just DO"? Then you hit wall after wall, verbal support but no one with budget will open their checkbook and commit to the ideas? This session covers stories and lessons from a Red Hat community architect who has walked this path several times. Learn to hack the bureacracy, uncover and plug into the corporate backplane, and create something that lives beyond you as champion. Even in a willing organization, the challenges are likely similar to what you deal with. You have to discern the parts that are unique to your organization, what is typical and how is it typically handled, and how you can align those magnetic particles toward ongoing support for open source software projects. Speaker Karsten Wade brings a flexible, lightweight model that draws upon experience working bottom-up, top-down, and side-to-side to stitch together sponsorship and recognition from across and outside of Red Hat. From the unconference to the Board room. Karsten takes his model from his experience at Red Hat trying to: get technical writing to happen upstream with the code (Fedora Project); bring in a great friend often mis-perceived as a competitor (CentOS Project); establish sustainable support and processes for community infrastructure ( https://osci.io ); and so on. Once again Karsten has found himself speaking in third-person about his passion for radically transparent open infrastructure of participation. He is really excited about how modern automation, source control, and other dev/ops practices have made it super-easy and even more fun to participate in free/open source projects in creating and running the infrastructure. Karsten and his team of sysadmins at Red Hat work directly in upstream projects and are members of many communities, most relevant here being https://OpenSourceInfra.org and https://osci.io . Message to the reviewers ======================== I'm not sure I have the best fit for Topic. It has some spiritual fit with legal and license discussions, in that they are a subset of the process of plugging into the corporate backplane. This is an extension of my interest and participation in the recent focus on #openinfra amongst a growing community that also are regular SCALE attendees. I suspect there may be other similar discussions proposed by other members of the opensourceinfra.org / #openinfra community. I haven't had the time to ask around. :) If there seem to be anywhere that it would make sense to merge this topic, let's talk about it. I could shorten my approach to share the presentation with some other voices who have walked similar pathways. ideas ===== * figure out time scales and map across them - quarterly, fiscal year, lifecycles, project release cycle, etc. * find stakeholders, keep adding * practice an iterative open organization decision process format (URL) - meaning you start with what you have, you add people & voices, you simplify & amplify your message internally, practice wise communication, keep the decision circle relatively small & well identified, address all concerns & put things on the roadmap / parking lot / trash bin.