I'm a Red Hat employed engineer, working on all Fedora, CentOS Stream and RHEL. This is what each means for me in particular (but should also be applicable in general) in practice:
* RHEL - only when I'm bound by some legal requirement (embargo, etc.) I do work 'RHEL only' (not visible in CentOS stream). In practice, such work is expected to be seen in CentOS Stream once the legal barrier falls / expires.
* CentOS Stream - all work (except abovementioned) for RHEL is done here. The code has been available here (for 2 years already for C9S): https://gitlab.com/redhat/centos-stream/ Are you missing anything? (codebase-wise) This means my work on RHEL is visible unlike ever before. Open to submissions via merge requests Also merge requests where I develop changes are open to examination during my development of them. (unlike anytime before)
* Fedora - unlike RHEL or CentOS, this is the place where I can develop new features. I don't have this space downstream. So tuning packaging, trying out various enhancements, adopting big upstream changes, packing latest greatest upstream releases. All that will be branched to form a new RHEL one day. This is the only way for me to introduce big changes. As I see it, both RHEL and Fedora profit from that to maximum.
And I don't expect this relationship to go away anytime soon.
However I might have misunderstood the core of this discussion.
--
Michal Schorm Software Engineer Core Services - Databases Team Red Hat
--
On Thu, Jun 22, 2023 at 11:39 AM Miroslav Suchý msuchy@redhat.com wrote:
Dne 22. 06. 23 v 10:44 Michael J Gruber napsal(a):
In each case, the way it was done and communicated was literally begging for bad press. ...
So, the signal is either "we don't care about our upstream" or "we do not understand upstream's importance and concerns".
None of the last two. It is first one out of these three: wrongly communicated and begging for bad press.
I think that RH engineers are pretty bad in communicating things. Me included.
-- Miroslav Suchy, RHCA Red Hat, Manager, Packit and CPT, #brno, #fedora-buildsys _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue