Thread: [Codestriker-user] linking, module, project and scm repository

SourceForge Headquarters 1320 Columbia Street Suite 310 San Diego, CA 92101 +1 (858) 422-6466

is there a way to link module, project and scm repository such that
when a project is selected, the scm repo and module are automatically
selected?

-- 
Aamer Akhter / aa...@gm...

On Thu, 16 Dec 2004 04:43, Aamer Akhter wrote:
> is there a way to link module, project and scm repository such that
> when a project is selected, the scm repo and module are automatically
> selected?

At this stage no.  Most users seem to work on only a single project at a 
time, so having the cookie remember their last project + repository 
selection seems to work ok in practice.

In your situation, do you have users which are members of multiple 
projects?

-- 
Cheers,
David

On Thu, 16 Dec 2004 10:26:48 +1100, David Sitsky
<si...@us...> wrote:
> On Thu, 16 Dec 2004 04:43, Aamer Akhter wrote:
> > is there a way to link module, project and scm repository such that
> > when a project is selected, the scm repo and module are automatically
> > selected?
> 
> At this stage no.  Most users seem to work on only a single project at a
> time, so having the cookie remember their last project + repository
> selection seems to work ok in practice.
> 
> In your situation, do you have users which are members of multiple
> projects?

yup. actually we have an internal sourceforge type server and the plan
was to create linkages between sourceforge and codestriker. i think at
least in our case the reviews will happen such that:

project = {repository, module} => project specific mailing list (for
review notifications)

so, even in the same repository there may be multiple modules that
would go to different reviewers etc.

i did notice that the one secod attempts, the fields were
autopopulated, so now i know where that was coming from ;-).

btw. thanks for writing codestriker, it solves a great need for us.

> 
> --
> Cheers,
> David
> 
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://productguide.itmanagersjournal.com/
> _______________________________________________
> Codestriker-user mailing list
> Cod...@li...
> https://lists.sourceforge.net/lists/listinfo/codestriker-user
> 

-- 
Aamer Akhter / aa...@gm...

Hi Aamer,

> yup. actually we have an internal sourceforge type server and the plan
> was to create linkages between sourceforge and codestriker. i think at
> least in our case the reviews will happen such that:
>
> project = {repository, module} => project specific mailing list (for
> review notifications)

Yes that association does make sense.  I have always toyed with the idea of 
adding extra fields into the project table, so that a default repository 
and Cc field for the create topic screen could be set initially.

It might also make sense for the user's cookie to be set per-project, so 
that the repository, and other fields will be remember per-project, rather 
than on a global basis as it is done now.

> btw. thanks for writing codestriker, it solves a great need for us.

No worries, we are always happy to hear feedback like that!  Let us know if 
you have any other ideas, or have any submissions to give to us.

-- 
Cheers,
David