Monthly Archives: December 2014

It’s official – 2015 has been deemed “the year of open source” for EMC. Sorry VDI / EUC, you’ve had your turn at the top of the charts! This new priority prompts a great question though: what would make EMC bother to embrace Open Source? As my good friend @vTexan LOVES to say: “If you don’t like change, you’re going to like irrelevance even less.” I’m sure EMC technically had a ‘choice’ to embrace Open Source, but not doing so is against every tenant of the Federations’ stance towards giving their customers that same opportunity – CHOICE.

So you have EMC products, and you want to participate in the open source ecosystem – what do you do? First, Head to the official EMC Github Page – and bookmark it. Grab some of the existing code and fork it (I love saying that. forgive me.). But I already have a project in mind Brian, I want to publish this internal tool I’ve created for everyone else to enjoy! Cool. Up Top! High Five! In fact, #DevHigh5 !

Get in the #DevHigh5 ! program, and get recognized. Joining is free. The resulting international celebrity status in the community is your problem. 🙂

Step 1: Put it on GitHub – “if it’s not on GitHub, it doesn’t exist”.
Step 2: Document – I know you’re already doing this, but for real – give it some good documentation. I hear doing it in markdown gets you brownie points.
Step 3: Open Testing – I’m sure it works in your lab, but broadening that scope will help ensure the product is more broadly accepted and adopted.
Step 4: Verify EMC Requirements – EMC will need to ensure it conforms with certain guidelines, but also – you’ll want to stay involved at some level as the code is shared with other users and projects, right?
Step 5: Publish the project – there’s a few ways to do this, depending on the code and who wants to own it – you’ll know what works best for EMC and you here.