Public organizations are confusing #259
Description
So the idea that organizations can be public is fine, but this concept needs more thought; it makes no sense to allow any user to create a public organization and allow that public organization to be seen in MY list of organizations (I've removed public orgs from being listed).
We can have a separate page where we list the public organizations (for data discovery this can be interesting), but that needs to be separate from what users see in their space.
In short, this area needs improvement and further design considerations.
Can you also explain how this works permission wise? If I create a public organization, does it mean people can create new datasets within it (write permissions)? Or can they just see it? What if I create a private repository within a public organization? That shouldn't be listed (it currently is).