<div dir="ltr"><div class="gmail_default" style="font-family:monospace,monospace"><br></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, May 25, 2017 at 10:01 PM, zengchen <span dir="ltr"><<a href="mailto:chenzeng765@163.com" target="_blank">chenzeng765@163.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="line-height:1.7;color:#000000;font-size:14px;font-family:Arial"><br><div>Hi john:</div><div> I have seen your updates on the bp. I agree with your plan on how to develop the codes.</div><div> However, there is one issue I have to remind you that at present, Fuxi not only can convert</div><div> Cinder volume to Docker, but also Manila file. So, do you consider to involve Manila part of codes</div><div> in the new Fuxi-golang? </div></div></blockquote><div><div class="gmail_default" style="font-family:monospace,monospace;display:inline">Agreed, that's a really good and important point. Yes, I believe Ben Swartzlander </div> <div class="gmail_default" style="font-family:monospace,monospace;display:inline">is interested, we can check with him and make sure but I certainly hope that Manila would be interested.</div></div><div><div class="gmail_default" style="font-family:monospace,monospace;display:inline"></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="line-height:1.7;color:#000000;font-size:14px;font-family:Arial"><div>Besides, IMO, It is better to create a repository for Fuxi-golang, because</div><div> Fuxi is the project of Openstack,</div></div></blockquote><div><div class="gmail_default" style="font-family:monospace,monospace;display:inline">Yeah, that seems fine; I just didn't know if there needed to be any more conversation with other folks on any of this before charing ahead on new repos etc. Doesn't matter much to me though.</div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="line-height:1.7;color:#000000;font-size:14px;font-family:Arial"><div><br></div><div> Thanks very much!</div><div><br></div><div>Best Wishes!</div><span class="HOEnZb"><font color="#888888"><div>zengchen</div></font></span><div><div class="h5"><br><br><br><div style="zoom:1"></div><div id="m_-8751243243780895446divNeteaseMailCard"></div><br>At 2017-05-25 22:47:29, "John Griffith" <<a href="mailto:john.griffith8@gmail.com" target="_blank">john.griffith8@gmail.com</a>> wrote:<br> <blockquote id="m_-8751243243780895446isReplyContent" style="PADDING-LEFT:1ex;MARGIN:0px 0px 0px 0.8ex;BORDER-LEFT:#ccc 1px solid"><div dir="ltr"><div style="font-family:monospace,monospace"><br></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, May 25, 2017 at 5:50 AM, zengchen <span dir="ltr"><<a href="mailto:chenzeng765@163.com" target="_blank">chenzeng765@163.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="line-height:1.7;color:#000000;font-size:14px;font-family:Arial"><div>Very sorry to foget attaching the link for bp of rewriting Fuxi with go language.<br><a href="https://blueprints.launchpad.net/fuxi/+spec/convert-to-golang" target="_blank">https://blueprints.launchpad.n<wbr>et/fuxi/+spec/convert-to-golan<wbr>g</a><br><br></div><div><div class="m_-8751243243780895446h5">
<div style="ZOOM:1"></div>
<div id="m_-8751243243780895446m_-3973502905928574635divNeteaseMailCard"></div>
<div><br></div>At 2017-05-25 19:46:54, "zengchen" <<a href="mailto:chenzeng765@163.com" target="_blank">chenzeng765@163.com</a>> wrote:<br>
<blockquote style="BORDER-LEFT:#ccc 1px solid;MARGIN:0px 0px 0px 0.8ex;PADDING-LEFT:1ex" id="m_-8751243243780895446m_-3973502905928574635isReplyContent">
<div style="LINE-HEIGHT:1.7;FONT-FAMILY:Arial;COLOR:#000000;FONT-SIZE:14px">
<div>Hi guys:</div>
<div> hongbin had committed a bp of rewriting Fuxi with go language[1]. My question is where to commit codes for it.</div>
<div>We have two choice, 1. create a new repository, 2. create a new branch. IMO, the first one is much better. Because</div>
<div>there are many differences in the layer of infrastructure, such as CI. What's your opinion? Thanks very much</div>
<div> </div>
<div>Best Wishes</div>
<div>zengchen</div></div></blockquote></div></div></div><br>______________________________<wbr>______________________________<wbr>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.op<wbr>enstack.org?subject:unsubscrib<wbr>e</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/openstac<wbr>k-dev</a><br>
<br></blockquote></div><div style="font-family:monospace,monospace">Hi Zengchen,</div><div style="font-family:monospace,monospace"><br></div><div style="font-family:monospace,monospace">For now I was thinking just use Github and PR's outside of the OpenStack projects to bootstrap things and see how far we can get. I'll update the BP this morning with what I believe to be the key tasks to work through.</div><div style="font-family:monospace,monospace"><br></div><div style="font-family:monospace,monospace">Thanks,</div><div style="font-family:monospace,monospace">John</div><br></div></div>
</blockquote></div></div></div><br>______________________________<wbr>______________________________<wbr>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.<wbr>openstack.org?subject:<wbr>unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a><br>
<br></blockquote></div><br></div></div>