Talk:General guidelines
IRC guidelines
There are already some rudimentary guidelines in duplicate in General troubleshooting and it would probably make sense to move them here. They are currently flagged with Template:Move to IRC but this may be a better place actually. Opinions?
-- NetSysFire (talk) 08:36, 18 July 2021 (UTC)
- The section in General troubleshooting moved to Arch_IRC_channels#Collaborative_debugging. That section is not guidelines I think. So could we just close this? --Fengchao (talk) 13:16, 27 February 2023 (UTC)
Forum rules
On the forums, there's a thread called README: Forum Rules. It has some overlap with General guidelines#Forums. Given this, is the General guidelines#Forums section still relevant?
Perhaps General guidelines#Forums should be changed to just link to https://bbs.archlinux.org/viewtopic.php?id=130309 ?
-- nl6720 (talk) 10:33, 18 July 2021 (UTC)
- General guidelines#Forums (previously "Forum Ettiquette", then expanded to become what is now the "Code of Conduct" circa 2016) supersede the README: Forum Rules. If anything, the README should be retired in favour of the General guidelines, but the former is still linked to in https://bbs.archlinux.org/misc.php?action=rules (likely need an admin to change that, mods cannot)
- -- WorMzy (talk) 12:01, 18 July 2021 (UTC)
- I think the CoC and General Guidelines should stay, and the "Forum Rules" link should point to the CoC rather than that outdated Forum topic. I regularly link to the General Guidelines, so in my opinion it is very much still relevant and should be retained.
- The "Arch Linux Support Only" text could also be more prominent in the CoC.
- -- 2ManyDogs (talk) 13:28, 29 June 2022 (UTC)
- Changes to the code of conduct are out of scope. It lives in https://gitlab.archlinux.org/archlinux/service-agreements now and changing it may require a legal review from lawyers. -- nl6720 (talk) 13:38, 29 June 2022 (UTC)
Reply to specific thread in a mailing list
Last time I tried to reply to an archlinux mailing list, I had a pretty horrible experience. It was long before the change to python3.
There was a specific, non-standard field that needed to be set to reply to a specific thread, or every email would start a new thread. I was not only inconvenienced by this, but ridiculed for my incompetence.
I found it very difficult to find any email client capable of setting the specific field necessary. Finally I was able to work out how to do it with git and only git.
The current instructions make no mention of that field (which I will have to look up again; can't remember what it was).
Is this no longer required, or has it remained omitted this entire time? quequotion (talk) 10:27, 14 February 2023 (UTC)
- @Quequotion It's currently in section 2.4 . A ton of clients have this feature, including Thunderbird and GNOME Evolution. Just click "Reply to list".
- If you're talking about the "reply-to" header... even Gmail supports that. Aaron Liu (talk) 20:08, 3 January 2024 (UTC)
Use full URL in commit messages to packaging?
Packaging merge request guidelines state
- When referencing (or closing) a ticket or merge request in a commit message, use the full URL to the ticket or merge request.
However, the full URL can be very long and redundant, putting this in conflict with the Git standard of having commit messages be 72 chars wide. Should I understand that the guideline is to ignore commit message width guidelines in favor of stable URLs, or can we have exceptions to the full URL rule? --Gesh (talk) 21:45, 8 February 2026 (UTC)
- The full URL is preferred. The commit message formatting is based on conventions, not standards, hence best-effort. — Lahwaacz (talk) 11:48, 1 March 2026 (UTC)