Vendor neutral documentation #20207
Replies: 1 comment
-
|
We can't "move" the access.rh.com docs -- these are the RHEL product documentation, and our team isnt' even writing them, and we can't just maintain a "fork" of them for both legal and also capacity reasons. We actually keep the RHEL docs links in the Debian/Ubuntu/arch packages as well -- they are publicly accessible, and we found that better than disabling them entirely. However, I understand if you don't want to link to them in openSUSE -- so how about we provide a build-time knob to hide them? Most of them are in manifest.json, so we can either remove them at
We can certainly find a way to conditionalize these. |
Beta Was this translation helpful? Give feedback.
-
while the cockpit project has a decent amount of vendor neutral documentation at https://cockpit-project.org/documentation.html there are many links that point to redhat documentation. On top of this all of the help links inside cockpit point to redhat.
If we could move all the documentation to https://cockpit-project.org at SUSE we would be able to leave the documentation as it is. However as it points to redhat documentation we have to make our own documentation duplicating work. A single vendor neutral documentation would allow us to unify our documentation efforts and produce a better higher quality document
Beta Was this translation helpful? Give feedback.
All reactions