*** UPDATE *** As of last Friday (2023-Oct-12), CentOS Stream Issues may be accessed without a login. - https://lnkd.in/gAbsk9Um Other SSO systems will also hook into Red Hat's Jira configuration, so signing the Red Hat EULA is no longer required. A huge thanks goes to Gordon Messmer and Florian Weimer for addressing this. *** ORIGINAL POST (NO LONGER CORRECT) *** Can someone from @Red Hat please confirm that ... 1) if one wants to file any bugs with CentOS Stream (even 'next' aka 10) ... 2) one has to create a Red Hat Login, which means .. 3) one has to agree to the EULA (at least in North America), which means ... 4) well ... you tell me, especially if and when confirming the 'workflow' ** I'm a Red Hat customer, as well a long-time Red Hat Architect and Advocate, and have long agreed to the EULA. I.e., I'm not the one that will 'take issue.' But ... a lot of people, and the entire community one wishes to engage on Stream, has not. This isn't a complaint. It's a just an ... "If I see this ... others will too," and I have no 'recourse' when they ask me question but to 'point it out.' Please advise. I'm trying to avoid telling everyone in the community, who wants to contribute on CentOS Stream 10, when they ask me, that they have to agree to the Red Hat EULA, at least in North America, to help Red Hat help ... well ... itself. **Workflow example ... Go to: https://lnkd.in/gyG2H8WA Click: Red Hat Issues ('next' CentOS Stream 10, or even 'existing' 9 or 8) Click: 'login in' on the page that says 'Error' about 'not logged in' Click: 'Register for a Red Hat account' Enter: (your data) but ... Do NOT Check: 'I have read and agree to the Enterprise Agreement' Click: 'Create my account' See: 'You have to agree with Terms and Conditions' (in red) Click: 'Enterpise Agreement' (North America returns Red Hat NA EULA) Again, please advise ASAP. This is going to be a 'show stopper' for many in the community. I want to assume I am incorrect and have done something wrong in my procedure. Although, to be honest, even if I did something wrong ... all this is just adding to the 'mass confusion' that is causing much of the FUD among the community. Please understand it's becoming very, very difficult for long-time Red Hat Advocates like myself to continue on our ... well now ... a good quarter century 'revolution' together. I'm really biting my tongue, but with Bugzilla now officially going away, I fear the only contributors will be Red Hat customers, as 'mailing lists' are far less efficient. Note the term 'contributors' ... no one wins in that case, and definitely not Red Hat. Again, I hope I'm very, very wrong here, and merely 'screwed up' in my procedure. And I somehow 'just overlooked' a non-EULA route to bug reporting other than e-mail lists.
Gordon Messmer
6mo
If I select "Log in" from Jira, I'll get a form on sso.redhat.com that prompts me to accept the enterprise agreement when creating an account. However, if I navigate directly to sso.redhat.com and attempt to create an account, I get a slightly different form, which does not prompt me to accept any agreements. It's (temporarily) difficult for me to follow the process end-to-end to verify that an account created via the latter process will allow me to interact with Jira without accepting the enterprise agreement, but I've asked for clarification on the centos-devel mailing list.
John Boero
6mo
And the original CentOS acquisition was about "togetherness...."
Linux, Open Source and Red Hat Geek
6mo*** UPDATE *** As of last Friday (2023-Oct-12), CentOS Stream Issues may be accessed without a login. - https://lnkd.in/gAbsk9Um Other SSO systems will also hook into Red Hat's Jira configuration, so signing the Red Hat EULA is no longer required. A huge thanks goes to Gordon Messmer and Florian Weimer for addressing this.