Page 1 of 1
SourceForge Tip: Monitoring
Posted: Sat Sep 17, 2005 7:14 am
by Boomzilla
The Monitoring capability in the latest version of SourceForge is quite powerful. By default, if you are assigned a tracker artifacts, task etc you are set to Monitor it i.e. any subsequent updates will be e-mailed to you and the e-mail address you registered against your account.
If you have not interacted with an artifact, document, release etc, you can flag the item(s) and click on the Monitor button to manually set monitoring.
To monitor entire tools on a per-project basis, click on "My Workspace" at the top of the page and then "Monitoring" (the yellow-bell icon).
Select projects in which you are interested and then use the controls in the "Monitored Applications" tab to select applications to Monitor. For each one you select you'll get e-mail notification for each new item created, as well as for changes to items you are not already, explicitly monitoring. Control over e-mail (immediate, daily digest and turn off) is via the e-mail preferences tab.
Col
Re: SourceForge Tip: Monitoring
Posted: Sat Sep 17, 2005 3:06 pm
by sabra
Thanks a lot for the huge effort you are putting into this fantastic application.
I must have missed something though:
In the old mamboforge, after pressing the "FILES" tab, you could set monitoring EVEN WHEN THERE WERE NO FILES RELEASED YET.
In the new forge, when there are no "FILE RELEASES" yet, how exactly do you set monitoring (I will mostly appreciate an exact step-by-step description)
Thanks a lot again.
Re: SourceForge Tip: Monitoring
Posted: Sat Sep 17, 2005 4:57 pm
by Boomzilla
Steps to monitor "File Releases" and receive notification when new releases are added or existing ones are updated:
1. Click "My Workspace" on the top nav bar
2. Click "Monitoring" (yellow bell icon) on the tool bar
3. In the left hand list of projects, click on the project in which you want to monitor File Releases
4. Select the "Monitored Applications" tab
5. Check the "File Releases" check box and click save.
Hope this helps!
Col
Re: SourceForge Tip: Monitoring
Posted: Sat Sep 17, 2005 5:08 pm
by kenmcd
Boomzilla wrote:3. In the left hand list of projects, click on the project in which you want to monitor File Releases
As soon as I click on Monitoring, my left hand list only shows my own projects.
I want to add monitoring for other projects which have not yet released any files.
Re: SourceForge Tip: Monitoring
Posted: Sat Sep 17, 2005 9:01 pm
by Boomzilla
Ah ha!. To do that you must be a member of the project. From the projects list check the box next to the project that contains the File Release app that you want to monitor and click "Request Membership" - once the project admin has approved your membership then you'll see the project listed in your Monitoring page.
Now, this raises a good point. Public projects with default user permissions that allow anonymous/users that are not members of the project to access the File Release system should be monitorable (to the extent defined in the default project permissions). I'll raise this as an enhancement request.
Col
Re: SourceForge Tip: Monitoring
Posted: Sat Sep 17, 2005 9:15 pm
by sabra
Colin,
Thanks a lot for your detailed answer.
In the old mamboforge application we could monitor file releases, EVEN BEFORE THERE WAS ANY FILE RELEASE. This was very convenient, since many projects release files some time after their registration. Very often I could monitor file release at the time they were announced.
Hopefully, this feature CAN and WILL be implemented into the current application too.
Many thanks.
Re: SourceForge Tip: Monitoring
Posted: Sat Sep 17, 2005 9:55 pm
by Boomzilla
Understood and thanks for the feedback.
Col
Re: SourceForge Tip: Monitoring
Posted: Mon Sep 26, 2005 9:50 pm
by torkil
Thanks for the heads up. I was twisting my brain backwards to find this out. I tried to go over the steps lots of times... but no luck...
Hope to see this feature sometime soon!
Re: SourceForge Tip: Monitoring
Posted: Fri Oct 14, 2005 6:51 pm
by ¥
My attempt to monitor a forum produced a "timeout" - gave it a few tries, same result?