No matter the size of the organization, running an Open Source Programs Office requires staying on top of several things at once. While the processes between organizations might vary, many of run into a common set of needs and have subsequently developed a set of tools to manage corporate scale open source needs. As part of the TODO Group, we have started sharing those tools with each other and the open source community at large.
Growing a successful open source project takes more than code; it takes a healthy community where contributors can engage in deep conversations with respect. A code of conduct can be one important tool in helping a community uphold its own values. Last year, the TODO Group explored building a code of conduct template. Our goal was to share our experiences with each other, and encourage other communities to consider similar principles when building their open source projects.
Update: We will not be continuing work on the open code of conduct. See our followup post for more information. We believe open source communities should be a welcoming place for all participants. Through our experiences within the TODO Group, we strongly believe that a code of conduct helps set the ground rules for participation in communities and helps build a culture of respect. By adopting and honoring a code of conduct, communities can communicate their values, set expectations and outline a process for dealing with unwelcome behavior when it arises.
This time around we feature Benjamin VanEvery (@bvanevery) from Box on how a company new to open source gets started developing an Open Source Office. The goal of this post is to shed some light on starting up an Open Source Office by sharing experiences at Box. Several past blog articles have focused on why each of our companies got involved in open source. Each has been enlightening to read through and get a glimpse of what open source means to the individual companies how it impacts their cultures.
We had an opportunity to speak at OSCON 2016, the slides are provided below: Thank you to everyone who attended our session and asked questions! If you’re interested in joining the TODO Group, please reach out over Twitter! See a follow up blog from Ben VanEvery about his experience starting the Open Source Office at Box.
This is the next in our series of blog posts from TODO Group members, explaining why each company is committed to open source software. This week, we feature Gianugo Rabellino (@gianugo), Sr. Director, Open Source Communities at Microsoft Open Technologies. Five years ago I was flying back from my interview at Microsoft and jotting down a pros and cons list. I ended up focusing on one item. It was on both columns and it was staring at me.
This is the fifth in a series of blog posts from TODO Group members, explaining why each company is committed to open source software. This week, we feature Chris Aniszczyk (@cra), who’s in charge of open source at Twitter. Since Twitter’s early days, open source has been a pervasive part of our engineering culture. Every Tweet you send and receive touches a plethora of open source software on its journey from our Linux-based infrastructure to your device.
This is the fourth in a series of blog posts from TODO Group members, explaining why each company is committed to open source software. This week, we feature Brandon Keepers (@bkeepers), who is heading up the open source efforts at GitHub. From the very beginning, GitHub has been about open source. Scratching the itch of better code collaboration turned into a company built on and for open source; from the philosophies that founded the company, to the servers running the infrastructure, to the languages and libraries we use to build applications, to the millions of public repositories hosted on them.
This is the third in a series of blog posts from TODO Group members, explaining why each company is committed to open source software. This week, we feature Benjamin VanEvery (@bvanevery) and Nicholas Zakas (@slicknet), who oversee the open source activities at Box. We see running our open source program as being a logical extension to the type of work Boxers do every day. Like many tech companies, our technology stack includes open source projects.
This is the second in a series of blog posts from TODO Group members, explaining why each company is committed to open source software. This week, we feature Gil Yehuda (@gyehuda), who’s in charge of open source at Yahoo!. Since my company does not sell software, the choice to open source code is rather simple. Consider the alternative: keeping code a proprietary secret. Keeping secrets is expensive. Proprietary code needs to be maintained as other code dependencies often create the need to tweak things.