feat(interview): Project visibility [1]

[jochenklar]

This PR adds a new visibility field to Project. private is the current behavior, internal allows everybody to access the project like a guest (read only). I added a choice field in case we need a public choice in the future.

At on point we probably want to restrict projects to groups/sites but this should be better done using yet another field.

[MyPyDavid]

I think that the implementation so far looks good.

Our use case would probably require the site permissions as well.
Could we not make a rule based on user.role.member and project.owner.role.member to filter a bit for Site already? That when the current user is also a member of the same site as the project.owner?

[jochenklar]

Yes, of course. But then you cannot create template projects for all sites right? We could add a choice same site or something like this. Or we add something in settings since you might want to prevent users to add projects to other sites. Actually we need to restrict the feature to site_admins anyway, since otherwise people could just spam other peoples projects list...

[MyPyDavid]

Yeah maybe, but as long as Project does not have a sites field, the filtering could also be done just in the front-end on the projects table. Maybe users can select from which project.owners they want to see the shared projects to prevent spammable projects?
I thought this feature was meant for all users to use the project as template and not only for site_admins.