"Add your current user to the user group i2c before logging out and back in." -- is this definitely necessary? @TheKnightSky since you added it, can you clarify why, and where/how you found this out? I'm not doubting you, it's just that I didn't know about this requirement and OpenRGB seems to be working just fine for me. Maybe I have no i2c RGB devices, or something is different on CachyOS..? NeatNit (talk) 22:52, 25 May 2026 (UTC)

I think I had it mixed up when I was reviewing Wireshark, it does seem to only optionally require i2c-tools for that kind of access. Thanks for catching that. Also I would say add the next branch section things into installation and format it a bit better. See Style, it should help you out a bit. :) TheKnightSky (talk) 02:36, 26 May 2026 (UTC)

Thanks! As I'm really new to the wiki (and Arch in general, via CachyOS) (and I have some real-life obligations that I'd rather not procrastinate more than I already have), I think it would be better if you make the changes to the page. I'll learn from your example and I'll read the style guides at a later time before future wiki edits.

Basically I thought the information I added is rather crucial for new users, so I figured it's best to just put the information on the wiki first in my best guess for the style, and allow experienced editors like you to polish it up. I'll learn the style eventually, but there's no need to stall this page. NeatNit (talk) 07:30, 26 May 2026 (UTC)

I would recommend trying to make the style changes and formatting by yourself. After your edits, if there are any errors I'll try and catch them. TheKnightSky (talk) 11:47, 27 May 2026 (UTC)

Okay, I gave it a shot. NeatNit (talk) 12:13, 28 May 2026 (UTC)

Hi @Erus Iluvatar, I think it's a bad idea to recommend the released version as default. Or at least, it should be made very clear that the AUR package offers many benefits and is no less stable. Side note, I am trying to get OpenRGB to release a new version as a stopgap, but the lead developer's efforts are mostly going towards developing next. It's a hobby project with a small team, so it's understandable that it's hard to get attention on this.

I can agree with the removal of the "next" version from this article, but the reference to it should also be removed from the Plugins section. NeatNit (talk) 18:42, 28 May 2026 (UTC)

Hi :)

We usually don't "recommend" things, but present the available options with the pros and cons of each.

I'm offline for tonight, feel free to adjust the wording to give more emphasis to the -git version and be explicit that it's a "stable with more hardware". If you have the time, could fix the reference I forgot? Otherwise I'll handle it tomorrow :P

-- Erus Iluvatar (talk) 18:50, 28 May 2026 (UTC)

Sure, I've removed the reference.

You said we don't "recommend" things, but the current phrasing seems to implicitly encourage the Arch package as the default option, and only describing the AUR option after the fact. It seems to me equally valid to say to install the AUR package in the first sentence, and expand on the other options second.

However, I'll sleep on it, maybe I'll change my mind by tomorrow. I'm also having another go in the OpenRGB discord to ask for an update to be released. NeatNit (talk) 19:06, 28 May 2026 (UTC)

How about this?

"""

OpenRGB can be installed with the openrgb-git^AUR package, which is equivalent to the pipeline version.

Some users may prefer the openrgb package, which tracks the released version. Due to the long release cycles, recent hardware is not supported in this version, and it may contain bugs which have already been fixed in the pipeline version.

Install the optional i2c-tools for RAM / Motherboard RGB control on desktop devices.

"""

@Erus Iluvatar, what do you think? NeatNit (talk) 10:37, 30 May 2026 (UTC)

Hmm, having both as equals would be fine, but this puts -git as the "goto". Upstream states "Arch users can also install from the Extra repository or from the AUR for the pipeline version." in its readme and the last rc which we package is 8 month old which would only leave relatively recent hardware uncovered.

Here's something:

OpenRGB can be installed either with the openrgb package, which tracks the released version and may not support your hardware or openrgb-git^AUR (equivalent to the pipeline release from upstream) for a stable yet more featured package"

-- Erus Iluvatar (talk) 20:22, 30 May 2026 (UTC)

Good news. Let's not change it for now. I finally got a reply from the developer agreeing that it's a good idea to release a new version. Being cautiously optimistic, it should happen this week or next as there's a specific set of pending merge requests he wants to merge before the release. So I think we can just wait it out and then the text currently live will be good advice for users. NeatNit (talk) 11:52, 1 June 2026 (UTC)

Excellent! Closing :) --Erus Iluvatar (talk) 16:10, 1 June 2026 (UTC)

I sort of disagree about the -next-git version removal completely with reference to Help:Style#Notes, Warnings, Tips. As the mention and simple explanation of it provides "in-depth knowledge on something that otherwise would be considered a bit extraneous to the article." we could mention it in a note instead. Same thing for the plugin scheme for it. TheKnightSky (talk) 02:06, 29 May 2026 (UTC)

As I linked in my edit summary, it's not about tip/note/warning but a general rule on installation sections: development versions are rarely something we should push on readers unless upstream is known to consider -git as their main supported version. Erus Iluvatar (talk) 20:25, 30 May 2026 (UTC)