Open source + MOG: A Q&A with MOG’s Director of Engineering
We recently submitted two pieces of software to open source, a pretty great milestone for our young company! MOG’s social media mistress sat down with Sylvain Rebaud, MOG’s Director of Engineering, to explore MOG’s relationship with open source. Before we dive in to the good stuff (including a look behind MOG’s velvet curtains and some advice from Sylvain to young engineers), let’s take a look at what open source means.
(from opensource.org)
Open source is a development method for software that harnesses the power of distributed peer review and transparency of process. The promise of open source is better quality, higher reliability, more flexibility, lower cost, and an end to predatory vendor lock-in.
What does that have to do with MOG? Essentially, embracing open source means practicing certain standards in production and development that promote public access to our end product’s source materials. And though MOG don’t have a public API quite yet, it is on our roadmap.
Zoë: How does submitting MOG software to open source relate to MOG’s primary mission to create the most incredible music-listening experience possible?
Sylvain: What we published so far may not help MOG directly. But it’s a way to give back to the community for all the other open source tools we’re using to make this service. In the long run, when we start opening up the API to a wider audience, we will have more sample code and tools we will open source to let people embrace our service with less friction.
Z: What’s your history with open source?
S: I have a long history with open source projects. I was a main contributor to the original XBMC project (XBox Media Center) to which I provided my own code (UPnP SDK Library). The XBMC project is what powers the Boxee box and software. It has a HUGE following. I am also familiar with Open Source Licenses. I sell my software under a Dual License. GPL for Open source projects and Commercial for Closed source projects. I can do that because I wrote the software entirely myself.
Z: What software did MOG submit and why? Why is it exciting?
S: On my side, I submitted AirLogger: http://github.com/c0diq/airlogger
It came out of a need to access the MOG app log while connected to a USB accessory (such as BMW headunit or other partners hardware we’re integrating with or TVs). In this situation, we can’t rely on the USB connection to the PC to see what’s going on. So I wrote this tool to read the log and broadcast it over the network where you can look at it while staying connected to the USB accessory. It’s just easier to debug that way. (I also wanted to learn a bit about node.js) This is exciting because I am sure a LOT of people are having the same issues when developing for USB Accessories. The market is growing and that includes TVs as the iPhone can output video now (a mirror of the iPhone screen or an entirely separate UI). This is an upcoming MOG feature, by the way.
Z: How do you see open source of benefit to the future of MOG and the future of streaming music?
S: As I described earlier, there may be more things we want to give back to the community (like backend node.js tools). In return, open source community contributes back to MOG, fixes bugs, add new features. It’s a win-win situation. And yes, your competition can see your code, but as long as the secret sauce is not exposed, it’s all good.
And one more thing – a piece of advice to young engineers out there – being active in an open source project is critical to getting hired. It means you’re passionate about what you do. Some companies won’t hire you if you don’t have that on your resume.












