Apache Logo
The Apache Way Contribute ASF Sponsors

Formal board meeting minutes from 2010 through present. Please Note: The board typically approves minutes from one meeting during the next board meeting, so minutes will be published roughly one month later than the scheduled date. Other corporate records are published, as is an alternate categorized view of all board meeting minutes.

2017 | 2016 | 2015 | 2014 | 2013 | 2012 | 2011 | 2010 | 2009 | 2008 | 2007 | 2006 | 2005 | 2004 | 2003 | 2002 | 2001 | 2000 | 1999 | Pre-organization meetings

Flink

15 Mar 2017 [Stephan Ewen / Isabel]

Report was filed, but display is awaiting the approval of the Board minutes.

21 Dec 2016 [Stephan Ewen / Brett]

DESCRIPTION

Apache Flink is a distributed data streaming system for batch and streaming
data analysis on top of a streaming dataflow engine. Flink's stack contains
functional batch and streaming analysis APIs in Java and Scala and libraries
for various use cases.

Flink interacts and integrates with several Apache projects in the broader
ecosystem of data storage and computing, such as Apache Beam (incubating),
Hadoop, Kafka, HBase, Cassandra, Bahir, and others.

ISSUES

  - There are no issues that require board attention.

STATUS AND ACTIVITY

  - The Flink community is heading towards the 1.2 release, which is the
    biggest release so far. The community decided to add backwards
    compatibility of "application state" from this release on (in addition
    to API compatibility since version 1.0.0).

    Releasing version 1.2 is also the blocker for merging a large feature
    branch on resource management that many contributors have worked on
    over the last months.

  - The community is also in the progress of releasing the bug fix release
    1.1.4.  This release is the result of a major effort with large
    production users to address robustness issues found in such
    installations.

  - There will be 'Flink Forward' conferences in San Francisco (April 2017)
    and Berlin (September 2017). The PMC will be in touch with the organizers
    to make sure the event is endorsed by the Flink community and respects
    the Apache trademark guidelines.

  - 'data Artisans' conducted a survey among Flink users and contributors,
    with the goal to share the results with the community.  The survey is
    currently being evaluated, results to be shared soon.

  - In the previous quarter, the Flink community started working together
    with the Apache Bahir community. The first connectors are now exclusively
    managed by the Bahir project, and not part of the Flink project any more.

  - Several community members have started to voice concerns that the Flink
    code base is getting very intensive to build and test. Individual
    discussions in these threads suggested to kick of a proper discussion
    after the 1.2 release is out.

COMMUNITY

There was no new PMC addition since the last report.
The latest PMC addition was July 2nd, 2015 (Maximilian Michels)

No new committers have been added since the last report.
The last committer addition was Tzu-Li (Gordon) Tai on August, 26th, 2016.

Flink currently has 24 committers and 16 PMC members.

RELEASES

The following releases were made since the last board report:

 → 1.1.3 was released on October, 12th, 2016

ACTIVITY ON JIRA / MAILING LISTS

Both user@f.a.o and dev@f.a.o lists are quite active, with mails getting
answered by a mix of committers and non-committers.

JIRA is even more active than in the three month period before
(730 JIRA tickets created, 545 JIRA tickets resolved)

21 Sep 2016 [Stephan Ewen / Mark]

DESCRIPTION

Apache Flink is a distributed data streaming system for batch and streaming
data analysis on top of a streaming dataflow engine.  Flink's stack contains
functional batch and streaming analysis APIs in Java and Scala and libraries
for various use cases.

Flink interacts and integrates with several Apache projects in the broader
ecosystem of data storage and computing, such as Apache Hadoop, Kafka, HBase,
Cassandra.

ISSUES

  - There are no issues that require board attention.

STATUS AND ACTIVITY

  - The Flink community started working together with the Apache Bahir
    community.  Some of the streaming connectors from Flink are now maintained
    under the Bahir umbrella. This allows for faster independent release
    cycles and more lightweight processes to add new connectors.

    We discussed as an alternative to create an independent subproject of
    Flink, but the community favored to work with Bahir. The Bahir community
    was very open to the idea and it looks like both committers and
    contributors are quite happy with the result.

  - The second edition of the "Flink Forward" conference took place in Berlin
    from September 12th to 14th. It featured a series of talks about use
    cases, applications, and in-depth technical discussions, as well as a
    training session. About 350 people attended.

    A good amount of Flink committers were at the conference as well and
    participated with talks and discussions about various aspects of the
    system.

  - The community adopted the "Improvement Proposal" concept from the Kafka
    community, under the name "FLIP" = "Flink Improvement Proposal", and uses
    the Wiki for that.

    Improvement proposals are proposed major changes with thorough design
    docs. Once discussed and approved (via mailing list), they are usually
    broken down into JIRA issues which are linked.

    We found that this complements JIRA and the mailing lists, because (1)
    there is one place where interested users and contributors can find an
    overview of all major additions/changes that have been proposed and are
    pending, and (2) the Wiki document sums up the final conceptual designs
    nicely while JIRA tracks the implementation aspects.

  - In the previous quarter, the Flink community introduces the concept of
    "shepherds".  Shepherds are experts/trackers of components, but have no
    authoritative power.

    The concept seems to not have discouraged anyone to look across component
    boundaries, and occasionally, it has helped for threads to be picked up.
    Overall, however, it has not been picked up as much as hoped for. Maybe it
    will be picked up better over time (it might simply take a while until
    everybody intuitively adopts such able concept). For now, it does not seem
    to have any downsides.

COMMUNITY

There was no new PMC addition since the last report.
The latest PMC addition was July 2nd, 2015 (Maximilian Michels)

Tzu-Li (Gordon) Tai was added as a committer on August, 26th, 2016.

Flink currently has 24 committers and 16 PMC members.

RELEASES

The following releases were made since the last board report:

 - 1.1.0 was released on August, 4th, 2016
 - 1.1.1 was released on August, 10th, 2016
 - 1.1.2 was released on September, 5th, 2016

ACTIVITY ON JIRA / MAILING LISTS

Development speed is fast, we are seeing more thorough use of
JIRA, more fine grained issues, more discussion.

15 Jun 2016 [Stephan Ewen / Bertrand]

DESCRIPTION

Apache Flink is a distributed data streaming system for batch and streaming
data analysis on top of a streaming dataflow engine.  Flink's stack contains
functional batch and streaming analysis APIs in Java and Scala and libraries
for various use cases.  Flink interacts and integrates with several Apache
projects in the broader ecosystem of technology around Apache Hadoop and
Apache Kafka.

ISSUES

 - There are no issues that require board attention.

STATUS AND ACTIVITY

 - Shane informed us that the "Apache Flink" trademark has been approved,
   but still needs to be officially issued.

 - Since the 1.0 release, the community growth seems to have accelerated.

 - As a response, the community decided to promote a "shepherd" concept
   within the community.  Every component (like API, distributed runtime,
   library, ...) has one or more shepherds, which are experts of that
   component, and act as people to contact for issues and questions that
   cannot be answered by the broad community.

   We decided to go with the name "shepherd", rather than "maintainer",
   because it is a non-authoritative role, but a guiding role.

   Shepherds are mostly committers, but also some non-committers volunteered.
   This looks like a nice way to identify prospects for future committers.

   The shepherds should also feel responsible for driving/moderating (not
   deciding) the resolution of community contributions.

   We are still in the phase of trying this out, hope to be able to report
   results in the next board report.

 - There will be a conference on Apache Flink and Stream Processing in
   September called "Flink Forward" (http://flink-forward.org/). The
   organizers are in touch with the PMC. The program committee will be five
   people from the Apache stream processing ecosystem.

 - Flink has been integrated with more Apache projects, like BigTop (done by
   the Flink and BigTop community) and Mahout (mostly done by the Mahout
   community).

 - Since the 1.0 release, the community brought measures in place to check
   binary backwards compatibility.

 - So far, the Flink community has accepted the majority of contributions,
   such as for connectors for integration with external systems.  We have,
   however, seen quite a few times the contributors were not interested in
   following up and maintaining the contribution, and a tough maintenance job
   was imposed on the community for barely used and unfamiliar code.

   As a results, there are discussions about encouraging contributors to
   create individual independent projects for such connectors, if there are
   no additional people in the community that would back the contribution.

COMMUNITY

There was no new PMC addition since the last report.

The latest PMC addition was July 2nd, 2015 (Maximilian Michels)
The latest committer addition was on March, 8th, 2016 (Greg Hogan)

Flink currently has 23 committers and 16 PMC members.

RELEASES

The following releases were made since the last board report:

 - 1.0.1 was released on Tue Apr 05 2016
 - 1.0.2 was released on Fri Apr 22 2016
 - 1.0.3 was released on Wed May 11 2016

ACTIVITY ON JIRA / MAILING LISTS

Development speed continues to be healthy.

 - 439 JIRA tickets created in the last 3 months
 - 318 JIRA tickets closed/resolved in the last 3 months

Compared to previous quarters, dev mailing list activity is increasing
a bit, but user mailing list activity is increasing a lot.

 - dev@flink.apache.org:
    - 381 subscribers (up 58 in the last 3 months):
    - 1396 emails sent to list (1176 in previous quarter)

 - user@flink.apache.org:
    - 533 subscribers (up 119 in the last 3 months):
    - 2211 emails sent to list (1368 in previous quarter)

16 Mar 2016 [Stephan Ewen / Greg]

DESCRIPTION

Flink is a distributed data streaming system for batch and streaming data
analysis on top of a streaming dataflow engine.
Flink's stack contains functional batch and streaming analysis APIs in
Java and Scala and libraries for various use cases.
Flink interacts and integrates with several Apache projects in the broader
ecosystem of technology around Apache Hadoop and Apache Kafka.


ISSUES

 - There are no issues that require board attention.


STATUS AND ACTIVITY

 - The recent months where dominated by the efforts to release Flink 1.0, which
   was officially announced by the ASF on March, 8th.
 - The 1.0 release was themed around backwards compatibility, and operational
   features.  A complex event processing library was added as well.
 - A roadmap for the first half of 2016 has been published by the community on
   the mailing lists end of December.
 - Flink seems to get a decent amount of interest, several upcoming conference
   talks (e.g., Strata, Hadoop Summit, Kafka Summit, OSCon, ApacheCon, and
   several Meetups)
 - The latest release (1.0.0) saw slightly fewer contributors (64 people) than
   the previous one (0.10.0 had 79 contributors), because some features and
   contributions were held off / delayed in order to establish the 1.0
   relevant tools (like compatibility checks).


COMMUNITY

 - There was no new PMC addition since the last report.
   The latest PMC addition was July 2nd, 2015 (Maximilian Michels)

 - There were two committers added since the last report
    - ChengXiang Li was added on January, 20th, 2016
    - Greg Hogan was added on March, 8th, 2016

Flink currently has 23 committers and 16 PMC members


RELEASES

The following releases were made since the last board report:

 - 0.10.2 was released on February, 10th, 2016
 - 1.0.0 was released on March, 8th, 2016


ACTIVITY ON JIRA / MAILING LISTS

Development speed continues to be healthy.

 - 440 JIRA tickets created in the last 3 months
 - 374 JIRA tickets closed/resolved in the last 3 months


Compared to previous quarters, there is a bit of a shift in mailing list
activity from the dev list to the users list.

 - dev@flink.apache.org:
    - 323 subscribers (up 68 in the last 3 months):
    - 1266 emails sent to list (1617 in previous quarter)

 - user@flink.apache.org:
    - 414 subscribers (up 97 in the last 3 months):
    - 1528 emails sent to list (1225 in previous quarter)

 - issues@flink.apache.org:
    - 54 subscribers (up 9 in the last 3 months):
    - 8794 emails sent to list (11290 in previous quarter)

16 Dec 2015 [Stephan Ewen / Chris]

DESCRIPTION

Flink is a distributed data streaming system for batch and streaming data
analysis on top of a streaming dataflow engine.
Flink's stack contains functional batch and streaming analysis APIs in
Java and Scala and libraries for various use cases.

Flink interacts and integrates with several Apache projects in the broader
ecosystem of technology around Hadoop.


ISSUES

 - There are no issues that require board attention.


STATUS AND ACTIVITY

 - The community has released version 0.10, which had a strong focus on
   hardening the data streaming capabilities and adding major features like
   master high availability.

 - The community is actively working towards a version 1.0 and discussing which
   APIs and components will be maintained backwards compatible.

 - There was a 2 day conference on Flink on Berlin in October, with
   community-selected talks, which had attracted around 250 participants.

 - The Flink community is in a good growing phase. The latest release had
   contributions from 79 people across many organizations.


COMMUNITY

 - The newest PMC member was added July 2nd, 2015 (Maximilian Michels)
 - The newest committer was added August 31st 2015 (Matthias J. Sax)

Flink currently has 21 committers and 16 PMC members


RELEASES

The following releases were made since the last board report:

 - 0.10.1 was released on Thu Nov 26 2015
 - 0.10.0 was released on Fri Nov 13 2015


ACTIVITY ON JIRA / MAILING LISTS

 - 506 JIRA tickets created in the last 3 months
 - 434 JIRA tickets closed/resolved in the last 3 months

 - dev@flink.apache.org:
    - 249 subscribers (up 35 in the last 3 months):
    - 1708 emails sent to list (1729 in previous quarter)

 - news@flink.apache.org:
    - 105 subscribers (up 18 in the last 3 months):
    - 1 emails sent to list (2 in previous quarter)

 - user@flink.apache.org:
    - 308 subscribers (up 73 in the last 3 months):
    - 1340 emails sent to list (1176 in previous quarter)

 - issues@flink.apache.org:
    - 42 subscribers (up 4 in the last 3 months):
    - 12105 emails sent to list (10466 in previous quarter)

16 Sep 2015 [Stephan Ewen / Chris]

DESCRIPTION

Flink is a distributed data streaming system for batch and streaming data
analysis on top of a streaming dataflow engine.
Flink's stack contains functional batch and streaming analysis APIs in
Java and Scala and libraries for various use cases.

Flink interacts and integrates with several Apache projects, including
Hadoop (YARN, HDFS, MapReduce), Kafka, HBase, Zeppelin, MRQL, Tez, Orc,
HCatalog.


ISSUES

 - There are no issues that require board attention.


STATUS AND ACTIVITY

 - The community is working towards version 0.10, which contains several new
   major features, like an overhaul of the streaming API, high availability.
   The community aims to graduate the streaming API out of beta status and make
   it stable.

 - The question about a releasing version 1.0 has been brought up in the
   community, as APIs and operational features mature.

 - Flink is seeing an increasing number of users and contributors, and the
   community is discussing ways to handle the load, make pull requests and
   patches more efficient to review, and to guide contributors towards
   making productive contributions. Current efforts include more precise
   guidelines and automated QA technology.

 - Interest in Flink is growing, we are seeing more and more meetup groups
   springing up, as well as a 2-day conference on Flink in October in Berlin.

 - The community is looking to diversify the technical expertise.
   Right now, most people contribute to libraries, APIs, tools, integration.
   We would like to get more people knowledgeable about the core. Efforts in
   talks and documentation are currently happening.


COMMUNITY

 - The project has one new PMC member since the last report
   (Maximilian Michels was added July 2nd, 2015)

 - The project has 4 new committers since the last board report

   - Andra Lungu was added as a committer on June 08th, 2015
    (voted in before last report, accepted and added since)
   - Chiwan Park was added as a committer on June 22 2015
   - Chesnay Schepler was added as a committer on Tue, August 11th, 2015
   - Matthias J. Sax was added as a committer on Mon, August 31st 2015

 - Flink currently has 21 committers and 16 PMC members


RELEASES

The following releases were made since the last board report

 - 0.9.0 was released on June 24th, 2015
 - 0.9.1 was released on August 31st, 2015


MAILING LISTS

 - dev@flink.apache.org:
    - 214 subscribers (up 40 in the last 3 months):
    - 1661 emails sent to list (1956 in previous quarter)

 - user@flink.apache.org:
    - 233 subscribers (up 74 in the last 3 months):
    - 1183 emails sent to list (756 in previous quarter)

 - issues@flink.apache.org:
    - 40 subscribers (up 2 in the last 3 months):
    - 10271 emails sent to list (8179 in previous quarter)


JIRA ACTIVITY

 - 446 JIRA tickets created in the last 3 months
 - 350 JIRA tickets closed/resolved in the last 3 months

17 Jun 2015 [Stephan Ewen / Brett]

DESCRIPTION

Flink is a distributed data analytics system for batch and streaming data
analysis on top of a streaming dataflow engine.
Flink's stack contains functional batch and streaming analysis APIs in
Java and Scala and libraries for various use cases.
Flink is a citizen of the Hadoop ecosystem and interacts
with HDFS, YARN, MapReduce, HBase, and Tez.


ISSUES

There are no issues that require board attention.


STATUS

The Flink community is preparing the release of version 0.9, which marks
the biggest additions to Flink since the project creation. The system
is adding strong functionality for stream processing and libraries
for various use cases.

Flink has integrated with various other Apache projects (Tez, Zeppelin, Samoa).

The community is growing, we see increasingly articles and meetups on Flink
appearing.


COMMUNITY

* Last committer was voted in May 30th, 2015 (Andra Lungu)

* Vote to add Chiwan Park as committer is happening as of writing this report.

* Last PMC member was added December 17, 2014, when all committers and a subset
  of the mentors formed the project Flink PMC during graduation.

* Project has currently 18 committers and 15 PMC members.

* The project community is active (May: 274 messages in user mailing list,
  491 messages in dev mailing list, 2758 messages in issues mailing list)

* JIRA reports 194 new issues and 152 solved issues in the last 30 days


COMMUNITY OBJECTIVES

* Growing the user community further via talks and meetups and integration with
  other projects. The Flink PMC plans to organize a track at the Apache Big
  Data conference.

* Integration with other Apache projects is continuously happening:
  - Apache Zeppelin (incubating) has added support for Flink
  - Apache Samoa (incubating) integration is a pending patch
  - Apache Tez integration is part of the next release.
  - Integration with ORC and HCatalogue are work in progress.

RELEASES

 * Date of last release: April 13th, 2015 (version 0.9.0-milestone-1)
 * Release candidate creation for 0.9.0 is happening as of writing this report.

18 Mar 2015 [Stephan Ewen / Doug]

DESCRIPTION

Flink is a distributed data analytics system for expressive, declarative,
and efficient batch and streaming data processing and analysis.
Flink's stack contains functional batch and streaming analysis APIs in
Java and Scala, a type analysis and serialization framework, a library of
out-of-core enabled operators, distributed task scheduling, and a data
streaming network subsystem.
Flink is a citizen of the Hadoop ecosystem and interacts
with HDFS, YARN, MapReduce, HBase, and Tez.


ISSUES

There are no issues that require board attention.


STATUS

The Flink community is working towards to next version (0.9) which
builds Flink into a proper hybrid batch/streaming system with hardened
guarantees.

The community is growing, we see increased interest in contributions
from companies that were not previously involved with Flink.


COMMUNITY

* Last committer was voted in March 5th, 2015 (Paris Carbone)

* Last PMC member was added December 17, 2014, when all committers and a subset
  of the mentors formed the project Flink PMC during graduation.

* Project has currently 17 committers and 15 PMC members.

* The project community is active (February: 123 messages in user mailing list,
  545 messages in dev mailing list, 1980 messages in issues mailing list)

* JIRA reports 185 new issues and 120 solved issues in the last 30 days


COMMUNITY OBJECTIVES

* Growing the user community further. The community will give talks at
  various meetups and conferences, including Hadoop Summit, Strata, ApacheCon.

* Integration with other Apache projects is work in progress.
  Patches that integrate Flink with Tez and SAMOA are available.


RELEASES

 * Date of last release: February 19th, 2015 (version 0.8.1)

18 Feb 2015 [Stephan Ewen / Rich]

DESCRIPTION

Flink is a distributed Big Data system for expressive, declarative,
and efficient batch and streaming data processing and analysis.
Flink’s stack contains functional batch and streaming analysis APIs in
Java and Scala, a type analysis and serialization framework, a library of
out-of-core enabled operators, distributed task scheduling, and a data
streaming network subsystem.
Flink is a citizen of the Hadoop ecosystem and interacts
with HDFS, YARN, MapReduce, HBase, and Tez.


ISSUES

There are no issues that require board attention.


STATUS

Flink graduated in December from the Incubator. The transition is complete
by now, the first release and committer addition as a TLP have happened.

The community is growing, judging from mailing list activity, number of
meetup group talks, bug reports, etc


COMMUNITY

* Last committer was voted in February 6th, 2015 (Maximilian Michels)

* Last PMC member was added December 17, 2014, when all committers and a subset
  of the mentors formed the project Flink PMC during graduation.

* The project community is active (February 1st to 11th: 57 messages in user
  mailing list, 191 messages in dev mailing list, 244 messages in commits
  list, 887 messages in issues mailing list)

* Community is actively developing the software. JIRA reports 139 new
  issues and 121 solved issues in the last 30 days

* The issue of trademarking Flink is still ongoing. The process has started
  (same as last month)


COMMUNITY OBJECTIVES

* Growing the user community further

* Integration with other Apache projects is work in progress.
  As of the last 30 days specifically SAMOA (incubating) and Tez (per mailing
  lists).


RELEASES

 * Date of last release: January 19th, 2015 (version 0.8.0)
 * Candidate for release version 0.8.1 has been created (February 10th).

21 Jan 2015 [Stephan Ewen / Sam]

DESCRIPTION
-----------
Flink is a distributed Big Data system for expressive, declarative,
and efficient batch and streaming data processing and analysis.

Flink’s stack contains functional batch and streaming analysis APIs in
Java and Scala, a type analysis and serialization framework, a library of
out-of-core enabled operators, distributed task scheduling, and a data
streaming network subsystem.

Flink is a citizen of the Hadoop ecosystem and interacts with HDFS, YARN,
MapReduce, HBase, and Tez.


ISSUES
------
There are no issues that require board attention.


STATUS
------
Flink recently graduated in December from the Incubator. The infrastructure
for becoming a top-level project has been set up, the renaming of the mailing
lists is partially done (as of the time of writing this report).

The Apache press team announced the graduation on January 12th. There is a
decent media echo.


COMMUNITY
---------
* Last committer was voted in November 20th, 2014 (Timo Walther)

* When graduating to a TLP (December 17, 2014), all committers and
  a subset of the mentors formed the project Flink PMC

* The project community is active and growing
 (January 1st to 11th: 25 messages in user mailing list,
  180 messages in dev mailing list, 126 messages in commits list,
  314 messages in issues mailing list)

* Community is actively developing the software.
  JIRA reports 72 new issues and 54 solved issues in the last 30 days

* The issue of trademarking Flink is still ongoing. The process has started.

* December and January have various Flink-related meetups (sample below):
 - December 11th – Netherlands Hadoop User Group
 - January 21st – Bay Area Hadoop User Group
 - January 28 – Bay Area Tez User Group
 - January 28th – Berlin Flink User Group


COMMUNITY OBJECTIVES
--------------------
* Defining and agreeing upon a new 6-12 months roadmap (currently discussed
  on the mailing lists)

* Growing the user community further

* As a special case of the community growth, Flink would like to interact
  stronger with other Apache projects (TLP and Incubator). Roadmap draft
  includes integrating for example with Zeppelin, SAMOA, Tez, and Mahout.
  Integration with Hive is under discussion.


RELEASES
--------
* Date of last release: Oct 26th (0.7-incubating),
  while Flink was still in the incubator.

* Release candidates for version 0.8 have been created
  (RC1 rejected by PMC vote, RC2 validation happening as of the
   time of writing this report)

17 Dec 2014

Establish the Apache Flink Project

 WHEREAS, the Board of Directors deems it to be in the best
 interests of the Foundation and consistent with the
 Foundation's purpose to establish a Project Management
 Committee charged with the creation and maintenance of
 open-source software, for distribution at no charge to
 the public, related to fast and reliable large-scale data
 analysis with focus on programmability, optimizability,
 efficiency, and combination of batch and streaming data
 processing.

 NOW, THEREFORE, BE IT RESOLVED, that a Project Management
 Committee (PMC), to be known as the "Apache Flink Project",
 be and hereby is established pursuant to Bylaws of the
 Foundation; and be it further

 RESOLVED, that the Apache Flink Project be and hereby is
 responsible for the creation and maintenance of software
 related to fast and reliable large-scale data analysis
 with focus on programmability, optimizability, efficiency,
 and combination of batch and streaming data processing;
 and be it further

 RESOLVED, that the office of "Vice President, Apache Flink" be
 and hereby is created, the person holding such office to
 serve at the direction of the Board of Directors as the chair
 of the Apache Flink Project, and to have primary responsibility
 for management of the projects within the scope of
 responsibility of the Apache Flink Project; and be it further

 RESOLVED, that the persons listed immediately below be and
 hereby are appointed to serve as the initial members of the
 Apache Flink Project:

    * Márton Balassi            <mbalassi@apache.org>
    * Ufuk Celebi               <uce@apache.org>
    * Stephan Ewen              <sewen@apache.org>
    * Gyula Fora                <gyfora@apache.org>
    * Alan Gates                <gates@apache.org>
    * Fabian Hueske             <fhueske@apache.org>
    * Vasiliki Kalavri          <vasia@apache.org>
    * Aljoscha Krettek          <aljoscha@apache.org>
    * Robert Metzger            <rmetzger@apache.org>
    * Till Rohrmann             <trohrmann@apache.org>
    * Henry Saputra             <hsaputra@apache.org>
    * Sebastian Schelter        <ssc@apache.org>
    * Kostas Tzoumas            <ktzoumas@apache.org>
    * Timo Walther              <twalthr@apache.org>
    * Daniel Warneke            <warneke@apache.org>

 NOW, THEREFORE, BE IT FURTHER RESOLVED, that Stephan Ewen
 be appointed to the office of Vice President, Apache Flink, to
 serve in accordance with and subject to the direction of the
 Board of Directors and the Bylaws of the Foundation until
 death, resignation, retirement, removal or disqualification,
 or until a successor is appointed; and be it further

 RESOLVED, that the initial Apache Flink PMC be and hereby is
 tasked with the creation of a set of bylaws intended to
 encourage open development and increased participation in the
 Apache Flink Project; and be it further

 RESOLVED, that the Apache Flink Project be and hereby
 is tasked with the migration and rationalization of the Apache
 Incubator Flink podling; and be it further

 RESOLVED, that all responsibilities pertaining to the Apache
 Incubator Flink podling encumbered upon the Apache Incubator
 Project are hereafter discharged.

 Special Order 7B, Establish the Apache Flink Project , was
 approved by Unanimous Vote of the directors present.

19 Nov 2014

Flink is an open source system for expressive, declarative, fast, and
efficient data analysis. Flink combines the scalability and programming
flexibility of distributed MapReduce-like platforms with the efficiency, out-
of-core execution, and query optimization capabilities found in parallel
databases. Flink was originally known as Stratosphere when it entered the
Incubator.

Flink has been incubating since 2014-04-14.

Three most important issues to address in the move towards graduation:

 1. Community growth


Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?

  None

How has the community developed since the last report?

 Two new committers were voted into the project: Márton Balassi and Gyula
 Fóra. There were presentations on Flink at the VLDB keynote, a meetup in
 Stockholm (more than 150 participants), one in Pasadena, CA and two
 meetups in Berlin.  There are upcoming talks in Palo Alto, CA and at the
 Apache Con in Budapest. The dev@flink mailing list had more than 300
 messages on average in the last months. The user@ list 124 in October.

How has the project developed since the last report?

 Flink has released two major versions (0.6-incubating and 0.7-incubating)
 in the last three months. (There was also a minor bugfix release for the
 0.6-incubating release). The Apache MRQL (incubating) project has added
 support for running programs with Flink. There is an effort within the
Flink community to integrate with Apache Tez.

Date of last release:

 2014-10-26

When were the last committers or PMC members elected?

  2014-09-06


Signed-off-by:

 [ ](flink) Sean Owen
 [x](flink) Ted Dunning
 [ ](flink) Owen O'Malley
 [X](flink) Henry Saputra
 [ ](flink) Ashutosh Chauhan
 [X](flink) Alan Gates

20 Aug 2014

Flink is an open source system for expressive, declarative, fast, and
efficient data analysis. Flink combines the scalability and programming
flexibility of distributed MapReduce-like platforms with the efficiency,
out-of-core execution, and query optimization capabilities found in parallel
databases. Flink was originally known as Stratosphere when it entered the
Incubator.

Flink has been incubating since 2014-04-14.

Three most important issues to address in the move towards graduation:

 1. First incubator release
 2. Continue with community growth
 3. More comfortable with ASF policies and processes

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?

 None

How has the community developed since the last report?

 One new committer has been accepted into the project.
 We received a large external code contribution and pending reviews.
 The project started a bi-weekly Hangout.

How has the project developed since the last report?

 The project has moved all infrastructure to Apache,
 the source code has been renamed to the "org.apache.flink" namespace.
 We are finalizing the preparations for the first Incubator release

Date of last release:

 2014-05-31 (no incubator release yet)

When were the last committers or PMC members elected?

 2014-07-10

Signed-off-by:

 [ ](flink) Sean Owen
 [ ](flink) Ted Dunning
 [ ](flink) Owen O'Malley
 [X](flink) Henry Saputra
 [ ](flink) Ashutosh Chauhan

16 Jul 2014

Flink is an open source system for expressive, declarative, fast, and
efficient data analysis. Flink combines the scalability and programming
flexibility of distributed MapReduce-like platforms with the efficiency,
out-of-core execution, and query optimization capabilities found in parallel
databases. Flink was originally known as Stratosphere when it entered the
Incubator.

Flink has been incubating since 2014-04-14.

Three most important issues to address in the move towards graduation:

 1. The new name ("Flink") has still not been confirmed by the trademark
    team.
 2. Setup of release infrastructure and first release
 3. Continue with community growth

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
of?

 None.

How has the community developed since the last report?

 Two presentations (Meetup in Nice by a committer, one in Budapest by a
 contributor), new users are showing up on the mailing list and on JIRA.

How has the project developed since the last report?

 Most of the infrastructure setup has been done. Users start using the new
 mailing lists.
 In the last month, 21 authors have pushed 120 commits to master. On
 master, 910 files have changed and there have been 74,313 additions and
 37,094 deletions.

Date of last release:

 2014-05-31 (no incubator release yet)

When were the last committers or PMC members elected?

 None.


Signed-off-by:

 [ ](flink) Sean Owen
 [ ](flink) Ted Dunning
 [ ](flink) Owen O'Malley
 [X](flink) Henry Saputra
 [ ](flink) Ashutosh Chauhan
 [X](flink) Alan Gates

18 Jun 2014

Flink is an open source system for expressive, declarative, fast, and
efficient data analysis. Flink combines the scalability and programming
flexibility of distributed MapReduce-like platforms with the efficiency,
out- of-core execution, and query optimization capabilities found in
parallel databases.

Flink has been incubating since 2014-04-14.

Three most important issues to address in the move towards graduation:

 1. Infrastructure setup (git, JIRA, mailing list renaming)
 2. Release
 3. Build an ASF community

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?

 None.

How has the community developed since the last report?

 The community still "lives" outside the ASF since the infrastructure is
 not ready.

 Two new contributors opened pull requests since the last report.

How has the project developed since the last report?

 The community has voted for a new name, so the project is moving away from
 its old name "Stratosphere" to the new one: "Flink".

 We are still waiting for Infra to rename the mailing list, to create a
 JIRA (blocked by the mailing list) and create a Git repository (blocked by
 the SGA (which we already provided)).

 We released a new major release (0.5) outside the ASF.

Date of last release:

 2014-05-31 (no incubator release yet)

When were the last committers or PMC members elected?

 Only initial committers.

Signed-off-by:

 [ ](flink) Sean Owen
 [X](flink) Ted Dunning
 [ ](flink) Owen O'Malley
 [X](flink) Henry Saputra
 [ ](flink) Ashutosh Chauhan
 [X](flink) Alan Gates

Shepherd/Mentor notes:

 Konstantin Boudnik (cos):

   Project dev@ list has healthy traffic.  Some of the mentors are active
   on the list and helping community. No visible issues.