Dear Open Hub Users,
We’re excited to announce that we will be moving the Open Hub Forum to https://community.synopsys.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@example.com
When a project has no enlistments, Ohloh supports specifying a reason for this, such as that the project does not use version control, or uses a version control system Ohloh does not support. However, some projects have part of their history in a repo Ohloh supports, but not all of it; the version control may have gone private, or the project may have switched to a version control system Ohloh does not support. Ohloh needs a way to specify this even for projects with enlistments. Ohloh should also distinguish between specifying that information for the current repository or for historical data, and should consider the former a problem (red icon) but the latter at most a warning (yellow icon) if anything.
For a concrete example, see the Aptitude project. It once used CVS, and Ohloh has the information from that repository, but it now uses Mercurial, and Ohloh has no record of that.