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]
Hello,
What's up with KDE statistics? there is 0 activity and 0 commits if I compare to any large project using http://www.ohloh.net/projects/compare.
This is because we've had trouble keeping up with the KDE repository lately.
About a month ago, it looks like some went through and deleted the dozens and dozens of smaller repositories for KDE and replaced them with one giant repository. Ohloh has been struggling to download this large repository ever since, and until we catch up we're not going to be able to display any of the current activity.
I've done some housecleaning on the KDE downloads, and will keep an eye on them this week to make sure they are going through.
Also, I'm going to do an experiment and try to use our newer Subversion downloader. It uses svnsync to create a local mirror on an Ohloh server, and if the KDE server supports svnsync then the download will go much faster than with our older brute-force downloader.
Robin
Great news -- it looks like the KDE server supports svnsync, and our new download of KDE is going very quickly. I'm optimistic that KDE will be updated within a day our two and we should be able to keep up very easily.
Any progress there? Seems there was no update since 2007-09-24 what is near 1/2 year yet :-/
For KDE to get a new report, the stars must align and all of the following must happen:
All current KDE enlistments must all complete their downloads. If any one of them is failed or incomplete, the report will not update.
The project must remain undisturbed for several weeks to complete these downloads. KDE is colossal, and it takes a very long time to download the entire history. Once the initial download is finished, updates are quick, but we can't ever seem to finish the initial downloads, because....
People are impatient, and they keep deleting, adding, and generally changing around the enlistments without consulting with us, which keeps the project in a state of continuous update. This needs to stop, because it wastes our server resources and makes it very hard for me to figure out what's going on.
I tried using our new svnsync adapter for KDE, which is much faster than our normal downloader, but after several weeks of work and 90% completion, someone last week decided to summarily delete that enlistment and replace it with something else. Sigh.
I will again try to clean up KDE. I will try to figure out how to stop people from editing the project until we get these initial downloads completed.
Sorry if I am losing my patience. I know it's our own fault, because downloads are slow and we don't have good communication about the state of the project during this time. I'll see if I can make this better.
Hi Robin,
first thanks for the fast and detailed feedback.
Seems I just don't have any clue what an enlistment is and therefore can't really suggest a solution there. But if there is something what can be done at the KDE-side to complete that mission, please just say what we can do there :)
update: oh, it's possible for each user to delete the enlistments :-( Probably restrict such an important functionality?