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]
I'd suggest rescheduling code download not in a first come first serve manner, but by taking into account how often the codebase has been changed in the past. For example calculate the time between the last commit and the last download and schedule the next download at the same distance in the future.
To mask out irregularities, you could for example also use not the last commit, but the last-10th commit and divide the time by 10.
This should reduce the load to the servers caused by inactive or less-active projects.