Hristo Marinov
hricky
https://matrix.to/#/#bootc:fedoraproject.org https://matrix.to/#/#coreos:fedoraproject.org https://matrix.to/#/#atomic-desktops:fedoraproject.org https://matrix.to/#/#silverblue:fedoraproject.org https://matrix.to/#/#kinoite:fedoraproject.org https://matrix.to/#/#fedora-forgejo:fedoraproject.org https://matrix.to/#/#docs:fedoraproject.org
While I don't have formal governance experience, I'm an active contributor to several teams and organizations focused on image-based systems. This is the very area where Fedora is leading innovation. This gives me both technical depth in Fedora's modern directions and practical insight into how image-based approaches are being adopted across the ecosystem. Additionally, as an independent contributor, I bring a perspective focused on the broader community's needs.
Fedora's leadership in image-based systems is a significant opportunity. The Atomic Initiative is advancing this space meaningfully. However, when such initiatives conclude, we must ensure contributors remain engaged and their work integrates into sustainable community practices.
More broadly, as AI becomes increasingly present in development workflows, we need thoughtful governance around how Fedora engages with it. This is about authorship, accountability, and the moral questions around code provenance and community contribution. Fedora's values should guide how we engage with these technologies responsibly.
I initially needed an OS for on-premise servers, which led me to CentOS. The transition forced a reassessment, and during that process, I discovered Fedora's emerging work on image-based systems. That discovery led me to get involved in related teams, which deepened my commitment to this community. Now, as an active contributor in that space, what keeps me here is the community itself. I'm inspired by it, and that's what drives my continued involvement.
Metadata Update from @amoloney: - Issue set to the milestone: F44 - Issue tagged with: Council
Metadata Update from @amoloney: - Issue private status set to: False (was: True)
Metadata Update from @amoloney: - Issue status updated to: Closed (was: Open)