tag:blogger.com,1999:blog-24623504.post6317433019066280727..comments2024-02-22T07:53:51.695+11:00Comments on Cameron Shorter: OSGeo-Live metrics going public in next releaseCameron Shorterhttp://www.blogger.com/profile/11881171259428356695noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-24623504.post-11652823924314186852016-01-31T21:52:50.866+11:002016-01-31T21:52:50.866+11:00Thanks Brad for the suggestion.
For the problem yo...Thanks Brad for the suggestion.<br />For the problem you describe with OpenHub not reading the fossil version system, how about using fossil->git mirroring, then ask OpenHub to read the git mirror? It seems to be possible according to this blog post: http://blog.fraggod.net/2011/05/02/fossil-to-git-export-and-mirroring.htmlCameron Shorterhttps://www.blogger.com/profile/11881171259428356695noreply@blogger.comtag:blogger.com,1999:blog-24623504.post-41872757532561012272016-01-31T17:19:14.281+11:002016-01-31T17:19:14.281+11:00Unfortunately there are some projects where the me...Unfortunately there are some projects where the metrics are bogus and unfixable. One example is spatialite, which now uses a DVCS called fossil (as used by sqlite). OpenHub doesn't support fossil, so we can't fix the commit metrics.<br /><br />For GMT, there are definitely later revisions: http://gmt.soest.hawaii.edu/projects/gmt/repository/entry/trunk - that may or may not be fixable.<br /><br />I'd suggest removing any OpenHub summaries in that situation - the disclaimer is not really a substitute for knowingly presenting incorrect data.Brad Hardshttps://www.blogger.com/profile/00027299538990758492noreply@blogger.com