I think it's my turn to produce the report; the draft is below. I could only think of one item for "most important unfinished issues to address before graduating", suggestions would be appreciated.
--- # Otava 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: * Upgrade to support the latest versions of Python, including upgrading to the latest signal-processing-algorithms library. * * ## How has the community developed since the last report? Two 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`. * Simplified our configuration management. * 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? Yes. ## 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: (otava) Dave Fisher Comments: (otava) Enrico Olivelli Comments: (otava) Lari Hotari Comments: (otava) Mick Semb Wever Comments: --- On Thu, Aug 21, 2025 at 7:12 AM Alexander Sorokoumov < [email protected]> wrote: > I will only be able to get to it at the end of next week earliest, so would > appreciate it if someone else picks it up. > > Best, > Alex > > On Thu, Aug 21, 2025 at 12:53 PM Henrik Ingo <[email protected]> wrote: > > > Now that there's plenty of time, it's a good moment to ask if someone > else > > wnats to have a go? > > > > Our last report was in July and is here: > > https://cwiki.apache.org/confluence/display/INCUBATOR/June2025#otava > > > > henrik > > > > On Thu, Aug 21, 2025 at 9:13 AM <[email protected]> wrote: > > > > > Dear podling, > > > > > > This email was sent by an automated system on behalf of the Apache > > > Incubator PMC. It is an initial reminder to give you plenty of time to > > > prepare your quarterly board report. > > > > > > The board meeting is scheduled for Wed, 17 September 2025. > > > The report for your podling will form a part of the Incubator PMC > > > report. The Incubator PMC requires your report to be submitted 2 weeks > > > before the board meeting, to allow sufficient time for review and > > > submission (Wed, September 03). > > > > > > Please submit your report with sufficient time to allow the Incubator > > > PMC, and subsequently board members to review and digest. Again, the > > > very latest you should submit your report is 2 weeks prior to the board > > > meeting. > > > > > > Candidate names should not be made public before people are actually > > > elected, so please do not include the names of potential committers or > > > PPMC members in your report. > > > > > > Thanks, > > > > > > The Apache Incubator PMC > > > > > > Submitting your Report > > > > > > ---------------------- > > > > > > Your report should contain the following: > > > > > > * Your project name > > > * A brief description of your project, which assumes no knowledge of > > > the project or necessarily of its field > > > * A list of the three most important issues to address in the move > > > towards graduation. > > > * Any issues that the Incubator PMC or ASF Board might wish/need to > be > > > aware of > > > * How has the community developed since the last report > > > * How has the project developed since the last report. > > > * How does the podling rate their own maturity. > > > > > > This should be appended to the Incubator Wiki page at: > > > > > > https://cwiki.apache.org/confluence/display/INCUBATOR/September2025 > > > > > > Note: This is manually populated. You may need to wait a little before > > > this page is created from a template. > > > > > > Note: The format of the report has changed to use markdown. > > > > > > Mentors > > > ------- > > > > > > Mentors should review reports for their project(s) and sign them off on > > > the Incubator wiki page. Signing off reports shows that you are > > > following the project - projects that are not signed may raise alarms > > > for the Incubator PMC. > > > > > > Incubator PMC > > > > > > > > > -- > > *nyrkio.com <http://nyrkio.com/>* ~ *git blame for performance* > > > > Henrik Ingo, CEO > > [email protected] LinkedIn: > > www.linkedin.com/in/heingo > > +358 40 569 7354 Twitter: > > twitter.com/h_ingo > > >
