Web IDE button should fork and open forked project when selected from read-only project
Problem to solve
When a user browses to a project that they don't have write permission to they're unable to directly access the Web IDE from the main project page. This limits someone from quickly opening an editor to contribute to a project.
Intended users
All users who might contribute to a public project via the Web IDE via code or documentation or other kinds of contributions.
Proposal
The Web IDE button should be available in all public projects even if a user does not have Write access to that specific project. When a user who does not have write access to the project, the Web IDE button should create a fork of the project in the users namespace (regardless of other available namespaces) and then open the forked project in the Web IDE.
During the forking process we should provide information to user (similar to the standard fork process) that the project is being forked and that the Web IDE will open shortly.
Permissions and Security
This model should support all public projects where a user might have view access and be able to fork the project.
What does success look like, and how can we measure that?
Success should be an increase in the number of forked and then edited in the Web IDE projects. We could implement additional instrumentation on the Web IDE button, but with existing measurements we can measure number of forks and Web IDE usage to make broad correlations.