We can simply lock non-contributors out of creating projects on this install. I think that's appropriate -- do you want to do the honors?

• Create a project called "Progenitors of Order".
• Give it a cool icon.
• Add everyone you trust to create projects to it.
• In Applications -> Projects -> Edit Policies, set "Can Create Projects" to "Members of Project: Progenitors of Order".

My question is, do we feel it's ok to create objects with no policys (in general).

The create workflow is kind of buggy right now in that projects can end up literally without policies -- that's just a bug and will be fixed by the move to ApplicationTransactions (D7370, D7371, etc.) After that, they'll get (presumably configurable) default policies, like other objects created through non-policy interfaces.

I think it's OK to create projects with default policies, and OK not to prompt for them on a lightweight workflow.

I also think it's fine to make that workflow heavier, but maybe after T1344/T390/T3190 so we can get more fields there? My vague guess is that the fields in order of importance are:

• Name
• Type
• Hashtag
• Members
• Join Policy
• Edit Policy
• Blurb
• View Policy

So maybe we toss "Blurb" and replace it with other stuff higher up on that list?

Oh as along we have defaults, that's cool. Close this then?

I think we can leave it open -- I do think that dialog is worth another look once we have more of the fields built out. The fact that "blub" is there but none of that almost-certainly-more-important stuff is is pretty silly.