+1 too I can help start a draft on the wiki based on historical user requests and trends in the ecosystem. And of course, the roadmap is a living and breathing document which will continue to evolve over time based on continuous feedback, and more.
-Vineet On Thu, Jun 23, 2016 at 8:18 AM, Kavinder Dhaliwal <[email protected]> wrote: > +1 I'm in favor of this. The Zeppelin roadmap is very community driven and > having something similar for HAWQ will go a long way to getting more > feedback about the overall direction and goals of HAWQ. > > On Thu, Jun 23, 2016 at 2:02 AM, Lei Chang <[email protected]> wrote: > > > Hi Guys, > > > > I noticed there are a lot of requests about hawq roadmaps coming from the > > offline hawq activities (meetup et al). > > > > Although we have the list of backlog JIRAs on our JIRA page > > < > > > https://issues.apache.org/jira/browse/HAWQ/?selectedTab=com.atlassian.jira.jira-projects-plugin:roadmap-panel > > >. > > But it does not give a high level description. A good example from other > > communities is here: > > https://cwiki.apache.org/confluence/display/ZEPPELIN/Zeppelin+Roadmap > > > > So I am proposing we have a similar HAWQ Roadmap page maintained on our > > wiki page. > > > > Thoughts? > > > > Cheers > > Lei > > >
