<div dir="ltr">OKAY. I'll do it.<div class="gmail_extra"><br><div class="gmail_quote">On 17 January 2018 at 18:58, Colin Snover <span dir="ltr"><<a href="mailto:scummvm-devel@zetafleet.com" target="_blank">scummvm-devel@zetafleet.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF">
<div class="gmail-m_-5119148477050559137moz-cite-prefix">Unfortunately, I still do not see the
answers to the specific questions I asked about the way ScummVM’s
GSoC operates. Those questions are again:<span class="gmail-"><br>
<br>
* What is the way in which work units are allocated?<br></span></div></div></blockquote><div><br></div><div><span style="color:rgb(0,0,0);font-family:verdana,tahoma,arial,helvetica,sans-serif;font-size:12px">..prepare a </span><b style="color:rgb(0,0,0);font-family:verdana,tahoma,arial,helvetica,sans-serif;font-size:12px">comprehensive and detailed plan for all 12 weeks of your project</b><span style="color:rgb(0,0,0);font-family:verdana,tahoma,arial,helvetica,sans-serif;font-size:12px">. Include risk mitigation (you might fall ill, a phase in your project be more complicated than anticipated, etc.) and any existing commitments such as exams, vacations etc.</span><ul style="list-style-type:square;margin:0.3em 0px 0px 1.6em;padding:0px;color:rgb(0,0,0);font-family:verdana,tahoma,arial,helvetica,sans-serif;font-size:12px"><li style="margin-bottom:0.1em"><i>This plan will help you and us to decide at any time during the project how well you are progressing. It forces you to think about what you need to do beforehand, and provides a guideline for you while GSoC is progressing.</i></li></ul></div><div><br></div><div><span style="color:rgb(0,0,0);font-family:verdana,tahoma,arial,helvetica,sans-serif;font-size:12px">Create a timeline for the project</span><ul style="list-style-type:square;margin:0.3em 0px 0px 1.6em;padding:0px;color:rgb(0,0,0);font-family:verdana,tahoma,arial,helvetica,sans-serif;font-size:12px"><li style="margin-bottom:0.1em">Again, we don't expect you to have a full-on, hour-by-hour break down.</li><li style="margin-bottom:0.1em">We assume that the schedule <i>can</i> and <i>will</i> change as the project goes on.</li><li style="margin-bottom:0.1em">That said, we want to make sure everything can fit into the GSoC timeline and that you think about how long things will take.</li></ul></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div bgcolor="#FFFFFF"><div class="gmail-m_-5119148477050559137moz-cite-prefix"><span class="gmail-">
* How and where is the work progress tracked?<br></span></div></div></blockquote><div><span style="color:rgb(0,0,0);font-family:verdana,tahoma,arial,helvetica,sans-serif;font-size:12px">... we ask you to </span><b style="color:rgb(0,0,0);font-family:verdana,tahoma,arial,helvetica,sans-serif;font-size:12px">keep a weblog</b><span style="color:rgb(0,0,0);font-family:verdana,tahoma,arial,helvetica,sans-serif;font-size:12px"> (BLOG) with posts on a weekly or more frequent basis detailing your progress and experiences with your project/GSoC.</span><ul style="list-style-type:square;margin:0.3em 0px 0px 1.6em;padding:0px;color:rgb(0,0,0);font-family:verdana,tahoma,arial,helvetica,sans-serif;font-size:12px"><li style="margin-bottom:0.1em"><i>This provides a valuable avenue for feedback and helps involvement of the wider community. It also helps you to sort your thoughts and determine your own progress. Note that the blogs will be aggregated onto <a rel="nofollow" class="external gmail-text" href="http://planet.scummvm.org/" style="color:rgb(90,54,150);background:url("http://wiki.scummvm.org/skins/ScummModern/scummmodern/external.png?8ea75") 100% 50% no-repeat;font-size:11px;padding:0px 13px 0px 0px">ScummVM's Planet site</a> so language and tone should be set accordingly.</i></li></ul><div><span style="color:rgb(0,0,0);font-family:verdana,tahoma,arial,helvetica,sans-serif;font-size:12px">... we expect you to </span><b style="color:rgb(0,0,0);font-family:verdana,tahoma,arial,helvetica,sans-serif;font-size:12px">commit early, commit often</b><span style="color:rgb(0,0,0);font-family:verdana,tahoma,arial,helvetica,sans-serif;font-size:12px">.</span><ul style="list-style-type:square;margin:0.3em 0px 0px 1.6em;padding:0px;color:rgb(0,0,0);font-family:verdana,tahoma,arial,helvetica,sans-serif;font-size:12px"><li style="margin-bottom:0.1em"><i>We judge students' code based on what is checked in and take the view that 'if it's not checked in it does not exist' for the purposes of GSoC reviews. Don't be shy about this. You may feel your code is not 'good enough', but the best way to learn whether it actually is good or not, and also to get valuable hints on how to improve it, is to show it to us. Trust us, we will give you constructive feedback and won't bash you for what you produce.</i></li></ul></div></div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div bgcolor="#FFFFFF"><div class="gmail-m_-5119148477050559137moz-cite-prefix"><span class="gmail-">
* What is the process for making adjustments to the scope of the
work if it appears that the schedule is too aggressive and
milestones are not being met?<br></span></div></div></blockquote><div><span style="color:rgb(0,0,0);font-family:verdana,tahoma,arial,helvetica,sans-serif;font-size:12px">... we require you to </span><b style="color:rgb(0,0,0);font-family:verdana,tahoma,arial,helvetica,sans-serif;font-size:12px">communicate with your mentor</b><span style="color:rgb(0,0,0);font-family:verdana,tahoma,arial,helvetica,sans-serif;font-size:12px"> every second day. </span><b style="color:rgb(0,0,0);font-family:verdana,tahoma,arial,helvetica,sans-serif;font-size:12px">Failing to do so for more than three days without arrangement will cause you to be dropped from the program.</b><span style="color:rgb(0,0,0);font-family:verdana,tahoma,arial,helvetica,sans-serif;font-size:12px"></span><ul style="list-style-type:square;margin:0.3em 0px 0px 1.6em;padding:0px;color:rgb(0,0,0);font-family:verdana,tahoma,arial,helvetica,sans-serif;font-size:12px"><li style="margin-bottom:0.1em"><i>Consider that GSoC is a full time obligation. If you don't show up on a regular job for three days in a row, without any prior notice or reporting in as ill, you also run a high risk of being fired. Now, this is not exactly a regular day job and you don't have to come into an office every day. But communication is absolutely essential to a successful GSoC project and experience has shown that students that do not check in with their mentors (and the wider community) tend to struggle and produce weaker outputs. <span style="background-color:rgb(255,255,0)">In particular, if you feel you are behind your schedule or otherwise in troubles, talk to us as soon as possible.</span> Do not hide from your mentor -- they are here to help you at all times. Finally, this obligation doesn't have to be a burden, but rather should be a fun opportunity to chat with a nice fellow coder about interesting topics.</i></li></ul></div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div bgcolor="#FFFFFF"><div class="gmail-m_-5119148477050559137moz-cite-prefix"><span class="gmail-">
* Is there a set criteria for a task to be considered completed
successfully?<br></span></div></div></blockquote><div><ol style="margin:0.3em 0px 0px 3.2em;padding:0px;color:rgb(0,0,0);font-family:verdana,tahoma,arial,helvetica,sans-serif;font-size:12px"><li style="margin-bottom:0.1em"><ul style="list-style-type:square;margin:0.3em 0px 0px 1.6em;padding:0px"><li style="margin-bottom:0.1em">Using the skelton, <span style="background-color:rgb(255,255,0)">create Milestones</span> for the project. IE:<ul style="margin:0.3em 0px 0px 1.6em;padding:0px"><li style="margin-bottom:0.1em">The engine can read .scr files</li><li style="margin-bottom:0.1em">Create API for creating a hardware accelerated texture</li><li style="margin-bottom:0.1em">The engine can move the character</li></ul></li><li style="margin-bottom:0.1em">This is makes sure we all understand the complexities of the project</li></ul></li><li style="margin-bottom:0.1em">Create a timeline for the project<ul style="list-style-type:square;margin:0.3em 0px 0px 1.6em;padding:0px"><li style="margin-bottom:0.1em">Again, we don't expect you to have a full-on, hour-by-hour break down.</li><li style="margin-bottom:0.1em">We assume that the schedule <i>can</i> and <i>will</i> change as the project goes on.</li><li style="margin-bottom:0.1em">That said, we want to make sure everything can fit into the GSoC timeline and that you think about how long things will take.</li></ul></li></ol></div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div bgcolor="#FFFFFF"><div class="gmail-m_-5119148477050559137moz-cite-prefix"><span class="gmail-">
<br></span>
Since I am still not seeing what you are seeing, could you please
help me and cut and paste the specific text from the project rules
which answers each of these questions in a response to this email?<br></div></div></blockquote><div>I did that, hope it is clearer now.</div><div><br></div><div><br></div><div>Eugene</div></div></div></div>