# Why open-source timelines/roadmaps don't work

**URL:** <https://discourse.julialang.org/t/why-open-source-timelines-roadmaps-dont-work/99518>\
**Category:** Internals & Design\
**Created:** [May 28, 2023, 4:32pm UTC](https://discourse.julialang.org/t/why-open-source-timelines-roadmaps-dont-work/99518 "2023-05-28T16:32:10Z")\
**Posts on this page:** 1\
**Showing post:** 17

<div class="post-metadata">

**Author:** ![tim.holy](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/tim.holy/32/52_2.png) [@tim.holy](https://discourse.julialang.org/u/tim.holy)\
**Post date:** [May 30, 2023, 1:30pm UTC](https://discourse.julialang.org/t/why-open-source-timelines-roadmaps-dont-work/99518/17 "2023-05-30T13:30:33Z")

</div>

> [@Amval](#):
>
> I guess what I am trying to say is that having some sort of roadmap could help with better identifying gaps, prioritising, geting some community support, etc…

> [@RoyiAvital](#):
>
> The main gap is what are the goals and what is being worked on.  
> This gap doesn’t exist for the group of core developers, as the answer is in the PR’s and Issues.
> 
> To bridge the gap, we need to create a simple communication paths.  
> A timely forum post or a blog post will do wonders. It will benefit all sides

These are great roles for community participation! One of you could start a “this week in Julia development” newsletter, where you monitor Julia’s GitHub and then write things up in an manner that can be understood by a wider audience. That way it doesn’t slow down developers and word gets out about the cool happenings in Julia development.

---

_[View the full topic](https://discourse.julialang.org/t/why-open-source-timelines-roadmaps-dont-work/99518)._