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.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]
Subversion revisions
Hi Ohloh. :)
When browsing the commit history (for projects or positions) I keep wondering what good it does to know the ohloh commit number but on the other hand not being able to tell the number of the revision in the repository. I realize that this is not generally applicable for all kinds of repositories (at least not for cvs and git) but is there a way to specialize here for subversion repositories?
Example: http://www.ohloh.net/projects/6065/contributors/54600/commits/17481346
Thanks for any answer.
Hagen.
Hi Hagen,
It probably does you no good at all to know what the Ohloh commit number is :-). It's probably stupid for us to even have it on the page (although it does help us in debugging sometimes).
Storing the native source control revision numbers in the database is a good idea, and I'm not exactly sure how we got this far without it.
With CVS, a timestamp is the best we can do, since CVS doesn't really have a concept of an atomic commit. With Git, we do keep the original SHA1 of the commit in the database.
With Subversion it's a little bit messy. We do have the original revision numbers (we need them when we pull incremental code updates), but they are not actually stored in the database -- they are stored on disk with the actual source code. This makes it difficult to show them on the website. It might not be too difficult to get these numbers into the database.
In the coming months there's going to be a lot of upheaval in our source control adapters, as we move to organize and open up the code. This might be something we can clean up then.
