Skip to content
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

sys/riotboot: documentation issues #11243

Open
gschorcht opened this issue Mar 23, 2019 · 2 comments
Open

sys/riotboot: documentation issues #11243

gschorcht opened this issue Mar 23, 2019 · 2 comments
Assignees
Labels
Area: doc Area: Documentation Type: bug The issue reports a bug / The PR fixes a bug (including spelling errors)

Comments

@gschorcht
Copy link
Contributor

Description

The documentation of the riotboot module and its associated files has the following problems:

  1. Documentation in sys/include/slot.h causes a problem in Modules / System page and further in Modules / System / Helpers ....

  2. Documentation structure for associated files and pseudomodules seems to be a bit confusing. Documentation of associated files and pseudomodules is quite difficult to find in Modules / System page

    Due the alphabetical order they are difficult to find.

  3. Page titles for riotboot_hdr and expecially riotboot_slot are not self explaining or even confusing.

Expected results

Even though it is possible to define pseudomodules riotboot_%, these pseudomodules are not used. In fact, there is only one module riotbootand riotboot_flashwrite, riotboot_hdr and riotboot_slot are simply parts of the riotboot module.

IMHO, it would be better to have one page Module / System / Riotboot ... or something self explaining for module riotboot and to add the documentation of associated files or pseudomodules to that group.

Related Issues/PRs

PR #11181

@gschorcht gschorcht added Type: bug The issue reports a bug / The PR fixes a bug (including spelling errors) Area: doc Area: Documentation labels Mar 23, 2019
@stale
Copy link

stale bot commented Sep 24, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you want me to ignore this issue, please mark it with the "State: don't stale" label. Thank you for your contributions.

@stale stale bot added the State: stale State: The issue / PR has no activity for >185 days label Sep 24, 2019
@kaspar030
Copy link
Contributor

unstale

@stale stale bot removed the State: stale State: The issue / PR has no activity for >185 days label Sep 24, 2019
@aabadie aabadie assigned fjmolinas and unassigned kaspar030 and kYc0o Oct 16, 2019
@MrKevinWeiss MrKevinWeiss added this to the Release 2021.07 milestone Jun 22, 2021
@MrKevinWeiss MrKevinWeiss removed this from the Release 2021.07 milestone Jul 15, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: doc Area: Documentation Type: bug The issue reports a bug / The PR fixes a bug (including spelling errors)
Projects
None yet
Development

No branches or pull requests

5 participants