When scheduling any “live” meeting, it would be good to poll the dev@ mailing list for timezones and schedule accordingly to maximize potential participation. I would also suggest announcing any meeting at least 72 hours before it takes place.
And when holding any off-list meetings, its important to bring any discussion items back to the dev@ list. Since this is just a code walkthrough I’m not concerned, but something to keep in mind. -Taylor > On Nov 17, 2016, at 1:50 PM, chandresh pancholi > <chandreshpancholi...@gmail.com> wrote: > > Once we have the session i will create on boarding document for new > contributors. > > On Fri, Nov 18, 2016 at 12:15 AM, Edward Capriolo <edlinuxg...@gmail.com> > wrote: > >> That sounds like a good idea. Since we launched I have touched enough parts >> of the code-base that I have a solid understanding of the majority of >> things. At minimum I can put together a power point. Or a screen share >> walk through. >> >> Ill start on that soon. >> >> >> On Thu, Nov 17, 2016 at 12:42 PM, chandresh pancholi < >> chandreshpancholi...@gmail.com> wrote: >> >>> Hi, >>> >>> We are looking forward to our first release. It would be great if we have >>> one codebase session where Ed can walk us through. >>> >>> We can record the session which would help new contributors in ramping >> up. >>> >>> >>> -- >>> Chandresh Pancholi >>> Senior Software Engineer >>> Flipkart.com >>> Email-id:chandresh.panch...@flipkart.com >>> Contact:08951803660 >>> >> > > > > -- > Chandresh Pancholi > Senior Software Engineer > Flipkart.com > Email-id:chandresh.panch...@flipkart.com > Contact:08951803660
