667
edits
Changes
no edit summary
== Talk Details ==
* '''Date''': Oct 11, 2006
* '''Speaker''': Mike Connor
== Media ==
* [http://ilearn.senecac.on.ca/mozillalectures/lecture4part1.html Part I] (streaming)
* [http://ilearn.senecac.on.ca/mozillalectures/lecture4part2.html Part II] (streaming)
* [http://ilearn.senecac.on.ca/mozillalectures/mozillalecture4.mp3 MP3] (93 MB)
== Talk Outline ==
=== Part I ===
<table style="width: 100%;" class="standard-table" cellborder=1 border=1 cellpadding=2 cellspacing=0>
<tr><th>Time</th><th>Topic</th><tr>
<tr><td>1:18</td><td>Introduction of himself</td></tr>
<tr><td>1:45</td><td>What is a bug?</td></tr>
<tr><td>3:55</td><td>Bugzilla how bugs are described</td></tr>
<tr><td>4:30</td><td>How to read a a bug in bugzilla</td></tr>
<tr><td>5:28</td><td>How to deal with bugs in bugzilla</td></tr>
<tr><td>8:15</td><td>Understanding bug numbers</td></tr>
<tr><td>9:17</td><td>Firefox "won't fix" idea</td></tr>
<tr><td>14:07</td><td>Prioritizing features, functionality and bugs</td></tr>
<tr><td>18:28</td><td>blocker triage, workaround for bugs when released software is shipped</td></tr>
<tr><td>22:57</td><td>When switching browser version causing bugs</td></tr>
<tr><td>24:25</td><td>CVS patch</td></tr>
<tr><td>25:30</td><td>Patches waiting for review</td></tr>
<tr><td>26:22</td><td>Process of looking into a patch</td></tr>
<tr><td>28:50</td><td>What point should a bug should be stopped fixing? </td></tr>
<tr><td>33:33</td><td>When and how to rewrite the code</td></tr>
<tr><td>36:15</td><td>Issues with rewriting code</td></tr>
<tr><td>37:00</td><td>working in the open is different from close source view</td></tr>
<tr><td>42:15</td><td>Open Source community contribution</td></tr>
<tr><td>47:55</td><td>Writing patches which fixes the issue</td></tr>
</table>
=== Part II ===
<table style="width: 100%;" class="standard-table" cellborder=1 border=1 cellpadding=2 cellspacing=0>
<tr><th>Time</th><th>Topic</th><tr>
<tr><td>0:00</td><td>Major challenges facing by bug patching</td></tr>
<tr><td>3:23</td><td>Second review of patches</td></tr>
<tr><td>8:22</td><td>How does the Mozilla licenses related in the Rsesponsibilities of submitting a patch</td></tr>
<tr><td>10:37</td><td>Are all patches reviewed?</td></tr>
<tr><td>14:33</td><td>Automation to treeosh</td></tr>
<tr><td>16:16</td><td>Last step of the life cycle: QA</td></tr>
<tr><td>23:25</td><td>Ice Weezel</td></tr>
<tr><td>28:16</td><td>Saying "No" to bug fixes</td></tr>
<tr><td>33:23</td><td>Question from Dave Hamp-Gonzalves</td></tr>
<tr><td>38:17</td><td>Tricks on finding a good first good</td></tr>
</table>
* '''Date''': Oct 11, 2006
* '''Speaker''': Mike Connor
== Media ==
* [http://ilearn.senecac.on.ca/mozillalectures/lecture4part1.html Part I] (streaming)
* [http://ilearn.senecac.on.ca/mozillalectures/lecture4part2.html Part II] (streaming)
* [http://ilearn.senecac.on.ca/mozillalectures/mozillalecture4.mp3 MP3] (93 MB)
== Talk Outline ==
=== Part I ===
<table style="width: 100%;" class="standard-table" cellborder=1 border=1 cellpadding=2 cellspacing=0>
<tr><th>Time</th><th>Topic</th><tr>
<tr><td>1:18</td><td>Introduction of himself</td></tr>
<tr><td>1:45</td><td>What is a bug?</td></tr>
<tr><td>3:55</td><td>Bugzilla how bugs are described</td></tr>
<tr><td>4:30</td><td>How to read a a bug in bugzilla</td></tr>
<tr><td>5:28</td><td>How to deal with bugs in bugzilla</td></tr>
<tr><td>8:15</td><td>Understanding bug numbers</td></tr>
<tr><td>9:17</td><td>Firefox "won't fix" idea</td></tr>
<tr><td>14:07</td><td>Prioritizing features, functionality and bugs</td></tr>
<tr><td>18:28</td><td>blocker triage, workaround for bugs when released software is shipped</td></tr>
<tr><td>22:57</td><td>When switching browser version causing bugs</td></tr>
<tr><td>24:25</td><td>CVS patch</td></tr>
<tr><td>25:30</td><td>Patches waiting for review</td></tr>
<tr><td>26:22</td><td>Process of looking into a patch</td></tr>
<tr><td>28:50</td><td>What point should a bug should be stopped fixing? </td></tr>
<tr><td>33:33</td><td>When and how to rewrite the code</td></tr>
<tr><td>36:15</td><td>Issues with rewriting code</td></tr>
<tr><td>37:00</td><td>working in the open is different from close source view</td></tr>
<tr><td>42:15</td><td>Open Source community contribution</td></tr>
<tr><td>47:55</td><td>Writing patches which fixes the issue</td></tr>
</table>
=== Part II ===
<table style="width: 100%;" class="standard-table" cellborder=1 border=1 cellpadding=2 cellspacing=0>
<tr><th>Time</th><th>Topic</th><tr>
<tr><td>0:00</td><td>Major challenges facing by bug patching</td></tr>
<tr><td>3:23</td><td>Second review of patches</td></tr>
<tr><td>8:22</td><td>How does the Mozilla licenses related in the Rsesponsibilities of submitting a patch</td></tr>
<tr><td>10:37</td><td>Are all patches reviewed?</td></tr>
<tr><td>14:33</td><td>Automation to treeosh</td></tr>
<tr><td>16:16</td><td>Last step of the life cycle: QA</td></tr>
<tr><td>23:25</td><td>Ice Weezel</td></tr>
<tr><td>28:16</td><td>Saying "No" to bug fixes</td></tr>
<tr><td>33:23</td><td>Question from Dave Hamp-Gonzalves</td></tr>
<tr><td>38:17</td><td>Tricks on finding a good first good</td></tr>
</table>