Comment 3 for bug 567065

There is one valid use case for creating an empty branch--so that an admin can make it private before the code is pushed.

We could explain this case in the item:
   * Create a new, empty branch in Launchpad and link to this series so that an Admin can make it private.

Since this form is for setting up the project and series, I think we expect the the project privacy to be configured *before* the development series branch is set. We could remove this option from the form and add a message that explain that private branches should be setup first.
    * Request an admin to setup branch privacy before configuring the project's focus of development branch.

I would like to make both messages dependant on a commercial license, but I think our workflow is broken. Users often configure the project before redeeming a commercial voucher.

I think I favour showing the empty branch option only when the project has a commercial license, and the option should explain that this is for setting a private branch. Can we automatically make the project visible to the project owner?