- 14 Mar, 2022 1 commit
-
-
Evangelos Foutras authored
The default security policy doesn't allow executing asciidoctor.
-
- 22 Aug, 2021 1 commit
-
-
Morten Linderud authored
Signed-off-by:
Morten Linderud <morten@linderud.pw>
-
- 21 Aug, 2021 3 commits
-
-
Kristian Klausen authored
Fix #2
-
-
Fixes: c84f07e4 ("Apply 1 suggestion(s) to 1 file(s)")
-
- 17 Aug, 2021 8 commits
-
-
Sven-Hendrik Haase authored
-
Sven-Hendrik Haase authored
-
Sven-Hendrik Haase authored
-
-
-
-
Sven-Hendrik Haase authored
-
Sven-Hendrik Haase authored
-
- 16 Aug, 2021 2 commits
-
-
Sven-Hendrik Haase authored
-
-
- 15 Aug, 2021 2 commits
-
-
Sven-Hendrik Haase authored
We only have strictly necessary cookies and as such we're not legally required to provide an exhaustive list of which cookies we make use of.
-
-
- 18 Jul, 2021 5 commits
-
-
-
-
-
-
Sven-Hendrik Haase authored
-
- 17 Jul, 2021 1 commit
-
-
nl6720 authored
* Use HTTPS where possible. * Use ArchWiki's prettier short URLs (/title/ instead of /index.php/).
-
- 15 Jul, 2021 5 commits
-
-
Jonas Witschel authored
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).
-
Jonas Witschel authored
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.
-
Jonas Witschel authored
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.
-
Jonas Witschel authored
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".
-
David Runge authored
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.
-
- 14 Jul, 2021 2 commits
-
-
David Runge authored
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.
-
David Runge authored
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).
-
- 12 Jul, 2021 1 commit
-
-
David Runge authored
.editorconfig: Add editorconfig file to ensure the same formatting among all markdown files.
-
- 31 May, 2021 3 commits
-
-
Sven-Hendrik Haase authored
-
Sven-Hendrik Haase authored
- 11 Jan, 2021 2 commits
-
-
pkgstats is hosted on a different domain and has its own privacy policy.
-
-
- 09 Jan, 2021 1 commit
-
-
nl6720 authored
Reported in https://wiki.archlinux.org/index.php/Talk:Code_of_conduct#Typo_in_Cross-posting_section .
-
- 30 Oct, 2020 1 commit
-
-
Jakub Klinkovský authored
-
- 25 Oct, 2020 2 commits
-
-
Jakub Klinkovský authored
-
Jakub Klinkovský authored
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
-