Hello Fengguang,
Thank you very much for your reply.
<snip>
lkp-tests is designed to be reusable by other projects. It should
relatively easy to reuse its code.
We would like to setup a call so we are able to explain our use case. We can go over how we do things from our side, and from this it would be good to figure out who is the best person will be to achieve this.
compass-ci services all run in containers, which makes their build
dependency clear.
Though there may still be a ton of boring/messy works in trying to
integrating different parts of lkp-tests/compass-ci to LKFT in order to
create a complete solution.
Perhaps, we would like to work together to triage this and work out the best way to tackle it.
Another tough question is whether LKFT duplicate the code and evolve
standalone, or reuse code in place while trying to modify
various places of the code to work in a different situation.
We are committed to collaborating with other frameworks, CompassCI included of course, and as a result, we will be pushing out changes back to you or LKP proper, where ever it makes sense.
compass-ci grows on top of lkp-tests in the very beginning, which makes
the development natural and simple.
With your team's help in achieving the goals outlined in this email, we hope that will be the case.
Regards
Ben
Thanks,
Fengguang