I manage the community leadership portion of the Open Source and Standards (OSAS) team at Red Hat. Our team works to help ensure the success of the community upstream projects, which are so important to Red Hat. This includes Fedora, CentOS, RDO, oVirt, Project Atomic, and many others. You can read about what we're working on and find events where our team and other Red Hat employees are presenting at community.redhat.com or follow us on Twitter at @redhatopen.
A short while ago I was reviewing one of my Twitter lists and I happened upon a tweet that led me to NethServer, an open source project that featured a product the likes of which I had been looking for in recent months.
We believe the Cubic SoC board has a lot more performance and capability than other similar products out there (e.g., Arduino or Raspberry Pi) and -- using the Cyclone FPGA's pin migration capability -- adding additional hardware resources by building the same board with a larger capacity FPGA is possible. All that processing power does, however, come at a price premium, probably retailing for sub-$200, which we believe is still very accessible for many hobbyists and commercial product developers.
A recent Red Hat survey on mobile trends revealed that 70 percent of organizations plan to embrace the Internet of Things in the next 5 years. So where is Red Hat on the IoT stage?
To further understand Red Hat's IoT strategy, I reached out to the company's Senior Director of Product Marketing, Mark Coggin.
I'm Lee Schlesinger, currently managing editor for the Spiceworks Community. Spiceworks provides a free downloadable help desk and network inventory application, and hosts a community for IT pros to discuss both work and off-topic issues. Though we have a pretty popular Linux group in the community, many of the community members, who we call SpiceHeads, work in Microsoft-centric shops.
Most PTL’s are elected because they are the most technical contributor on a particular project. They are rarely elected for leadership skills. Most of our top technical contributors struggle with leadership, and naturally shy away from it. This frequently leads to dysfunction in community dynamics, as the PTL continues to focus on contributing at a very high level, and puts limited effort into leadership work. Doing things like setting project vision, tracking and celebrating milestones, providing team members with actionable feedback, and sharing the project vision with community members outside the project are all good ways of exhibiting leadership. Doing those things as a part time effort can yield limited results in terms of team unity, and effectiveness. My suggestion to open source project leaders is to earmark considerable time for leadership work, and scale back direct contribution work. A well empowered, motivated, and effective team can produce much more velocity than a PTL individually focused on strong contribution, and ignoring leadership responsibilities in order to do it.