<div dir="ltr"><div><div>Really appreciate the initiative!! <br><br></div>It would be good to start doing more of knowledge sharing sessions for other components too. How about a weekly slot which can be recorded well too. (Lets book Kadamba in BLR office, so we can do a decent recording of BJ session).<br><br></div><div>-Amar<br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jul 25, 2017 at 10:21 AM, Nithya Balachandran <span dir="ltr"><<a href="mailto:nbalacha@redhat.com" target="_blank">nbalacha@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote"><span class="">On 25 July 2017 at 10:13, Raghavendra Gowdappa <span dir="ltr"><<a href="mailto:rgowdapp@redhat.com" target="_blank">rgowdapp@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi all,<br>
<br>
Each one of you have been mentioned as a Peer to one or more components I am a maintainer of [1] and is relatively new to the component. So, we need to come up with ways where effective knowledge transfer is done to enable you to take independent decisions for issues concerned. Some of the ways I can think of are:<br>
<br>
>From me,<br>
* giving a high level architectural overview<br>
* giving a code walk-through explaining idiosyncrasies<br>
<br>
>From you,<br>
* scourging through bugzilla/mailing lists for issues on individual components and finding RCA and fixes. I can help you to prioritize and with discussions to the best of my capacity.<br>
* reading/changing/thinking about code and architecture. If the component is active, code reviewing is definitely a good way to start and to keep informed about component.<br>
* identifying weak points and suggesting improvements to the component. IOW, charting roadmap.<br>
<br>
I would like to hear from you on how to go about this exercise. Suggestions and help with logistics of organizing talks/sessions (if necessary) are welcome.<br></blockquote><div><br></div></span><div>This sounds great. I think it would be a good idea if everyone on this list could attend all the talks for every component (or at least some) so we have multiple people who understand the basics even if they are all not peers.</div><div><br></div><div>Can we also add comments to the code for these xlators so new devs find it easier to understand?</div><div><br></div><div>Regards,</div><div>Nithya</div><span class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
[1] <a href="https://review.gluster.org/17583" rel="noreferrer" target="_blank">https://review.gluster.org/175<wbr>83</a><br>
<br>
regards,<br>
Raghavendra<br>
</blockquote></span></div><br></div></div>
<br>______________________________<wbr>_________________<br>
maintainers mailing list<br>
<a href="mailto:maintainers@gluster.org">maintainers@gluster.org</a><br>
<a href="http://lists.gluster.org/mailman/listinfo/maintainers" rel="noreferrer" target="_blank">http://lists.gluster.org/<wbr>mailman/listinfo/maintainers</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div>Amar Tumballi (amarts)<br></div></div></div></div></div>
</div>