Cool, my question is when do you think we should have a git repo for 'wok' (in kimchi-project org)?

IMHO, we should have it right now and then start working on that repo instead of current one. ----- Original message ----- From: Aline Manera <alinefm(a)linux.vnet.ibm.com&gt; To: Harshal Patil/India/IBM@IBMIN, kimchi-devel(a)ovirt.org Cc: Subject: Re: [Kimchi-devel] Should wok be a fork of kimchi? Date: Fri, Aug 7, 2015 1:25 AM Hi Harshal, As long as we complete the transition to wok framework, ie, make wok framework and Kimchi as plugin stable, 'wok' will be a new git repository into kimchi-project organization on github. And Kimchi and Ginger will be loaded as submodules. Regards, Aline Manera On 06/08/2015 16:46, Harshal Patil wrote: > Hi, > We are seeing lately how wok is positioned so differently than > kimchi is in many aspects. There are talks about changing UI > frameworks (bootstrap), and then having separate plugins (kimchi, > ginger). Wok is not going to be anything like the way kimchi is > today. It even has different name ('wok' instead of kimchi <next > version>) > Considering that should have wok development in a forked (from > existing kimchi) repo, having it as a branch of kimchi master > fails to make any sense to me. > > _______________________________________________ > Kimchi-devel mailing list > Kimchi-devel(a)ovirt.org <mailto:Kimchi-devel@ovirt.org> > http://lists.ovirt.org/mailman/listinfo/kimchi-devel