This post was written by Christopher Bennage (@bennage), a member of the Microsoft patterns & practices team.
A few months ago, we announced that we were handing Prism over to new owners. We put a lot of time and effort into identifying owners that would invest in the project and support the community.
Today, we are announcing a similar transition of ownership for Unity.
The new owners for Unity are:
Pablo Cibraro. Pablo is an internationally recognized expert with over 15 years of experience in designing and implementing large distributed systems with Microsoft technologies. For the last 9 years Pablo has helped numerous Microsoft teams develop tools and frameworks for building service-oriented applications. Pablo now focuses on technologies that enable developers to build large scale systems and web applications with focus on mobile, such as HTML5, Node.js, ASP.NET and Microsoft Azure.
Pedro Wood. Pedro has been working as a software developer, architect and dev lead in a wide variety of business areas for more than 20 years. Pedro is a frequent contributor in open source projects and enjoys being part of the .NET community in Argentina.
Why are we transitioning to new owners? That’s a natural question to ask.
The .NET community has a rich history of dependency injection containers, dating back before the introduction of Unity. Dependency injection containers for .NET have continued to mature and evolve significantly. In addition, open source components are now more accepted. The need for having an “official” container from Microsoft is no longer as widespread as it once was. We did spend a few months in 2014 thoughtfully experimenting for a “Unity 4”. However, we began to recognize that the p&p team was not equipped to carry the project forward.
At the same time, we believe that it would have been a poor choice to simply call the project “done”. We wanted to support all those who had invested in the library. After consulting with internal teams and p&p alumni, we asked Pablo and Pedro to assume the mantle.
Be sure to read the official announcement from the new team and follow their work on the new GitHub repo. Let them know what you’d like to see in future releases of Unity and help them continue to grow the community.