[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Proposal] Apache Beam's Public Project Roadmap

OK, I have one note: what about longer-term "roadmap", in quotes because that just means it is "ideas for the future". Like the Spark runner could have a written roadmap that includes lots of TODOs that extend far into the future. It gives a menu of things to think about when filling this out each quarter. Users and contributors could potentially comment / upvote.

I think this is probably a separate thing than what you have here - it could just be a public gdoc with no particular structure, or JIRA tags bundled into some kind of report - but what do you think?


On Wed, Jun 6, 2018 at 8:37 PM Kenneth Knowles <klk@xxxxxxxxxx> wrote:
This is great. I'm really excited to build a community process for this.


On Wed, Jun 6, 2018 at 5:05 PM Griselda Cuevas <gris@xxxxxxxxxx> wrote:
Hi Beam Community, 

I'd like to propose the creation of a Public Project Roadmap. Here are the details as well as some artifacts I started already. 




Create a simple spreadsheet-based project roadmap to generate an overview of all the efforts driven by different members of the community. I propose doing something like this tracker I put together [1]. 


The ultimate purpose of this roadmap is to create a tool and method to make our project more transparent and efficient. It will help us map dependencies, identify collaboration areas and communicate future releases to users more clearly. 


We could update the current status of the roadmap every three months (quarter), following these guidelines and timeline [2].