<div dir="ltr"><br><br><div class="gmail_quote"><div dir="ltr">On Wed, Sep 19, 2018 at 9:39 AM Sankarshan Mukhopadhyay <<a href="mailto:sankarshan.mukhopadhyay@gmail.com">sankarshan.mukhopadhyay@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Wed, Sep 19, 2018 at 9:34 AM Amar Tumballi <<a href="mailto:atumball@redhat.com" target="_blank">atumball@redhat.com</a>> wrote:<br>
<br>
[snip]<br>
<br>
> GCS Status:<br>
><br>
> Deploy scripts mostly working fine: <a href="https://github.com/kshlm/gd2-k8s" rel="noreferrer" target="_blank">https://github.com/kshlm/gd2-k8s</a><br>
><br>
> Few more patches required in GD2.<br>
><br>
> Where to send the PR ?<br>
><br>
> Plan is to send it to GCS, as the plan is to get more issues and discussions, along with documentation on that repo.<br>
><br>
<br>
What is the best way for a peripheral participant/audience to be aware<br>
of GCS? Is it going to be in the monthly report?<br></blockquote><div><br></div><div>The plan is to keep community up to date about the progress on GCS at least with a report of every alternate weeks, if not on weekly basis. <br></div><div> <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
-- <br>
sankarshan mukhopadhyay<br>
<<a href="https://about.me/sankarshan.mukhopadhyay" rel="noreferrer" target="_blank">https://about.me/sankarshan.mukhopadhyay</a>><br>
_______________________________________________<br>
maintainers mailing list<br>
<a href="mailto:maintainers@gluster.org" target="_blank">maintainers@gluster.org</a><br>
<a href="https://lists.gluster.org/mailman/listinfo/maintainers" rel="noreferrer" target="_blank">https://lists.gluster.org/mailman/listinfo/maintainers</a><br>
</blockquote></div></div>