Thanks for your interest in making this tool available in Slicer. It looks like a valuable tool. Here are some high-level answers and some comments.
There are many examples to look at (TotalSegmentator, Auto3DSeg, MHub, etc) so you can see that there is not yet one clear suggested architecture. But porting your model to run inside one of those already supported frameworks could be the easiest option. For example, retraining with MONAI Auto3DSeg would let you simply publish the model and weights. I see you use tensorflow, which you might be able to make work, but most of the community use PyTorch, so adapting to that path would make development and maintenance easier.
Also I see that your model is GPL licensed. We discourage this for many reasons (you can search the forum archives for threads on this topic). If you absolutely must retain the GPL license, it may prevent you from using some of the distribution methods I mentioned above.
If you end up using GPL for any code you distribute please put a clear disclaimer of this at the top of the readme so that others don’t accidentally incorporate any of your code as this would cause problems for everyone.
First of all, thank you, sir!
What is the best and easiest way to integrate it?
If I want to do it, how should I proceed? Is it a straightforward process?
Also, I don’t fully understand the GPL license—could you please explain what it means and whether it affects integration?
I’m not sure I can add much beyond what I said before. There are plenty of examples that you can look at.
Regarding GPL, it’s a problem for many of us that even looking at GPL code could put you at risk of someone claiming you need to apply that license to all your work. Again, it’s a well discussed topic so you can look up the arguments on all sides.