Rename Tails Greeter to be more plain
During the expert review, “Tails Greeter” wasn’t an intuitive name. She would have preferred “Tails Welcome Screen” or something similar.
I understand that “Greeter” comes from the backend technology from GNOME.
We could check how other projects are calling such screens.
Related to Tails -
|Related to Tails - Feature #14544: Spend software developer time on smallish UX improvements||In Progress||2018-08-31|
|Blocks Tails - Bug #17136: Persistence preset: Greeter settings||In Progress|
|Blocks Tails - Feature #17247: Core work 2020Q1 → 2020Q2: Technical writing||Confirmed|
#6 Updated by sajolida 2020-03-05 17:16:06
- Type of work changed from User interface design to End-user documentation
Hmm… Actually, it seems like the word “Greeter” is not used anywhere
in user-facing strings in the code. Then, this change only makes sense
in the documentation on the website.
We could call it “the Welcome Screen” and not change a ting in the code.
This would become a job for the Technical Writing team.
@cbrownstein: What do you think?
#12 Updated by sajolida 2020-03-25 04:12:58
- File 0001-Rename-doc-first_steps-startup_options-into-welcome_.patch added
- Status changed from Confirmed to Needs Validation
- Assignee set to cbrownstein
- Target version set to Tails_4.5
@intrigeri: Here a patch for puppet-tails.git for once 4.5 is out.
@cbrownstein: I also worked on this as part of doc/17492-secure-boot (I’ll push it when I’m done with
Feature #17492) because I was touching the same files already to adjust to Secure Boot. Sorry for the huge branch! But I made nice commits, hopefully. The commits for this ticket are 533c1b1bc7 and e257c1fbee.
- I left “Greeter” in internal documents (blueprint) and very old news.
- ‘Welcome Screen’ formatted as a feature, like Persistent Storage. I’ll document better these things in Bug #16221.
#15 Updated by intrigeri 2020-03-25 09:47:14
> Here a patch for puppet-tails.git for once 4.5 is out.
LGTM. I’m tracking this in my org-mode. Is it fine if I do this in the few days that follow the release, as opposed to “in the next few minutes/hours”?
> Ah, and shall we rename “Greeter” into “Welcome Screen” on Redmine as well? I leave it up to you.
I see that you’ve renamed “Greeter” into “Welcome Screen” in the contributors doc too, so IMO we should do the same in Redmine/GitLab. I’m tracking this locally as well.
#16 Updated by sajolida 2020-03-25 18:53:49
> Is it fine if I do this in the few days that follow the release, as opposed to “in the next few minutes/hours”?
> I see that you’ve renamed “Greeter” into “Welcome Screen” in the contributors doc too, so IMO we should do the same in Redmine/GitLab. I’m tracking this locally as well.
Great. I had a note about asking you to do this but apparently I lost it
half-way through :)
#21 Updated by intrigeri 2020-04-15 06:08:18
I’ve renamed the Redmine “Affected tool”:
- Verified that we have no custom query (that I have access to) pointing to Affected tool = Greeter
- Added “Welcome Screen” to the list of possible values
- Listed all issues (even if they’re closed) that had Affected tool = Greeter
- Set Affected tool = Welcome Screen on all these issues
- Remove “Greeter” from the list of possible values
- grep’ed our repo for links to Redmine queries that used the old value → none
I see some remaining references to “Greeter” in
wiki/src/contribute/how/documentation/style_guide/*.mdwn. Could you please fix them? I guess it’s not worth the overhead of reopening this issue nor filing a new one.
#22 Updated by sajolida 2020-04-16 21:09:42
Wow! I thought it would be a matter of renaming a field in Redmine and not mangling all tickets :(
Thanks for double-checking!
- In /contribute/how/documentation/style_guide.mdwn these are mentions to not use the word Greeter anymore:
With an article. Not *Tails Greeter* or *the Greeter*.
- /contribute/how/documentation/style_guide/*.mdwn will go away with doc/8948-persistent-storage
So we’re all good.