Asked in Slack, it's too late to add to the IPMC report now. I will share it here for the benefit of anyone reading this. We can also reuse some of it for the next report. Looking back, it seems it's only a week or so until we are invited to submit the report for May Board meeting.
# Hunter 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, and the project name Otava was approved by VP Brand 2025-02-09.) ## Three most important unfinished issues to address before graduating: * Publish the first release under the new name. [jira]( https://github.com/apache/otava/issues/51) * Publish the existence of Apache Otava (Incubating), and our first release. * Nurture a growing community that includes also new members/contributors that have not used Otava (Hunter) before we joined Apache Incubator * 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 headers, 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. We apologize for missing the deadline for submitting this 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. ## How has the community developed since the last report? We recently accepted and merged 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 uses 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. ## How has the project developed since the last report? The last time we submitted a report was in February 2025. Shortly after that, 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 It appears we are now ready to start the process of creating a source release, sign it, etc... [jira](https://github.com/apache/otava/issues/51) ## How does the podling rate their own 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: 1/5 * Quality: 5/5 * Community: 7/7 * Consensus: 4/5 (Check CS10...) * Independence: 2/2 * Brand: 4/4 On Mon, Apr 14, 2025 at 7:09 PM Alexander Sorokoumov < aleksandr.sorokou...@gmail.com> wrote: > The draft looks great! Thank you for stepping in, Henrik! > > Best, > Alex > > On Mon, Apr 14, 2025 at 4:57 AM Henrik Ingo <hen...@nyrkio.com> wrote: > > > Draft monthly report: > > > > > https://docs.google.com/document/d/163WlEOWFl090OFOz_ElBKVER_dHd5RF8BUdQEUnVIOw/edit?usp=sharing > > > > Not yet in Markdown format > > > > henrik > > > > On Mon, Apr 14, 2025 at 2:10 PM Henrik Ingo <hen...@nyrkio.com> wrote: > > > > > Hi Justin > > > > > > Thanks for raising this. > > > > > > I had not even realized we failed to report in March. It seems the > > > reminder hasn't reached us because our name change finally had happened > > in > > > March. There is discussion in my inbox about the technical reasons for > > > this, but in the mean time nobody seems to have woken up to the fact > that > > > we still need to produce the report, reminder or not. At the time this > > > discussion was just one out of many details to track regarding the name > > > change, half of which I personally struggled to even understand what > they > > > do, as this is my first time as committer / PMC for any ASF project. > > > > > > April's report, it seems we have failed to explicitly agree on who is > > > responsible for each report. For my part I assumed it would happen in a > > > certain way, but now in hindsight I must admit we never agreed about an > > > arrangement beyond February. > > > > > > It seems the board meeting is 2 days from now. Should we still submit a > > > report, even if it has missed the podling deadline? I will draft one > in a > > > few hours anyway. > > > > > > henrik > > > > > > On Mon, Apr 14, 2025 at 9:48 AM Justin Mclean <jmcl...@apache.org> > > wrote: > > > > > >> Hi, > > >> > > >> This is teh second time in a row that the project has failed to > report. > > >> Can someone from the PPMC please explain why this occurred? > > >> > > >> Kind Regards, > > >> Justin > > >> > > > > > >
