Category:OpenDevOps

As software engineering has become increasingly complex, the Open Source ecosystem has evolved along with it. From the early days with an open source set of command line tools, developer libraries, and an OS kernel, through the development of network services, and on to desktop applications like LibreOffice, GIMP, and KDEnlive. I think the next "most important battleground" is enterprise application development.

To develop enterprise grade software, you need a suite of applications that work together. To continue bringing engineers into Open Source development, the tools engineers are using on a day-to-day basis to be Open Source. If we cannot demonstrate, in the office, that Open Source produces viable software, it is hard to make the case that it is. Conversely, if engineers are using and relying on Open Source every day, they will be more inclined to see it is an important thing in their lives, and they will be more likely to contribute.

A DevOps ecosystem for remote teams includes a number of components: 1. Forum server, for discussing topics that evolve over days or weeks. 1. Chat system, for immediate interaction. 1. Videoconferencing, for video interaction. 1. Wiki server, for long-term evolving information provision. 1. Network-enabled office suite, for collaborative document development. 1. Real office suite, for making high quality docs. 1. Source code repository, for version control. 1. Ticket tracker, for change requests. 1. Kanban board, for project tracking.