**Rush** wrote on `2014-07-15 18:13:13 (UTC)`

@MissGayle I'm not sure yet how to respond since the process itself doesn't exist :)

Ok, so a few general thoughts re: project creation I have been hoarding...

* Naming scheme should depend on the type of project (these determine the icon and picture and maybe color?)

-- work queues (buckets for work to be organized into...overlapping)
-- group of people
-- straight up tag

 * In order to have a naming scheme projects can't be editable by users once created?  Otherwise we spend a lot of time ensuring consistent levels of abstraction, and organization and then it's all out the window post-creation process.  

* Project creation isn't a super user priv, just one that requires understanding how this stuff is organized for consistency across the install.   I would say, team leads, etc can create?  Assuming reasonable good faith in the context for people we trust.

* This one is sure to be fun :)  projects should be not be camel case, also known as lower case only please.

There are a few reasons but the most overt can be demonstrated like this:

this exists: http://fab.wmflabs.org/project/view/40/

Often referenced within the install as http://fab.wmflabs.org/tag/<project>

But, only lower case non-space references work:

http://fab.wmflabs.org/tag/trusted_user_tool/

this type of reference being pretty standard we are going to dig ourselves into a weird space where Security is a project in the project field, yet /tag/Security doesn't reference the object (/tag/security does).  That is how it works currently, and it's already confusing and weird.

That means spaces and capitals within a project name force an inconsistency in reference

* Before creating people centric projects for assigning of rights, etc.  An effort should be made to ensure it doesn't exist as another name already. (same logic applied all around I guess)

* For non-people oriented projects restricting who can join them, not sure if it makes sense?

* I'm not sure how we limit comment ability unless it's the broader view/edit permissions?

* The who can join/edit/see type permissions need to be specified in phabricator user account terms
or group terms

Using the request here as a first-through-the-breach  instance I have done this:

http://fab.wmflabs.org/T458

Mostly for discussion...


tl;dr to get a new project:

* create a request task and associate http://fab.wmflabs.org/tag/phabricator-request-project/
* gets reviewed in same manner as a gerrit change, etc.  Can be commented on, certain people can do the work, etc