Day 2 of EclipseCon 2013 and we’ve already been seeing some strong interest in the M2M community and the kinds of projects we have been working on!
The story so far
There were two M2M events on day one. The first was the M2M tutorial featuring some real hardware (Raspberry Pi and Arduino), using the Koneki Lua Development Tooling to deploy scripts to the embedded Mihini runtime on the Pi to drive and take input from sensors over Modbus. I cheated a little and mixed in a bit of MQTT using the Paho Lua client, to have my kit publishing temperature and light data to a broker instead It is early days for Eclipse Mihini, but it was a really slick demo and tutorial, and I’m looking forward to playing with this a lot more.
The evening Birds of a Feather session gave a group of us a couple of open hours to hack around with our Pi and Arduino kits. My own efforts were slightly thwarted by a European soldering iron and a 110V power supply, so I wasn’t able to assemble the add-on board I wanted for my Raspberry Pi, but I’ll get back to that in the future. For those looking to explore their new Raspberry Pis and hardware / GPIO interaction from Java, take a look at the pi4j project.
Building a community
One useful “war story” that was told today was in Benjamin Cabé’s Building the M2M Community talk. The slides will follow, but it was good to hear about the progress of the community and projects involved (yes, ok, I’m a Committer on one of them…) and also to hear about his “Community Manager Toolbox” for tracking and responding to community discussions. I use a very similar set of tools when I engage with the Cloud Foundry and MQTT communities (and others that I’m involved with).
Here’s a summary:
- Slideshare – monitor who favourites and downloads slides related to your project
- Twitter – monitor hashtags, engage complainers
- YouTube – screencasts, demos, build channel to aggregate content
- StackOverflow – answer questionss (even old ones), find answers that need to be complemented)
- Github – monitor forks, stars, look for people using your tech (include Gists)
- Google Alerts
- IFTTT – e.g. if Eclipse wiki changes get Gtalk notification recipe
- Google Analytics for your site
- LinkedIn – monitor groups, post news and relay blog posts
In short: Engage the community. Be very public about what you are working on and where the roadmap is going. Get management buy-in for your projects to persuade them of the value of opening them to the community (use metrics to demonstrate take-up).
Working on standards
The other thing that has been going on today “behind the scenes” at EclipseCon has been the first meeting of the OASIS MQTT Technical Committee. It is exciting to see that Richard Coppen and Raphael Cohn have been elected as co chairs of the group, with seven sponsoring organisations from across the technology and messaging market and 35 publically-visible members – lots of interest in MQTT!