Really appreciate the initiative!! 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).
-Amar On Tue, Jul 25, 2017 at 10:21 AM, Nithya Balachandran <[email protected]> wrote: > > > On 25 July 2017 at 10:13, Raghavendra Gowdappa <[email protected]> > wrote: > >> Hi all, >> >> 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: >> >> From me, >> * giving a high level architectural overview >> * giving a code walk-through explaining idiosyncrasies >> >> From you, >> * 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. >> * 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. >> * identifying weak points and suggesting improvements to the component. >> IOW, charting roadmap. >> >> 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. >> > > 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. > > Can we also add comments to the code for these xlators so new devs find it > easier to understand? > > Regards, > Nithya > >> >> [1] https://review.gluster.org/17583 >> >> regards, >> Raghavendra >> > > > _______________________________________________ > maintainers mailing list > [email protected] > http://lists.gluster.org/mailman/listinfo/maintainers > > -- Amar Tumballi (amarts)
_______________________________________________ maintainers mailing list [email protected] http://lists.gluster.org/mailman/listinfo/maintainers
