This was extracted (@ 2025-10-29 19: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.
ASF Members may have access to a
private draft
WARNING: these pages may omit some original contents of the minutes.
Apache Otava (incubating) performs statistical analysis of performance
test results stored in CSV files, PostgreSQL, BigQuery, or Graphite
database. It finds change-points and notifies about possible performance
regressions.
A typical use-case of otava is as follows:
* A set of performance tests is scheduled repeatedly, such as after each
commit is pushed.
* The resulting metrics of the test runs are stored in a time series
database (Graphite) or appended to CSV files.
* Otava is launched by a Jenkins/Cron job (or an operator) to analyze the
recorded metrics regularly.
* Otava notifies about significant changes in recorded metrics by
outputting text reports or sending Slack notifications.
* Otava is capable of finding even small, but persistent shifts in metric
values, despite noise in data. It adapts automatically to the level of
noise in data and tries to notify only about persistent, statistically
significant changes, be it in the system under test or in the
environment.
* Otava has been incubating since 2024-11-27. Otava entered Incubation as
Hunter. The project name Otava was approved by VP Brand 2025-02-09.
### Three most important unfinished issues to address before graduating:
1. Upgrade to support the latest versions of Python, including upgrading
to
the latest signal-processing-algorithms library.
2. Do more releases, so that it is a routine, repeatable process.
3. Grow the community and ultimately vote to admit new committers and PPMC
members. Do more publicity around the releases and the project in general.
This is an item where we certainly hope to see new contributors.
### Are there any issues that the IPMC or ASF Board need to be aware of?
No.
### How has the community developed since the last report?
We've seen engagement in the mailing lists and/or PRs from four out of
five of the project's committers since the last report.
Three new contributors have reached out via the mailing list and/or
GitHub, showing interest in the project and starting work on open issues.
### How has the project developed since the last report?
* We have completed our first release.
* Updated our build system to use `uv` instead of `poetry`.
* Changed our configuration management for ease of use.
* Starting the work to migrate to modern python versions.
### How would you assess the podling's maturity?
* [ ] Initial setup
* [ ] Working towards first release
* [X] Community building
* [ ] Nearing graduation
* [ ] Other:
A self review based on https://s.apache.org/727vc
* Code 5/5
* Licenses and Copyright: 5/5
* Releases: 4/5
* Quality: 5/5
* Community: 7/7
* Consensus: 4/5 (Missing: CS10)
* Independence: 2/2
* Brand: 4/4
### Date of last release:
The last release was on July 17, 2025.
### When were the last committers or PPMC members elected?
The major contributors during the past 8 years were listed as PPMC members
in the project application phase. We have not elected any new members after
that.
### Have your mentors been helpful and responsive?
Our mentors have been helpful and responsive.
Nothing is falling through the cracks.
### Is the PPMC managing the podling's brand / trademarks?
This isn't yet an issue, as the new name of the project is quite unknown
yet.
### Signed-off-by:
- [X] (otava) Dave Fisher
Comments:
- [ ] (otava) Enrico Olivelli
Comments:
- [ ] (otava) Lari Hotari
Comments:
- [ ] (otava) Mick Semb Wever
Comments:
### IPMC/Shepherd notes:
Apache Otava (incubating) performs statistical analysis of performance test
results stored in CSV files, PostgreSQL, BigQuery, or Graphite database. It
finds change-points and notifies about possible performance regressions.
A typical use-case of otava is as follows:
* A set of performance tests is scheduled repeatedly, such as after each
commit is pushed.
* The resulting metrics of the test runs are stored in a time series
database (Graphite) or appended to CSV files.
* Otava is launched by a Jenkins/Cron job (or an operator) to analyze the
recorded metrics regularly.
* Otava notifies about significant changes in recorded metrics by
outputting text reports or sending Slack notifications.
* Otava is capable of finding even small, but persistent shifts in metric
values, despite noise in data. It adapts automatically to the level of
noise in data and tries to notify only about persistent, statistically
significant changes, be it in the system under test or in the environment.
Otava has been incubating since 2024-11-27. Otava entered Incubation as
Hunter.
The project name Otava was approved by VP Brand 2025-02-09.
### Three most important unfinished issues to address before graduating:
1. Publish the first release under the new name.
(https://github.com/apache/otava/issues/51) The first release was under
voting as the deadline to submit this report to the Incubator PMC passed.
2. Publish the existence of Apache Otava (Incubating), and our first
release.
3. Nurture a growing community that includes also new
members/contributors that have not used Otava (Hunter) before we joined
Apache Incubator
4. Make more releases. In particular, the first release intentionally is
not that different from what already existed before we became an Incubator
project. It is merely a change of project name and ownership (ASF) and the
license, and a re-union of many forks into a clear upstream project. For
future releases we hope to modernize python version, build tooling, and of
course add new features and integrations.
### Are there any issues that the IPMC or ASF Board need to be aware of?
Nothing is blocking us now.
### How has the community developed since the last report?
We recently accepted the first (documentation) contribution from a user who
does not belong to the pre-ASF group of Otava users and contributors. A
handful of more people submitted issues or sent an email to the mailing
list. This level of attention is already more than we are used to receiving
during the previous 8 years developing this code base.
The interactions we had, were mostly held back by the fact we have not yet
made our first release, and that until then, Otava only supported python
3.8, which is no longer officially supported. We expect interest in the
project to increase after the first release (as ASF incubating project) and
upgrading python version. (The release will include support for python 3.9
and 3.10 and will likely happen within hours after the deadline to submit
this report.
### How has the project developed since the last report?
The last time we submitted a report was in February 2025.
We apologize for twice failing to submit a report. There seems to still be
teething issues with basic project governance tasks and responsibilities.
We know we can do better, there's just a lot to absorb when becoming a
proper ASF project for the first time.
Shortly after our previous report, a new name "Otava" was approved for the
project. Otava is the Finnish name for the "Big Bear" constellation, one of
the largest and brightest star constellations in the Northern night sky.
Otava historically had an important function in navigating, as it was
commonly used to find the North Star, which is at the other end of a
straight line drawn from the right most 2 stars in Otava.
Most work in the project since then was to
* Change the project name across ASF infrastructure
* Change the project name everywhere in code and documentation. This
includes file names, executable names and tar file name.
* Publish a project website at otava.apache.org
* As this report was submitted, our first release was undergoing voting on
the incubator general mailing list.
### How would you assess the podling's maturity?
A self review based on
https://community.apache.org/apache-way/apache-project-maturity-model.html
* Code 3/5
* Licenses and Copyright: 5/5
* Releases: 4/5
* Quality: 5/5
* Community: 7/7
* Consensus: 4/5 (Missing: CS10)
* Independence: 2/2
* Brand: 4/4
### Date of last release:
The first release was happening as this report was submitted
### When were the last committers or PPMC members elected?
So far, the initial committers and PPMC members were those listed in the
initial proposal.
Some of those, haven't actually showed up in the incubator project now that
we are active.
### Have your mentors been helpful and responsive?
Yes!
Submitting this report is a routine we need to get more accustomed to doing.
### Is the PPMC managing the podling's brand / trademarks?
Not an issue yet, as the name is new.
### Signed-off-by:
- [X] (otava) Dave Fisher
Comments:
- [ ] (otava) Enrico Olivelli
Comments:
- [ ] (otava) Lari Hotari
Comments:
- [ ] (otava) Mick Semb Wever
Comments:
### IPMC/Shepherd notes:
Apache Otava (incubating) performs statistical analysis of performance test
results stored in CSV files, PostgreSQL, BigQuery, or Graphite database. It
finds change-points and notifies about possible performance regressions.
A typical use-case of otava is as follows:
* A set of performance tests is scheduled repeatedly, such as after each
commit is pushed.
* The resulting metrics of the test runs are stored in a time series
database (Graphite) or appended to CSV files.
* Otava is launched by a Jenkins/Cron job (or an operator) to analyze the
recorded metrics regularly.
* Otava notifies about significant changes in recorded metrics by
outputting text reports or sending Slack notifications.
* Otava is capable of finding even small, but persistent shifts in metric
values, despite noise in data. It adapts automatically to the level of
noise in data and tries to notify only about persistent, statistically
significant changes, be it in the system under test or in the environment.
Otava has been incubating since 2024-11-27. Otava entered Incubation as
Hunter.
The project name Otava was approved by VP Brand 2025-02-09.
### Three most important unfinished issues to address before graduating:
1. Publish the first release under the new name.
(https://github.com/apache/otava/issues/51) The first release was under
voting as the deadline to submit this report to the Incubator PMC passed.
2. Publish the existence of Apache Otava (Incubating), and our first
release.
3. Nurture a growing community that includes also new
members/contributors that have not used Otava (Hunter) before we joined
Apache Incubator
4. Make more releases. In particular, the first release intentionally is
not that different from what already existed before we became an Incubator
project. It is merely a change of project name and ownership (ASF) and the
license, and a re-union of many forks into a clear upstream project. For
future releases we hope to modernize python version, build tooling, and of
course add new features and integrations.
### Are there any issues that the IPMC or ASF Board need to be aware of?
Nothing is blocking us now.
### How has the community developed since the last report?
We recently accepted the first (documentation) contribution from a user who
does not belong to the pre-ASF group of Otava users and contributors. A
handful of more people submitted issues or sent an email to the mailing
list. This level of attention is already more than we are used to receiving
during the previous 8 years developing this code base.
The interactions we had, were mostly held back by the fact we have not yet
made our first release, and that until then, Otava only supported python
3.8, which is no longer officially supported. We expect interest in the
project to increase after the first release (as ASF incubating project) and
upgrading python version. (The release will include support for python 3.9
and 3.10 and will likely happen within hours after the deadline to submit
this report.
### How has the project developed since the last report?
The last time we submitted a report was in February 2025.
We apologize for twice failing to submit a report. There seems to still be
teething issues with basic project governance tasks and responsibilities.
We know we can do better, there's just a lot to absorb when becoming a
proper ASF project for the first time.
Shortly after our previous report, a new name "Otava" was approved for the
project. Otava is the Finnish name for the "Big Bear" constellation, one of
the largest and brightest star constellations in the Northern night sky.
Otava historically had an important function in navigating, as it was
commonly used to find the North Star, which is at the other end of a
straight line drawn from the right most 2 stars in Otava.
Most work in the project since then was to
* Change the project name across ASF infrastructure
* Change the project name everywhere in code and documentation. This
includes file names, executable names and tar file name.
* Publish a project website at otava.apache.org
* As this report was submitted, our first release was undergoing voting on
the incubator general mailing list.
### How would you assess the podling's maturity?
A self review based on
https://community.apache.org/apache-way/apache-project-maturity-model.html
* Code 3/5
* Licenses and Copyright: 5/5
* Releases: 4/5
* Quality: 5/5
* Community: 7/7
* Consensus: 4/5 (Missing: CS10)
* Independence: 2/2
* Brand: 4/4
### Date of last release:
The first release was happening as this report was submitted
### When were the last committers or PPMC members elected?
So far, the initial committers and PPMC members were those listed in the
initial proposal.
Some of those, haven't actually showed up in the incubator project now that
we are active.
### Have your mentors been helpful and responsive?
Yes!
Submitting this report is a routine we need to get more accustomed to doing.
### Is the PPMC managing the podling's brand / trademarks?
Not an issue yet, as the name is new.
### Signed-off-by:
- [X] (otava) Dave Fisher
Comments:
- [ ] (otava) Enrico Olivelli
Comments:
- [ ] (otava) Lari Hotari
Comments:
- [ ] (otava) Mick Semb Wever
Comments:
### IPMC/Shepherd notes: