Hi Konstantin,
thank you for starting this discussion again. It is a pitty that we have
never implemented FLIP-60 because it was the result of long offline
discussions with a lot of people closer working on the documentation topic.
I think splitting the documentation into *Option 1:
Hi everyone,
Thanks for bringing this up for discussion Konstantin. I do think we are
currently not serving Flink users proper documentation, which hurts Flink's
adoption and results in unnecessary opened Jira tickets, Stackoverflow
posts and email threads which in the end also cause a strain on
To summarize, I tend to Option 2 "Language First" in case we could find a
way to eliminate documentation duplication.
On Wed, Mar 23, 2022 at 5:02 PM Dian Fu wrote:
> Hi Konstantin,
>
> Thanks a lot for bringing up this discussion.
>
> Currently, the Python documentation is more like a mixture
Hi Dian,
Thank you for sharing your thoughts. What do you propose going forward? I
am not sure I got this from your email.
Best,
Konstantin
On Wed, Mar 23, 2022 at 10:03 AM Dian Fu wrote:
> Hi Konstantin,
>
> Thanks a lot for bringing up this discussion.
>
> Currently, the Python
Hi Konstantin,
Thanks a lot for bringing up this discussion.
Currently, the Python documentation is more like a mixture of Option 1 and
Option 2. It contains two parts:
1) The first part is the independent page [1] which could be seen as the
main entrypoint for Python users.
2) The second part
Hi Jark,
Thank you for joining the discussion. I am totally fine with the "Language
Tabs". Would be good to hear what the PyFlink community thinks, because the
Python Documentation is the biggest exception to the "Language Tabs"
approach.
@Jark Wu : Do you agree that SQL should be separate from
Hi Konstantin,
Thanks for starting this discussion.
>From my perspective, I prefer the "Language Tabs" approach.
But maybe we can improve the tabs to move to the sidebar or top menu,
which allows users to first decide on their language and then the API.
IMO, programming languages are just like
Hi everyone,
I would like to discuss a particular aspect of our documentation: the
top-level structure with respect to languages and APIs. The current
structure is inconsistent and the direction is unclear to me, which makes
it hard for me to contribute gradual improvements.
Currently, the
