Workflow Confusing When Fetching a Project

[Brett Alton]

To begin, we must add the groundcontrol PPA (this is only until groundcontrol is included in Lucid). Then we must update APT and install groundcontrol. This is all fine.

To begin using groundcontrol, we must run lp-groundcontrol or 'System > Preferences > Ground Control Configuration', then we must traverse to ~/Projects.

Here we are presented to 'Fetch Project'. So say I search 'Ground Control' and select 'lp:groundcontrol'. Then we must manually select 'Fetch Branch' where we are presented not with projects, but with branches of the project. Did I just added 'lp:groundcontrol'? That's what it seemed like to me.

Wouldn't it make sense to include 'Fetch Branch' at the same time as 'Fetch Project' so that both are done in one swoop? 'Fetch Branch' can still exist inside every project folder (e.g. ~/Projects/ground-control/) but to have the branch downloaded at the same time I fetch a project makes logical sense to me. No need to merge the two dialogues, just run one after the other and allow the person to hit 'cancel' if they don't want to fetch a branch after fetching a project.

[Martin Owens (doctormo)]

The problem is for projects like inkscape, where code branches are 300MB downloads and you may want to get a different branch.

What perhaps might be useful is a checkbox that's by default checked that allows you to automatically down a branch.

[Alex Launi (alexlauni)]

Why was this marked invalid? This is a reasonable bug- and one I was about to file. What about this- After you pick a project to work on present the user with another list where they can select branches to pull down, with trunk selected by default.

[Martin Owens (doctormo)]

The bug was confusing and more suited for a feature voting site were the requirements can be worked out and then posted as a bug report. I can't find any work to do here, so it's not valid.

Feel free to open up a new one though.