<div dir="auto"><div dir="auto">*****************</div><div dir="auto"> </div><div>Hello, I would prefer if you kept all discussion public, on the mailing list or #wayland IRC channel in Freenode, if possible, as I cannot really do private guidance for everyone. As for learning, I suppose you can follow what's going on in IRC and the mailing list, look at submitted patches, try things for yourself, pick a topic you want to work on, and then just dive in and ask questions. Reading patch review comments can be enlightening as well, and when you wonder why a piece of code is like it is, you can use 'git blame' to find the commit that made it so, the commit message should help with understanding though it doesn't always. Due to the lack of documentation, especially for Weston and libweston, asking questions in IRC is often an effective way to get forward. Thanks, pq</div><div dir="auto"> </div><div dir="auto">******************</div><div dir="auto"> </div><div dir="auto">Thanks for the guidance. <div class="gmail_quote" dir="auto"><div dir="ltr">On Thu, Apr 5, 2018, 14:08 Pekka Paalanen <<a href="mailto:ppaalanen@gmail.com" target="_blank" rel="noreferrer">ppaalanen@gmail.com</a>> wrote: </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Thu, 5 Apr 2018 13:30:16 +0530 Sagar Tewari <<a href="mailto:iaansagar@gmail.com" rel="noreferrer noreferrer" target="_blank">iaansagar@gmail.com</a>> wrote: > Hi, > > Thanks for quick reply. I'm interested in contributing to the weston > ecosystem. How do you suggest I should start learning about it? Hello, I would prefer if you kept all discussion public, on the mailing list or #wayland IRC channel in Freenode, if possible, as I cannot really do private guidance for everyone. As for learning, I suppose you can follow what's going on in IRC and the mailing list, look at submitted patches, try things for yourself, pick a topic you want to work on, and then just dive in and ask questions. Reading patch review comments can be enlightening as well, and when you wonder why a piece of code is like it is, you can use 'git blame' to find the commit that made it so, the commit message should help with understanding though it doesn't always. Due to the lack of documentation, especially for Weston and libweston, asking questions in IRC is often an effective way to get forward. Thanks, pq </blockquote></div></div></div>