/
2025-01-29 TCR document changes

2025-01-29 TCR document changes

Date

Attendees 

Discussion items

TimeItemWhoNotes
1 minScribeAll

Jenn Colt is next, followed by Florian Gleixner

Reminder:  Please copy/paste the Zoom chat into the notes.  If you miss it, this is saved along with the meeting recording, but having it here has benefits.

60 minTCR documentation change PRs

Notes:

  • Clarifying major severity code smell
    • Sonar doesn't use the word major any more, we should use one of the terms in Sonar
    • Change to 'issues' to covered the things Sonar has consolidated
      • Some former smells are now in issues and not in hotspots
    • This represents a slightly higher bar
    • Change will need to be communicated
    • In theory this new standard should also be applied to existing modules
    • Ready to merge
  • Expand criteria for consuming APIs
    • Should the criteria be divided into front and back end?
    • Chose to go with the split route
    • Ready to merge
  • Use ASF 3rd Party License Policy for module evaluation
    • Categorizes into yes, no, maybe. In maybe you have to give acknowledgment. Simplest way to do this would be in the readmes of the modules. Would be a new request of the teams.
    • Making the tooling for the steps clearer and share with reviewers and dev teams
    • For now get links and list set up, tooling can get added in another PR
    • Ready to merge
  • Static code analysis
    • Not ready to merge. Could close until topic resurfaces. Closing may be simpler and then next time have a more cleanly scoped discussion.
    • Closing. Subgroup is still on the list if people want to revive it.
  • Jira statuses
  • Fix broken links on environment variables
  • Merge eval form into eval criteria
    • Consolidate everything into criteria document, add checkboxes
    • Need to merge this one last to avoid conflicts
  • Julian Ladisch will take on doing the merging
  • Serials management
    • Talking to team
-Zoom Chat