Re: [Codestriker-user] Feature request

[David S. <si...@us...>]

Hi Matthew,

> 1) Developers being able to create topics under a different developer's
> e-mail, as well as the rights to delete topics.
>     - Suggested solution => Add rights related to logging into
> CodeStriker
>     Rights:
>         Admin Rights:
>             Delete topics
>             Add, Edit, Delete, Modify rights of users
>
>         Basic Rights (functionality):
>             Create topics
>             "Your e-mail address field" will be disabled and
> automatically filled in with user login (user e-mail)
>
> <For now we could add users via SQL into the database, but it would be
> nice to have a "Users" section to "Add, Edit, Delete, Change rights,
> etc.">

Yes... I suspect we'll be working on this once we get 1.8.0 out the door, 
this is something I am very keen to do. 1.8.0 will provide the capability 
to modify topic attributes, so having some form of security here will be 
useful, however 1.8.0 will also provide a complete audit trail of how a 
topic has been changed.  We'll have something similar to how Bugzilla 
manages its users.

> 2) Multiple differential data for the same CVS file. The scenario came
> up that developers need to be able to commit code multiple times to
> correlate work with another developer, but be able to save all the
> differences that they have made to a particular file over a period of
> time before the modifications were reviewed. Other developers would also
> be committing their changes, so the differences saved should only
> include what the first developer changed. Hopefully the following
> example illustrates.

This doesn't make any sense to me!  Why can't you "fold" all of the 
differences together into one diff segment?  This is how things are 
normally done in a Code reviewing situation, or when patch files are 
generated.  Before generating a "cvs diff", you usually need to do a "cvs 
update -d" to ensure that your working copying is bought uptodate with 
what is in the repository.  This will "merge" all changes together from 
other authors so that when you do a "cvs diff", all the changes are in one 
diff segment.

I don't think this answers your question... perhaps if you can give a more 
detailed example from a process perspective as to when you would ever want 
to generate a diff file with multiple diff segments for the same file.  In 
all cases, they are usually merged together into a single segment, 
otherwise its more work for the reviewer - they'd want to see all changes 
for a single file in one place, not in multiple places.

-- 
Cheers,
David