= proposal title Sponsoring Open Source Projects - From the Shadows to Sustainable Karsten 'quaid' Wade = description (400 char) In every organization are the seeds of sustainable support for open source projects, often buried in the shadows and needing a path to the light. Whether straight-cash, people-time, or useful-resources, are you providing enough? Too much? How will it survive the next budget planning cycle? This is a case study of that journey for Red Hat's sponsoring of infrastructure for open source communities. = abstract On one hand, this is a story of how we found and gathered together fragmented sponsorships across a corporation, arranged them together over common ground, and gained individually and as an organization from the synergy. This story is of bringing together many groups with similar ideas, needs, and visions into a useful collaboration that solved real problems while saving real money. This is the story -- as of today -- of Red Hat's support for open source community infrastructure. On the other hand, this is part of a model you can consider, adapt, and apply to bring sponsorships in your organizations out of the shadows and into sustainability so that the time and efforts of your people, the computing services and resources, and monetary donations can be something much more than giving back. In this case study I will tell the story of: * How we are working to make sure we are aware of where and how we sponsor infrastructure for open source projects ("community infrastructure"), and of knowing if we are spending enough in the right areas. * How our team saw an opportunity to resolve specific pain points for the Ceph and CentOS projects, and how we grew that solution to create gravity and help other projects by iterating and growing on the original vision. * The pains and challenges that drove us to make this effort; the risk in not preventing (or even causing) infrastructure problems in upstream projects where we invest significant developer resources. * How we used the Open Organization Model to gather information, form stakeholders, and reach consensus to go from a single data center vision to a strategy for sustainable support of key community infrastructure. And how the Open Organization Model helped support us in remembering to fail early and often so we could iterate and learn. = cfp guidelines OSCON Business Summit – Open Source in Enterprise Case Studies Over the years we’ve included many different viewpoints on open source. Among those is how enterprises can use, benefit from, and give back to open source—and why they would want to do so. This special track is all about the business side of open source, specifically case studies. Aimed at business stakeholders from CXOs to team leads, this track will give insight into why your software development/engineering teams chose open source, why open source is already coursing through the veins of your business and why that is something you can use to your advantage. Open source is a catalyst for digital transformation. People learn best through stories and we want to hear yours. If you would like to present a case study at this year’s conference, your session should describe your personal experience solving a real-world problem. Your proposal should provide a synopsis of the situation; outline the pain points your organization or team was experiencing; walk through the decision-making process and the strategy that came out of it; explain the successes, failures, and lessons learned along the way. Use metrics and share data to describe the outcomes and make recommendations (at least 3-5). We encourage presenters to invite discussion and Q&A throughout the session. = video submission script Hi, this video is because I don't have anything recent that would give quite the ... understanding I'm looking for. There are some videos out there from OSCON, from SCALE, from other events. Plenty to be proud of but nothing on the mark. My name is Karsten Wade, I'm a community architect at Red Hat. Over the years I've worked on -- and spoken about -- Fedora, CentOS, the open source way, and open community infrastructure. My experience in these areas range from project leader to team leader, from engineering manager to program manager, from technical writer to architect of communities. I've got a story to tell that I think will be interesting for business audiences as well as technical people who care about the sustainability of open source projects, in particular the underlying infrastructure -- servers and services, people and budgets -- that make all the fun development and writing possible. We grew into all this organically at Red Hat, and for more than a decade it's been a little burr under my saddle .. grain of sand in my shoe ... pea under my mattress ... a deep annoyance that took a while to get to the surface. This was the knowledge that as an organization built on a foundation of successful open source projects we needed to make two specific things happen: 1. Create understanding that sponsorship of community infrastructure is key lifeblood for projects, not just in making them possible, but in keeping them free and open and accessible to all. The tools and methods you choose matter in keeping the 'freedom' in 'open source'. 2. Bake all that into company processes so that when people move around, organizations change, budgets are adjusted, people leave teams or the company, someone new takes on an existing job role ... all of that and none of it causes a piece of community infra to fall down, disappear, be forgotten about, not paid for, etc. So this is a story of Red Hat going all the way from workstations under people's desks acting as servers through many years of honest effort honestly applied, the occasional shadow-moves and last minute saves, and bringing us to the present where we are working with the CIO and corporate IT to present a unified view of this essential way Red Hat sponsors communities.