Martin Walsh wrote:
> Well at the moment it is effectively a repository management app. You
> cannot search projects etc. If a Leader gets redirected to the SCM
> console from the portal,...
I agree with Danek - your use case seems incomplete. I'd
add some context, such as: Why would people use this
app? Who would they be (and would their actions differ based
on their roles)? What tasks would they have in mind? Where
would they have been immediately before coming here?
When I think about this, there are two users that come to mind:
1) I am a OS.o site admin who needs to play god and fix something.
I login directly to repo.OS.o app and diddle away at cross-
project things, possibly looking under the covers to diagnose
systemic problems.
2) I am a project leader. I am logged into os.o and playing with
my projects. I decide I need to do something with the repos
associated with one of my projects. It is notable that I
don't really care about the repos used by other projects,
because I don't have the authority to do anything with them.
I can't think of any other common use cases - in particular,
I would expect general participants trolling for interesting
stuff to be searching thru and for projects, not repos...
In both these use cases, the repo app provides repo admin
functionality; general repo browsing, searching, viewing etc
seems more of a service that needs to be provided to other
parts of the app suite to allow them to better integrate
the repos into their views of the world.
-John
