| |
@@ -59,6 +59,9 @@
|
| |
. **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.__
|
| |
+ . **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.
|
| |
. **Test your process.** If possible, use a fresh guest VM — or at least a brand-new user account. Run your process from beginning to end to ensure it works. Fix, rinse, and repeat.
|
| |
|
| |
== Image and screenshot tips
|
| |
