Github user tillrohrmann commented on a diff in the pull request:

    https://github.com/apache/flink/pull/688#discussion_r30787534
  
    --- Diff: docs/libs/ml/index.md ---
    @@ -20,8 +20,100 @@ specific language governing permissions and limitations
     under the License.
     -->
     
    +The Machine Learning (ML) library for Flink is a new effort to bring 
scalable ML tools to the Flink
    +community. Our goal is is to design and implement a system that is 
scalable and can deal with
    +problems of various sizes, whether your data size is measured in megabytes 
or terabytes and beyond.
    +We call this library FlinkML.
    +
    +An important concern for developers of ML systems is the amount of glue 
code that developers are
    +forced to write [1] in the process of implementing an end-to-end ML 
system. Our goal with FlinkML
    +is to help developers keep glue code to a minimum. The Flink ecosystem 
provides a great setting to
    +tackle this problem, with its scalable ETL capabilities that can be easily 
combined inside the same
    +program with FlinkML, allowing the development of robust pipelines without 
the need to use yet
    +another technology for data ingestion and data munging.
    +
    +Another goal for FlinkML is to make the library easy to use. To that end 
we will be providing
    +detailed documentation along with examples for every part of the system. 
Our aim is that developers
    +will be able to get started with writing their ML pipelines quickly, using 
familiar programming
    +concepts and terminology.
    --- End diff --
    
    Then we should add another section to the outline: "How to contribute" 
where we state this. That's maybe also a good place to put the "how to 
implement a new pipeline operator" with the implicit classes.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to