Add Cello 2024 Q1/Annual report

[yeasy]

Add Cello 2024 Q1/Annual report for TOC review

[arsulegai]

The team has showcased a commendable consistency in terms of bi-weekly meetings and participation. I have noticed that these meetings are well-recorded and have a regular attendance from a consistent group of participants. This, in conjunction with participation from at least three companies, is a positive sign of collaborative effort.

Further, an increase in the issue count indicates improved documentation and increased activity. I appreciate the swift actions taken by the team, which reflects their dedication and commitment to the project.

However, there are areas that need improvement. There is a consistent delay in reporting to the TOC as seen in Q3 and Q4 of 2023. Despite the record of meetings showing active participation, the maintainers are not showing enough activity. There are also inconsistencies in quarterly reports, notably the missing V1.1.0 release in the annual report that was promised in the Q4 report.

The activity in 2023 significantly reduced compared to 2022, which is a cause for concern. Additionally, the cello repository saw fewer code merges, with minor documentation related PRs being the only visible activity on GitHub.

Certain strategic decisions also raise concerns, like the release of Fabric version 2.5 LTS while 3.0 is planned. Also, there is a noticeable skew with 60% of contributions coming from just two organizations and a similar trend is observed in contributors working outside of working hours.

To improve, I suggest aligning with the Fabric strategy and fostering collaboration with the Bevel project, which could bring in new contributors. I also recommend addressing the project's low legal compliance, as regular scan alerts indicate it as an area that needs immediate attention.

[ryjones]

@yeasy

[VRamakrishna]

I'm adding my approval so the PR can be merged once @yeasy updates the report as per suggestions made by others.