Talk:General guidelines

From ArchWiki

Extend the no-bots clause for IRC

Recent event's have shown that people interpret the

  • There is only one official channel bot. phrik!~archbot@archlinux/bot/phrik. Do not spam bot commands and limit your usage to things that are helpful. If you want to bring your own bot into any Arch Linux channel, ask the operators before doing so.

Rule in very different ways and have been sneaking in bridges to other chat protocols (usually discord) into the #archlinux channel. This is against freenode's 'no logging without permission' guidelines, which the channel operators adopt for #archlinux.

I would like to extend or supplement that rule with something like:

  • Bridging channels to other communication protocols like discord, matrix, slack, etc. is not allowed without the permission of the channel operators.
  • Do not publish logs, processed or not, to the public without asking the operators for permission.

I'm not entirely happy with the explicit mention of these three messengers and would welcome suggestions to generalize it. Merging these two into the existing "no Bots" clause would be fine but I fear it would make it overly long and hard to read.

Namarrgon (talk) 12:28, 1 May 2019 (UTC)

How about: "Do not publish logs without the permission of operators, nor bridge to other protocols like discord, slack etc., without permission". Jasonwryan (talk) 07:55, 2 May 2019 (UTC)

Move to GitLab

Since the Privacy policy is moving to GitLab, I think it would make sense to move the Code of conduct into the same repo to keep the community-wide legal stuff in one place. Other advantages would be markdown, natural reviews via the GitLab flow and maybe also better visibility. Opinions?

-- Lahwaacz (talk) 22:11, 15 October 2020 (UTC)

Unlike the Privacy Policy or Terms of Service, the Code of Conduct does not start with "DRAFT DRAFT DRAFT...". Can we redirect this page already? -- nl6720 (talk) 15:51, 20 December 2020 (UTC)
I'd say yes :) -- Lahwaacz (talk) 16:31, 20 December 2020 (UTC)
The redirect is now in place and I think I fixed all sections links. The only thing left are the translations. Legal agreements shouldn't really have unofficial translations... Should we redirect them all of to archlinux-service-agreements:code-of-conduct? -- nl6720 (talk) 10:13, 9 January 2021 (UTC)
Further action is delayed until is closed. -- nl6720 (talk) 09:15, 26 June 2021 (UTC)
That issue is now closed. I flagged all translations (Special:PrefixIndex/Code of conduct () for moving to "General guidelines (language)". -- nl6720 (talk) 15:44, 17 July 2021 (UTC)
I added DeveloperWiki talk:TrademarkPolicy#Move to GitLab, this may be relevant here.
-- NetSysFire (talk) 08:34, 18 July 2021 (UTC)

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)

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 ?

-- 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 (likely need an admin to change that, mods cannot)
-- WorMzy (talk) 12:01, 18 July 2021 (UTC)

Reply to mailing list

Emails sent out by mailing lists are not mangled anymore. They do not contain a Reply-To header with the mailing list address meaning the mailing list needs to be explicitly set as the recipient when replying.

This should be documented in General guidelines#Mailing lists. See draft below.

-- nl6720 (talk) 10:05, 12 June 2022 (UTC)

Draft: Reply to mailing list

When replying to a mailing list thread, make sure to reply to the mailing list instead of the author of the original email. Most email clients should provide a "reply to mailing list" feature among the reply options, if not, input the mailing list email address in the To field manually.

For mailing lists that do not require subscribing, such as arch-mirrors-announce and aur-requests, use reply to all and make sure the mailing list is among the recipients.