Forums : Technical Issue Help
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]
Project re-hosted at same url after being offline for 2 years, afraid of losing history on ohloh or not gathering new commits correctly.
Due to a series of unfortunate events I had to submit a takedown for one of my projects (Mubox) back in 2010.
The project has been resubmitted to the original location, but the location no longer has the contrib history from 2009 (original authoring).
Ohloh, thankfully, still has a full record of that history.
I have two questions:
Will ohloh lose history now that the project has been re-hosted and has no longer has any history?
Is there anything I can do to change the existing enlistment and then re-add the current host location to begin gathering new commit details?
Basically, I love ohloh analytics since my target audience is full of skeptics, and ohloh history helps to legitimize the app.
Thanks!
Shaun,
We can only evaluate live repositories and any failed enlistment will cause the update of any other enlistment to fail to be analyzed. We often suggest using backups restored to a free hosting server to act as history with the caveat that it is likely to cause distortion to Lines-of-Code counts (same code from two sources counts twice), Contributors detail figures and Estimated Cost figures. We also suggest that managers might maintain a Current project and a Legacy project or a Current project and an Overall project so that the effects of the distortions can be put in perspective. Think about these choices and let me know what you decide.
Thanks!
P.S. Enlistments entered with slightly different transport parameters (like svn: and https: transports) count as different enlistments and will not interfere with one another. Slight path alterations can accomplish the same but the same exact enlistment in two separate projects will be shared and wipe out the history you want to preserve.
Makes sense, so I think at some point I'll remove and re-enlist the project to wipe the old history and start 'fresh'.
Maybe consider switching over to git between now and then to avoid this kind of issue in the future.
Thanks for the info.