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]
After a month, the NetBeans enlistment process status is:
Step 3 of 3: Counting lines of source code (Running 571/121301)
About 3 weeks ago I posted a similar message to this forum here: http://www.ohloh.net/forums/10/topics/6730
At that time, the status was at 583/126238 so it seems it's actually gone backwards!
I know the NetBeans repository is extremely large.
The best case scenario would be for someone to look at the problem and fix it, but if that's not possible that maybe we should stop the process since it's just wasting cycles, causing confusion, etc. Also I would suggest that in that case the NetBeans project is deleted because the current information from the old repositories is very misleading and bad information is worse than none. :)
Marcus,
I suspect you're right in one respect... bad information is worse than none
... We have been having a debate here about the practicalities of projects with large enlistments and those with many, many middle-sized enlistments as well. Please wait a while before making any decisions until we have formulated some guidance. I know I am too close to the issue to make sensible judgements on my own and must rely on those with a better perspective overall.
The going backwards
concern is only appearances. We are at this time 35% done with the count (remember, we started at 195890 commits) and the appearance of backwards motion doesn't take into account the changing number of commits remaining.
Once I have some guidance, I will share it with you.
Thanks for your patience!
P.S. Fortunately, a re-fetch like we are performing here should be a rare occurrence. If we can get past this stage and the following first update, things should (with luck) become smoother...