Write Container Submission Guidance

[Danulf]

Writing OSS is fun but when you publish and distribute it there are guidelines often imposed upon you by the OSS that you are using and dependent upon.

Write a document that provides the guidelines we need to follow when publishing a container.

[msheller]

Big +1 to this!

One core question I haven't figured out yet is whether MONAI is publishing more than just base containers. For example, would these guidelines apply to ML model developers building on MONAI?

[Danulf]

@msheller I hope we aren't publishing base containers. Instead, I hope we pull a maintained base container from someplace like NGC and simply add stuff on top within the guidance and context of those licenses. In the best case, we don't publish a container at all but simply provide the scripts to build a container for you.

Our issue here is licensing. Anytime you touch GNU licensed code, you have to "make it available" which means, in essence, yet another repository of that code (either a zip file or in our github or...). I worry that containers can bring with them a fairly deep dependency tree and we would have to analyze all the code that goes into the container to properly meet the licensing requirements. As a project, we don't have those tools developed (yet).