Forums : Suggestions for Ohloh 2.0
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
info@openhub.net
Suggestion by mdpdev
It would be great to know when the next update of the source control data is planed or to have notification by mail when it's done.
We modified some data in our svn and we are waiting for 8 days now. Thanks in advance and congratulations for this very useful site.
I second that. This is an important feature to have. Experiencing long delays is OK as long as you know what's the hold up and how long it's going to take. A queue position (if applicable) or the time frame would be great.
Continue the great work. :)
Hum, why you need to know when is the next update?
Some problems in our svn have been fixed. We just want to know if some warning has disappeared ...
Checking every day is not so fun :-) ... even if the site is so glamorous.
Maybe a good solution is a new feature (in the enlistment tab) to request a priority update. People who doesn't need update could be delayed.
Hi mdpdev,
No one wants to know how long it will take us to update all of these projects more than I do. Sometimes we are able to update every project within 24 hours, other times we are not so lucky.
The question of the update queue comes up quite often, so I'm going to get a little bit long-winded and explain how projects are selected for update, and why it's almost impossible to publish a schedule.
We have a large farm of servers, and the source code for an individual project is stored redundantly on a random selection of 2 or 3 servers. For efficiency reasons, project updates only run on machines that already have a copy of the project source code. When an individual server becomes idle, it checks its collection of source code for the project with the oldest report, and updates that project. In general, the oldest projects get updated first.
However, new projects always go to the front of the queue, and if we are very busy with new projects (like we have been lately), it can take a very long time before we start updating old projects again.
We've been continually expanding our server farm over the last year to increase capacity. Last week, we implemented a major change to how we store code, which shut us down for a couple of days, but should speed us up considerably in the long run. Coupled with the recent increase in new project requests, we are fairly backed up right now.
Email notifications of project updates is a likely feature. We're looking at providing email notifications in general, and update notifications shouldn't be too difficult.
All excuses aside, it is within my power to push your project to the front of the queue, and I am happy to indulge requests for updates. Which project are you looking for?
So, uh, new project enlistments are running way behind then?
I added a project and it's enlistment some 6 hours ago and it is apparently sitting in the queue still heh.
On a related matter, when a particular project hasn't been updated for say like 14-15 days it would be interesting if there would be a note or possibly description telling why this is so (like if the server was dead at previous attempt or whatever).
Dear Robin, thank you for all these explanations. Our project is Lutece (7203). We are conscious of the load of treatment. The first loading lasted 8 hours. The information presented on your site is relevant and pleasant to consult, at the same time for the users but also for us. We are impatient to see the next evolutions.
Cheer still for this site which we will follow with much interest.
Email notifications of project updates is a likely feature. We're looking at providing email notifications in general, and update notifications shouldn't be too difficult.
What about a RSS feed listing projects just updated? Then it should be fairly easy for anyone to watch for updates of projects they are interested in.
Also if you can publish somewhere current length of the queue, everybody can get a picture of how long is it likely going to take before next update to existing projects happen.
It might be interesting to see the number of projects in queue before certain project gets updated (for example, on KDevelop's or Firefox's project page, a small line mentioning number of projects that need to be updated before KDevelop or Firefox gets updated).
And if/when that is done, perhaps a small graph of total number of projects in queue on all servers displayed through time ;)
