@markkua and I would like to help shape the way Marigold is integrated. We need to discuss this internally and with you to plan this design carefully and enable the pipeline's extensibility to other modalities (which are brewing). In the meantime, can @yiyixuxu please point us to a PR for a community pipeline promotion to the core so we can use it as a reference? Particularly, I'm curious to see how core philosophy is maintained (1) to balance modularity vs ensuring the quality of operation in a default setting and (2) automated test suite, if any

A PR #7524 to the community pipeline is just created for some small updates. Please also take this update into consideration.

hey @toshas and @markkua
For 'MarigoldPipeline`, it seems like it will be pretty straightforward, so it will not require any drastic changes. If no one from the community picks this up, I will work on it. We will definitely ask you to review it.

we don't have an example of community pipeline -> official pipeline that's already merged and can serve as a good reference. Marigold has the chance to become the first to come from the community! two other community pipelines are being moved to official pipelines, feel free to take a look at the PRs; they are both more challenging than MarigoldPipeline: face-id requires a different design when integrated into core; and ControlNet-XS, the original implementation deviates a lot from our style so a lot of works need to be done to refactor it

face-id: #7186
controlnet-xs: #6772

We need to discuss this internally and with you to plan this design carefully and enable the pipeline's extensibility to other modalities (which are brewing)

do we have a channel with you on slack?

do we have a channel with you on slack?

Yes, hf-marigold-colab, I asked to add you there