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]
Is ohloh sufficiently completely open-source that there is something I could do, or other darcs-loving developers could do, to facilitate ohloh tracking darcs repositories?
Darcs is easy to work with on the command-line, so I wouldn't expect it to be too hard, but I would need some help understand how repositories are pulled and parsed by ohloh.
Regards,
Zooko
Hi zooko,
The short answer is not yet
.
Opening up our code base is one of our top development priorities right now. We are working towards cleaning up the source control interfaces and opening them up so that the community can contribute new source control adapters. This is probably several months away.
Distributed source control systems like Darcs and Mercurial are probably the easiest to integrate into Ohloh, since they provide their own internal mechanisms for storing, backing up, and synchronizing changes between copies. Ohloh is currently mostly built on Git (we convert CVS and some Subversion to Git internally), so source control systems similar in structure to Git have a low barrier to entry on Ohloh.
The real challenges always come in the edge cases; and of course, sorting out branches hasn't been fun in any source control system I've seen so far...
Thanks for your offer to help; we'll need it! :-)
Robin
I'm a long time user and occasional contributor to the tailor project, and I'm pretty sure I could help you use tailor (which is itself in Python) to programmatically, automatically import darcs into git.
Let me know.
P.S. You are exactly right about the branches -- tailor does the easy thing, which is pretend that branches don't exist. If you want to convert one single line of darcs history into one single line of git history, tailor is a perfect tool.