Project visibility button

[bethcg]

Motivation

Some users want to change the visibility (private, public, internal) of their projects. Currently, this can be only done through the Gitlab settings. It is not intuitive how to do it, if you are not an experienced user.

View of Renku Project/Settings page

View of Gitlab Project/Settings page

Proposal

There are mainly two options:

• Create a button in the Project page / Settings that allows the user to change the visibility of the project (this may have some corner cases that need to be tackled).
• Create a button that redirects the user to the Gitlab settings project page within the Renku Project page/ Settings and give indications to the user on how to do the change (and include it in the documentation page).

[jdupre81]

as discussed last week, here is the design for the use case:
Change visibility of my own project + Message on a Confirmation box
Figma prototype

change.visibility.own.project.confirmation.mov

[lorenzo-cavazzi]

A few details:

• For the visibilities, re-use the same text/description we have in the "New project" page (mind they are swapped in the prototype above)
  
• Do not allow changing visibilities if the project is forked because it's probably going to fail
• If the project is part of a group, check the visibility restrictions: E.G. if the group is internal, users can pick only internal and private, but not public.
• Use the tooltip to explain why users cannot change visibilities in those cases ("Cannot change visibility on forked projects. Please check our documentation" or "This project is inside a private group. Visibility cannon be more permissive then the group one."). No need to show a tooltip when there is nothing relevant to explain.
• Keep in mind changing visibility might be restricted for other reasons. Errors will happen 😒 . We should keep this in mind for the confirmation modal: when the users confirm the visibility change, we need to wait until it's done and show a green confirmation when all is good, or a red error when something goes wrong with the GitLab message.