GitLab

* Use HTTPS where possible.
* Use ArchWiki's prettier short URLs (/title/ instead of /index.php/).

The current enforcement procedure is not very specific and as a result it can
be hard to enforce: it is unclear who can be contacted if behaviour running
afoul of the Code of Conduct is witnessed, who makes the final decision on the
actions taken, how these decisions are communicated, ... The current procedure
is also geared quite specifically towards users, it is not clear what happens
if staff members are directly involved.

Try to clarify the open questions by outlining a standard procedure that should
be followed, while trying to keep the spirit of the current enforcement
procedure (issue a warning first by default, if it goes unheeded, further
actions can be taken).

The "Freedom" section is very verbose and its purpose for the Code of Conduct
is not entirely clear. The most relevant part seems to be the last few
sentences (basically "these rules are necessary limitations to create a
functioning community"). Extract these and move them to the preamble, remove
the rest of the section.

The remaining introduction of the "Correctness" section can be moved under
"Examples of unwanted behaviour" under the umbrella term "overly broad
questions". Add a link for "help vampirism" from the now removed Forum
guidelines to this subsection to make it a little clearer what kind of
questions are unwanted.

The remaining "Arch Linux distribution support ONLY" subsection doesn't really
fit into the rest of the Code of Conduct, so promote it to a separate section
to make it more visible.

The distinction of "Legality" and "Correctness" seems a bit arbitrary, most of
these are just examples of unwanted behaviour following from the overarching
guidelines outlined under "Respect".

code-of-conduct.md:
Fix the wiki link to the historic version of the Code of Conduct in the
"About this document" section.
The location changed due to hosting the "General guidelines" (i.e.
technical guidelines) on the Arch wiki again.

code-of-conduct.md:
Replace the in-document links for the specific fora guidelines with a
link to the "General guidelines" wiki article
(https://wiki.archlinux.org/title/General_guidelines) and move it to a
"Further reading" section.
Point out that guidelines for the specific communication channels are
not part of the Terms of Service.
Add a notice to the "Further reading" section that users are expected to
review the respective communication channel guidelines before each use
of any of the communication channels.
Add note to the "Further reading" section, that changes to links in that
section and the guidelines themselves may change outside of the 30 days
notice period of changes to the Code of Conduct itself.

code-of-conduct.md:
Remove the specific fora guidelines from the Code of Conduct, as they
are technical guidelines, which will be maintained outside of the Terms
of Service on the Arch Wiki
(https://wiki.archlinux.org/title/General_guidelines).

.editorconfig:
Add editorconfig file to ensure the same formatting among all markdown
files.

https://archlinux.org/news/move-of-official-irc-channels-to-liberachat/

pkgstats is hosted on a different domain and has its own privacy policy.

Reported in https://wiki.archlinux.org/index.php/Talk:Code_of_conduct#Typo_in_Cross-posting_section .

Replaced one instance of "website" with "websites", and "site" with
"service". Also replaced "when you access the website" with
"when you access an Arch service".

This fixes the first point of this wiki discussion:
https://wiki.archlinux.org/index.php/ArchWiki_talk:Privacy_policy#Rights_under_GDPR

Permalink to the source: Revision as of 13:59, 27 May 2020
https://wiki.archlinux.org/index.php?title=Code_of_conduct&oldid=616582

The original author of the document is jasonwryan (begun in May 2016),
over the years many fundamental changes by various wiki editors
followed. The history can be found here:
https://wiki.archlinux.org/index.php?title=Code_of_conduct&action=history

Adding a link is nice (and maybe even required by the license), using
abbreviations is acceptable as per the examples here:
https://wiki.creativecommons.org/wiki/License_Versions#Attribution-specific_elements

This makes it a bit easier to read without a markdown renderer.

The attribution reads much better when the license of this document is
pointed out explicitly, and why should we not use the latest version?

- link to the home page instead of the list of news
- add a clause about continued use of Arch services

The domain is used at the top to specify the scope of the policy. Plain
text should use either "Arch website" or "Arch service".

The paragraph about data security was improved and the statement about
providing services from secure systems was added.

The main change is that the scope of the policy is specified explicitly,
using the archlinux.org domain seemed like the best identificator.