You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@flink.apache.org by Kostas Kloudas <kk...@apache.org> on 2019/12/16 09:29:05 UTC
Documentation tasks for release-1.10
Hi all,
With the feature-freeze for the release-1.10 already past us, it is
time to focus a little bit on documenting the new features that the
community added to this release, and improving the already existing
documentation based on questions that we see in Flink's mailing lists.
To this end, I have create an umbrella issue
https://issues.apache.org/jira/browse/FLINK-15273 to monitor the
pending documentation tasks. This is by no means an exhaustive list of
the tasks, so feel free to add more.
Having a central place with all these tasks will also allow more
easily other members of the community, not necessarily people who
implemented the features, to get involved with the project. This is a
really helpful way to get in touch with the community and help the
project reach even greater audiences, as a feature that is not
documented is non-existent to users.
Thanks a lot,
Kostas
Re: Documentation tasks for release-1.10
Posted by vino yang <ya...@gmail.com>.
+1 for centralizing all the documentation issues so that the community can
take more effective to fix them.
Best,
Vino
Xintong Song <to...@gmail.com> 于2019年12月16日周一 下午6:02写道：
> Thank you Kostas.
> Big +1 for keeping all the documentation related issues at one place.
>
> I've added the documentation task for resource management.
>
> Thank you~
>
> Xintong Song
>
>
>
> On Mon, Dec 16, 2019 at 5:29 PM Kostas Kloudas <kk...@apache.org>
> wrote:
>
>> Hi all,
>>
>> With the feature-freeze for the release-1.10 already past us, it is
>> time to focus a little bit on documenting the new features that the
>> community added to this release, and improving the already existing
>> documentation based on questions that we see in Flink's mailing lists.
>>
>> To this end, I have create an umbrella issue
>> https://issues.apache.org/jira/browse/FLINK-15273 to monitor the
>> pending documentation tasks. This is by no means an exhaustive list of
>> the tasks, so feel free to add more.
>>
>> Having a central place with all these tasks will also allow more
>> easily other members of the community, not necessarily people who
>> implemented the features, to get involved with the project. This is a
>> really helpful way to get in touch with the community and help the
>> project reach even greater audiences, as a feature that is not
>> documented is non-existent to users.
>>
>> Thanks a lot,
>> Kostas
>>
>
Re: Documentation tasks for release-1.10
Posted by vino yang <ya...@gmail.com>.
+1 for centralizing all the documentation issues so that the community can
take more effective to fix them.
Best,
Vino
Xintong Song <to...@gmail.com> 于2019年12月16日周一 下午6:02写道：
> Thank you Kostas.
> Big +1 for keeping all the documentation related issues at one place.
>
> I've added the documentation task for resource management.
>
> Thank you~
>
> Xintong Song
>
>
>
> On Mon, Dec 16, 2019 at 5:29 PM Kostas Kloudas <kk...@apache.org>
> wrote:
>
>> Hi all,
>>
>> With the feature-freeze for the release-1.10 already past us, it is
>> time to focus a little bit on documenting the new features that the
>> community added to this release, and improving the already existing
>> documentation based on questions that we see in Flink's mailing lists.
>>
>> To this end, I have create an umbrella issue
>> https://issues.apache.org/jira/browse/FLINK-15273 to monitor the
>> pending documentation tasks. This is by no means an exhaustive list of
>> the tasks, so feel free to add more.
>>
>> Having a central place with all these tasks will also allow more
>> easily other members of the community, not necessarily people who
>> implemented the features, to get involved with the project. This is a
>> really helpful way to get in touch with the community and help the
>> project reach even greater audiences, as a feature that is not
>> documented is non-existent to users.
>>
>> Thanks a lot,
>> Kostas
>>
>
Re: Documentation tasks for release-1.10
Posted by Xintong Song <to...@gmail.com>.
Thank you Kostas.
Big +1 for keeping all the documentation related issues at one place.
I've added the documentation task for resource management.
Thank you~
Xintong Song
On Mon, Dec 16, 2019 at 5:29 PM Kostas Kloudas <kk...@apache.org> wrote:
> Hi all,
>
> With the feature-freeze for the release-1.10 already past us, it is
> time to focus a little bit on documenting the new features that the
> community added to this release, and improving the already existing
> documentation based on questions that we see in Flink's mailing lists.
>
> To this end, I have create an umbrella issue
> https://issues.apache.org/jira/browse/FLINK-15273 to monitor the
> pending documentation tasks. This is by no means an exhaustive list of
> the tasks, so feel free to add more.
>
> Having a central place with all these tasks will also allow more
> easily other members of the community, not necessarily people who
> implemented the features, to get involved with the project. This is a
> really helpful way to get in touch with the community and help the
> project reach even greater audiences, as a feature that is not
> documented is non-existent to users.
>
> Thanks a lot,
> Kostas
>
Re: Documentation tasks for release-1.10
Posted by Xintong Song <to...@gmail.com>.
Thank you Kostas.
Big +1 for keeping all the documentation related issues at one place.
I've added the documentation task for resource management.
Thank you~
Xintong Song
On Mon, Dec 16, 2019 at 5:29 PM Kostas Kloudas <kk...@apache.org> wrote:
> Hi all,
>
> With the feature-freeze for the release-1.10 already past us, it is
> time to focus a little bit on documenting the new features that the
> community added to this release, and improving the already existing
> documentation based on questions that we see in Flink's mailing lists.
>
> To this end, I have create an umbrella issue
> https://issues.apache.org/jira/browse/FLINK-15273 to monitor the
> pending documentation tasks. This is by no means an exhaustive list of
> the tasks, so feel free to add more.
>
> Having a central place with all these tasks will also allow more
> easily other members of the community, not necessarily people who
> implemented the features, to get involved with the project. This is a
> really helpful way to get in touch with the community and help the
> project reach even greater audiences, as a feature that is not
> documented is non-existent to users.
>
> Thanks a lot,
> Kostas
>