Forums : Feedback Forum
Dear Open Hub Users,
We’re excited to announce that we will be moving the Open Hub Forum to
https://community.blackduck.com/s/black-duck-open-hub.
Beginning immediately, users can head over,
register,
get technical help and discuss issue pertinent to the Open Hub. Registered users can also subscribe to Open Hub announcements here.
On May 1, 2020, we will be freezing https://www.openhub.net/forums and users will not be able to create new discussions. If you have any questions and concerns, please email us at
[email protected]
Subversion hooks
I'm using sf.net and it is possible to send an email after updating the sources. It would be nice, if every project has an email-account, where sf.net can send an empty mail to inform you, that the repository has chanced and you had to scan the sources.
This feature is used on http://cia.navi.cx/ and I find it great.
Is this possible? - I know: Impossible is nothing.
I second this proposal
I'm not keen on this idea. Firstly, ohloh doesn't update often enough at the moment, second you can implement this yourself if you are in control of the subversion config. Ohloh is about metrics, I don't think it should have to deal with sending out hundreds of emails to people. Just my two cents.
Wells, I think what mars_3-142 is suggesting is not outcoming mail from Ohloh, but notifications to Ohloh each time code changes are committed. This may help schedule Ohloh's updates in a more rational way.
I agree dartar. I wanted to email to ohloh to update the stats.
Hi guys,
We are, at this moment, up-to-date with project reports (within a few days). This meets our current (weekly) quality-of-service goal. We don't have immediate plans to turn into a real-time reporting engine. We do, however, have the goal to move our QOS to a daily turnaround within the next few months.
I don't mind adding a update this report
feature for projects but I wonder if it's worth the effort when we could work on other (in my mind, more pressing features). Thoughts?
jason, to me this feature (post-commit update triggers) only makes sense if the average update rate is too slow for very active projects and too fast for lazy projects. Ideally Ohloh may not want to download every day a huge codebase for a project that has only one or two commits a year, at the cost of slowing down updates of smaller and more active projects. If your hardware upgrade allows daily updates for any project, this feature request becomes somewhat irrelevant.