Feedback from evaluation in a corporate environment

[Ian Clatworthy]

Michael Gliwinski wrote:

> How about combining init, init-repo and init-workspace into a new init which 
> supports different tree (workspace) organizations, e.g.
> 
>   bzr init --repo    # mostly useful for advanced cases
>   bzr init --plain-branch    # ditto
>   bzr init --shared-tree
>   bzr init --feature-branches
>   ... etc ...

+1. I'll going to rename feature-branches to branch-in-trunk and repo to
shared-repository though.

> Others also suggested 'bzr init/create --shared/--single', but IMO it might be 
> better to go that one step ahead and start thinking in high-level terms of 
> workspace organization.

> One question that pops up in my mind when thinking about it is, would it be 
> useful to abstract the workspace organization model, so that it could be 
> re-used, possibly configurable, etc.?

That's precisely the direction I'm going. The Initialize dialog in
Explorer will be based on a registry of workspace models. The available
models will be sorted alphabetically, e.g. radio buttons of

[*] Branch in trunk
[ ] Plain branch
[ ] Shared repository
[ ] Shared repository no trees
[ ] Shared tree

Plugins (like scmproj) will be able to add their own models so the list
could easily grow to include:

[ ] Co-located branch
[ ] Loom
[ ] Pipeline
[ ] SCM project

The Initialize dialog will simply map to an init-workspace command with
'new' as an alias. Command line users will then be able to do stuff like:

  bzr new --shared-tree
  bzr new --scm-project

See
https://code.edge.launchpad.net/~ian-clatworthy/bzr-explorer/extensible-init-workspace
if you wish to track my progress on this. I plan to have this included
in Explorer 1.0beta later this month.

Ian C.