It seems a perpetual journey for me to help my employers understand the value associated with full participation with the global Open Source community. Sure, everyone leeches the value, but what happens when you move from GET to GET, POST, PATCH within that ecosystem. As CSC looks at a number of the forces that are re-shaping IT, it is important for CSC to be an active participant and a transformational partner for our customers. There are many technical, policy and more importantly cultural barriers to full community participation that need to be overcome. Whether we want to talk about the shift from IP/Patent centric defensive strategies, the legal ramifications associated with contract compliance and confidentiality, to the changes in skills and the retention of now publicly recognizable employees. There are many books written on this, but CSC is getting there! First comes the forced education that Open Source participation isn’t necessarily FREE (as in speech or beer). Not to mention the “soft” training around HOW to participate in these communities and the meritocracy that is/needs to be ever present alongside the discussions around the global nature, the timeliness and attention required. Finally, the obligatory training around licenses, copyright, and compliance that ensure that we are good community citizens. The good news, CSC is ready. Today we announce both the launching of CSC’s Open Source Community program, alongside the training materials and the first projects into the community via our github (http://csc.github.io). You will notice that we’re embracing “Free as in Beer” with the APL2.0 as our default license so that other collaborators can fully leverage their participation in our projects! Of the first projects, one that is exceedingly meaningful to me is Hanlon, some may remember a contribution that a few amazing guys (Nick Weaver and Tom McSweeney made while at EMC). Today we’re taking Razor to the next level, alongside some key partners that I will allow to announce themselves. Hanlon serves to take over where we left off with Razor: restructuring and reorganizing the codebase, and changing the way that the API (RESTful of course) and CLI are implemented (via Grape, JRuby, etc…) to simplify and improve portability. Much more to come via Tom McSweeney’s blog. We have a substantial backlog of projects for whom open sourcing is the best way to advance the state of the art, and underwrite, with transparency our new approach to open application development and systems integration. Stay tuned as we begin to empty the queue over the next couple of weeks!