(Forwarding to dev list from the PR on roadmap.)

Given that we now have a main roadmap Webpage with some content, we were
wondering if there should be a section on IO related efforts. We already
have following Webpage on current and upcoming IO transforms.
https://beam.apache.org/documentation/io/built-in/

IO roadmap page can be an expanded version of above where we can include
following among other things.
(1) More details about some of the upcoming IO transforms that we expect to
be very popular.
(2) Major IO related efforts such as cross-platform IO and SDF (to
complement what will be available in portability roadmap on these features).
(3) Other IO related efforts (for example, documentation, performance
testing).

I think we have three options.

(1) Add a top level IO roadmap.
(2) Add IO roadmap sub-sections under each SDK instead of at top level.
(3) We don't need a IO roadmap since we already have
https://beam.apache.org/documentation/io/built-in/

WDYT ?

Thanks,
Cham


---------- Forwarded message ---------
From: Chamikara Jayalath <notificati...@github.com>
Date: Thu, Oct 25, 2018 at 7:07 PM
Subject: Re: [apache/beam] [Website] Add roadmap at top level (#6718)
To: apache/beam <b...@noreply.github.com>
Cc: Chamikara Jayalath <chamik...@google.com>, Your activity <
your_activ...@noreply.github.com>


Ok. Makes sense. Kenn and others, WDYT ? We can start writing down a
roadmap for IO if there's no objection. It can include more details about
some of the proposed IO mentioned in
https://beam.apache.org/documentation/io/built-in/ as well as information
on upcoming major IO related efforts such as cross-language IO support and
SDF (in addition to what will be available in portability roadmap for these
features).

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<https://github.com/apache/beam/pull/6718#issuecomment-433262537>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AKUZEUcsbL6bhjOfeRiNZmqtab3PDWBjks5uom5KgaJpZM4Xj9s1>
.

Reply via email to