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

User improvements #612

Merged
merged 11 commits into from
Oct 23, 2023
Merged

User improvements #612

merged 11 commits into from
Oct 23, 2023

Conversation

vanmaegima
Copy link
Member

@vanmaegima vanmaegima commented Oct 18, 2023

Readiness

  • Merge (pending reviews)
  • Merge after date or event
  • Draft

Overview

This brings usability improvements, focusing to ease customer support.
This covers general customer/CS feedback as well.

Checklist

Optional. Add a 'x' to steps taken.
You can fill this out after opening the PR. "Did I..."

  • Run spelling and grammar check, preferably with linter.
  • Avoid changing any header associated with a link/reference.
  • Step through instructions (or ask someone to do so).
  • Review for wordiness
  • Match tone and style of page/section.
  • Run make linkcheck.
  • View HTML in a browser to check rendering.
  • Use semantic newlines.
  • follow best practices for commits.
    • Descriptive title written in the imperative.
    • Include brief overview of QA steps taken.
    • Mention any related issues numbers.
    • End message with sign off/DCO line (-s, --signoff).
    • Sign commit with your gpg key (-S, --gpg-sign).
    • Squash commits if needed.
  • Request PR review by a technical writer and at least one peer.

Comments

Any thing else that a maintainer/reviewer should know.
This could include potential issues, rational for approach, etc.

@vanmaegima vanmaegima requested review from kprosise, angolini and a team October 18, 2023 21:34
@mike-scott
Copy link
Contributor

@vanmaegima These are great changes. LGTM, let's see what @Tim-Anderson says.

@vanmaegima
Copy link
Member Author

@kprosise I've reviewed the vale errors but I think it's ok ignoring them for now (most seem false negatives). Let me know if you'd like me to fix any of them. Also I don't know why the docs run is failing (maybe a package update again?).

Copy link
Contributor

@kprosise kprosise left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some small suggestions, otherwise it LGTM!

source/reference-manual/security/factory-keys.rst Outdated Show resolved Hide resolved
source/user-guide/troubleshooting/troubleshooting.rst Outdated Show resolved Hide resolved
source/user-guide/troubleshooting/troubleshooting.rst Outdated Show resolved Hide resolved
source/user-guide/troubleshooting/troubleshooting.rst Outdated Show resolved Hide resolved
@kprosise
Copy link
Contributor

@kprosise I've reviewed the vale errors but I think it's ok ignoring them for now (most seem false negatives). Let me know if you'd like me to fix any of them. Also I don't know why the docs run is failing (maybe a package update again?).

Yeah, the vale issues can mostly be ignored here...even when technically accurate,  there can be exceptions. 

I'll take a look at why the run is failing.

Copy link
Contributor

@Tim-Anderson Tim-Anderson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A few comments and one question

source/reference-manual/linux/linux-distro.rst Outdated Show resolved Hide resolved
@kprosise
Copy link
Contributor

@vanmaegima Whenever you're ready, just squash and I'll then go ahead and merge.

@vanmaegima
Copy link
Member Author

@kprosise just waiting a couple of days for the lmp-dev-reg comments to close.

Signed-off-by: Vanessa Maegima <[email protected]>
This covers feedback from CS team to clarify the use of distros.

Signed-off-by: Vanessa Maegima <[email protected]>
lmp-mfgtool is now used across different SoC families and not only
i.mx, so fix that.

Signed-off-by: Vanessa Maegima <[email protected]>
This is now covered under Platform Customizing, so remove this
example for maintainability.

Signed-off-by: Vanessa Maegima <[email protected]>
Make the page clearer so we have a directly link to point to customers
that links to the needed information.

Signed-off-by: Vanessa Maegima <[email protected]>
This brings us directly links that can be pointed to customers
for each specific architecture.

Signed-off-by: Vanessa Maegima <[email protected]>
This blog brings helpful information when trying to use different
set of keys in the factory.

Signed-off-by: Vanessa Maegima <[email protected]>
This is required in case there is a change in the used build keys.

Signed-off-by: Vanessa Maegima <[email protected]>
@doanac
Copy link
Member

doanac commented Oct 20, 2023

Copy link
Collaborator

@angolini angolini left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

source/user-guide/troubleshooting/troubleshooting.rst Outdated Show resolved Hide resolved
source/user-guide/troubleshooting/troubleshooting.rst Outdated Show resolved Hide resolved
source/user-guide/troubleshooting/troubleshooting.rst Outdated Show resolved Hide resolved
@doanac
Copy link
Member

doanac commented Oct 20, 2023

@vanmaegima
Copy link
Member Author

@kprosise this one should be good to go as well, if vale errors can be ignored

Copy link
Contributor

@Tim-Anderson Tim-Anderson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just one more nit on spelling error but other than that LGTM

source/user-guide/troubleshooting/troubleshooting.rst Outdated Show resolved Hide resolved
Copy link
Member

@vkhoroz vkhoroz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

This is a good content.
I believe @vanmaegima and @angolini should be able to resolve the leftover nuances.

@doanac
Copy link
Member

doanac commented Oct 20, 2023

This is used to run fiovb_printenv from a container to retrieve custom
RPMB variables.

Signed-off-by: Vanessa Maegima <[email protected]>
@doanac
Copy link
Member

doanac commented Oct 20, 2023

@kprosise kprosise merged commit a4bd80f into foundriesio:main Oct 23, 2023
1 check failed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants