Attendees: Michael Bouschen, Tilmann Zäschke, Tobias Bouschen, Craig Russell
Next meeting: Tuesday June 9 1100 PDT 2000 CEST Agenda: 1. Possibility of running the JDO project through Glasswing security scan New PR #126 "Add draft project security threat-model document" https://github.com/apache/db-jdo/pull/126 Proposed answers by Til at https://github.com/apache/db-jdo/blob/pr/PR-126-answers/draft-THREAT-MODEL.md Items for review: Tilmann has proposed answers to questions in the draft thread model. Some discussion is still needed on some of the questions. Section 14 Q6 Q7 Q10 Q12 Q13 Q17 where do other projects keep their threat models and SKILLS? AI Craig ask Jarek how to respond to Q17 and use of (maintainer) in answers? Tilmann's result of running Claude Opus against the jdo-dev repo. https://issues.apache.org/jira/browse/JDO-861 2. Trusted Release project The VOTE was initiated but the email never was sent to [email protected] <mailto:[email protected]> but was sent instead to [email protected] <mailto:[email protected]> The VOTE email was forwarded to [email protected] <mailto:[email protected]>. AI Craig give feedback to ATR team to use jdo-dev for voting. AI everyone review the email and validate the release and vote using the tool. Verify that using the tool, email is sent to jdo-dev mail list as well as recording the vote. This is just a test. Nothing will actually be uploaded to the downloads repo. 3. JIRA JDO-812 "Move to JDK 11 as the lowest supported version" https://issues.apache.org/jira/browse/JDO-812 4. JDO-847 "Create SBOM files" https://issues.apache.org/jira/browse/JDO-847 5. sonarcloud issues JIRA JDO-819 "Code quality analysis" https://issues.apache.org/jira/browse/JDO-819 JIRA JDO-823 "Fix sonarcloud issues of type Code Smells" https://issues.apache.org/jira/browse/JDO-823 Sonarcloud link: https://sonarcloud.io/summary/overall?id=db-jdo Cognitive Complexity of methods should not be too high: https://sonarcloud.io/project/issues?resolved=false&rules=java%3AS3776&severities=CRITICAL&types=CODE_SMELL&id=db-jdo Raw types should not be used: https://sonarcloud.io/project/issues?resolved=false&rules=java%3AS3740&severities=MAJOR&id=db-jdo 6. Other issues Action Items from weeks past: [Mar 17 2026] AI Everyone look at the Sonarcloud items. [Jul 01 2025] AI everyone take a look at the process for alpha testing. May require a file in the dist directory to get started. [Nov 12 2024] AI Michael see if it makes sense to add Map.contains(Entry e) to the JDO API. This would be useful to have queries where e.g. the user is interested in finding all Employees where the phone number is of key "home" and value "+16508617767". [Nov 05 2024] AI Michael create a JIRA for containsEntry, include the current test case and we can continue from here. [Jul 13 2023] AI All Open a new JIRA for Android since having JNDI in the API disallows use with Android [Jun 08 2023] AI All make a JIRA: JDO support for Java Records https://openjdk.org/jeps/395 [Dec 09 2021] AI Craig: Try to contact all current/former participants in JDO development and see if and how they want to be recognized on the JDO and DB web sites.https://db.apache.org/whoweare.html [Oct 07 2021] AI Craig send a private message to all JSR-243 Expert Group members asking if they wish to continue. [Mar 25 2021] AI Craig: investigate "merging" papajdo and apache.clr accounts [Oct 17 2014] AI Matthew any updates for "Modify specification to address NoSQL datastores "https://issues.apache.org/jira/browse/JDO-651 Craig L Russell [email protected]
