<div dir="ltr"><img width="0" height="0" class="mailtrack-img" alt="" style="display:flex" src="https://mailtrack.io/trace/mail/bebaa4e425e5ee6e9c1f21ed32c50f678ccebf63.png?u=2276813"><div></div><br>Anyone willing to fill answer to the first question of "You and Community" is more than welcomed. Please e-mail me back with the answer so that I can add it to my proposal. I will also request mentors of this project to send their answers.<div><br></div><div>Q: <span id="gmail-docs-internal-guid-76d56e28-52d3-7741-278b-54eb59a240eb"><span style="font-size:11pt;font-family:Roboto;color:rgb(37,37,37);background-color:transparent;font-weight:700;font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">If your project is successfully completed, what will its impact be on the Sugar Labs community? Give 3 answers, each 1-3 paragraphs in length. The first one should be yours. The other two should be answers from members of the Sugar Labs community, at least one of whom should be a Sugar Labs GSoC mentor. Provide email contact information for non-GSoC mentors</span></span></div><div><br></div><div>Thanks,</div><div>Yash Agrawal</div><div>IRC: yashagrawal3<br><div>
</div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Mar 23, 2018 at 5:53 PM, Yash Agrawal <span dir="ltr"><<a href="mailto:yagrawal900@gmail.com" target="_blank">yagrawal900@gmail.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"><img width="0" height="0" class="m_-101560018448341529mailtrack-img" alt="" style="display:flex" src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7"><div>Iteration 1 of GSoC : <a href="https://docs.google.com/document/d/1SLCS5CLv_j1yjnk6RuIS7gdOKxJ2XvNUqzbMR0Zxn7U/edit#" target="_blank">https://docs.google.com/<wbr>document/d/1SLCS5CLv_<wbr>j1yjnk6RuIS7gdOKxJ2XvNUqzbMR0Z<wbr>xn7U/edit#</a></div><div><br></div><div></div>Hello Carlos,<div><br></div><div>Thanks for your review. I have already tested every activity I mentioned on the list. I have added a buffer week to release to all activities which were not released because of testing delay or any hard bug to solve. I am also flexible with the timeline I proposed, any changes can be made after discussion with mentors. Without actually diving deep into their code, it will be very hard to know if any difficult issue will arise. If this case arises, I am willing to work extra hours to keep up with the timeline.</div><div> <br></div><div>Hello James,</div><div><br></div><div>I have tried to make every change you suggested. Please review.</div><div><br></div><div>Anyone<br><br><div>
</div></div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Mar 23, 2018 at 3:40 AM, James Cameron <span dir="ltr"><<a href="mailto:quozl@laptop.org" target="_blank">quozl@laptop.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span>On Thu, Mar 22, 2018 at 10:26:48PM +0530, Yash Agrawal wrote:<br>
> I have completed the first draft of my GSoC Proposal. Please review<br>
> and give your suggestions. Any suggestion/request for an activity to<br>
> port is also welcomed.<br>
<br>
</span>Your work so far on porting activities to GTK+ 3 has been very good,<br>
so I don't expect any significant problems that can't be solved by<br>
asking questions or more coding.<br>
<br>
I've reviewed and have some comments;<br>
<br>
- where the proposal template asks "please send us URLs", and "some<br>
other demonstration of your work", you might add your GitHub profile<br>
URL and some of the pull requests you've worked on recently. You do<br>
mention these much later, but it is good to answer the question.<br>
<br>
(because although some of us know what you've been doing, the Google<br>
Open Source team won't know this until you tell them).<br>
<br>
- use terms consistently and correctly, and avoid unnecessary<br>
abbreviations; e.g. "pull request" instead of "PR", "Sugar" instead<br>
of "sugar", "Sugar Toolkit" instead of {sugar-toolkit,<br>
sugar-toolkit-gtk3}, "Ubuntu" instead of "ubuntu", "Fedora" instead<br>
of "fedora", "GTK+ 2" instead of {GTK2, GTK+ 2.x, Gtk, Gtk+},<br>
"GStreamer" instead of "GST", and (perhaps) "PyGObject API" instead<br>
of "PyGI",<br>
<br>
(because the inconsistent use within the document, and against<br>
external references, makes it harder to read).<br>
<br>
- in your list of activities, use the value for name from<br>
<a href="http://activity.info" rel="noreferrer" target="_blank">activity.info</a> rather than the GitHub repository name,<br>
<br>
(because this is the name by which the activity is best known to<br>
other people,)<br>
<br>
- the activity Labyrinth has a GTK+ 3 port already, and there are<br>
several repositories that are not proper clones or forks. See my<br>
audit in <a href="https://github.com/sugarlabs/laybrinth-activity/issues/1" rel="noreferrer" target="_blank">https://github.com/sugarlabs/l<wbr>aybrinth-activity/issues/1</a><br>
<br>
- you might plan how to encourage testing of your work by Sugar Labs<br>
community,<br>
<br>
- you might mention how your work will be affected by or benefit from<br>
the Port to Python 3 project,<br>
<span class="m_-101560018448341529HOEnZb"><font color="#888888"><br>
--<br>
James Cameron<br>
<a href="http://quozl.netrek.org/" rel="noreferrer" target="_blank">http://quozl.netrek.org/</a><br>
</font></span><div class="m_-101560018448341529HOEnZb"><div class="m_-101560018448341529h5">______________________________<wbr>_________________<br>
Sugar-devel mailing list<br>
<a href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank">Sugar-devel@lists.sugarlabs.or<wbr>g</a><br>
<a href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/lis<wbr>tinfo/sugar-devel</a><br>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>