Forums : Ohloh General Discussion
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]
Support for mercurial
+1 once more, since I use Mercurial for still more projects.
For example my pyMarkdown Minisite project now works quite nice - it is based on Mercurial and Markdown and makes creating and managing simple sites extremely easy.
It is just one of the projects which Ohloh doesn't track because of the missing Mercurial support.
At the moment that means, I just use the bitbucket site as development site of my new projects instead of the Ohloh site:
- Example: 1w6 at bitbucket
So please get us Mercurial support (before Bitbucket offers most of the things you offer), so I can use the Ohloh site as reference for my projects again.
If you took the time to read a few posts back, I noted that I submitted a method to track mercurial projects. When the devs have time to integrate it, they will.
I took the time, when you posted the method in the first place (I answered back then).
But since your post it's been more then 20 days.
Perhaps Ohloh could estimate when this might be added? That would keep people from constantly prodding.
People just want to know where they should get their projects tracked.. if Ohloh is going to include HG in the next few weeks, there is no point in setting up tracking somewhere else.
If its going to be a year, well .. someone might want to start sending pings to cia.vc on each commit, or import their existing HG + history to git so it can be tracked.
I don't mean to be a pain in the butt, I'm just trying to figure out which way to go :)
+1 for Mercurial.. I'm using it too..
hg-fast-export.sh from git-fast-export (available at repo.or.cz) works wonderfully. You need a local hg repository, but then you just dump to git and use your standard tools...
I would really like to see this too.
I use mercurial for all of my projects, and it seems like there are a lot of other ohloh projects do to. The solution
thus far is to export as git and enlist that, but this results in very out-of-date statistics as these git mirrors don't get updated often and/or don't last long.
+1 for mercurial!
+1 as well, you are missing some quite relevant projects because of lack of hg support :(
Dear ohloh, please open source your tools so somebody can write an hg importer for you. If your business lives off of open source projects, maybe it's appropriate that you give something more than an LOC counter back to the community.
+1 for mercurial!
It's been written, it just has to be integrated. Take the time to read previous posts and you'd realize this.
+1 for integrating Mercurial :)
+1 for integrating just in case it will be done someday ,)
It's possible something to wish for xmas or the new year.. ;)
How about this: 5€ for Mercurial support till Xmas.
If I get my present, you get yours :)
(Yes, this is a promise. If you integrate Mercurial till Xmas, you get 5€ from me, no (other) strings attached, and I keep my promises.)
@everyone else: Why don't you join in to make Mercurial support worth their while? I'm just a student, else I'd give more, but I think if everyone in this thread gives just humble 5€, Mercurial support till Xmas should pay off quite well for ohloh directly (on the long run Mercurial support will pay off anyway, but if they need some incentive to put it on the important AND pressing
list, why don't we offer that?)
I would spend 5€ as well just to get this finally done. It's just a mess to use git as fallback to have statistics here.
Add my 5€ to the list, too.
And my axe!
The new release, brings a few important features, like permission inheritance for the .hg/store files, and many new UI improvements. The full release notes, are copied below as they were posted my Matt Mackall on the mailing list of Mercurial After nearly three years of development (and nearly that many of production use) we’re proud to announce the release of Mercurial 1.0. Thanks to the countless people who’ve contributed to development and testing.
fchris
Social Bookmarking
It looks like hg is going to be added 'when and if' it happens. I'm not inclined to change my stuff to git or svn just to have it tracked. Mirroring free software stuff via another VCS just to have it tracked is a terminally stupid waste of time.
Great code analyzer, neat widgets .. beyond that I barely use Ohloh anymore. It would be neat to participate if my stuff was actually tracked .. but its not, so ..
I'm not prodding, I realize they'll get around to it when and if they do. I just think its a shame to alienate so many (Xen, RPM, etc) because of their choice of VCS.
I stopped holding my breath months ago. A Goolgle SOC student contributed what was needed to integrate hg, Ohloh didn't (and does not) see it as important. Hopefully that will change, I doubt it.
What sucks is, Ohloh has become an authority. So I just have to eat lower scores because of my choice of version control software. Oh well.
If someone from Ohloh could just reply .. is it going to happen, if so, approximately when?
This thread might just stop growing, even if the answer is no.
I'm happy to say that for the last few days I have been working full time towards Mercurial support.
But before this can happen, our first goal is to open up Ohloh's source control adapter code so that the community can inspect and contribute.
There is some considerable cleaning to do in the Ohloh codebase. I'm in the process of isolating all of our source control code into stand-alone libraries.
The end result of this work will probably be a series of command line tools that can mirror and do basic stand-alone analysis of source control repositories. Effectively, I'm writing a wrapper that allows Ohloh to treat all source control systems the same.
When this is finished, it should be straightforward to implement a wrapper for Mercurial.
I don't have any firm ETA. I'm hopeful that this won't take more than a few weeks, but I can never be sure whether internal Ohloh demands will pull me away from the work. And it may always prove to be harder than I thought. :-)
Thanks,
Robin
Robin, that sounds great!
Thanks for working on it. I'll be sure to donate something too, when that stuff appears. :)
Robin, glad to hear you're implementing a framework rather than my quick hack for Mercurial support :)