Feedback from Google on Launcher App
Main issue: https://gitlab.com/gitlab-org/gitlab-ce/issues/20545
Feedback
-
Can you please edit your tagline to omit the word "GitLab"? We felt it was redundant with the title of the solution. -
What are the differences between Community and Enterprise Editions? Is it a difference in features, support, or something different? We should clarify the differences. -
We would like the "Learn More" section of the Overview to link to a solution-specific page. Are there separate pages for the Community and Enterprise offerings that we could link to? -
Is there a reason you chose SSD as the default disk type? This is significantly more expensive than a standard disk, so we like to avoid this option when possible. @marin for input on this. -
The "version" listed should be updated to the correct version number. -
Please add the operating system to the tech stack on the righthand side. This is not available in the Partner Portal and has to be done manually in the DM templates. -
The "About GitLab" section of your listing still has the holding text and needs to be updated. -
All solutions are required to have a Tutorials & Documentation, Maintenance & Support, and EULA information entered. These sections are not in your listing. -
The Getting Started Guide you linked in an earlier email does not work anymore. @axil can you please look into this? The link we had is dead. -
Your admin portal is inaccessible by default because the ports were not opened. @marin which ports do we need to open to handle this? -
We are concerned about the process flow for the admin portal: - Admin portal asks the user to create a password. Does not ask to specify the user name initially.
- Then after you create the password, it shows you a login page. As a user you are confused because thats the first time you see user name field being asked. You enter your user name and the password you just created. You get invalid credentials.
- Then you notice a button to register. You then go to registration screen by clicking on the button, recreated the user name and password etc. then it will let you into the admin console.
-
Please use the autogen password capability to assign a temp password upon deployment. The current workflow of setting the password later creates a security concern. -
It appears that you can only SSH if you change the username to "root". @marin thoughts? -
The license ID that was attached to the Enterprise version is incorrect. You attached the Community license by mistake. @balasankarc can you please revisit this? -
Can you please add Next Steps in your post-deployment page to walk the user through getting started with their new deployment?