The split takes place in naturally occuring steps during the migration to the new WDQS backend. The wdqs-proxy and the wdqs-mwsparql services have already been split into their own git repositories.

Current status:

The following components have been separated into their own repositories:

• wdqs-streaming-producer - formerly rdf-streaming-producer
• wdqs-streaming-consumer - formerly rdf-streaming-consumer
• wdqs-data-processing - formerly rdf-spark-tools
• wdqs-common - A collection of the code shared between the above mentioned components (includes classes from tools, common and testTools)

Open Questions:

• The original repository contains a set of command line tools which have not been transitioned into their own Gitlab repositories. It is unclear which are still required and which are deprecated. This will become more clear as the migration effort to the new triple store continues.

@trueg, what is the current status of this one?

@DSantamaria the status is unchanged. We have separated repositories as listed above and the question regarding the tools is still open. I would like to keep this open to eventually document the decision on the remaining code in tools which is not used in the post-migration plans yet.

After some discussion within the team, I will resolve this issue as being completed. While we did not extract all code from the original rdf repository yet, we did create all the new Gitlab repositories we need. Any additional tools can be merged into one of those new repositories, if required. They will most likely be debugging tools.