Visibility option when creating a repo is misleading

[sstine]

• Gitea version (or commit ref): 1.0.0+280-g0642cb33
• Git version: 2.9.3
• Operating system: alpine:3.4
• Database (use [x]):
  • PostgreSQL
  • MySQL
  • SQLite
• Can you reproduce the bug at https://try.gitea.io:
  • Yes (provide example URL)
  • No
  • Not relevant
• Log gist:

Description

The UI is a little misleading when it comes to selecting whether your repo should be private or public. It says "This repository is private" and the checkbox is a boolean on that statement, but to the user it looks like the UI is saying that the repo is private (even if the box is unchecked). This surprises the user when the repo they create is actually public. It would be more clear to take the approach that Github uses (screenshot below).

Screenshots

Proposed solution:

---

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

[wrouesnel]

It's also not clear what this does with organization memberships. It seems that unless I check "visibility", organization members can't see or access the repo.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.