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

update priority screenshots for Qubes 4.1 #113

Merged
merged 2 commits into from
Jul 7, 2022
Merged

Conversation

cfm
Copy link
Member

@cfm cfm commented Jul 7, 2022

Towards #105, updates priority screenshots—i.e., those that will be helpful for upcoming guided installations with pilot participants—for Qubes 4.1, per #105 (comment).

Checklist

  • In GitHub's visual diff, screenshots are correct and identical except for the intended differences between Qubes 4.0 and 4.1.

@cfm cfm added the qubes-4.1 label Jul 7, 2022
@cfm cfm requested a review from eloquence July 7, 2022 19:59
Copy link
Member

@eloquence eloquence left a comment

Choose a reason for hiding this comment

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

Looks good! Merging without forwarding stable tag until the main 4.1 docs PR lands.

A minor thing we may want to standardize going forward is the username used in screenshots. I used nbly as a fake journalist name, but we should probably just standardize on user since that's what we recommend using in the install docs.

@eloquence eloquence merged commit 5af6a3a into main Jul 7, 2022
@cfm
Copy link
Member Author

cfm commented Jul 8, 2022

Fair, but tricky when the screenshot machine is also a developer's primary workstation. (Which this machine isn't yet, but it will be soon!) I would consider redaction to be adequate to avoid confusion (not really to provide any privacy); would you, @eloquence?

@legoktm legoktm deleted the 105-screenshots branch June 10, 2024 16:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants