From 40e338a9c12d2222d26f2ceb72311d70f4082706 Mon Sep 17 00:00:00 2001 From: Till Maas Date: Nov 12 2020 08:13:31 +0000 Subject: Use recommended Copr notation The content tips recommend to use Coprr instead of COPR. Use this notation in the guidelines, too, for consistency. --- diff --git a/modules/ROOT/pages/writing-guidelines.adoc b/modules/ROOT/pages/writing-guidelines.adoc index 1c4352a..84a4aee 100644 --- a/modules/ROOT/pages/writing-guidelines.adoc +++ b/modules/ROOT/pages/writing-guidelines.adoc @@ -58,7 +58,7 @@ These tips are about things to do — and avoid — in what you tell users to do . **Prefer free software where practical (and officially packaged software wherever possible).** The Magazine can still cover non-FOSS software to be used on Fedora, where we know or suspect that software is very popular and useful to Fedora users. (Google Chrome is a good example.) But if your article is covering a general process, use FOSS software. . **Use libvirt/KVM in tips, not VirtualBox or other hypervisors.** Frequently people coming from other platforms have VirtualBox experience. However, the KVM hypervisor and libvirt in Fedora are FOSS and part of the platform. Use them, write about them, love them. . **Unless necessary, use Fedora family distributions.** The Fedora Magazine promotes Fedora. Unless the point of your article is to specifically explain a cross-distribution mechanism, use installations, containers, or distributions within its family (Fedora, CentOS, RHEL). -. **Copr software must be accompanied by a caveat.** The Copr build system is not managed by the Fedora release team and does not provide official software builds. If you cover some software from Copr, ensure there’s no official build. If not, include a statement like this: __COPR is not officially supported by Fedora infrastructure. Use packages at your own risk.__ +. **Copr software must be accompanied by a caveat.** The Copr build system is not managed by the Fedora release team and does not provide official software builds. If you cover some software from Copr, ensure there’s no official build. If not, include a statement like this: __Copr is not officially supported by Fedora infrastructure. Use packages at your own risk.__ . **Avoid exclusionary or problematic language.** These are examples of terminology to avoid wherever possible in articles: .. **blacklist/whitelist** — Use __allowlist/denylist__ instead, which is more directly descriptive of the purpose. .. **master/slave** — Use __primary/secondary__, __primary/replica__, __active/passive__, __active/standby__, or another similar construct.