User Tools

Site Tools


gsocadvice

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
gsocadvice [2020/03/30 09:14]
be.ing [How Do I Write A Great Application?]
gsocadvice [2020/03/30 09:30] (current)
be.ing [Application evaluation criteria]
Line 77: Line 77:
   * Has the student demonstrated that they have the ability to work with Mixxx'​s code? The best way to do this is by submitting pull requests and getting them merged. It can also be okay if a student works on a bug but is unable to solve it before the application deadline if they demonstrate competence working with the Mixxx code. Students //must// have submitted a pull request to Mixxx or provide links to code they have written before in their application (ideally both).   * Has the student demonstrated that they have the ability to work with Mixxx'​s code? The best way to do this is by submitting pull requests and getting them merged. It can also be okay if a student works on a bug but is unable to solve it before the application deadline if they demonstrate competence working with the Mixxx code. Students //must// have submitted a pull request to Mixxx or provide links to code they have written before in their application (ideally both).
   * Has the student demonstrated that they can work independently and solve problems on their own without asking for help every step of the way?   * Has the student demonstrated that they can work independently and solve problems on their own without asking for help every step of the way?
-  * Does the student understand the design and technical details of what will be required to implement their proposal? What classes would need to be modified and how? How would the classes interact? We are not looking for you to have every detail figured out; you won't know that until you actually write the code. But we want to see that you understand the code you'll be working with and have a general plan of how to change it.+  * Does the student understand the design and technical details of what will be required to implement their proposal? What classes would need to be modified and how? Do new classes need to be added? How would the classes interact? We are not looking for you to have every detail figured out; you won't know that until you actually write the code. But we want to see that you understand the code you'll be working with and have a general plan of how to change it.
   * Is the proposed timeline realistic considering any other obligations the student may have during GSOC?   * Is the proposed timeline realistic considering any other obligations the student may have during GSOC?
  
gsocadvice.txt ยท Last modified: 2020/03/30 09:30 by be.ing