Confirmed users
5,365
edits
Thunderbird/StatusMeetings/2012-10-02: Difference between revisions
Thunderbird/StatusMeetings/2012-10-02 (view source)
Revision as of 17:17, 2 October 2012
, 2 October 2012→GSoC Summary
| Line 76: | Line 76: | ||
* Lessons to take away: | * Lessons to take away: | ||
** It is critical that students post patches regularly to Bugzilla, or up to their Github fork, regardless of their quality. This way, the mentor can keep tabs on progress, and the student has a back-up in case disaster strikes. | ** It is critical that students post patches regularly to Bugzilla, or up to their Github fork, regardless of their quality. This way, the mentor can keep tabs on progress, and the student has a back-up in case disaster strikes. | ||
** It is also important that students are aware of how long ui review and code review takes, and budget that in to their timeline. | ** It is also important that students are aware of how long ui review and code review takes, and budget that in to their timeline (i.e. reviews along with fixes post-review and re-reviews take at least 4 or 5 days, it's not the type of thing you can do in 48 hours; better yet is to do reviews of work in progress code) | ||
==== Schedule and Progress ==== | ==== Schedule and Progress ==== | ||