This was extracted (@ 2024-04-17 22:10) from a list of minutes which have been approved by the Board.
Please Note The Board typically approves the minutes of the previous meeting at the beginning of every Board meeting; therefore, the list below does not normally contain details from the minutes of the most recent Board meeting.

WARNING: these pages may omit some original contents of the minutes.
This is due to changes in the layout of the source minutes over the years. Fixes are being worked on.

Meeting times vary, the exact schedule is available to ASF Members and Officers, search for "calendar" in the Foundation's private index page (svn:foundation/private-index.html).

Pekko

17 Apr 2024 [PJ Fanning / Willem] ¶

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

20 Mar 2024 ¶

Establish the Apache Pekko 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 a toolkit and an ecosystem for building highly
 concurrent, distributed, reactive and resilient applications for Java
 and Scala.

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

 RESOLVED, that the Apache Pekko be and hereby is responsible for
 the creation and maintenance of software related to a toolkit and an
 ecosystem for building highly concurrent, distributed, reactive and
 resilient applications for Java and Scala; and be it further

 RESOLVED, that the office of "Vice President, Apache Pekko" 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
 Pekko Project, and to have primary responsibility for management of the
 projects within the scope of responsibility of the Apache Pekko
 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 Pekko
 Project:

 * Jonas Chapuis <jchapuis@apache.org>
 * Matthew de Detrich <mdedetrich@apache.org>
 * Arnout Engelen <engelen@apache.org>
 * PJ Fanning <fanningpj@apache.org>
 * Sean Glover <seanglover@apache.org>
 * Guobin Li <liguobin@apache.org>
 * Justin Mclean <jmclean@apache.org>
 * Greg Methvin <gregm@apache.org>
 * Alexandru Nedelcu <alexelcu@apache.org>
 * Jean-Baptiste Onofré <jbonofre@apache.org>
 * He Pin <hepin@apache.org>
 * Samuele Resca <samueler@apache.org>
 * Johannes Rudolph <jrudolph@apache.org>
 * Dani Schroeter <dsc@apache.org>
 * Roman Shaposhnik <rvs@apache.org>
 * Ryan Skraba <rskraba@apache.org>
 * Nicolas Vollmar <nvollmar@apache.org>
 * Claude Warren <claude@apache.org>
 * Sheng Wu <wusheng@apache.org>

 NOW, THEREFORE, BE IT FURTHER RESOLVED, that PJ Fanning be appointed to
 the office of Vice President, Apache Pekko, 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.

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

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

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

18 Oct 2023 ¶

Pekko is a toolkit and an ecosystem for building highly concurrent,
distributed, reactive and resilient applications for Java and Scala.

Pekko has been incubating since 2022-10-24.

### Three most important unfinished issues to address before graduating:

 1. Continue v1.0.0 releases. The main modules have v1.0.0 releases but
 some modules are not yet released.
 2. Community Building.
 3. Plan future priorities.

### Are there any issues that the IPMC or ASF Board need to be aware of?

 Nothing of note.

### How has the community developed since the last report?

 Community engagement is pretty low. We're still hoping to increase it now
 that main modules have releases.

### How has the project developed since the last report?

 Main modules have seen releases.

### How would you assess the podling's maturity?
 Please feel free to add your own commentary.

 - [ ] Initial setup
 - [ ] Working towards first release
 - [X] Community building
 - [ ] Nearing graduation
 - [ ] Other:

### Date of last release:

 2023-09-05

### When were the last committers or PPMC members elected?

 2023-03-09 (new committer) -- no new PPMC members added - a recent
 committer invite was rejected by the person we invited

### Have your mentors been helpful and responsive?
 Mentors have been supportive. One issue is that we need some help with
 Incubator release votes. We have one open for 2 weeks and haven't yet
 received 3 votes.

### Is the PPMC managing the podling's brand / trademarks?

 VP, Brand has approved the name (https://s.apache.org/h2cwg)

### Signed-off-by:

 - [X] (pekko) PJ Fanning
    Comments:
 - [X] (pekko) Justin McLean
    Comments:
 - [ ] (pekko) Roman Shaposhnik
    Comments:
 - [ ] (pekko) Wu Sheng
    Comments:
 - [ ] (pekko) Ryan Skraba
    Comments:
 - [ ] (pekko) JB Onofré
    Comments:
 - [ ] (pekko) Claude Warren
    Comments:

### IPMC/Shepherd notes:

 The Podling Project is keep moving, and the project active contributor is
 around 15 for a year.

19 Jul 2023 ¶

Pekko is a toolkit and an ecosystem for building highly concurrent,
distributed, reactive and resilient applications for Java and Scala.

Pekko has been incubating since 2022-10-24.

### Three most important unfinished issues to address before graduating:
 1. Complete the work to mention all 3rd party source in the Pekko code
 base.
 2. Get a milestone release done - at least for the core modules. This
 would facilitate the wider OSS community. We would hope that other OSS
 projects that currently support Akka would look to also support Apache
 Pekko.
 3. Community Building.

### Are there any issues that the IPMC or ASF Board need to be aware of?
 Nothing of note

### How has the community developed since the last report?
 Community engagement is pretty low. We're hoping it will pick up if we
 get a release out.

### How has the project developed since the last report?
 We're close to getting a release done for the core modules.

### How would you assess the podling's maturity?
 Please feel free to add your own commentary.

 - [ ] Initial setup
 - [X] Working towards first release
 - [X] Community building
 - [ ] Nearing graduation
 - [ ] Other:

### Date of last release:
 None yet.

### When were the last committers or PPMC members elected?
 2023-03-09 (new committer) -- no new PPMC members added

### Have your mentors been helpful and responsive?
 There were some knotty issues to discuss about how to manage the license
 headers and similar issues but the conversations were very constructive.

### Is the PPMC managing the podling's brand / trademarks?
 VP, Brand has approved the name (https://s.apache.org/h2cwg)

### Signed-off-by:

 - [X] (pekko) PJ Fanning
    Comments:
 - [X] (pekko) Justin McLean
    Comments:
 - [ ] (pekko) Roman Shaposhnik
    Comments:
 - [ ] (pekko) Wu Sheng
    Comments:
 - [ ] (pekko) Ryan Skraba
    Comments:
 - [ ] (pekko) JB Onofré
    Comments:
 - [ ] (pekko) Claude Warren
    Comments:

### IPMC/Shepherd notes:

19 Apr 2023 ¶

Pekko is a toolkit and an ecosystem for building highly concurrent,
distributed, reactive and resilient applications for Java and Scala.

Pekko has been incubating since 2022-10-24.

### Three most important unfinished issues to address before graduating:

 1. Complete the work on updating the file headers and docs to reflect the
new branding and licensing.
 2. Get the core web site and documentation up.
 3. Get a milestone release done - at least for the core modules. This
would facilitate the wider OSS community. We would hope that other OSS
projects that currently support Akka would look to also support Apache
Pekko.

### Are there any issues that the IPMC or ASF Board need to be aware of?
 Nothing of note

### How has the community developed since the last report?
 We recently added a new committer (Arnout Engelen).

### How has the project developed since the last report?
 Some reasonable progress with getting the code migrated.

### How would you assess the podling's maturity?
 Please feel free to add your own commentary.

 - [X] Initial setup
 - [X] Working towards first release
 - [X] Community building
 - [ ] Nearing graduation
 - [ ] Other:

### Date of last release:

 None yet.

### When were the last committers or PPMC members elected?

 2023-03-09 (new committer) -- no new PPMC members added

### Have your mentors been helpful and responsive?
 There were some knotty issues to discuss about how to manage the license
headers and similar issues but the conversations were very constructive.

### Is the PPMC managing the podling's brand / trademarks?
 * The Pekko project has been widely discussed in Social Media and blogs.
No issues to report.
 * Pekko project did an initial Trademark search to verify the name
availability for software products
 * VP, Brand has approved the name (https://s.apache.org/h2cwg)

### Signed-off-by:

 - [X] (pekko) PJ Fanning
    Comments: Progress being made
 - [X] (pekko) Justin McLean
    Comments:
 - [ ] (pekko) Roman Shaposhnik
    Comments:
 - [ ] (pekko) Wu Sheng
    Comments:
 - [ ] (pekko) Ryan Skraba
    Comments:  The community is forming nicely: good decision-making
together as the project advances.
 - [X] (pekko) JB Onofré
    Comments:  Good progress so far
 - [X] (pekko) Claude Warren
    Comments:

### IPMC/Shepherd notes:

18 Jan 2023 ¶

Pekko is a toolkit and an ecosystem for building highly concurrent,
distributed, reactive and resilient applications for Java and Scala.

Pekko has been incubating since 2022-10-24.

### Three most important unfinished issues to address before graduating:

 1. Complete the work on updating the file headers and docs to reflect the
 new branding and licensing.
 2. Get the core web site and documentation up.
 3. Get a milestone release done - at least for the core modules. This
 would facilitate the wider OSS community. We would hope that other OSS
 projects that currently support Akka would look to also support Apache
 Pekko.

### Are there any issues that the IPMC or ASF Board need to be aware of?

 * Nothing of note.

### How has the community developed since the last report?

 * There are 24 PPMC members. There are no extra committers (i.e. 24
 committers too). A good proportion of these are active.

### How has the project developed since the last report?

 * Very early days.

### How would you assess the podling's maturity?
 Please feel free to add your own commentary.

 - [X] Initial setup
 - [ ] Working towards first release
 - [ ] Community building
 - [ ] Nearing graduation
 - [ ] Other:

### Date of last release:

 * None yet.

### When were the last committers or PPMC members elected?

 * None added since we started the PPMC.

### Have your mentors been helpful and responsive?

 * There were some knotty issues to discuss about how to manage the
 license headers and similar issues but the conversations were very
 constructive.

### Is the PPMC managing the podling's brand / trademarks?

 * The Pekko project has been widely discussed in Social Media and blogs.
 No issues to report.
 * Pekko project did an initial Trademark search to verify the name
 availability for software products
 * VP, Brand has approved the name (https://s.apache.org/h2cwg)

### Signed-off-by:

 - [X] (pekko) PJ Fanning
    Comments: Might be worth laying out a high level set of tasks and
    seeing if we can get volunteers to take on specific tasks.
 - [X] (pekko) Justin McLean
    Comments:
 - [ ] (pekko) Roman Shaposhnik
    Comments:
 - [ ] (pekko) Wu Sheng
    Comments:
 - [X] (pekko) Ryan Skraba
    Comments:  Good starting momentum.
 - [X] (pekko) JB Onofré
    Comments:  Podling is ramping up.
 - [X] (pekko) Claude Warren
    Comments:  Community is beginning to coalesce.  The main issues facing
    the development of the community is the ability to progress with
    development, we have a number of people asking what they can do, but many
    actions blocked by lack of consensus around specific topics.  Now that the
    outstanding legal questions have been answered I think the project will
    begin to progress more rapidly.

### IPMC/Shepherd notes:

--------------------
## SeaTunnel
SeaTunnel is a very easy-to-use ultra-high-performance distributed data
integration platform that supports real-time synchronization of massive
data.

SeaTunnel has been incubating since 2021-12-09.

### Three most important unfinished issues to address before graduating:

 None, we plan to graduate.

### Are there any issues that the IPMC or ASF Board need to be aware of?
 None.

### How has the community developed since the last report?

 The community ushers in 33 new contributors, bringing the total number to
 157 now,300+ pull requests have been merged since SeaTunnel entered the
 last report.

 We participated in the meetup held by ALC India and gained some new
 contributors and users.

### How has the project developed since the last report?
 We released SeaTunnel Zeta, which is the result of six months of hard work
 by the community and an engine specially developed for data
 synchronization.

### How would you assess the podling's maturity?
 Please feel free to add your own commentary.

 - [ ] Initial setup
 - [ ] Working towards first release
 - [ ] Community building
 - [X] Nearing graduation
 - [ ] Other:

### Date of last release:
 Dec 29, 2022

### When were the last committers or PPMC members elected?
 - We elected Guangdong and Liu Li as a committer.
 - We elected Chao Tian and Jun Gao as a PPMC.

### Have your mentors been helpful and responsive?
 Yes, always responsive and helpful. They gave a lot of great suggestions
 on
 community building.

### Is the PPMC managing the podling's brand / trademarks?
 No known issues, but further investigation is still required by the
 SeaTunnel community.
### Signed-off-by:

 - [X] (seatunnel) Zhenxu Ke
    Comments:
 - [X] (seatunnel) William-GuoWei
    Comments:
 - [X] (seatunnel) Lidong Dai
    Comments:
 - [ ] (seatunnel) Ted Liu
    Comments:
 - [ ] (seatunnel) Kevin Ratnasekera
    Comments:
 - [ ] (seatunnel) JB Onofré
    Comments:
 - [ ] (seatunnel) Willem Ning Jiang
    Comments:

### IPMC/Shepherd notes: