@microsoft-github-policy-service agree

I've made some updates to the Dockerfile in my fork, shuffled stuff around and made it a bit quicker to rebuild. Should we collaborate on a fork and then do a pull request that's more robust? Seems we have a bit of overlap in how we want to use it, and it'll be harder for the team to merge if we diverge

@bitplane let's do it, and perhaps, what we could do is:

• we use yours to land a dockerfile for the Gradio-based app, not to create a headless version
• I point my PR to your branch for that, and build off of that

so that we chain it this way:

1. your PR: lands a dockerfile that dockerizes what the authors had built, and that's it
2. my PR: extends yours to add the headless version

it will also enable reviewing the changes more effectively and keep the changes separate logically,

thoughts?