Here the Iroha Annual Report notes in preparation for the meeting tomorrow:

Iroha Annual Review 2024 Notes

Project Health

Overall, the project appears to be in good health as indicated in the review and by looking at the LFX Insights.
- Once I switched the LFX Insights to stable year-by-year comparisons (recommendation in PR).
The activity on the project seems stable, year over year, although by commits, the code contributions a bit down.
- That said, the progress on Iroha v2 and in successfully transitioning the Ursa code into Iroha indicates the "important" things are being done in a timely fashion.
The examples of use are impressive -- two significant CBDC deployments and the Fraud Intelligence project (that I didn't really understand...).
The year-by-year comparison of the contributor and organizational leaderboards was interesting -- seeing that many of the the same people/organizations are still around, and that there is new and globally diverse interest.
The LFX Insights Activity Dependency metric is a little concerning (55% of activity from one person, 94% from one organization), but from my experience, I'm a little suspect of the activity charts in LFX Insights. Its not surprising to have a team lead/community organizer (especially one that is a developer) doing a lot of the activities in the various project repos.
- The organizational dependency is not ideal. Deployed blockchains should be decentralized by nature, and if production networks are getting built (as they seem to be), contributions from others should come.

The stated progress on Iroha 2 looks good, and a working system is near -- impressive!
The rollout of the projects based on Iroha is likewise really impressive.

All the criteria are fulfilled. However, we do note that there is a lack of diversity in the area of "contributing organizations", as the vast majority of contributions are from just one organization.
Should remain in Graduated status

While I found information about Iroha 1 and Iroha 2, the introductory documents were virtually identical -- with no indication of the difference between or the status of Iroha 2.0 for adopters. Insiders might know more, but as an outsider, I was left wondering. Suggest adding that to at least the Iroha 2 README, or perhaps to the Iroha Hyperledger Wiki Project page.
In addition to the Iroha 1 versus Iroha 2 bullet above, is there a page for roadmap in general?
The github README still has a dead link to Jira for issue management, and no link to the Iroha wiki which appears to have some good information.
I had not realized that Iroha was being actively used for CBDC uses cases and definitely think that should be touted by the project. Perhaps it is and I'm just not aware of it.

No specific recommendations about Iroha per se. Some of the comments from other Annual Reviews apply, notably:

Create an Iroha ecosystem page similar to the Fabric ecosystem page (https://wiki.hyperledger.org/display/fabric/Ecosystem). This would be helpful to the community, as currently it is hard to understand how the repos complement each other. This could be done as a pair -- one for Iroha 1 and one for Iroha 2.
Write blog articles and run workshops periodically with Hyperledger staff's help.
Signal openness towards more adding organizations to the project to reduce the organizational dependency.