[Weekly Meeting] [2024-02-02] - Meeting Notes

[porcelli]

• Community

  • Weekly Meetings
    • Hosting
      • Agreed to be on Zoom
    • Minutes
      • Agreed to be used GitHub Discussions
      • Discuss on ML to define the repository
  • Website
    • Live! (But just a placeholder)
  • Blog
    • To be defined
    • Today
      • Federated + Provided
      • WordPress
        • Infra not available on Apache
  • Calendar
    • Google Calendar with shared writing access among stakeholders
  • SonataFlow Logo
    • Red Hat willing to work and provide options to be voted in ML

• Infrastructure

  • We are starving Apache Jenkins infra
    • With other projects too, but we play big role on this
    • Dominik: adjust nightlies, maybe only on commits…

• Test failures

  • Native failings
    • Follow up on Zulip channel
  • Serverless Operator failure handled by Domik - in progress

• 10.0.0 Release Blockers

  • Oracle JDBC
    • Francisco will offer a new PR in ~1 week timeline to address existing concerns, otherwise we agree to remove everything
  • Reproducible builds
    • Runtimes
      • Tibor: next week dedicated.
        • Maven plugin binary and it’s trying to remove it, it seems to work
        • Similar issues to Drools, there’s need to make the same clean that Mario had for Drools
          • Need rewrite?
          • Mario: Add directly the drools dependency
    • Apps [can't be done in parallel with Runtimes]
    • Optaplanner - YAY!
      • Done
    • Images
      • SonataFlow are reproducibles now
      • Early next week new updates!
      • Limited to Semantic (due metadata issues)
    • What about other projects?
      • Seems that there’s different interpretations
    • Serverless Operator
      • Done!
  • Kogito Operator Deprecation
    • Impact Issue to be opened
      • Add a link to release noted to the issue that have information about the deprecation
      • No changes seems to be needed other than docs and exclude it
      • Some images will be removed because not used more
  • KIE Tools Circular Dependencies
    • Next week an update

• Rebranded Quarkus Extensions

  • Refined proposal
  • Once +1s from ML Ricardo will start SonataFlow

---

Recording:

https://us06web.zoom.us/rec/share/GDLI-goFbcfjtaQbNcXR9c7U_a45z4WQphn377NMkqlIpMisPVk7vLn29mhH2ZJZ.c1Pvx8h0XKe0Sbl1
Passcode: aP5=j6vK

[porcelli]

Meeting summary by Zoom AI Companion

Quick recap

The team discussed the use of Github for meeting minutes and tracking meeting notes using a new category in Cncf. They also discussed the current state of the Apache website and the community's interest in blogging and content strategy. The team agreed to use a shared Google Calendar for managing their schedule. They also identified potential blockers in their project, particularly the binding of the project to a single individual, and issues with Oracle Gdb, code testing, version control, and Oracle builds. The team also discussed the complexities of interacting with Apache and the progress on several projects.
 
 

Summary

Github, Meeting Notes, and Apache Website

Eduardo Cerqueira raised a query about using Github for meeting minutes, to which Alex Porcelli clarified its intended use as a platform for discussions rather than issues. Ricardo Zanini proposed a method to track meeting notes using a new category in Cncf, which includes action items and notifications for responsible individuals. The idea of hosting meeting notes on a specific git repository was also discussed, with the key issues repo being suggested as a potential location, but Alex suggested further discussion on the mailing list. The meeting also touched upon the current state of the Apache website, which is live but lacks adequate information.

Blogging, Calendar, and Infrastructure Discussion

Alex Porcelli and Mark Proctor’s iPhone discussed the community's interest in the blogging and content strategy, but no strategy was yet defined. Alex mentioned a placeholder for a blog on the landing page and shared his contact with Pasha Infra regarding the blog infrastructure. They acknowledged the need to focus on new generation content and discussed the challenges of creating a hybrid blogging platform. The team also discussed managing a shared calendar, with Ederign proposing using Google tools and Dominik Hanak noting potential issues with Apache's terms of service. They eventually agreed to use a shared Google Calendar, granting individual contributors write access and others read access.

Project Blockers, Oracle Gdb, Voting System, Apache Consensus, Dead Code

Alex Porcelli identified potential blockers in their project, particularly the binding of the project to a single individual and an issue with Oracle Gdb. The team discussed the approach to these issues, with Ederign suggesting a voting system and Alex emphasizing the need for Apache consensus. A decision to remove certain Oracle-related code was postponed due to Francisco's ongoing work on it. The discussion also emphasized the importance of avoiding creating dead code and the potential legal implications, but no final decision was reached.

Code Testing, Version Control, and Oracle Builds

The team discussed issues with code testing, version control, and Oracle builds. Alex suggested either fixing the code or removing it temporarily. Tibor began working on the issue with builds next week. Luca confirmed reproducible builds for both tours and off the planet. Tibor Zimányi discussed a problem with running times in different modules and considered creating scripts to solve it. Mario suggested adding the Druze Youtube module, which Tibor agreed to investigate. The team agreed to prioritize dependencies and aim to reuse as much as possible to avoid code duplication. Ricardo Zanini reported successfully making the images reproducible by removing package managers and planned to verify a few things in the next few days. The team also discussed the issue of image timestamps and the need for approval from the Ipmc members.

Apache Interpretation and Legal Clarity Concerns

Alex Porcelli discussed the complexities of interacting with Apache, highlighting the different interpretations and restrictions among various teams. He noted that while they have duties as committers, they should not fight unnecessary battles and should instead focus on releasing their project. Mario Fusco suggested relaxing some constraints where possible. Mark Proctor’s iPhone raised concerns about ambiguity in the legal thread, emphasizing the need for clarity. Alex agreed, noting the organization's complexity and the need to understand its hierarchy better.

Progress and Issues on Projects

Alex and Ricardo Zanini discussed the progress on several projects. Ricardo Zanini confirmed that the email task was completed and he was moving on to the operator. They also discussed the issue of the old Cujid operator duplication, with Ricardo Zanini planning to open an issue in the repository to discuss the impact and update all the repositories. Ricardo Zanini also mentioned the need to remove certain examples and sections from the documentation and images from the image side. Mark suggested pasting the final proposal into the excel sheet and checking for any negative responses before executing it. Ricardo Zanini also mentioned that he was working on a new logo for the project.

Jenkins CI/CD Performance and Cloud Usage Concerns

Jan Šťastný raised concerns about stretching Jenkins ci bandwidth due to nightly builds taking longer than usual, which he attributed to shared executors on the Jenkins notes. He suggested exploring donations of nodes to improve the situation. Alex Porcelli agreed to discuss this issue further and mentioned they are exploring options like dedicated VMs for Jenkins of Apache Kie. Dominik Hanak proposed investigating ways to reduce their cloud usage. Mario Fusco agreed to look into native build completion issues, which Jan promised to send more details about. Finally, Dominik Hanak mentioned a failure in Cochito service operator nightly builds, which he planned to fix by Monday or Tuesday.

Next steps

• Ricardo will create a thread on the mailing list to discuss where to host the meeting notes and other organization reports.
• Create a shared Google Calendar for the community with read access for all and write access for key stakeholders.
• Discuss and decide on the future of the Oracle code and its potential impact on the release.
• Francisco will work on testing the relevant parts of Gdb and report back next week.
• Ricardo will create an issue in the repository explaining the decision to remove the old Cujid operator and its impact on other repositories.
• Ricardo will archive and update all the repositories referencing the legacy operator and link to the issue in the release notes.
• Mark will chase Chris for an update on the refining list.
• Chris will send the final proposal to the mailing list.
• Ricardo will work on the Sonata Flow part and discuss with the person from the company about the new logo proposals.
• Mario will look into the native build completion problem in Kafka.

AI-generated content may be inaccurate or misleading. Always check for accuracy.