Summary

What is the problem or use case, what are we trying to achieve?
Expand our ruff linting rules to automatically enforce guidelines in CODING-STANDARDS.md, improve code quality and consistency, and reduce review overhead.

Motivation

Who is the affected end user?

Who are the stakeholders?

All contributors and reviewers in Python team projects.

How does this affect the end user?

Are they blocked? Are they annoyed? Are they confused?

A slower pace of changes and higher potential for bugs or inconsistencies.

How likely is it that this problem or use case will occur?

Main path? Edge case?

Many code contributions.

If the problem does occur, what are the consequences and how severe are they?

Minor annoyance at a log message? Performance concern? Outage/unavailability? Failover can't complete?

More inconsistent code quality, worse maintainability, higher potential for bugs.

Is this issue urgent?

Does this ticket have a required timeline? What is it?

The sooner this is implemented, the faster Python changes can iterate.

Is this ticket required by a downstream team?

Needed by e.g. Atlas, Shell, Compass?
No.

Is this ticket only for tests?

Is this ticket have any functional impact, or is it just test improvements?
Only maintainability improvements.

Cast of Characters

Engineering Lead:
Document Author:
POCers:
Product Owner:
Program Manager:
Stakeholders:

Channels & Docs

Slack Channel

[Scope Document|some.url]

[Technical Design Document|some.url]