Forums : Feedback Forum

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 protected]

Enlistments : make Ohloh more flexible

Hi,

First, thanks for Ohloh. It's a great project.

Ohloh currently doesn't play well at all with projects that move from one location to another even within the same SVN repository. This is a very common case, for example a KDE project will typically start in playground/ then move to kdereview/ then to some KDE/ module.

Concrete requests:
1) please make it possible to add an enlistment covering a definite timespan in the past. For example, Ohloh currently warns people that Eigen (project 5393) has short revision control history because its current location was created only recently. But before that it existed at another location. So, I would like to add an enlistment for that old location that doesn't exist anymore. Ohloh doesn't accept that, complaining that the server didn't reply to a svn info request. The timespan needs to have not only a definite end but also a definite start: I don't want ohloh to analyze what happened before September 1, 2007 at that location (basically I had been trying to refactor another unmaintained project as a starting point for mine, and I gave up and restarted from scratch at that date. So any data from before Sep 1, 2007 would only serve to make the LOC curves very strange)

2) If that is feasible, consider (maybe optionally as it could break things) following the references of svn cp and svn mv. I mean, when Ohloh find that an enlistment starts at a given date, this is not necessarily the date when that code was created from scratch, often if was copied/moved from somewhere else and SVN remembers that.

Cheers,
Benoit

Benoit Jacob over 15 years ago
 

Hi Benoit,

These are two solid recommendations. You've hit the nail on the head with the two main problems in our current Subversion support, and there is some progress towards your requests.

Your first request shouldn't really be that difficult, and given some more development time it should be feasible. Using this ability, it would also be possible to work around Ohloh's limitations regarding svn cp and svn mv.

The second request is much more difficult than it seems at first, and so less likely to happen soon, but in the long term of Ohloh I'm hoping we'll get there.

I am currently in the process of some much-needed refactoring of all of our source control adapter code. Two things will arise from this: first, the code should be much easier to work on and improve, making your requests easier to implement. Second, we'll be opening up the source code, which opens up an opportunity for interested outsiders to help us along.

Thanks,
Robin

Robin Luckey over 15 years ago
 

Hi Robin,

Thanks very much for your reply.
I am looking forward to these improvements!

Cheers,
Benoit

Benoit Jacob over 15 years ago