Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify RHEL support options #2759

Merged
merged 1 commit into from
Aug 2, 2023

Conversation

matt335672
Copy link
Member

As someone who has worked as a professional RHEL sysadmin for a few years in the past, I've been following the recent developments around the availability of RHEL with some interest.

The announcement from Red Hat is here. A good quality discussion around the issues which covers both sides of the argument can be found in this LWN article

I'd like to focus on the implications of this announcement for this project in particular.

From our perspective, it's become a lot more complex to support RHEL directly, as an exact copy of a point-release of RHEL is no longer available for free.

I'm including the developer subscription for RHEL in this. Signing up for the developer subscription requires agreeing to the Red Hat Developer Subscription for Individuals. This includes these paragraphs:-

By accepting the Program Terms, you represent that you are acting on your own personal behalf and not as a representative or on behalf of an entity and will be using the Individual Developer Subscriptions solely as set forth in this document. Red Hat is relying on your representations as a condition of our providing you access.
. . .
If you use the Individual Developer Subscriptions for any other purposes or beyond the parameters described in these Program Terms, you are in violation of Red Hat’s Enterprise Agreement and are required to pay the Subscription fees that would apply to such use, in addition to any and all other remedies available to Red Hat under applicable law. Examples of such violations include, but are not limited to,

Personally I'm not happy with signing up for this to support xrdp on RHEL, as I don't have any personal liability insurance which would cover me if I made a mistake in this area.

With all the above in mind, I'd like to propose a small change to @metalefty's issue template. Applying this change will result in the user being presented with the following:-

image

Feedback is welcome. Does anyone think I'm over-reacting? Is the wording correct?

@metalefty
Copy link
Member

metalefty commented Aug 1, 2023

Good point, I don't think it's overreacted. I'm now a member of AlmaLinux so I think I need to act friendly to Red Hat.

Red Hat might not be happy if I use the free developer subscription to reproduce xrdp issues a Red Hat customer encountered. Especially when I get sponsorship. It means I get paid using a RHEL subscription.

@matt335672
Copy link
Member Author

That means neither of us is happy to directly support xrdp on Red Hat given the current situation. I'll merge this. We can always back it out if Red Hat change their minds.

@matt335672 matt335672 merged commit 9bbb2ec into neutrinolabs:devel Aug 2, 2023
13 checks passed
@matt335672 matt335672 deleted the update_issue_template branch August 2, 2023 11:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants