-
Couldn't load subscription status.
- Fork 67
Checkbox remote nomenclature documentation upgrade #562
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Following a discussion with the documentation team that led to the creation of a PR on their side[1], make sure to be in the docs/ directory before triggering the different commands. This should make woke work as expected. Please note that according to woke doc[2], the parameter to set this is "workdir". [1] canonical/sphinx-docs-starter-pack#40 [2] https://github.com/marketplace/actions/run-woke
- Update glossary to include terms like DUT, Testbed, as well as Checkbox Controller and Checkbox Testbed - Clean up rst markup - Add links to glossary terms or other sections when it makes sense
Not sure why testbed is marked as an unkown word, it's in the wiktionary: https://en.wiktionary.org/wiki/testbed
Following proposal to provide better naming for Checkbox remote[1], it was decided to use the following terms: - "controller" for the entity that connects to remote DUT - "agent" for the entity that runs on DUT or Zapper connected (directly attached via various interfaces) to DUT to execute tests Since "testbed" had been originally used for the second term in the first draft, this commit addresses the "testbed" -> "agent" change. [1] https://docs.google.com/document/d/1GuR5xudmxgZ3bRMSRcuy0bZyX3We3UvooP0WT_VcXSA/
This was still useful when Checkbox was published on it, but it's not anymore.
7de0406 to
67122b4
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
one small mistake, some comments and a question below
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very good job with the new nomenclature, +1
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One thing I think needs changing.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
TYVM!
+1
* Run commands from the docs/ directory Following a discussion with the documentation team that led to the creation of a PR on their side[1], make sure to be in the docs/ directory before triggering the different commands. This should make woke work as expected. Please note that according to woke doc[2], the parameter to set this is "workdir". [1] canonical/sphinx-docs-starter-pack#40 [2] https://github.com/marketplace/actions/run-woke * Update glossary and clean up doc pages - Update glossary to include terms like DUT, Testbed, as well as Checkbox Controller and Checkbox Testbed - Clean up rst markup - Add links to glossary terms or other sections when it makes sense * Replace references to master and slave Fix CHECKBOX-658 * Rework the Checkbox remote interrupt screen explanation * Rework the page about the Checkbox remote service * Add words to spelling ignore list Not sure why testbed is marked as an unkown word, it's in the wiktionary: https://en.wiktionary.org/wiki/testbed * Fix rst reference to the launcher doc * Replace mentions of "testbed" with "agent" Following proposal to provide better naming for Checkbox remote[1], it was decided to use the following terms: - "controller" for the entity that connects to remote DUT - "agent" for the entity that runs on DUT or Zapper connected (directly attached via various interfaces) to DUT to execute tests Since "testbed" had been originally used for the second term in the first draft, this commit addresses the "testbed" -> "agent" change. [1] https://docs.google.com/document/d/1GuR5xudmxgZ3bRMSRcuy0bZyX3We3UvooP0WT_VcXSA/ * Rename [daemon] section of the launchers into [agent] section * Remove PyPI from glossary This was still useful when Checkbox was published on it, but it's not anymore. * Use warning instead of note for field deprecation comment * Address feedback regarding service and configs pages * Rename reference from DUT to Agent in configs page * Update remote explanation
* Run commands from the docs/ directory Following a discussion with the documentation team that led to the creation of a PR on their side[1], make sure to be in the docs/ directory before triggering the different commands. This should make woke work as expected. Please note that according to woke doc[2], the parameter to set this is "workdir". [1] canonical/sphinx-docs-starter-pack#40 [2] https://github.com/marketplace/actions/run-woke * Update glossary and clean up doc pages - Update glossary to include terms like DUT, Testbed, as well as Checkbox Controller and Checkbox Testbed - Clean up rst markup - Add links to glossary terms or other sections when it makes sense * Replace references to master and slave Fix CHECKBOX-658 * Rework the Checkbox remote interrupt screen explanation * Rework the page about the Checkbox remote service * Add words to spelling ignore list Not sure why testbed is marked as an unkown word, it's in the wiktionary: https://en.wiktionary.org/wiki/testbed * Fix rst reference to the launcher doc * Replace mentions of "testbed" with "agent" Following proposal to provide better naming for Checkbox remote[1], it was decided to use the following terms: - "controller" for the entity that connects to remote DUT - "agent" for the entity that runs on DUT or Zapper connected (directly attached via various interfaces) to DUT to execute tests Since "testbed" had been originally used for the second term in the first draft, this commit addresses the "testbed" -> "agent" change. [1] https://docs.google.com/document/d/1GuR5xudmxgZ3bRMSRcuy0bZyX3We3UvooP0WT_VcXSA/ * Rename [daemon] section of the launchers into [agent] section * Remove PyPI from glossary This was still useful when Checkbox was published on it, but it's not anymore. * Use warning instead of note for field deprecation comment * Address feedback regarding service and configs pages * Rename reference from DUT to Agent in configs page * Update remote explanation
Description
After deciding on the new nomenclature (Testbed and Controller), the documentation needed to be updated.
This PR
Part 4. requires some attention, because I'm not entirely sure about Checkbox internals with regards to snap/daemon/service and how each of these interact with each others. I've removed what I thought was not necessary, but I could be wrong.
Click here to see the changes in action!
I've split my work into different commits for easier review.
Resolved issues
Fixes CHECKBOX-658
Tests
Checked that pages looked OK during rewriting using
make run, and checked inclusive language, spelling and links with