Forums : Suggestions for Ohloh 2.0

automate enlistment failure fixing

I regularly encounter enlistment failures or inconsistencies. Filing a bug report for each of them doesn't seem scalable or user friendly.

Can't those fixes be automated, by for instance re-adding those failed enlistments (>1 month) in the backend?

You could prioritize those based on the activity of each enlistment. If the commit activity was low anyway, they get a lower priority.

Enlistments with a low commit activity could even have a lower update cycle (like once a month), to focus resources on updating enlistments which are actually in use.

3600cb90dc9524744a423be43d2f1c18?&s=42&rating=pg&d=http%3a%2f%2fopenhub.net%2fanon80
Wim Muskee almost 4 years ago
 

Wim,

Indeed many of these kinds of automated measures are currently in-place. The problem is, the failure modes get more creative as we discover them. (There are now 139 documented failure modes being monitored and I know that represents many more...) That said, there are the core of some good ideas here and I will ask management to look at your suggestions with a view to adding some input into the planning for future sprints.

Thanks!

C06ad304d5a864f33eed63121a0407be?&s=42&rating=pg&d=http%3a%2f%2fopenhub.net%2fanon80
ssnow-blackduck almost 4 years ago
 

Post a Response