[Users] Need volunteer to deal with issues reported in Zimbra Docker

[Marc Gadsdon]

Hi Brando

>> Given the work Zimbra and F9 are doing for Zimbra 9 (or whatever it's called),
>> could it be a duplication of effort to work on this when it's highly likely
>> that F9/Zimbra will release a similar solution fairly soon? Maybe there are
>> advantages to a community based solution?
> 
> There is no easy answer to this, i guess That's why i asked for comments from
> others.

Thinking about it purely in terms of not duplicating effort, I think we need clarification from Zimbra and the rest of the community. Personally, my feeling is that if F9 are spending a lot of time and energy on this, we should follow their lead and perhaps extend their efforts once published.

> If by citing Zimbra/F9 are you referring to this repo:
> https://github.com/Zimbra/zm-docker?

I'm not sure what that repro is - I had also noticed it - maybe it's the one F9 are working on?

> On the other hand, i've also seen https://github.com/Zimbra/docker-zcs-foss but
> it looks like something that was
> started recently, so not so much things, in terms of issues, came up yet.

I don't know about that repro either.

Maybe Jorge can clarify the different repros?

The background is [in case you did not know - forgive me if you do]: At the recent commit session in New York, a team from F9, working for Zimbra/Synacor gave a presentation on the work they are doing for the next major Zimbra release around HA/Always On. The way I understand it (as a sudo technical guy), is that they want to create a declarative stack which Kubenetes and Terraform will orchestrate management, versioning and upgrading of Zimbra using Docker containers. The objective being that "anyone" (even me!!) will be able to do a 'Docker run Zimbra' and "3 minutes later" they would have a fully functional Zimbra install...

Cheers,

Marc