As open source projects and communities grow, it becomes difficult to understand what’s going on inside. A public and up-to-date roadmap can encourage new contributors to join the project and guide the efforts of existing contributors, and also give confidence to adopters about the direction and sustainability of the projects. Is it easy to create a public roadmap? Probably. Is it easy to maintain it? Not exactly. Did we fail with it? Yes.

Oleg will share the experiences of public roadmaps in the projects he has contributed to: Jenkins, WireMock, Keptn, CDF, etc. He'll share the reasons and principles that have guided creation of *open* roadmaps, the challenges encountered, the techniques and technologies that could be used in your projects. We’ll talk about maintaining roadmaps, mistakes we made there and how we addressed them.

In particular, Oleg will describe building a roadmap with help of GitHub Projects and modern features offered by the GitHub ecosystem. That could be the easiest way for new projects and communities, and can be also useful for established projects.

* References and prior talks: https://docs.google.com/document/d/1M752I3AbE0GDdK0NpAdT9kKaiTBUjlbvUHggzfcqHZU/edit?usp=sharing
* First talk together with Mark Waite, specific for Jenkins: https://www.youtube.com/watch?v=KOZ7nbaAbp0