Virtuoso Open-Source Moved to GitHub


Ever since 2006 OpenLink Software has provided its Open-Source version of Virtuoso (VOS), the high-performance SQL server with a powerful RDF/SPARQL data management layer on top.

So far the sources have been developed in an internal cvs repository which was published through the Virtuoso sourceforge pages.

As of March 21. OpenLink took the next step towards Open Development by moving to git as its version management system. The sources are now hosted in the VOS GitHub repository.

Like mentioned on the VOS git usage pages OpenLink now accepts GitHub pull requests and patches. Be sure to read the notes on git branching policy in VOS which are based on the git-flow approach by Vincent Driessen – which by the way is an interesting read independent of VOS.

Most importantly it is now a lot simpler to follow the development of Virtuoso Open-Source. Simply clone the git repository and switch to the appropriate develop branch:

$ git clone git://github.com/openlink/virtuoso-opensource.git
$ cd virtuoso-opensource
$ git checkout -t remotes/origin/develop/6

For details on the used branches see the already mentioned VOS git usage guide.

Refer to the VOS building instructions if the following is not enough for you:

$ ./autogen.sh
$ ./configure --prefix=/usr/local --with-layout=<LAYOUT>
$ make
$ make install

where <LAYOUT> is one of Gnu, Debian, Gentoo, Redhat, Freebsd, opt, Openlink. The latter two force the prefix.

5 thoughts on “Virtuoso Open-Source Moved to GitHub

  1. Why github and not gitorious?
    Is there any technical reason?
    As far as I know gitorious has a open-source license, however, github hasn’t.

    Wouldn’t it make sense to use a service with open-source license?

  2. Pingback: Virtuoso Open-Source Moved to GitHub | Trueg’s Blog | cloudguys.net

  3. Sebastian… are you working with OpenLink right now? And were you involved in this migration?

    If both are true, then CONGRATULATIONS, and thanks for all!

  4. Pingback: Piccole note sul software libero – parte terza « HyperNext

Leave a comment