Forums : Suggestions for Ohloh 2.0
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]
git: author vs commiter
Hello,
git register both the AUTHOR and the COMMITTER of each changeset. Which one is considered by the ohloh analyzer?
We use the author field. We do not currently record the committer.
Hm. In this case I suspect it's not working correctly for the rbot project at least. According to the enlistments it was updated yesterday, but jesse keys isn't appearing among the contributors, although there is a commint by him, as you can see from the project's gitweb.
(By the way, browsing the commits list on ohloh gives me an error on pages from the second onwards)
Hi Giuseppe,
Two parts to this answer.
First, the Ohloh report for this project has not been updated since February 8. Any commits made after this time will not be visible on Ohloh.
It's true that we updated our copy of the Git repository since then, but we are still waiting on an update to the Subversion repository before the report will be updated. I've bumped the priority of this update and will keep an eye on it today.
Second, I'm still investigating the crash on page 2 of the commits list. There's some funny business going on; somehow our list of people has gotten out of sync. This is a pretty serious bug so I'll be working on it today.
Thanks,
Robin
Giuseppe,
Thanks for reporting these troubles. It turns out there was a very subtle-yet-fatal bug in some new code. This is now fixed, and you should be able to see all of the commit pages now.
The rbot project report has been updated, and we are now current as of March 1.
Thanks for your help,
Robin
Thank you very much for your quick action! Since we're talking about it, I have another question: the old svn repository of the project was fully migrated to git. Should I just remove the old enlistment, since all of those commits are already 'repeated' in the git version, or does your software automatically handle the situation?
Given that the svn site is very slow and prone to go offline/be temporary unreachable, maybe there is some flag to set that enlistment as 'obsolete', so that it's not checked any further for changes, rather than deleting it?
(Maybe I should have opened another topic to discuss this.)
Our system doesn't (yet) do too many automatic
things regarding commits.
If the Subversion repository was fully converted to Git, then yes, you should probably remove the Subversion repository from Ohloh, since it leads to duplicated commits and doubled lines of code.
We don't yet have the ability to mark a repository as obsolete
, but this could be coming very soon. I'm going to spend the next few days looking at ways to optimize our project updates, and flagging abandoned repositories is probably going to be one of the tactics we use.
Thanks,
Robin
Ok, I will remove the repository now. When the 'obsolete' feature is implemented, I'll consider undoing the action and marking it obsolete.