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

Change naming of zLUX on doc site as appropriate #214

Closed
nannanli opened this issue Nov 5, 2018 · 4 comments
Closed

Change naming of zLUX on doc site as appropriate #214

nannanli opened this issue Nov 5, 2018 · 4 comments
Assignees
Labels
area: docs Documentation issue or issues that have documentation impact area: webui Issues related to Zowe Application Framework (zLUX) or Zowe Desktop (MVD))

Comments

@nannanli
Copy link
Member

nannanli commented Nov 5, 2018

We renamed zLUX to Zowe Application Framework and MVD to Zowe Desktop in User Guide. However, in developer tutorials and samples, there are still some occurrences that confuse users.

Feedback from Alex on Zowe #zowe-onboarding channel:
Question on Naming Convention: I see the zowe document and there are many places call individual components as all ‘zowe’ or ‘zowe - something(zowe-cli)’ but zLUX seems like another name there - is there a reason for it? I see zLUX is another name for Zowe Application Framework, but it is being used mixed with Zowe again(i.e. Zowe zLUX). I am sorry if this has already been discussed but I would like to see a common naming convention to each components (server side, client side etc) and show in the beginning of the document

@nannanli nannanli added the area: webui Issues related to Zowe Application Framework (zLUX) or Zowe Desktop (MVD)) label Nov 5, 2018
@nannanli nannanli added the area: docs Documentation issue or issues that have documentation impact label Nov 7, 2018
jhenryRocket added a commit that referenced this issue Nov 13, 2018
I also fixed a typo
nannanli added a commit that referenced this issue Nov 14, 2018
@BrandonJenkins14
Copy link
Contributor

What is the status of this issue @jhenryRocket ? I see you did some work here, shall we close the issue? Thanks!

@jhenryRocket
Copy link
Contributor

Ultimately, I think Alex's idea: "I would like to see a common naming convention to each components (server side, client side etc) and show in the beginning of the document" is a good solution to this issue. Hopefully, this will be the case in a future release. (i.e. we no longer have references to zLUX.) Currently zLUX is used in the codebase.

@BrandonJenkins14
Copy link
Contributor

@AlysonAndresen @jasonenglish2039 Just a reminder that this issue exists - basically using consistent/correct terms throughout doc for things like "Zowe Desktop", formerly MVD.

jasonenglish2039 added a commit that referenced this issue May 17, 2019
…owe Application Framework" and "MVD"->"Zowe Desktop"
@jasonenglish2039
Copy link
Contributor

See commit to docs-staging referenced in the last comment in this issue (eb5c418). I searched the doc for instances of "zLUX" and "MVD." Changed "zLUX" to "Zowe Application Server" and "MVD" to "Zowe Desktop."

Note: Most instances of zLUX are in directory names or URLs or code. Those could not be changed obviously.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: docs Documentation issue or issues that have documentation impact area: webui Issues related to Zowe Application Framework (zLUX) or Zowe Desktop (MVD))
Projects
None yet
Development

No branches or pull requests

4 participants