{ "@context": { "CIP100": "https://github.com/cardano-foundation/CIPs/blob/master/CIP-0100/README.md#", "hashAlgorithm": "CIP100:hashAlgorithm", "body": { "@id": "CIP100:body", "@context": { "references": { "@id": "CIP100:references", "@container": "@set", "@context": { "GovernanceMetadata": "CIP100:GovernanceMetadataReference", "Other": "CIP100:OtherReference", "label": "CIP100:reference-label", "uri": "CIP100:reference-uri", "referenceHash": { "@id": "CIP100:referenceHash", "@context": { "hashDigest": "CIP100:hashDigest", "hashAlgorithm": "CIP100:hashAlgorithm" } } } }, "comment": "CIP100:comment", "externalUpdates": { "@id": "CIP100:externalUpdates", "@context": { "title": "CIP100:update-title", "uri": "CIP100:uri" } } } }, "authors": { "@id": "CIP100:authors", "@container": "@set", "@context": { "name": "http://xmlns.com/foaf/0.1/name", "witness": { "@id": "CIP100:witness", "@context": { "witnessAlgorithm": "CIP100:witnessAlgorithm", "publicKey": "CIP100:publicKey", "signature": "CIP100:signature" } } } } }, "authors": [], "body": { "comment": "Summary\nYoroi DRep votes ABSTAIN on \"IO: Developer Experience Initiative.\" This position is not a rejection of the goal, which Yoroi considers genuinely important, but a considered view on delivery structure and measurability.\nRationale\nThe diagnosis is correct and the direction is well-motivated. \nSurvey data from 109 Cardano developers and a comparative analysis of ecosystem growth rates give this proposal an unusually solid empirical foundation. Yoroi agrees that fragmented tooling, poor onboarding, and lack of ecosystem coordination are among the most actionable barriers to builder adoption.\n\nSeveral key outcomes depend on factors outside the proposer's direct control. \nThe success of the Developer Hub relies on buy-in from Cardano Foundation, Intersect, and the broader community. Adoption of cardano-init depends on third-party tooling maintainers integrating with it. These are not trivial dependencies, and the proposal would benefit from a clearer account of how alignment will be achieved and maintained.\n\nThe growth target needs a more defined attribution model. \nA 30% improvement in developer growth rate is a meaningful commitment, but developer acquisition is influenced by many factors beyond any single initiative. Yoroi would find it easier to evaluate progress if the proposal defined a clearer set of attributable metrics that sit within IO's direct sphere of delivery.\n\nConclusion\nYoroi believes developer experience is one of the highest-leverage areas the ecosystem can invest in, and we have genuine respect for the work IO is proposing here. Our abstain reflects a desire to see the delivery structure and measurement approach strengthened before committing treasury resources at this scale. We would welcome a revised proposal that addresses these points and look forward to supporting a stronger version of this initiative." }, "hashAlgorithm": "blake2b-256" }