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.
As time went on, we simply continued to ride the open source path. We assembled a huge collection of functional applications we had built for client sites that could be added to and modified for new ones. Shopping carts, contact forms, opt-in email list managers, employment opportunity listings, content editors, slide shows, all built as open source using PHP.
A few years later came the emergence of Content Management Systems, which contained—as a package—many of the functional elements we previously had relied upon our own resources to create. Drupal, Joomla!, Wordpress, and others were emerging as the default new development platforms for most digital agencies who had followed the same path as ours.
Venom, as described by its discoverer, Crowdstrike, an end-point security company, works by attacking QEMU's virtual Floppy Disk Controller (FDC). The first thing many of you think when learning this is: "Who cares, I've never used a floppy drive on my virtual machine (VM)!"
Ah, but, you don't have to activate the virtual floppy drive for a potential hacker snake to bite you. By default, the legacy floppy drive code is still in there, even though it's never been used. The corruption is still hiding in the code. So, even though you'd never dream of using a VM floppy drive, you're still open to attack.
It all sounds so straightforward: Put your code up on GitHub or start/join a project at the Apache Software Foundation (ASF), build a community of like-minded individuals, start a company, take in some funding, and then IPO. Or maybe not. One thing is certain: Running an open source company has unique challenges and opportunities. Although much has been written on the subject of open source and community building, I'd like to share three critical lessons learned in my travels as a co-founder and CTO of a venture-backed open source company.
The Open Networking Foundation (ONF), a non-profit organization dedicated to accelerating the adoption of open Software-Defined Networking (SDN), today announced the appointment of Dr. Bithika Khargharia as the director of product and community management. Bithika’s service to ONF is being provided by Extreme Networks, an ONF member company where Bithika is a principal architect of solutions and innovation. She will continue in her role at Extreme Networks while also taking on her new responsibilities with ONF.
Comcast joined the OpenDaylight Project today and we wanted to share how we’ve been using the OpenDaylight platform and how it fits into our long-term network direction.
We have been testing ODL since the project launched to see where it might fit in and have been impressed by the improvements in functionality and stability with each successive release. We have also been participating with our partner CableLabs on the OpenDaylight sub-project PacketCable PCMM, which aims to develop a southbound plugin for ODL that can manage service flows across Cable Modem Termination System (CMTS) devices.