I like the idea of presenting strategic and user impacting initiatives (ongoing and future) in an easy to consume format, but also think that "roadmap" sounds a bit too corporate...
Other projects, including Flink, Kafka and Spark have the concept of "Improvement Proposal" that could serve this purpose, so maybe it is time for "BIP"? There could then be an overview/list style page that shows in-progress and proposed items that gives the visitor an idea where the project is headed. Also, can we consider confluence for this? It is ASF hosted but easier to maintain than beam-site. Thanks, Thomas On Thu, Jun 7, 2018 at 4:59 AM, Kenneth Knowles <[email protected]> wrote: > 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? > > Kenn > > On Wed, Jun 6, 2018 at 8:37 PM Kenneth Knowles <[email protected]> wrote: > >> This is great. I'm really excited to build a community process for this. >> >> Kenn >> >> On Wed, Jun 6, 2018 at 5:05 PM Griselda Cuevas <[email protected]> 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. >>> >>> ---------------------------------------------------_________ >>> ____----------- >>> >>> *Proposal * >>> >>> >>> *What?* >>> >>> 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 >>> <https://docs.google.com/spreadsheets/d/1W6xvPmGyG8Nd9R7wkwgwRJvZdyLoBg6F3NCrPafbKmk/edit#gid=0> >>> [1]. >>> >>> >>> *Why?* >>> >>> *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. * >>> >>> >>> *How?* >>> >>> We could update the current status of the roadmap every three months >>> (quarter), following these guidelines and timeline >>> <https://docs.google.com/document/d/1jzASbp_5GrZdsF5YXau-MPh_v0jW6egJwL_Pyac5zeE/edit#heading=h.6dyyhz5krl9v> >>> [2]. >>> >>> >>> Thanks! >>> G >>> >>> [1]https://docs.google.com/spreadsheets/d/1W6xvPmGyG8Nd9R7wkwgwRJvZdyLoB >>> g6F3NCrPafbKmk/edit#gid=0 >>> >>> >>> [2]https://docs.google.com/document/d/1jzASbp_ >>> 5GrZdsF5YXau-MPh_v0jW6egJwL_Pyac5zeE/edit#heading=h.6dyyhz5krl9v >>> >>> >>>
