Sandbox

The feature that I would like to see is an email sent to all developers of a certain project, whenever there is a change in the SVN repository. This makes it easier to keep up with changes made.
Perhaps it is already in there and I haven't noticed, in that case perhaps someone can point me in the right direction.

Ronald

rsgallerydude wrote:The feature that I would like to see is an email sent to all developers of a certain project, whenever there is a change in the SVN repository. This makes it easier to keep up with changes made.
Perhaps it is already in there and I haven't noticed, in that case perhaps someone can point me in the right direction.

somehow I managed to get myself on the
"SourceForge monitoring digest for project Free Joomla! Templates "
of which I am a project member.
At a guess, this is sent as soon as you start monitoring something, and delivers a very comprehensive message, including changes that have been made on discussions, package releases, tasks,tracker... and... oh, no svn..

Might I suggest that any email sent for svn change only be sent once,  basically, the way this forum sends out mail per thread being watched or participated in regardless the amount of action on the thread, else with many commits, the mail might start to look like spam to spam catchers.

Might I suggest that any email sent for svn change only be sent once,  basically, the way this forum sends out mail per thread being watched or participated in regardless the amount of action on the thread, else with many commits, the mail might start to look like spam to spam catchers

Agreed, that is why there should be a difference between the interested user, who is monitoring a package, and a developer, who wants to know whenever there is something changed in SVN(or CVS).

Ronald

Regarding e-mail on commit.

There is no application monitoring for SCM's. You can view the committ logger to see all commits via the SourceForge UI - but you don't get e-mail based on this. What I've seen teams do is to require an association at check-in time e.g. when checking in code, you must associate it with, say, the tracker artifact that drove the change (bug or enhancement request perhaps). To see all commits you'd monitor the entire tracker application for the target project and voila!

Just a note on Monitoring. It's quite powerful and can be tuned to meet the needs of the individual.
Go to "My Workspace" and click on Montor - you can select projects of which you are a member and
refine the frequency of notifications (immediate, digest, off), and elect to monitor entire applications
on a per project basis.

Col

I agree that commit emails are a VERY desirable feature missing from the J!Forge. The popular book by Karl Fogel entitled "Producing Open Source Software" has very specific things to say about the benefits of commit emails:

http://producingoss.com/html-chunk/vc.h ... mit-emails