[Mona Arumugam] While it is true that the Scrum Team, including the developers, collaboratively create the DoD, but isn’t it little inaccurate to say that only developers confirm adherence to the DoD.
The Scrum Team as a whole, including the Product Owner and Scrum Master, collaboratively inspect and adapt the increment during the Review where the team evaluates whether the increment meets the DoD requirements and whether it is potentially releasable.
So I think it’s not very correct to say only Developers confirm the DoD.

[Karthik Nagarajan Venkataramani] For DoD what it means by the scrum team creates is, everyone shares their expectation of the what it means to them when it is called done. This includes quality measures, standards, security etc. And developers confirm those because it's the developers who are going to actually code, and if something is unrealistic they will deny. So with the overall team's input, it must be developers who confirm them.

[Pranshu Gupta] No it's not unfair that the Scrum team creates the DoD and Developers "conform" to that because in creation as well as in inspection and adaptation of DoD at a later stage, maybe during a retrospective requires collective intelligence of the Scrum Team while building an increment conforming to that DoD is done by Developers only. For example, the PO might be the only person aware about a security compliance that the increment is supposed to be aligned with at the beginning or at the time of creation of DoD. But the Developers are the actual doers who will be working on building that increment conforming to that compliance.

[Venkatram Boreda] The process of defining the "Definition of Done" (DoD) in Scrum is a collaborative effort within the Scrum Team, which typically includes the Product Owner, Scrum Master, and Developers. While the Developers often play a significant role in confirming that the work meets the DoD, the entire team should be involved in its creation to ensure a shared understanding of what work "done" means. This collaborative approach helps maintain transparency and alignment within the team.

It's important for the Scrum Team to work together in defining and confirming the DoD to ensure that everyone's expectations and standards are considered, preventing misunderstandings and fostering a sense of ownership among team members. This help team more balance and respect to each other.