Issue
When a reader/writer forks a private repository he may "appear" to fork it as public.

Result
This will create a forked project, but it will be empty and an error message is displayed. The user may still goto the the empty project.

Suggested Solution
A reader/writer should not have permission to fork a private project as public.

A project which is private should probably not be allowed to be forked as public unless the project has been changed to public.