From e7e6c4bc64b92b1efa4a1d83fe85d78c06c40598 Mon Sep 17 00:00:00 2001
From: Daniel Sheppard <dans@dansheps.com>
Date: Thu, 15 Sep 2022 21:08:41 -0500
Subject: [PATCH] Update CONTRIBUTING.md

---
 CONTRIBUTING.md | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 82f26e02..4c618474 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -18,9 +18,8 @@ When writing new definitions, there are some important guidelines to follow:
 - Every unique model number requires a discrete definition file, even if the set of components is identical.
 - Definition files must end in `.yaml`, or `.yml`
 - Use proper, human-friendly names when creating manufacturer directories (e.g. `Alcatel-Lucent` versus `alcatel`).
-- Include only components which are fixed to the chassis. Optional modular components should be omitted from the
-  definition. (Note that this does not exclude field-replaceable hardware that is expected to always be present, such
-  as power supplies.)
+- Include only components which are fixed to the chassis. Module bays and associated module types should be included for
+  all modular components which can be modelled in NetBox (network modules, power supplies, etc).
 - Name components exactly as they appear in the device's operating system (as opposed to the physical chassis label, if
   different).
 - Use the complete form of interface names where applicable. For example, use `TenGigabitEthernet1/2/3` instead of
-- 
GitLab