https://wiki.cdot.senecacollege.ca/w/api.php?action=feedcontributions&user=Eor&feedformat=atomCDOT Wiki - User contributions [en]2024-03-29T07:26:54ZUser contributionsMediaWiki 1.30.0https://wiki.cdot.senecacollege.ca/w/index.php?title=Club_Moz&diff=11541Club Moz2007-04-03T03:19:51Z<p>Eor: /* <b>Test Days</b> */</p>
<hr />
<div>=Purpose=<br />
<b>To help students get involved in the Mozilla community through its future endeavors in development, testing, support and hacking</b><br />
<br />
This club is open to technical and also non-technical people. If you don't know anything about open source or Mozilla, don't worry, we're here to help you get involved and we promise a good time :)<br />
<br />
<br />
=Committee=<br />
'''President:''' [[User:Themystic|Tom Aratyn]] (mystic)<br />
<br />
'''Vice President:''' Tiago Moreira (Tiago)<br />
<br />
'''Financial Officer:''' [[User:Elichak|Liz Chak]] (elichak)<br />
<br />
'''Events Coordinator:''' [[User:Pcvitori|Philip Vitorino]] (philly)<br />
<br />
'''Promotions Coordinator:''' [[User:Vpmirand|Vanessa Miranda]] (vanessa)<br />
<br />
'''Faculty Advisor:''' [[User:David.humphrey|Dave Humphrey]] (dave or humph)<br />
<br />
<br />
'''Email:''' clubmoz@gmail.com<br />
<br />
=Announcements=<br />
==<b>Want to work on some cool stuff? There are some cool projects waiting for you..</b>==<br />
*<b>If you're interested in any of these projects, speak to [[User:elichak | Liz Chak]] about getting involved</b><br />
*QA Site for more QA details: http://wiki.mozilla.org/Mozilla_QA_Community<br />
<br />
<br />
*<b>Talkback Report Challenge 1</b><br />
**Check out this link for detail: http://wiki.mozilla.org/Mozilla_QA_Community:Talkback_Report_Challenge_1<br />
<br />
*<b>Data mining of Hendrix data for creating reports of user feedback</b><br />
**To better understand major issues being reported and converting them into new bugs or finding and updating existing ones<br />
<br />
*<b>Litmus Extension</b> <br />
**We wanted to have an extension that would be able to serve users testcases to try and allow them to submit results to http://litmus.mozilla.org. We could expand the feature set of the extension to do a lot of other cool things with Bugzilla and Website Reporter integration... so we need some ideas there. <br />
**If you're interested, you could collaborate with [[User:Djhamp-g | David Hamp-Gonsalves]] to work on this together.<br />
<br />
*<b>QMO Help</b><br />
**Help needed in getting QMO together. If anyone is interested in website design, php hacking, or general graphics work, we can use some help getting QMO into better shape.<br />
**Link here: http://wiki.mozilla.org/Mozilla_QA_Community#QMO_Design_.26_Planning<br />
<br />
*<b>We are getting ready to ship Firefox 2.0.0.2 and 1.5.0.10</b><br />
**If you're interested in testing, you can run test cases through http://litmus.mozilla.org.<br />
<br />
==<b>Test Days</b>==<br />
* April 03, 2007 Test Day<br />
** This week our focus is on writing Test Cases<br />
** Here are links to some Test Case Writing Guidelines<br />
***http://wiki.mozilla.org/Mozilla_QA_Community:Test_Case_Writing_Day<br />
***http://wiki.mozilla.org/Mozilla_QA_Community:Test_Case_Writing_Day_Guideline<br />
***http://wiki.mozilla.org/Calendar:Test_Case_List#Display_of_Tasks<br />
** Also we will Explore on the QA Talkback crash report and Bug Day<br />
***http://wiki.mozilla.org/Mozilla_QA_Community<br />
** Here is where to download the nightly copy of Lightning and Sunbird. Again Lightning is an extension to Thunderbird(TB) and Sunbird is a stand alone application. You can download them ahead of time to try it out. Just a head up, we are going to do test cases for Drag and Drop feature. You might want to look around for that feature before you come. <br />
*** http://ftp.mozilla.org/pub/mozilla.org/calendar/lightning/nightly/latest-mozilla1.8/<br />
*** http://ftp.mozilla.org/pub/mozilla.org/calendar/sunbird/nightly/latest-mozilla1.8/<br />
<br />
* March 27, 2007 Test Day<br />
** http://wiki.mozilla.org/Mozilla_QA_Community<br />
** http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-mozilla1.8/<br />
** http://litmus.mozilla.org/<br />
** https://bugzilla.mozilla.org/<br />
** This is a sample of Vista Test Day in the past http://wiki.mozilla.org/Mozilla_QA_Community:WinVista2_Community_Test_Day<br />
<br />
* For Calendar, 13:00 UTC on February 9th 2007 to 01:00 UTC on February 10th 2007. http://wiki.mozilla.org/Calendar:Current_QA_TestDay<br />
*For Firefox 1.510 & 2.002 RC1 builds,Friday, February 9, 2007, from 7am - 5pm PST. http://wiki.mozilla.org/Mozilla_QA_Community:Firefox_1510_2002_Community_Test_Day<br />
<br />
==Other==<br />
*<big><b>Super Fun Hack Days are moved to T3073</b></big><br />
<br />
<br />
*<big><b>Firefox 2 is offically released!!</b></big> - Oct 24 2006<br />
<br />
=Events=<br />
One of the most fun aspects of Club Moz is the fact that we run events (like Super Fun Hack Day)! Come by and get involved!<br />
<br />
Due to some unfortunate events we have had to develop a policy regarding our [[Club Moz:Events:Policy| event policy]]. By attending you accept the policy.<br />
<br />
For a complete list of upcoming Club Moz events, check out our [http://www.google.com/calendar/embed?src=clubmoz%40gmail.com calendar]!<br />
<br />
<br />
==Super Fun Hack Day==<br />
<br />
===Event Agenda===<br />
'''Always'''<br />
*Work on interesting Mozilla related [[Project_List |projects]].<br />
*Meet others working on interesting.<br />
*Get free drinks for being a part of the community.<br />
<br />
'''February 8 '''<br />
* Make sure your User Page is up under "People". This is a place for you to list the projects you're working on and your progress. Other people may use this as a point of reference to who you are. Feel free to take ownership of your user page and the projects you're working on. <br />
* [[Club_Moz#Want_to_work_on_some_cool_stuff.3F_There_are_some_cool_projects_waiting_for_you.. | Wanna work on some cool stuff? There are some projects waiting for you..]]<br />
<br />
<br />
'''February 1''' - Calendar Test Day. Details [http://wiki.mozilla.org/Calendar:Current_QA_TestDay Here]<br />
<br />
===Event Details===<br />
'''Super Fun Hack Day every Thursday'''<br />
*Open to all students no matter your technical background or level. <br />
*Bring your energy and interest and we will help turn that into new abilities and new friends.<br />
*Come by T3073 on the third floor of the TEL building. <br />
*Food and Drinks will be provided after the event. We expect to be starting at around 3:20 pm going until... :)<br />
<br />
<br />
===Super Fun Hack Day Stuff===<br />
* Proposed Flyer ([[User:elichak | Liz Chak]] (elichak) and [[User:moe|Mohammad Tirtashi]] (moe))<br />
<gallery><br />
Image:Flyer.jpg|Hack Day Flyer<br />
</gallery><br />
*[[Hack day Issues|Notes on Hack Day Issues]]<br />
*[http://elichak.wordpress.com/ elichak's log about Super Fun Hack Day]<br />
<br />
<br />
===Issues With Hack day===<br />
<br />
* [[ Hack_day_Issues]]<br />
<br />
==Club Moz planning meetings==<br />
*Open to members of the club - everyone's voice matters<br />
*Date/Time: TBA<br />
<br />
==Meeting Minutes==<br />
<br />
* [[Club Moz:Meetings/November 9, 2006|November 9, 2006]]<br />
* [[Club Moz:Meetings/November 15, 2006|November 15, 2006]]<br />
* [[Club Moz:Meetings/November 22, 2006|November 22, 2006]]<br />
* [[Club Moz:Meetings/November 29, 2006|November 29, 2006]]<br />
* [[Club Moz:Meetings/January 9, 2006|January 9, 2006]]<br />
<br />
=News=<br />
*The Firefox2 party was a success. <br />
**Here are some [http://www.flickr.com/photos/moebt/sets/72157594346279843/ pictures].<br />
**More [http://www.flickr.com/photos/14311671@N00/ pictures]!<br />
<br />
*Club hangout on irc: irc://irc.mozilla.org/#clubmoz<br />
<br />
<br />
=Members=<br />
List of members still in progress<br />
<br />
Add your name here if you would like to be a member of Club Moz :)<br />
<br />
* [[User:dtolj|Dejan Tolj]] (dtolj)<br />
* [[User:Eldavey|Erin Davey]] (davey_girl)<br />
* [[User:Eor|Eva Or]] (eor)<br />
* [[User:jbmossop|Jeff Mossop]] (JBmossop)<br />
* [[User:Mdsouza|Mark D'Souza]] (mdsouza)<br />
* [[User:melz|Melissa Peh]] (melz)<br />
* [[User:mylau|Michael Lau]] (mylau)<br />
* [[User:moe|Mohammad Tirtashi]] (moe)<br />
* [[User:Paul|Paul Yanchun Gu]] (gpaul)<br />
* [[User:PStD|Paul St-Denis]] (pstdenis)<br />
* [[User:John64|John Ford]] (john64)<br />
* Tiago Moreira (Tiago)<br />
* Sid Kalra (crulshorukh)<br />
* [[User:djhamp-g| david hamp]] (inveigle)<br />
* [[User:jp| justin pacheco]] (jp)<br />
* [[User:robcee|Rob Campbell]], aka robcee, QA Engineer, Mozilla Corp.<br />
* [[User:Gavin|Gavin Sharp]]<br />
* [[User:Shaver|shaver]]<br />
* [[User:backinblakk|Lukas Blakk]] (lsblakk)<br />
* [[User:Saba Naqvi|Saba]] (snaqvi3)<br />
* [[User:ashughes|Anthony Hughes]] (ashughes)<br />
* [[User:armenzg|Armen Zambrano]] (armenzg)</div>Eorhttps://wiki.cdot.senecacollege.ca/w/index.php?title=Club_Moz&diff=11540Club Moz2007-04-03T03:02:58Z<p>Eor: /* <b>Test Days</b> */</p>
<hr />
<div>=Purpose=<br />
<b>To help students get involved in the Mozilla community through its future endeavors in development, testing, support and hacking</b><br />
<br />
This club is open to technical and also non-technical people. If you don't know anything about open source or Mozilla, don't worry, we're here to help you get involved and we promise a good time :)<br />
<br />
<br />
=Committee=<br />
'''President:''' [[User:Themystic|Tom Aratyn]] (mystic)<br />
<br />
'''Vice President:''' Tiago Moreira (Tiago)<br />
<br />
'''Financial Officer:''' [[User:Elichak|Liz Chak]] (elichak)<br />
<br />
'''Events Coordinator:''' [[User:Pcvitori|Philip Vitorino]] (philly)<br />
<br />
'''Promotions Coordinator:''' [[User:Vpmirand|Vanessa Miranda]] (vanessa)<br />
<br />
'''Faculty Advisor:''' [[User:David.humphrey|Dave Humphrey]] (dave or humph)<br />
<br />
<br />
'''Email:''' clubmoz@gmail.com<br />
<br />
=Announcements=<br />
==<b>Want to work on some cool stuff? There are some cool projects waiting for you..</b>==<br />
*<b>If you're interested in any of these projects, speak to [[User:elichak | Liz Chak]] about getting involved</b><br />
*QA Site for more QA details: http://wiki.mozilla.org/Mozilla_QA_Community<br />
<br />
<br />
*<b>Talkback Report Challenge 1</b><br />
**Check out this link for detail: http://wiki.mozilla.org/Mozilla_QA_Community:Talkback_Report_Challenge_1<br />
<br />
*<b>Data mining of Hendrix data for creating reports of user feedback</b><br />
**To better understand major issues being reported and converting them into new bugs or finding and updating existing ones<br />
<br />
*<b>Litmus Extension</b> <br />
**We wanted to have an extension that would be able to serve users testcases to try and allow them to submit results to http://litmus.mozilla.org. We could expand the feature set of the extension to do a lot of other cool things with Bugzilla and Website Reporter integration... so we need some ideas there. <br />
**If you're interested, you could collaborate with [[User:Djhamp-g | David Hamp-Gonsalves]] to work on this together.<br />
<br />
*<b>QMO Help</b><br />
**Help needed in getting QMO together. If anyone is interested in website design, php hacking, or general graphics work, we can use some help getting QMO into better shape.<br />
**Link here: http://wiki.mozilla.org/Mozilla_QA_Community#QMO_Design_.26_Planning<br />
<br />
*<b>We are getting ready to ship Firefox 2.0.0.2 and 1.5.0.10</b><br />
**If you're interested in testing, you can run test cases through http://litmus.mozilla.org.<br />
<br />
==<b>Test Days</b>==<br />
* April 03, 2007 Test Day<br />
** This week our focus is on writing Test Cases<br />
** Here are links to some Test Case Writing Guidelines<br />
***http://wiki.mozilla.org/Mozilla_QA_Community:Test_Case_Writing_Day<br />
***http://wiki.mozilla.org/Mozilla_QA_Community:Test_Case_Writing_Day_Guideline<br />
***http://wiki.mozilla.org/Calendar:Test_Case_List#Display_of_Tasks<br />
** Also we will Explore on the QA Talkback crash report and Bug Day<br />
***http://wiki.mozilla.org/Mozilla_QA_Community<br />
<br />
* March 27, 2007 Test Day<br />
** http://wiki.mozilla.org/Mozilla_QA_Community<br />
** http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-mozilla1.8/<br />
** http://litmus.mozilla.org/<br />
** https://bugzilla.mozilla.org/<br />
** This is a sample of Vista Test Day in the past http://wiki.mozilla.org/Mozilla_QA_Community:WinVista2_Community_Test_Day<br />
<br />
* For Calendar, 13:00 UTC on February 9th 2007 to 01:00 UTC on February 10th 2007. http://wiki.mozilla.org/Calendar:Current_QA_TestDay<br />
*For Firefox 1.510 & 2.002 RC1 builds,Friday, February 9, 2007, from 7am - 5pm PST. http://wiki.mozilla.org/Mozilla_QA_Community:Firefox_1510_2002_Community_Test_Day<br />
<br />
==Other==<br />
*<big><b>Super Fun Hack Days are moved to T3073</b></big><br />
<br />
<br />
*<big><b>Firefox 2 is offically released!!</b></big> - Oct 24 2006<br />
<br />
=Events=<br />
One of the most fun aspects of Club Moz is the fact that we run events (like Super Fun Hack Day)! Come by and get involved!<br />
<br />
Due to some unfortunate events we have had to develop a policy regarding our [[Club Moz:Events:Policy| event policy]]. By attending you accept the policy.<br />
<br />
For a complete list of upcoming Club Moz events, check out our [http://www.google.com/calendar/embed?src=clubmoz%40gmail.com calendar]!<br />
<br />
<br />
==Super Fun Hack Day==<br />
<br />
===Event Agenda===<br />
'''Always'''<br />
*Work on interesting Mozilla related [[Project_List |projects]].<br />
*Meet others working on interesting.<br />
*Get free drinks for being a part of the community.<br />
<br />
'''February 8 '''<br />
* Make sure your User Page is up under "People". This is a place for you to list the projects you're working on and your progress. Other people may use this as a point of reference to who you are. Feel free to take ownership of your user page and the projects you're working on. <br />
* [[Club_Moz#Want_to_work_on_some_cool_stuff.3F_There_are_some_cool_projects_waiting_for_you.. | Wanna work on some cool stuff? There are some projects waiting for you..]]<br />
<br />
<br />
'''February 1''' - Calendar Test Day. Details [http://wiki.mozilla.org/Calendar:Current_QA_TestDay Here]<br />
<br />
===Event Details===<br />
'''Super Fun Hack Day every Thursday'''<br />
*Open to all students no matter your technical background or level. <br />
*Bring your energy and interest and we will help turn that into new abilities and new friends.<br />
*Come by T3073 on the third floor of the TEL building. <br />
*Food and Drinks will be provided after the event. We expect to be starting at around 3:20 pm going until... :)<br />
<br />
<br />
===Super Fun Hack Day Stuff===<br />
* Proposed Flyer ([[User:elichak | Liz Chak]] (elichak) and [[User:moe|Mohammad Tirtashi]] (moe))<br />
<gallery><br />
Image:Flyer.jpg|Hack Day Flyer<br />
</gallery><br />
*[[Hack day Issues|Notes on Hack Day Issues]]<br />
*[http://elichak.wordpress.com/ elichak's log about Super Fun Hack Day]<br />
<br />
<br />
===Issues With Hack day===<br />
<br />
* [[ Hack_day_Issues]]<br />
<br />
==Club Moz planning meetings==<br />
*Open to members of the club - everyone's voice matters<br />
*Date/Time: TBA<br />
<br />
==Meeting Minutes==<br />
<br />
* [[Club Moz:Meetings/November 9, 2006|November 9, 2006]]<br />
* [[Club Moz:Meetings/November 15, 2006|November 15, 2006]]<br />
* [[Club Moz:Meetings/November 22, 2006|November 22, 2006]]<br />
* [[Club Moz:Meetings/November 29, 2006|November 29, 2006]]<br />
* [[Club Moz:Meetings/January 9, 2006|January 9, 2006]]<br />
<br />
=News=<br />
*The Firefox2 party was a success. <br />
**Here are some [http://www.flickr.com/photos/moebt/sets/72157594346279843/ pictures].<br />
**More [http://www.flickr.com/photos/14311671@N00/ pictures]!<br />
<br />
*Club hangout on irc: irc://irc.mozilla.org/#clubmoz<br />
<br />
<br />
=Members=<br />
List of members still in progress<br />
<br />
Add your name here if you would like to be a member of Club Moz :)<br />
<br />
* [[User:dtolj|Dejan Tolj]] (dtolj)<br />
* [[User:Eldavey|Erin Davey]] (davey_girl)<br />
* [[User:Eor|Eva Or]] (eor)<br />
* [[User:jbmossop|Jeff Mossop]] (JBmossop)<br />
* [[User:Mdsouza|Mark D'Souza]] (mdsouza)<br />
* [[User:melz|Melissa Peh]] (melz)<br />
* [[User:mylau|Michael Lau]] (mylau)<br />
* [[User:moe|Mohammad Tirtashi]] (moe)<br />
* [[User:Paul|Paul Yanchun Gu]] (gpaul)<br />
* [[User:PStD|Paul St-Denis]] (pstdenis)<br />
* [[User:John64|John Ford]] (john64)<br />
* Tiago Moreira (Tiago)<br />
* Sid Kalra (crulshorukh)<br />
* [[User:djhamp-g| david hamp]] (inveigle)<br />
* [[User:jp| justin pacheco]] (jp)<br />
* [[User:robcee|Rob Campbell]], aka robcee, QA Engineer, Mozilla Corp.<br />
* [[User:Gavin|Gavin Sharp]]<br />
* [[User:Shaver|shaver]]<br />
* [[User:backinblakk|Lukas Blakk]] (lsblakk)<br />
* [[User:Saba Naqvi|Saba]] (snaqvi3)<br />
* [[User:ashughes|Anthony Hughes]] (ashughes)<br />
* [[User:armenzg|Armen Zambrano]] (armenzg)</div>Eorhttps://wiki.cdot.senecacollege.ca/w/index.php?title=Club_Moz&diff=11416Club Moz2007-03-27T19:47:29Z<p>Eor: /* <b>Test Days</b> */</p>
<hr />
<div>=Purpose=<br />
<b>To help students get involved in the Mozilla community through its future endeavors in development, testing, support and hacking</b><br />
<br />
This club is open to technical and also non-technical people. If you don't know anything about open source or Mozilla, don't worry, we're here to help you get involved and we promise a good time :)<br />
<br />
<br />
=Committee=<br />
'''President:''' [[User:Themystic|Tom Aratyn]] (mystic)<br />
<br />
'''Vice President:''' Tiago Moreira (Tiago)<br />
<br />
'''Financial Officer:''' [[User:Elichak|Liz Chak]] (elichak)<br />
<br />
'''Events Coordinator:''' [[User:Pcvitori|Philip Vitorino]] (philly)<br />
<br />
'''Promotions Coordinator:''' [[User:Vpmirand|Vanessa Miranda]] (vanessa)<br />
<br />
'''Faculty Advisor:''' [[User:David.humphrey|Dave Humphrey]] (dave or humph)<br />
<br />
<br />
'''Email:''' clubmoz@gmail.com<br />
<br />
=Announcements=<br />
==<b>Want to work on some cool stuff? There are some cool projects waiting for you..</b>==<br />
*<b>If you're interested in any of these projects, speak to [[User:elichak | Liz Chak]] about getting involved</b><br />
*QA Site for more QA details: http://wiki.mozilla.org/Mozilla_QA_Community<br />
<br />
<br />
*<b>Talkback Report Challenge 1</b><br />
**Check out this link for detail: http://wiki.mozilla.org/Mozilla_QA_Community:Talkback_Report_Challenge_1<br />
<br />
*<b>Data mining of Hendrix data for creating reports of user feedback</b><br />
**To better understand major issues being reported and converting them into new bugs or finding and updating existing ones<br />
<br />
*<b>Litmus Extension</b> <br />
**We wanted to have an extension that would be able to serve users testcases to try and allow them to submit results to http://litmus.mozilla.org. We could expand the feature set of the extension to do a lot of other cool things with Bugzilla and Website Reporter integration... so we need some ideas there. <br />
**If you're interested, you could collaborate with [[User:Djhamp-g | David Hamp-Gonsalves]] to work on this together.<br />
<br />
*<b>QMO Help</b><br />
**Help needed in getting QMO together. If anyone is interested in website design, php hacking, or general graphics work, we can use some help getting QMO into better shape.<br />
**Link here: http://wiki.mozilla.org/Mozilla_QA_Community#QMO_Design_.26_Planning<br />
<br />
*<b>We are getting ready to ship Firefox 2.0.0.2 and 1.5.0.10</b><br />
**If you're interested in testing, you can run test cases through http://litmus.mozilla.org.<br />
<br />
==<b>Test Days</b>==<br />
* March 27, 2007 Test Day<br />
** http://wiki.mozilla.org/Mozilla_QA_Community<br />
** http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-mozilla1.8/<br />
** http://litmus.mozilla.org/<br />
** https://bugzilla.mozilla.org/<br />
** This is a sample of Vista Test Day in the past http://wiki.mozilla.org/Mozilla_QA_Community:WinVista2_Community_Test_Day<br />
<br />
* For Calendar, 13:00 UTC on February 9th 2007 to 01:00 UTC on February 10th 2007. http://wiki.mozilla.org/Calendar:Current_QA_TestDay<br />
*For Firefox 1.510 & 2.002 RC1 builds,Friday, February 9, 2007, from 7am - 5pm PST. http://wiki.mozilla.org/Mozilla_QA_Community:Firefox_1510_2002_Community_Test_Day<br />
<br />
==Other==<br />
*<big><b>Super Fun Hack Days are moved to T3073</b></big><br />
<br />
<br />
*<big><b>Firefox 2 is offically released!!</b></big> - Oct 24 2006<br />
<br />
=Events=<br />
One of the most fun aspects of Club Moz is the fact that we run events (like Super Fun Hack Day)! Come by and get involved!<br />
<br />
Due to some unfortunate events we have had to develop a policy regarding our [[Club Moz:Events:Policy| event policy]]. By attending you accept the policy.<br />
<br />
For a complete list of upcoming Club Moz events, check out our [http://www.google.com/calendar/embed?src=clubmoz%40gmail.com calendar]!<br />
<br />
<br />
==Super Fun Hack Day==<br />
<br />
===Event Agenda===<br />
'''Always'''<br />
*Work on interesting Mozilla related [[Project_List |projects]].<br />
*Meet others working on interesting.<br />
*Get free drinks for being a part of the community.<br />
<br />
'''February 8 '''<br />
* Make sure your User Page is up under "People". This is a place for you to list the projects you're working on and your progress. Other people may use this as a point of reference to who you are. Feel free to take ownership of your user page and the projects you're working on. <br />
* [[Club_Moz#Want_to_work_on_some_cool_stuff.3F_There_are_some_cool_projects_waiting_for_you.. | Wanna work on some cool stuff? There are some projects waiting for you..]]<br />
<br />
<br />
'''February 1''' - Calendar Test Day. Details [http://wiki.mozilla.org/Calendar:Current_QA_TestDay Here]<br />
<br />
===Event Details===<br />
'''Super Fun Hack Day every Thursday'''<br />
*Open to all students no matter your technical background or level. <br />
*Bring your energy and interest and we will help turn that into new abilities and new friends.<br />
*Come by T3073 on the third floor of the TEL building. <br />
*Food and Drinks will be provided after the event. We expect to be starting at around 3:20 pm going until... :)<br />
<br />
<br />
===Super Fun Hack Day Stuff===<br />
* Proposed Flyer ([[User:elichak | Liz Chak]] (elichak) and [[User:moe|Mohammad Tirtashi]] (moe))<br />
<gallery><br />
Image:Flyer.jpg|Hack Day Flyer<br />
</gallery><br />
*[[Hack day Issues|Notes on Hack Day Issues]]<br />
*[http://elichak.wordpress.com/ elichak's log about Super Fun Hack Day]<br />
<br />
<br />
===Issues With Hack day===<br />
<br />
* [[ Hack_day_Issues]]<br />
<br />
==Club Moz planning meetings==<br />
*Open to members of the club - everyone's voice matters<br />
*Date/Time: TBA<br />
<br />
==Meeting Minutes==<br />
<br />
* [[Club Moz:Meetings/November 9, 2006|November 9, 2006]]<br />
* [[Club Moz:Meetings/November 15, 2006|November 15, 2006]]<br />
* [[Club Moz:Meetings/November 22, 2006|November 22, 2006]]<br />
* [[Club Moz:Meetings/November 29, 2006|November 29, 2006]]<br />
* [[Club Moz:Meetings/January 9, 2006|January 9, 2006]]<br />
<br />
=News=<br />
*The Firefox2 party was a success. <br />
**Here are some [http://www.flickr.com/photos/moebt/sets/72157594346279843/ pictures].<br />
**More [http://www.flickr.com/photos/14311671@N00/ pictures]!<br />
<br />
*Club hangout on irc: irc://irc.mozilla.org/#clubmoz<br />
<br />
<br />
=Members=<br />
List of members still in progress<br />
<br />
Add your name here if you would like to be a member of Club Moz :)<br />
<br />
* [[User:dtolj|Dejan Tolj]] (dtolj)<br />
* [[User:Eldavey|Erin Davey]] (davey_girl)<br />
* [[User:Eor|Eva Or]] (eor)<br />
* [[User:jbmossop|Jeff Mossop]] (JBmossop)<br />
* [[User:Mdsouza|Mark D'Souza]] (mdsouza)<br />
* [[User:melz|Melissa Peh]] (melz)<br />
* [[User:mylau|Michael Lau]] (mylau)<br />
* [[User:moe|Mohammad Tirtashi]] (moe)<br />
* [[User:Paul|Paul Yanchun Gu]] (gpaul)<br />
* [[User:PStD|Paul St-Denis]] (pstdenis)<br />
* [[User:John64|John Ford]] (john64)<br />
* Tiago Moreira (Tiago)<br />
* Sid Kalra (crulshorukh)<br />
* [[User:djhamp-g| david hamp]] (inveigle)<br />
* [[User:jp| justin pacheco]] (jp)<br />
* [[User:robcee|Rob Campbell]], aka robcee, QA Engineer, Mozilla Corp.<br />
* [[User:Gavin|Gavin Sharp]]<br />
* [[User:Shaver|shaver]]<br />
* [[User:backinblakk|Lukas Blakk]] (lsblakk)<br />
* [[User:Saba Naqvi|Saba]] (snaqvi3)<br />
* [[User:ashughes|Anthony Hughes]] (ashughes)<br />
* [[User:armenzg|Armen Zambrano]] (armenzg)</div>Eorhttps://wiki.cdot.senecacollege.ca/w/index.php?title=Club_Moz&diff=10138Club Moz2007-02-08T22:13:43Z<p>Eor: /* <b>Want to work on some cool stuff? There are some cool projects waiting for you..</b> */</p>
<hr />
<div>=Purpose=<br />
<b>To help students get involved in the Mozilla community through its future endeavors in development, testing, support and hacking</b><br />
<br />
This club is open to technical and also non-technical people. If you don't know anything about open source or Mozilla, don't worry, we're here to help you get involved and we promise a good time :)<br />
<br />
<br />
=Committee=<br />
'''President:''' [[User:Themystic|Tom Aratyn]] (mystic)<br />
<br />
'''Vice President:''' Tiago Moreira (Tiago)<br />
<br />
'''Financial Officer:''' [[User:Elichak|Liz Chak]] (elichak)<br />
<br />
'''Events Coordinator:''' [[User:Pcvitori|Philip Vitorino]] (philly)<br />
<br />
'''Promotions Coordinator:''' [[User:Vpmirand|Vanessa Miranda]] (vanessa)<br />
<br />
'''Faculty Advisor:''' [[User:David.humphrey|Dave Humphrey]] (dave or humph)<br />
<br />
<br />
'''Email:''' clubmoz@gmail.com<br />
<br />
=Announcements=<br />
==<b>Want to work on some cool stuff? There are some cool projects waiting for you..</b>==<br />
*<b>If you're interested in any of these projects, speak to [[User:elichak | Liz Chak]] about getting involved</b><br />
*QA Site for more QA details: http://wiki.mozilla.org/Mozilla_QA_Community<br />
<br />
<br />
*<b>Talkback Report Challenge 1</b><br />
**Check out this link for detail: http://wiki.mozilla.org/Mozilla_QA_Community:Talkback_Report_Challenge_1<br />
<br />
*<b>Data mining of Hendrix data for creating reports of user feedback</b><br />
**To better understand major issues being reported and converting them into new bugs or finding and updating existing ones<br />
<br />
*<b>Litmus Extension</b> <br />
**We wanted to have an extension that would be able to serve users testcases to try and allow them to submit results to http://litmus.mozilla.org. We could expand the feature set of the extension to do a lot of other cool things with Bugzilla and Website Reporter integration... so we need some ideas there. <br />
**If you're interested, you could collaborate with [[User:Djhamp-g | David Hamp-Gonsalves]] to work on this together.<br />
<br />
*<b>QMO Help</b><br />
**Help needed in getting QMO together. If anyone is interested in website design, php hacking, or general graphics work, we can use some help getting QMO into better shape.<br />
**Link here: http://wiki.mozilla.org/Mozilla_QA_Community#QMO_Design_.26_Planning<br />
<br />
*<b>We are getting ready to ship Firefox 2.0.0.2 and 1.5.0.10</b><br />
**If you're interested in testing, you can run test cases through http://litmus.mozilla.org.<br />
<br />
==<b>Test Days</b>==<br />
* For Calendar, 13:00 UTC on February 9th 2007 to 01:00 UTC on February 10th 2007. http://wiki.mozilla.org/Calendar:Current_QA_TestDay<br />
*For Firefox 1.510 & 2.002 RC1 builds,Friday, February 9, 2007, from 7am - 5pm PST. http://wiki.mozilla.org/Mozilla_QA_Community:Firefox_1510_2002_Community_Test_Day<br />
<br />
==Other==<br />
*<big><b>Super Fun Hack Days are moved to T3073</b></big><br />
<br />
<br />
*<big><b>Firefox 2 is offically released!!</b></big> - Oct 24 2006<br />
<br />
=Events=<br />
One of the most fun aspects of Club Moz is the fact that we run events (like Super Fun Hack Day)! Come by and get involved!<br />
<br />
Due to some unfortunate events we have had to develop a policy regarding our [[Club Moz:Events:Policy| event policy]]. By attending you accept the policy.<br />
<br />
For a complete list of upcoming Club Moz events, check out our [http://www.google.com/calendar/embed?src=clubmoz%40gmail.com calendar]!<br />
<br />
<br />
==Super Fun Hack Day==<br />
<br />
===Event Agenda===<br />
<br />
'''February 8 '''<br />
* Make sure your User Page is up under "People". This is a place for you to list the projects you're working on and your progress. Other people may use this as a point of reference to who you are. Feel free to take ownership of your user page and the projects you're working on. <br />
* [[Club_Moz#Want_to_work_on_some_cool_stuff.3F_There_are_some_cool_projects_waiting_for_you.. | Wanna work on some cool stuff? There are some projects waiting for you..]]<br />
<br />
<br />
'''February 1''' - Calendar Test Day. Details [http://wiki.mozilla.org/Calendar:Current_QA_TestDay Here]<br />
<br />
===Event Details===<br />
'''Super Fun Hack Day every Thursday'''<br />
*Open to all students no matter your technical background or level. <br />
*Bring your energy and interest and we will help turn that into new abilities and new friends.<br />
*Come by T3073 on the third floor of the TEL building. <br />
*Food and Drinks will be provided after the event. We expect to be starting at around 3:20 pm going until... :)<br />
<br />
<br />
===Super Fun Hack Day Stuff===<br />
* Proposed Flyer ([[User:elichak | Liz Chak]] (elichak) and [[User:moe|Mohammad Tirtashi]] (moe))<br />
<gallery><br />
Image:Flyer.jpg|Hack Day Flyer<br />
</gallery><br />
*[[Hack day Issues|Notes on Hack Day Issues]]<br />
*[http://elichak.wordpress.com/ elichak's log about Super Fun Hack Day]<br />
<br />
<br />
===Issues With Hack day===<br />
<br />
* [[ Hack_day_Issues]]<br />
<br />
==Club Moz planning meetings==<br />
*Open to members of the club - everyone's voice matters<br />
*Date/Time: TBA<br />
*Location: T2091 - Linux Club<br />
<br />
<br />
===Meeting Minutes===<br />
<br />
* [[Club Moz:Meetings/November 9, 2006|November 9, 2006]]<br />
* [[Club Moz:Meetings/November 15, 2006|November 15, 2006]]<br />
* [[Club Moz:Meetings/November 22, 2006|November 22, 2006]]<br />
* [[Club Moz:Meetings/November 29, 2006|November 29, 2006]]<br />
* [[Club Moz:Meetings/January 9, 2006|January 9, 2006]]<br />
<br />
=News=<br />
*The Firefox2 party was a success. <br />
**Here are some [http://www.flickr.com/photos/moebt/sets/72157594346279843/ pictures].<br />
**More [http://www.flickr.com/photos/14311671@N00/ pictures]!<br />
<br />
*Club hangout on irc: irc://irc.mozilla.org/#clubmoz<br />
<br />
<br />
=Members=<br />
List of members still in progress<br />
<br />
Add your name here if you would like to be a member of Club Moz :)<br />
<br />
* [[User:dtolj|Dejan Tolj]] (dtolj)<br />
* [[User:Eldavey|Erin Davey]] (davey_girl)<br />
* [[User:Eor|Eva Or]] (eor)<br />
* [[User:jbmossop|Jeff Mossop]] (JBmossop)<br />
* [[User:Mdsouza|Mark D'Souza]] (mdsouza)<br />
* [[User:melz|Melissa Peh]] (melz)<br />
* [[User:mylau|Michael Lau]] (mylau)<br />
* [[User:moe|Mohammad Tirtashi]] (moe)<br />
* [[User:Paul|Paul Yanchun Gu]] (gpaul)<br />
* [[User:PStD|Paul St-Denis]] (pstdenis)<br />
* [[User:John64|John Ford]] (john64)<br />
* Tiago Moreira (Tiago)<br />
* Sid Kalra (crulshorukh)<br />
* [[User:djhamp-g| david hamp]] (inveigle)<br />
* [[User:jp| justin pacheco]] (jp)<br />
* [[User:robcee|Rob Campbell]], aka robcee, QA Engineer, Mozilla Corp.<br />
* [[User:Gavin|Gavin Sharp]]<br />
* [[User:Shaver|shaver]]<br />
* [[User:backinblakk|Lukas Blakk]] (lsblakk)<br />
* [[User:Saba Naqvi|Saba]] (snaqvi3)</div>Eorhttps://wiki.cdot.senecacollege.ca/w/index.php?title=Club_Moz&diff=10127Club Moz2007-02-08T18:30:49Z<p>Eor: </p>
<hr />
<div>=Purpose=<br />
<b>To help students get involved in the Mozilla community through its future endeavors in development, testing, support and hacking</b><br />
<br />
This club is open to technical and also non-technical people. If you don't know anything about open source or Mozilla, don't worry, we're here to help you get involved and we promise a good time :)<br />
<br />
<br />
=Committee=<br />
'''President:''' [[User:Themystic|Tom Aratyn]] (mystic)<br />
<br />
'''Vice President:''' Tiago Moreira (Tiago)<br />
<br />
'''Financial Officer:''' [[User:Elichak|Liz Chak]] (elichak)<br />
<br />
'''Events Coordinator:''' [[User:Pcvitori|Philip Vitorino]] (philly)<br />
<br />
'''Promotions Coordinator:''' [[User:Vpmirand|Vanessa Miranda]] (vanessa)<br />
<br />
'''Faculty Advisor:''' [[User:David.humphrey|Dave Humphrey]] (dave or humph)<br />
<br />
<br />
'''Email:''' clubmoz@gmail.com<br />
<br />
=Announcements=<br />
==<b>Want to work on some cool stuff? There are some cool projects waiting for you..</b>==<br />
*<b>If you're interested in any of these projects, speak to [[User:elichak | Liz Chak]] about getting involved</b><br />
*QA Site for more QA details: http://wiki.mozilla.org/Mozilla_QA_Community<br />
<br />
<br />
*<b>Talkback Report Challenge 1</b><br />
**Check out this link for detail: http://wiki.mozilla.org/Mozilla_QA_Community:Talkback_Report_Challenge_1<br />
<br />
*<b>Data mining of Hendrix data for creating reports of user feedback</b><br />
**To better understand major issues being reported and converting them into new bugs or finding and updating existing ones<br />
<br />
*<b>Litmus Extension</b> <br />
**We wanted to have an extension that would be able to serve users testcases to try and allow them to submit results to http://litmus.mozilla.org. We could expand the feature set of the extension to do a lot of other cool things with Bugzilla and Website Reporter integration... so we need some ideas there. <br />
**If you're interested, you could collaborate with [[User:Djhamp-g | David Hamp-Gonsalves]] to work on this together.<br />
<br />
*<b>QMO Help</b><br />
**Help needed in getting QMO together. If anyone is interested in website design, php hacking, or general graphics work, we can use some help getting QMO into better shape.<br />
<br />
*<b>We are getting ready to ship Firefox 2.0.0.2 and 1.5.0.10</b><br />
**If you're interested in testing, you can run test cases through http://litmus.mozilla.org.<br />
<br />
<br />
==<b>Test Days</b>==<br />
* For Calendar, 13:00 UTC on February 9th 2007 to 01:00 UTC on February 10th 2007. http://wiki.mozilla.org/Calendar:Current_QA_TestDay<br />
*For Firefox 1.510 & 2.002 RC1 builds,Friday, February 9, 2007, from 7am - 5pm PST. http://wiki.mozilla.org/Mozilla_QA_Community:Firefox_1510_2002_Community_Test_Day<br />
<br />
==Other==<br />
*<big><b>Super Fun Hack Days are moved to T3073</b></big><br />
<br />
<br />
*<big><b>Firefox 2 is offically released!!</b></big> - Oct 24 2006<br />
<br />
=Events=<br />
One of the most fun aspects of Club Moz is the fact that we run events (like Super Fun Hack Day)! Come by and get involved!<br />
<br />
Due to some unfortunate events we have had to develop a policy regarding our [[Club Moz:Events:Policy| event policy]]. By attending you accept the policy.<br />
<br />
For a complete list of upcoming Club Moz events, check out our [http://www.google.com/calendar/embed?src=clubmoz%40gmail.com calendar]!<br />
<br />
<br />
==Super Fun Hack Day==<br />
<br />
===Event Agenda===<br />
<br />
'''February 8 '''<br />
* Make sure your User Page is up under "People". This is a place for you to list the projects you're working on and your progress. Other people may use this as a point of reference to who you are. Feel free to take ownership of your user page and the projects you're working on. <br />
* [[Club_Moz#Want_to_work_on_some_cool_stuff.3F_There_are_some_cool_projects_waiting_for_you.. | Wanna work on some cool stuff? There are some projects waiting for you..]]<br />
<br />
<br />
'''February 1''' - Calendar Test Day. Details [http://wiki.mozilla.org/Calendar:Current_QA_TestDay Here]<br />
<br />
===Event Details===<br />
'''Super Fun Hack Day every Thursday'''<br />
*Open to all students no matter your technical background or level. <br />
*Bring your energy and interest and we will help turn that into new abilities and new friends.<br />
*Come by T3073 on the third floor of the TEL building. <br />
*Food and Drinks will be provided after the event. We expect to be starting at around 3:20 pm going until... :)<br />
<br />
<br />
===Super Fun Hack Day Stuff===<br />
* Proposed Flyer ([[User:elichak | Liz Chak]] (elichak) and [[User:moe|Mohammad Tirtashi]] (moe))<br />
<gallery><br />
Image:Flyer.jpg|Hack Day Flyer<br />
</gallery><br />
*[[Hack day Issues|Notes on Hack Day Issues]]<br />
*[http://elichak.wordpress.com/ elichak's log about Super Fun Hack Day]<br />
<br />
<br />
===Issues With Hack day===<br />
<br />
* [[ Hack_day_Issues]]<br />
<br />
==Club Moz planning meetings==<br />
*Open to members of the club - everyone's voice matters<br />
*Date/Time: TBA<br />
*Location: T2091 - Linux Club<br />
<br />
<br />
===Meeting Minutes===<br />
<br />
* [[Club Moz:Meetings/November 9, 2006|November 9, 2006]]<br />
* [[Club Moz:Meetings/November 15, 2006|November 15, 2006]]<br />
* [[Club Moz:Meetings/November 22, 2006|November 22, 2006]]<br />
* [[Club Moz:Meetings/November 29, 2006|November 29, 2006]]<br />
* [[Club Moz:Meetings/January 9, 2006|January 9, 2006]]<br />
<br />
=News=<br />
*The Firefox2 party was a success. <br />
**Here are some [http://www.flickr.com/photos/moebt/sets/72157594346279843/ pictures].<br />
**More [http://www.flickr.com/photos/14311671@N00/ pictures]!<br />
<br />
*Club hangout on irc: irc://irc.mozilla.org/#clubmoz<br />
<br />
<br />
=Members=<br />
List of members still in progress<br />
<br />
Add your name here if you would like to be a member of Club Moz :)<br />
<br />
* [[User:dtolj|Dejan Tolj]] (dtolj)<br />
* [[User:Eldavey|Erin Davey]] (davey_girl)<br />
* [[User:Eor|Eva Or]] (eor)<br />
* [[User:jbmossop|Jeff Mossop]] (JBmossop)<br />
* [[User:Mdsouza|Mark D'Souza]] (mdsouza)<br />
* [[User:melz|Melissa Peh]] (melz)<br />
* [[User:mylau|Michael Lau]] (mylau)<br />
* [[User:moe|Mohammad Tirtashi]] (moe)<br />
* [[User:Paul|Paul Yanchun Gu]] (gpaul)<br />
* [[User:PStD|Paul St-Denis]] (pstdenis)<br />
* [[User:John64|John Ford]] (john64)<br />
* Tiago Moreira (Tiago)<br />
* Sid Kalra (crulshorukh)<br />
* [[User:djhamp-g| david hamp]] (inveigle)<br />
* [[User:jp| justin pacheco]] (jp)<br />
* [[User:robcee|Rob Campbell]], aka robcee, QA Engineer, Mozilla Corp.<br />
* [[User:Gavin|Gavin Sharp]]<br />
* [[User:Shaver|shaver]]<br />
* [[User:backinblakk|Lukas Blakk]] (lsblakk)<br />
* [[User:Saba Naqvi|Saba]] (snaqvi3)</div>Eorhttps://wiki.cdot.senecacollege.ca/w/index.php?title=Club_Moz&diff=10126Club Moz2007-02-08T18:29:51Z<p>Eor: /* <b>Want to work on some cool stuff? There are some cool projects waiting for you..</b> */</p>
<hr />
<div>=Purpose=<br />
<b>To help students get involved in the Mozilla community through its future endeavors in development, testing, support and hacking</b><br />
<br />
This club is open to technical and also non-technical people. If you don't know anything about open source or Mozilla, don't worry, we're here to help you get involved and we promise a good time :)<br />
<br />
<br />
=Committee=<br />
'''President:''' [[User:Themystic|Tom Aratyn]] (mystic)<br />
<br />
'''Vice President:''' Tiago Moreira (Tiago)<br />
<br />
'''Financial Officer:''' [[User:Elichak|Liz Chak]] (elichak)<br />
<br />
'''Events Coordinator:''' [[User:Pcvitori|Philip Vitorino]] (philly)<br />
<br />
'''Promotions Coordinator:''' [[User:Vpmirand|Vanessa Miranda]] (vanessa)<br />
<br />
'''Faculty Advisor:''' [[User:David.humphrey|Dave Humphrey]] (dave or humph)<br />
<br />
<br />
'''Email:''' clubmoz@gmail.com<br />
<br />
=Announcements=<br />
==<b>Want to work on some cool stuff? There are some cool projects waiting for you..</b>==<br />
*<b>If you're interested in any of these projects, speak to [[User:elichak | Liz Chak]] about getting involved</b><br />
*QA Site for more QA details: http://wiki.mozilla.org/Mozilla_QA_Community<br />
<br />
<br />
*<b>Talkback Report Challenge 1</b><br />
**Check out this link for detail: http://wiki.mozilla.org/Mozilla_QA_Community:Talkback_Report_Challenge_1<br />
<br />
*<b>Data mining of Hendrix data for creating reports of user feedback</b><br />
**To better understand major issues being reported and converting them into new bugs or finding and updating existing ones<br />
<br />
*<b>Litmus Extension</b> <br />
**We wanted to have an extension that would be able to serve users testcases to try and allow them to submit results to http://litmus.mozilla.org. We could expand the feature set of the extension to do a lot of other cool things with Bugzilla and Website Reporter integration... so we need some ideas there. <br />
**If you're interested, you could collaborate with [[User:Djhamp-g | David Hamp-Gonsalves]] to work on this together.<br />
<br />
*<b>QMO Help</b><br />
**Help needed in getting QMO together. If anyone is interested in website design, php hacking, or general graphics work, we can use some help getting QMO into better shape.<br />
<br />
*<b>We are getting ready to ship Firefox 2.0.0.2 and 1.5.0.10</b><br />
**If you're interested in testing, you can run test cases through http://litmus.mozilla.org.<br />
<br />
==<b>Test Days</b>==<br />
* For Calendar, 13:00 UTC on February 9th 2007 to 01:00 UTC on February 10th 2007. http://wiki.mozilla.org/Calendar:Current_QA_TestDay<br />
*For Firefox 1.510 & 2.002 RC1 builds,Friday, February 9, 2007, from 7am - 5pm PST. http://wiki.mozilla.org/Mozilla_QA_Community:Firefox_1510_2002_Community_Test_Day<br />
<br />
==Other==<br />
*<big><b>Super Fun Hack Days are moved to T3073</b></big><br />
<br />
<br />
*<big><b>Firefox 2 is offically released!!</b></big> - Oct 24 2006<br />
<br />
=Events=<br />
One of the most fun aspects of Club Moz is the fact that we run events (like Super Fun Hack Day)! Come by and get involved!<br />
<br />
Due to some unfortunate events we have had to develop a policy regarding our [[Club Moz:Events:Policy| event policy]]. By attending you accept the policy.<br />
<br />
For a complete list of upcoming Club Moz events, check out our [http://www.google.com/calendar/embed?src=clubmoz%40gmail.com calendar]!<br />
<br />
<br />
==Super Fun Hack Day==<br />
<br />
===Event Agenda===<br />
<br />
'''February 8 '''<br />
* Make sure your User Page is up under "People". This is a place for you to list the projects you're working on and your progress. Other people may use this as a point of reference to who you are. Feel free to take ownership of your user page and the projects you're working on. <br />
* [[Club_Moz#Want_to_work_on_some_cool_stuff.3F_There_are_some_cool_projects_waiting_for_you.. | Wanna work on some cool stuff? There are some projects waiting for you..]]<br />
<br />
<br />
'''February 1''' - Calendar Test Day. Details [http://wiki.mozilla.org/Calendar:Current_QA_TestDay Here]<br />
<br />
===Event Details===<br />
'''Super Fun Hack Day every Thursday'''<br />
*Open to all students no matter your technical background or level. <br />
*Bring your energy and interest and we will help turn that into new abilities and new friends.<br />
*Come by T3073 on the third floor of the TEL building. <br />
*Food and Drinks will be provided after the event. We expect to be starting at around 3:20 pm going until... :)<br />
<br />
<br />
===Super Fun Hack Day Stuff===<br />
* Proposed Flyer ([[User:elichak | Liz Chak]] (elichak) and [[User:moe|Mohammad Tirtashi]] (moe))<br />
<gallery><br />
Image:Flyer.jpg|Hack Day Flyer<br />
</gallery><br />
*[[Hack day Issues|Notes on Hack Day Issues]]<br />
*[http://elichak.wordpress.com/ elichak's log about Super Fun Hack Day]<br />
<br />
<br />
===Issues With Hack day===<br />
<br />
* [[ Hack_day_Issues]]<br />
<br />
==Club Moz planning meetings==<br />
*Open to members of the club - everyone's voice matters<br />
*Date/Time: TBA<br />
*Location: T2091 - Linux Club<br />
<br />
<br />
===Meeting Minutes===<br />
<br />
* [[Club Moz:Meetings/November 9, 2006|November 9, 2006]]<br />
* [[Club Moz:Meetings/November 15, 2006|November 15, 2006]]<br />
* [[Club Moz:Meetings/November 22, 2006|November 22, 2006]]<br />
* [[Club Moz:Meetings/November 29, 2006|November 29, 2006]]<br />
* [[Club Moz:Meetings/January 9, 2006|January 9, 2006]]<br />
<br />
=News=<br />
*The Firefox2 party was a success. <br />
**Here are some [http://www.flickr.com/photos/moebt/sets/72157594346279843/ pictures].<br />
**More [http://www.flickr.com/photos/14311671@N00/ pictures]!<br />
<br />
*Club hangout on irc: irc://irc.mozilla.org/#clubmoz<br />
<br />
<br />
=Members=<br />
List of members still in progress<br />
<br />
Add your name here if you would like to be a member of Club Moz :)<br />
<br />
* [[User:dtolj|Dejan Tolj]] (dtolj)<br />
* [[User:Eldavey|Erin Davey]] (davey_girl)<br />
* [[User:Eor|Eva Or]] (eor)<br />
* [[User:jbmossop|Jeff Mossop]] (JBmossop)<br />
* [[User:Mdsouza|Mark D'Souza]] (mdsouza)<br />
* [[User:melz|Melissa Peh]] (melz)<br />
* [[User:mylau|Michael Lau]] (mylau)<br />
* [[User:moe|Mohammad Tirtashi]] (moe)<br />
* [[User:Paul|Paul Yanchun Gu]] (gpaul)<br />
* [[User:PStD|Paul St-Denis]] (pstdenis)<br />
* [[User:John64|John Ford]] (john64)<br />
* Tiago Moreira (Tiago)<br />
* Sid Kalra (crulshorukh)<br />
* [[User:djhamp-g| david hamp]] (inveigle)<br />
* [[User:jp| justin pacheco]] (jp)<br />
* [[User:robcee|Rob Campbell]], aka robcee, QA Engineer, Mozilla Corp.<br />
* [[User:Gavin|Gavin Sharp]]<br />
* [[User:Shaver|shaver]]<br />
* [[User:backinblakk|Lukas Blakk]] (lsblakk)<br />
* [[User:Saba Naqvi|Saba]] (snaqvi3)</div>Eorhttps://wiki.cdot.senecacollege.ca/w/index.php?title=Club_Moz&diff=10125Club Moz2007-02-08T18:29:22Z<p>Eor: /* <b>Want to work on some cool stuff? There are some cool projects waiting for you..</b> */</p>
<hr />
<div>=Purpose=<br />
<b>To help students get involved in the Mozilla community through its future endeavors in development, testing, support and hacking</b><br />
<br />
This club is open to technical and also non-technical people. If you don't know anything about open source or Mozilla, don't worry, we're here to help you get involved and we promise a good time :)<br />
<br />
<br />
=Committee=<br />
'''President:''' [[User:Themystic|Tom Aratyn]] (mystic)<br />
<br />
'''Vice President:''' Tiago Moreira (Tiago)<br />
<br />
'''Financial Officer:''' [[User:Elichak|Liz Chak]] (elichak)<br />
<br />
'''Events Coordinator:''' [[User:Pcvitori|Philip Vitorino]] (philly)<br />
<br />
'''Promotions Coordinator:''' [[User:Vpmirand|Vanessa Miranda]] (vanessa)<br />
<br />
'''Faculty Advisor:''' [[User:David.humphrey|Dave Humphrey]] (dave or humph)<br />
<br />
<br />
'''Email:''' clubmoz@gmail.com<br />
<br />
=Announcements=<br />
==<b>Want to work on some cool stuff? There are some cool projects waiting for you..</b>==<br />
*<b>If you're interested in any of these projects, speak to [[User:elichak | Liz Chak]] about getting involved</b><br />
*QA Site for more QA details: http://wiki.mozilla.org/Mozilla_QA_Community<br />
<br />
<br />
*<b>Talkback Report Challenge 1</b><br />
**Check out this link for detail: http://wiki.mozilla.org/Mozilla_QA_Community:Talkback_Report_Challenge_1<br />
<br />
*<b>Data mining of Hendrix data for creating reports of user feedback</b><br />
**To better understand major issues being reported and converting them into new bugs or finding and updating existing ones<br />
<br />
*<b>Litmus Extension</b> <br />
**We wanted to have an extension that would be able to serve users testcases to try and allow them to submit results to http://litmus.mozilla.org. We could expand the feature set of the extension to do a lot of other cool things with Bugzilla and Website Reporter integration... so we need some ideas there. <br />
**If you're interested, you could collaborate with [[User:Djhamp-g | David Hamp-Gonsalves]] to work on this together.<br />
<br />
*<b>QMO Help</b><br />
**Help needed in getting QMO together. If anyone is interested in website design, php hacking, or general graphics work, we can use some help getting QMO into better shape.<br />
<br />
*<b>We are getting ready to ship Firefox 2.0.0.2 and 1.5.0.10</b><br />
**If you're interested in testing, you can run test cases through http://litmus.mozilla.org.<br />
<br />
*<b>Do you like hacking scripts or building web apps?</b> <br />
**The Talkback Report Challenge might be a good way to polish those skills of yours<br />
<br />
==<b>Test Days</b>==<br />
* For Calendar, 13:00 UTC on February 9th 2007 to 01:00 UTC on February 10th 2007. http://wiki.mozilla.org/Calendar:Current_QA_TestDay<br />
*For Firefox 1.510 & 2.002 RC1 builds,Friday, February 9, 2007, from 7am - 5pm PST. http://wiki.mozilla.org/Mozilla_QA_Community:Firefox_1510_2002_Community_Test_Day<br />
<br />
==Other==<br />
*<big><b>Super Fun Hack Days are moved to T3073</b></big><br />
<br />
<br />
*<big><b>Firefox 2 is offically released!!</b></big> - Oct 24 2006<br />
<br />
=Events=<br />
One of the most fun aspects of Club Moz is the fact that we run events (like Super Fun Hack Day)! Come by and get involved!<br />
<br />
Due to some unfortunate events we have had to develop a policy regarding our [[Club Moz:Events:Policy| event policy]]. By attending you accept the policy.<br />
<br />
For a complete list of upcoming Club Moz events, check out our [http://www.google.com/calendar/embed?src=clubmoz%40gmail.com calendar]!<br />
<br />
<br />
==Super Fun Hack Day==<br />
<br />
===Event Agenda===<br />
<br />
'''February 8 '''<br />
* Make sure your User Page is up under "People". This is a place for you to list the projects you're working on and your progress. Other people may use this as a point of reference to who you are. Feel free to take ownership of your user page and the projects you're working on. <br />
* [[Club_Moz#Want_to_work_on_some_cool_stuff.3F_There_are_some_cool_projects_waiting_for_you.. | Wanna work on some cool stuff? There are some projects waiting for you..]]<br />
<br />
<br />
'''February 1''' - Calendar Test Day. Details [http://wiki.mozilla.org/Calendar:Current_QA_TestDay Here]<br />
<br />
===Event Details===<br />
'''Super Fun Hack Day every Thursday'''<br />
*Open to all students no matter your technical background or level. <br />
*Bring your energy and interest and we will help turn that into new abilities and new friends.<br />
*Come by T3073 on the third floor of the TEL building. <br />
*Food and Drinks will be provided after the event. We expect to be starting at around 3:20 pm going until... :)<br />
<br />
<br />
===Super Fun Hack Day Stuff===<br />
* Proposed Flyer ([[User:elichak | Liz Chak]] (elichak) and [[User:moe|Mohammad Tirtashi]] (moe))<br />
<gallery><br />
Image:Flyer.jpg|Hack Day Flyer<br />
</gallery><br />
*[[Hack day Issues|Notes on Hack Day Issues]]<br />
*[http://elichak.wordpress.com/ elichak's log about Super Fun Hack Day]<br />
<br />
<br />
===Issues With Hack day===<br />
<br />
* [[ Hack_day_Issues]]<br />
<br />
==Club Moz planning meetings==<br />
*Open to members of the club - everyone's voice matters<br />
*Date/Time: TBA<br />
*Location: T2091 - Linux Club<br />
<br />
<br />
===Meeting Minutes===<br />
<br />
* [[Club Moz:Meetings/November 9, 2006|November 9, 2006]]<br />
* [[Club Moz:Meetings/November 15, 2006|November 15, 2006]]<br />
* [[Club Moz:Meetings/November 22, 2006|November 22, 2006]]<br />
* [[Club Moz:Meetings/November 29, 2006|November 29, 2006]]<br />
* [[Club Moz:Meetings/January 9, 2006|January 9, 2006]]<br />
<br />
=News=<br />
*The Firefox2 party was a success. <br />
**Here are some [http://www.flickr.com/photos/moebt/sets/72157594346279843/ pictures].<br />
**More [http://www.flickr.com/photos/14311671@N00/ pictures]!<br />
<br />
*Club hangout on irc: irc://irc.mozilla.org/#clubmoz<br />
<br />
<br />
=Members=<br />
List of members still in progress<br />
<br />
Add your name here if you would like to be a member of Club Moz :)<br />
<br />
* [[User:dtolj|Dejan Tolj]] (dtolj)<br />
* [[User:Eldavey|Erin Davey]] (davey_girl)<br />
* [[User:Eor|Eva Or]] (eor)<br />
* [[User:jbmossop|Jeff Mossop]] (JBmossop)<br />
* [[User:Mdsouza|Mark D'Souza]] (mdsouza)<br />
* [[User:melz|Melissa Peh]] (melz)<br />
* [[User:mylau|Michael Lau]] (mylau)<br />
* [[User:moe|Mohammad Tirtashi]] (moe)<br />
* [[User:Paul|Paul Yanchun Gu]] (gpaul)<br />
* [[User:PStD|Paul St-Denis]] (pstdenis)<br />
* [[User:John64|John Ford]] (john64)<br />
* Tiago Moreira (Tiago)<br />
* Sid Kalra (crulshorukh)<br />
* [[User:djhamp-g| david hamp]] (inveigle)<br />
* [[User:jp| justin pacheco]] (jp)<br />
* [[User:robcee|Rob Campbell]], aka robcee, QA Engineer, Mozilla Corp.<br />
* [[User:Gavin|Gavin Sharp]]<br />
* [[User:Shaver|shaver]]<br />
* [[User:backinblakk|Lukas Blakk]] (lsblakk)<br />
* [[User:Saba Naqvi|Saba]] (snaqvi3)</div>Eorhttps://wiki.cdot.senecacollege.ca/w/index.php?title=Club_Moz&diff=10124Club Moz2007-02-08T18:28:49Z<p>Eor: /* <b>Want to work on some cool stuff? There are some cool projects waiting for you..</b> */</p>
<hr />
<div>=Purpose=<br />
<b>To help students get involved in the Mozilla community through its future endeavors in development, testing, support and hacking</b><br />
<br />
This club is open to technical and also non-technical people. If you don't know anything about open source or Mozilla, don't worry, we're here to help you get involved and we promise a good time :)<br />
<br />
<br />
=Committee=<br />
'''President:''' [[User:Themystic|Tom Aratyn]] (mystic)<br />
<br />
'''Vice President:''' Tiago Moreira (Tiago)<br />
<br />
'''Financial Officer:''' [[User:Elichak|Liz Chak]] (elichak)<br />
<br />
'''Events Coordinator:''' [[User:Pcvitori|Philip Vitorino]] (philly)<br />
<br />
'''Promotions Coordinator:''' [[User:Vpmirand|Vanessa Miranda]] (vanessa)<br />
<br />
'''Faculty Advisor:''' [[User:David.humphrey|Dave Humphrey]] (dave or humph)<br />
<br />
<br />
'''Email:''' clubmoz@gmail.com<br />
<br />
=Announcements=<br />
==<b>Want to work on some cool stuff? There are some cool projects waiting for you..</b>==<br />
*<b>If you're interested in any of these projects, speak to [[User:elichak | Liz Chak]] about getting involved</b><br />
*QA Site for more QA details: http://wiki.mozilla.org/Mozilla_QA_Community<br />
<br />
<br />
*<b>Talkback Report Challenge 1</b><br />
**Check out this link for detail: http://wiki.mozilla.org/Mozilla_QA_Community:Talkback_Report_Challenge_1<br />
<br />
*<b>Data mining of Hendrix data for creating reports of user feedback</b><br />
**To better understand major issues being reported and converting them into new bugs or finding and updating existing ones<br />
<br />
*<b>Litmus Extension</b> <br />
**We wanted to have an extension that would be able to serve users testcases to try and allow them to submit results to http://litmus.mozilla.org. We could expand the feature set of the extension to do a lot of other cool things with Bugzilla and Website Reporter integration... so we need some ideas there. <br />
**If you're interested, you could collaborate with [[User:Djhamp-g | David Hamp-Gonsalves]] to work on this together.<br />
<br />
*<b>QMO Help</b><br />
**Help needed in getting QMO together. If anyone is interested in website design, php hacking, or general graphics work, we can use some help getting QMO into better shape.<br />
<br />
**<b>We are getting ready to ship Firefox 2.0.0.2 and 1.5.0.10</b><br />
***If you're interested in testing, you can run test cases through http://litmus.mozilla.org.<br />
**<b>Do you like hacking scripts or building web apps?</b> <br />
***The Talkback Report Challenge might be a good way to polish those skills of yours<br />
<br />
==<b>Test Days</b>==<br />
* For Calendar, 13:00 UTC on February 9th 2007 to 01:00 UTC on February 10th 2007. http://wiki.mozilla.org/Calendar:Current_QA_TestDay<br />
*For Firefox 1.510 & 2.002 RC1 builds,Friday, February 9, 2007, from 7am - 5pm PST. http://wiki.mozilla.org/Mozilla_QA_Community:Firefox_1510_2002_Community_Test_Day<br />
<br />
==Other==<br />
*<big><b>Super Fun Hack Days are moved to T3073</b></big><br />
<br />
<br />
*<big><b>Firefox 2 is offically released!!</b></big> - Oct 24 2006<br />
<br />
=Events=<br />
One of the most fun aspects of Club Moz is the fact that we run events (like Super Fun Hack Day)! Come by and get involved!<br />
<br />
Due to some unfortunate events we have had to develop a policy regarding our [[Club Moz:Events:Policy| event policy]]. By attending you accept the policy.<br />
<br />
For a complete list of upcoming Club Moz events, check out our [http://www.google.com/calendar/embed?src=clubmoz%40gmail.com calendar]!<br />
<br />
<br />
==Super Fun Hack Day==<br />
<br />
===Event Agenda===<br />
<br />
'''February 8 '''<br />
* Make sure your User Page is up under "People". This is a place for you to list the projects you're working on and your progress. Other people may use this as a point of reference to who you are. Feel free to take ownership of your user page and the projects you're working on. <br />
* [[Club_Moz#Want_to_work_on_some_cool_stuff.3F_There_are_some_cool_projects_waiting_for_you.. | Wanna work on some cool stuff? There are some projects waiting for you..]]<br />
<br />
<br />
'''February 1''' - Calendar Test Day. Details [http://wiki.mozilla.org/Calendar:Current_QA_TestDay Here]<br />
<br />
===Event Details===<br />
'''Super Fun Hack Day every Thursday'''<br />
*Open to all students no matter your technical background or level. <br />
*Bring your energy and interest and we will help turn that into new abilities and new friends.<br />
*Come by T3073 on the third floor of the TEL building. <br />
*Food and Drinks will be provided after the event. We expect to be starting at around 3:20 pm going until... :)<br />
<br />
<br />
===Super Fun Hack Day Stuff===<br />
* Proposed Flyer ([[User:elichak | Liz Chak]] (elichak) and [[User:moe|Mohammad Tirtashi]] (moe))<br />
<gallery><br />
Image:Flyer.jpg|Hack Day Flyer<br />
</gallery><br />
*[[Hack day Issues|Notes on Hack Day Issues]]<br />
*[http://elichak.wordpress.com/ elichak's log about Super Fun Hack Day]<br />
<br />
<br />
===Issues With Hack day===<br />
<br />
* [[ Hack_day_Issues]]<br />
<br />
==Club Moz planning meetings==<br />
*Open to members of the club - everyone's voice matters<br />
*Date/Time: TBA<br />
*Location: T2091 - Linux Club<br />
<br />
<br />
===Meeting Minutes===<br />
<br />
* [[Club Moz:Meetings/November 9, 2006|November 9, 2006]]<br />
* [[Club Moz:Meetings/November 15, 2006|November 15, 2006]]<br />
* [[Club Moz:Meetings/November 22, 2006|November 22, 2006]]<br />
* [[Club Moz:Meetings/November 29, 2006|November 29, 2006]]<br />
* [[Club Moz:Meetings/January 9, 2006|January 9, 2006]]<br />
<br />
=News=<br />
*The Firefox2 party was a success. <br />
**Here are some [http://www.flickr.com/photos/moebt/sets/72157594346279843/ pictures].<br />
**More [http://www.flickr.com/photos/14311671@N00/ pictures]!<br />
<br />
*Club hangout on irc: irc://irc.mozilla.org/#clubmoz<br />
<br />
<br />
=Members=<br />
List of members still in progress<br />
<br />
Add your name here if you would like to be a member of Club Moz :)<br />
<br />
* [[User:dtolj|Dejan Tolj]] (dtolj)<br />
* [[User:Eldavey|Erin Davey]] (davey_girl)<br />
* [[User:Eor|Eva Or]] (eor)<br />
* [[User:jbmossop|Jeff Mossop]] (JBmossop)<br />
* [[User:Mdsouza|Mark D'Souza]] (mdsouza)<br />
* [[User:melz|Melissa Peh]] (melz)<br />
* [[User:mylau|Michael Lau]] (mylau)<br />
* [[User:moe|Mohammad Tirtashi]] (moe)<br />
* [[User:Paul|Paul Yanchun Gu]] (gpaul)<br />
* [[User:PStD|Paul St-Denis]] (pstdenis)<br />
* [[User:John64|John Ford]] (john64)<br />
* Tiago Moreira (Tiago)<br />
* Sid Kalra (crulshorukh)<br />
* [[User:djhamp-g| david hamp]] (inveigle)<br />
* [[User:jp| justin pacheco]] (jp)<br />
* [[User:robcee|Rob Campbell]], aka robcee, QA Engineer, Mozilla Corp.<br />
* [[User:Gavin|Gavin Sharp]]<br />
* [[User:Shaver|shaver]]<br />
* [[User:backinblakk|Lukas Blakk]] (lsblakk)<br />
* [[User:Saba Naqvi|Saba]] (snaqvi3)</div>Eorhttps://wiki.cdot.senecacollege.ca/w/index.php?title=Club_Moz&diff=10123Club Moz2007-02-08T18:28:37Z<p>Eor: /* <b>Want to work on some cool stuff? There are some cool projects waiting for you..</b> */</p>
<hr />
<div>=Purpose=<br />
<b>To help students get involved in the Mozilla community through its future endeavors in development, testing, support and hacking</b><br />
<br />
This club is open to technical and also non-technical people. If you don't know anything about open source or Mozilla, don't worry, we're here to help you get involved and we promise a good time :)<br />
<br />
<br />
=Committee=<br />
'''President:''' [[User:Themystic|Tom Aratyn]] (mystic)<br />
<br />
'''Vice President:''' Tiago Moreira (Tiago)<br />
<br />
'''Financial Officer:''' [[User:Elichak|Liz Chak]] (elichak)<br />
<br />
'''Events Coordinator:''' [[User:Pcvitori|Philip Vitorino]] (philly)<br />
<br />
'''Promotions Coordinator:''' [[User:Vpmirand|Vanessa Miranda]] (vanessa)<br />
<br />
'''Faculty Advisor:''' [[User:David.humphrey|Dave Humphrey]] (dave or humph)<br />
<br />
<br />
'''Email:''' clubmoz@gmail.com<br />
<br />
=Announcements=<br />
==<b>Want to work on some cool stuff? There are some cool projects waiting for you..</b>==<br />
*<b>If you're interested in any of these projects, speak to [[User:elichak | Liz Chak]] about getting involved</b><br />
*QA Site for more QA details: http://wiki.mozilla.org/Mozilla_QA_Community<br />
*Projects are:<br />
<br />
*<b>Talkback Report Challenge 1</b><br />
**Check out this link for detail: http://wiki.mozilla.org/Mozilla_QA_Community:Talkback_Report_Challenge_1<br />
<br />
*<b>Data mining of Hendrix data for creating reports of user feedback</b><br />
**To better understand major issues being reported and converting them into new bugs or finding and updating existing ones<br />
<br />
*<b>Litmus Extension</b> <br />
**We wanted to have an extension that would be able to serve users testcases to try and allow them to submit results to http://litmus.mozilla.org. We could expand the feature set of the extension to do a lot of other cool things with Bugzilla and Website Reporter integration... so we need some ideas there. <br />
**If you're interested, you could collaborate with [[User:Djhamp-g | David Hamp-Gonsalves]] to work on this together.<br />
<br />
*<b>QMO Help</b><br />
**Help needed in getting QMO together. If anyone is interested in website design, php hacking, or general graphics work, we can use some help getting QMO into better shape.<br />
<br />
**<b>We are getting ready to ship Firefox 2.0.0.2 and 1.5.0.10</b><br />
***If you're interested in testing, you can run test cases through http://litmus.mozilla.org.<br />
**<b>Do you like hacking scripts or building web apps?</b> <br />
***The Talkback Report Challenge might be a good way to polish those skills of yours<br />
<br />
==<b>Test Days</b>==<br />
* For Calendar, 13:00 UTC on February 9th 2007 to 01:00 UTC on February 10th 2007. http://wiki.mozilla.org/Calendar:Current_QA_TestDay<br />
*For Firefox 1.510 & 2.002 RC1 builds,Friday, February 9, 2007, from 7am - 5pm PST. http://wiki.mozilla.org/Mozilla_QA_Community:Firefox_1510_2002_Community_Test_Day<br />
<br />
==Other==<br />
*<big><b>Super Fun Hack Days are moved to T3073</b></big><br />
<br />
<br />
*<big><b>Firefox 2 is offically released!!</b></big> - Oct 24 2006<br />
<br />
=Events=<br />
One of the most fun aspects of Club Moz is the fact that we run events (like Super Fun Hack Day)! Come by and get involved!<br />
<br />
Due to some unfortunate events we have had to develop a policy regarding our [[Club Moz:Events:Policy| event policy]]. By attending you accept the policy.<br />
<br />
For a complete list of upcoming Club Moz events, check out our [http://www.google.com/calendar/embed?src=clubmoz%40gmail.com calendar]!<br />
<br />
<br />
==Super Fun Hack Day==<br />
<br />
===Event Agenda===<br />
<br />
'''February 8 '''<br />
* Make sure your User Page is up under "People". This is a place for you to list the projects you're working on and your progress. Other people may use this as a point of reference to who you are. Feel free to take ownership of your user page and the projects you're working on. <br />
* [[Club_Moz#Want_to_work_on_some_cool_stuff.3F_There_are_some_cool_projects_waiting_for_you.. | Wanna work on some cool stuff? There are some projects waiting for you..]]<br />
<br />
<br />
'''February 1''' - Calendar Test Day. Details [http://wiki.mozilla.org/Calendar:Current_QA_TestDay Here]<br />
<br />
===Event Details===<br />
'''Super Fun Hack Day every Thursday'''<br />
*Open to all students no matter your technical background or level. <br />
*Bring your energy and interest and we will help turn that into new abilities and new friends.<br />
*Come by T3073 on the third floor of the TEL building. <br />
*Food and Drinks will be provided after the event. We expect to be starting at around 3:20 pm going until... :)<br />
<br />
<br />
===Super Fun Hack Day Stuff===<br />
* Proposed Flyer ([[User:elichak | Liz Chak]] (elichak) and [[User:moe|Mohammad Tirtashi]] (moe))<br />
<gallery><br />
Image:Flyer.jpg|Hack Day Flyer<br />
</gallery><br />
*[[Hack day Issues|Notes on Hack Day Issues]]<br />
*[http://elichak.wordpress.com/ elichak's log about Super Fun Hack Day]<br />
<br />
<br />
===Issues With Hack day===<br />
<br />
* [[ Hack_day_Issues]]<br />
<br />
==Club Moz planning meetings==<br />
*Open to members of the club - everyone's voice matters<br />
*Date/Time: TBA<br />
*Location: T2091 - Linux Club<br />
<br />
<br />
===Meeting Minutes===<br />
<br />
* [[Club Moz:Meetings/November 9, 2006|November 9, 2006]]<br />
* [[Club Moz:Meetings/November 15, 2006|November 15, 2006]]<br />
* [[Club Moz:Meetings/November 22, 2006|November 22, 2006]]<br />
* [[Club Moz:Meetings/November 29, 2006|November 29, 2006]]<br />
* [[Club Moz:Meetings/January 9, 2006|January 9, 2006]]<br />
<br />
=News=<br />
*The Firefox2 party was a success. <br />
**Here are some [http://www.flickr.com/photos/moebt/sets/72157594346279843/ pictures].<br />
**More [http://www.flickr.com/photos/14311671@N00/ pictures]!<br />
<br />
*Club hangout on irc: irc://irc.mozilla.org/#clubmoz<br />
<br />
<br />
=Members=<br />
List of members still in progress<br />
<br />
Add your name here if you would like to be a member of Club Moz :)<br />
<br />
* [[User:dtolj|Dejan Tolj]] (dtolj)<br />
* [[User:Eldavey|Erin Davey]] (davey_girl)<br />
* [[User:Eor|Eva Or]] (eor)<br />
* [[User:jbmossop|Jeff Mossop]] (JBmossop)<br />
* [[User:Mdsouza|Mark D'Souza]] (mdsouza)<br />
* [[User:melz|Melissa Peh]] (melz)<br />
* [[User:mylau|Michael Lau]] (mylau)<br />
* [[User:moe|Mohammad Tirtashi]] (moe)<br />
* [[User:Paul|Paul Yanchun Gu]] (gpaul)<br />
* [[User:PStD|Paul St-Denis]] (pstdenis)<br />
* [[User:John64|John Ford]] (john64)<br />
* Tiago Moreira (Tiago)<br />
* Sid Kalra (crulshorukh)<br />
* [[User:djhamp-g| david hamp]] (inveigle)<br />
* [[User:jp| justin pacheco]] (jp)<br />
* [[User:robcee|Rob Campbell]], aka robcee, QA Engineer, Mozilla Corp.<br />
* [[User:Gavin|Gavin Sharp]]<br />
* [[User:Shaver|shaver]]<br />
* [[User:backinblakk|Lukas Blakk]] (lsblakk)<br />
* [[User:Saba Naqvi|Saba]] (snaqvi3)</div>Eorhttps://wiki.cdot.senecacollege.ca/w/index.php?title=Club_Moz&diff=10122Club Moz2007-02-08T18:27:37Z<p>Eor: /* <b>Want to work on some cool stuff? There are some cool projects waiting for you..</b> */</p>
<hr />
<div>=Purpose=<br />
<b>To help students get involved in the Mozilla community through its future endeavors in development, testing, support and hacking</b><br />
<br />
This club is open to technical and also non-technical people. If you don't know anything about open source or Mozilla, don't worry, we're here to help you get involved and we promise a good time :)<br />
<br />
<br />
=Committee=<br />
'''President:''' [[User:Themystic|Tom Aratyn]] (mystic)<br />
<br />
'''Vice President:''' Tiago Moreira (Tiago)<br />
<br />
'''Financial Officer:''' [[User:Elichak|Liz Chak]] (elichak)<br />
<br />
'''Events Coordinator:''' [[User:Pcvitori|Philip Vitorino]] (philly)<br />
<br />
'''Promotions Coordinator:''' [[User:Vpmirand|Vanessa Miranda]] (vanessa)<br />
<br />
'''Faculty Advisor:''' [[User:David.humphrey|Dave Humphrey]] (dave or humph)<br />
<br />
<br />
'''Email:''' clubmoz@gmail.com<br />
<br />
=Announcements=<br />
==<b>Want to work on some cool stuff? There are some cool projects waiting for you..</b>==<br />
*<b>If you're interested in any of these projects, speak to [[User:elichak | Liz Chak]] about getting involved</b><br />
*QA Site for more QA details: http://wiki.mozilla.org/Mozilla_QA_Community<br />
*Projects are:<br />
<br />
*#<b>Talkback Report Challenge 1</b><br />
***Check out this link for detail: http://wiki.mozilla.org/Mozilla_QA_Community:Talkback_Report_Challenge_1<br />
<br />
*#<b>Data mining of Hendrix data for creating reports of user feedback</b><br />
***To better understand major issues being reported and converting them into new bugs or finding and updating existing ones<br />
<br />
*#<b>Litmus Extension</b> <br />
***We wanted to have an extension that would be able to serve users testcases to try and allow them to submit results to http://litmus.mozilla.org. We could expand the feature set of the extension to do a lot of other cool things with Bugzilla and Website Reporter integration... so we need some ideas there. <br />
***If you're interested, you could collaborate with [[User:Djhamp-g | David Hamp-Gonsalves]] to work on this together.<br />
<br />
*#<b>QMO Help</b><br />
***Help needed in getting QMO together. If anyone is interested in website design, php hacking, or general graphics work, we can use some help getting QMO into better shape.<br />
<br />
**<b>We are getting ready to ship Firefox 2.0.0.2 and 1.5.0.10</b><br />
***If you're interested in testing, you can run test cases through http://litmus.mozilla.org.<br />
**<b>Do you like hacking scripts or building web apps?</b> <br />
***The Talkback Report Challenge might be a good way to polish those skills of yours<br />
<br />
==<b>Test Days</b>==<br />
* For Calendar, 13:00 UTC on February 9th 2007 to 01:00 UTC on February 10th 2007. http://wiki.mozilla.org/Calendar:Current_QA_TestDay<br />
*For Firefox 1.510 & 2.002 RC1 builds,Friday, February 9, 2007, from 7am - 5pm PST. http://wiki.mozilla.org/Mozilla_QA_Community:Firefox_1510_2002_Community_Test_Day<br />
<br />
==Other==<br />
*<big><b>Super Fun Hack Days are moved to T3073</b></big><br />
<br />
<br />
*<big><b>Firefox 2 is offically released!!</b></big> - Oct 24 2006<br />
<br />
=Events=<br />
One of the most fun aspects of Club Moz is the fact that we run events (like Super Fun Hack Day)! Come by and get involved!<br />
<br />
Due to some unfortunate events we have had to develop a policy regarding our [[Club Moz:Events:Policy| event policy]]. By attending you accept the policy.<br />
<br />
For a complete list of upcoming Club Moz events, check out our [http://www.google.com/calendar/embed?src=clubmoz%40gmail.com calendar]!<br />
<br />
<br />
==Super Fun Hack Day==<br />
<br />
===Event Agenda===<br />
<br />
'''February 8 '''<br />
* Make sure your User Page is up under "People". This is a place for you to list the projects you're working on and your progress. Other people may use this as a point of reference to who you are. Feel free to take ownership of your user page and the projects you're working on. <br />
* [[Club_Moz#Want_to_work_on_some_cool_stuff.3F_There_are_some_cool_projects_waiting_for_you.. | Wanna work on some cool stuff? There are some projects waiting for you..]]<br />
<br />
<br />
'''February 1''' - Calendar Test Day. Details [http://wiki.mozilla.org/Calendar:Current_QA_TestDay Here]<br />
<br />
===Event Details===<br />
'''Super Fun Hack Day every Thursday'''<br />
*Open to all students no matter your technical background or level. <br />
*Bring your energy and interest and we will help turn that into new abilities and new friends.<br />
*Come by T3073 on the third floor of the TEL building. <br />
*Food and Drinks will be provided after the event. We expect to be starting at around 3:20 pm going until... :)<br />
<br />
<br />
===Super Fun Hack Day Stuff===<br />
* Proposed Flyer ([[User:elichak | Liz Chak]] (elichak) and [[User:moe|Mohammad Tirtashi]] (moe))<br />
<gallery><br />
Image:Flyer.jpg|Hack Day Flyer<br />
</gallery><br />
*[[Hack day Issues|Notes on Hack Day Issues]]<br />
*[http://elichak.wordpress.com/ elichak's log about Super Fun Hack Day]<br />
<br />
<br />
===Issues With Hack day===<br />
<br />
* [[ Hack_day_Issues]]<br />
<br />
==Club Moz planning meetings==<br />
*Open to members of the club - everyone's voice matters<br />
*Date/Time: TBA<br />
*Location: T2091 - Linux Club<br />
<br />
<br />
===Meeting Minutes===<br />
<br />
* [[Club Moz:Meetings/November 9, 2006|November 9, 2006]]<br />
* [[Club Moz:Meetings/November 15, 2006|November 15, 2006]]<br />
* [[Club Moz:Meetings/November 22, 2006|November 22, 2006]]<br />
* [[Club Moz:Meetings/November 29, 2006|November 29, 2006]]<br />
* [[Club Moz:Meetings/January 9, 2006|January 9, 2006]]<br />
<br />
=News=<br />
*The Firefox2 party was a success. <br />
**Here are some [http://www.flickr.com/photos/moebt/sets/72157594346279843/ pictures].<br />
**More [http://www.flickr.com/photos/14311671@N00/ pictures]!<br />
<br />
*Club hangout on irc: irc://irc.mozilla.org/#clubmoz<br />
<br />
<br />
=Members=<br />
List of members still in progress<br />
<br />
Add your name here if you would like to be a member of Club Moz :)<br />
<br />
* [[User:dtolj|Dejan Tolj]] (dtolj)<br />
* [[User:Eldavey|Erin Davey]] (davey_girl)<br />
* [[User:Eor|Eva Or]] (eor)<br />
* [[User:jbmossop|Jeff Mossop]] (JBmossop)<br />
* [[User:Mdsouza|Mark D'Souza]] (mdsouza)<br />
* [[User:melz|Melissa Peh]] (melz)<br />
* [[User:mylau|Michael Lau]] (mylau)<br />
* [[User:moe|Mohammad Tirtashi]] (moe)<br />
* [[User:Paul|Paul Yanchun Gu]] (gpaul)<br />
* [[User:PStD|Paul St-Denis]] (pstdenis)<br />
* [[User:John64|John Ford]] (john64)<br />
* Tiago Moreira (Tiago)<br />
* Sid Kalra (crulshorukh)<br />
* [[User:djhamp-g| david hamp]] (inveigle)<br />
* [[User:jp| justin pacheco]] (jp)<br />
* [[User:robcee|Rob Campbell]], aka robcee, QA Engineer, Mozilla Corp.<br />
* [[User:Gavin|Gavin Sharp]]<br />
* [[User:Shaver|shaver]]<br />
* [[User:backinblakk|Lukas Blakk]] (lsblakk)<br />
* [[User:Saba Naqvi|Saba]] (snaqvi3)</div>Eorhttps://wiki.cdot.senecacollege.ca/w/index.php?title=Club_Moz&diff=10121Club Moz2007-02-08T18:24:09Z<p>Eor: /* <b>Want to work on some cool stuff? There are some cool projects waiting for you..</b> */</p>
<hr />
<div>=Purpose=<br />
<b>To help students get involved in the Mozilla community through its future endeavors in development, testing, support and hacking</b><br />
<br />
This club is open to technical and also non-technical people. If you don't know anything about open source or Mozilla, don't worry, we're here to help you get involved and we promise a good time :)<br />
<br />
<br />
=Committee=<br />
'''President:''' [[User:Themystic|Tom Aratyn]] (mystic)<br />
<br />
'''Vice President:''' Tiago Moreira (Tiago)<br />
<br />
'''Financial Officer:''' [[User:Elichak|Liz Chak]] (elichak)<br />
<br />
'''Events Coordinator:''' [[User:Pcvitori|Philip Vitorino]] (philly)<br />
<br />
'''Promotions Coordinator:''' [[User:Vpmirand|Vanessa Miranda]] (vanessa)<br />
<br />
'''Faculty Advisor:''' [[User:David.humphrey|Dave Humphrey]] (dave or humph)<br />
<br />
<br />
'''Email:''' clubmoz@gmail.com<br />
<br />
=Announcements=<br />
==<b>Want to work on some cool stuff? There are some cool projects waiting for you..</b>==<br />
*<b>If you're interested in any of these projects, speak to [[User:elichak | Liz Chak]] about getting involved</b><br />
*QA Site for more QA details: http://wiki.mozilla.org/Mozilla_QA_Community<br />
*Projects are:<br />
<br />
**<b>Talkback Report Challenge 1</b><br />
***Check out this link for detail: http://wiki.mozilla.org/Mozilla_QA_Community:Talkback_Report_Challenge_1<br />
<br />
**<b>Data mining of Hendrix data for creating reports of user feedback</b><br />
***To better understand major issues being reported and converting them into new bugs or finding and updating existing ones<br />
<br />
**<b>Litmus Extension</b> <br />
***We wanted to have an extension that would be able to serve users testcases to try and allow them to submit results to http://litmus.mozilla.org. We could expand the feature set of the extension to do a lot of other cool things with Bugzilla and Website Reporter integration... so we need some ideas there. <br />
***If you're interested, you could collaborate with [[User:Djhamp-g | David Hamp-Gonsalves]] to work on this together.<br />
<br />
**<b>QMO Help</b><br />
***Help needed in getting QMO together. If anyone is interested in website design, php hacking, or general graphics work, we can use some help getting QMO into better shape.<br />
<br />
**<b>We are getting ready to ship Firefox 2.0.0.2 and 1.5.0.10</b><br />
***If you're interested in testing, you can run test cases through http://litmus.mozilla.org.<br />
**<b>Do you like hacking scripts or building web apps?</b> <br />
***The Talkback Report Challenge might be a good way to polish those skills of yours<br />
<br />
==<b>Test Days</b>==<br />
* For Calendar, 13:00 UTC on February 9th 2007 to 01:00 UTC on February 10th 2007. http://wiki.mozilla.org/Calendar:Current_QA_TestDay<br />
*For Firefox 1.510 & 2.002 RC1 builds,Friday, February 9, 2007, from 7am - 5pm PST. http://wiki.mozilla.org/Mozilla_QA_Community:Firefox_1510_2002_Community_Test_Day<br />
<br />
==Other==<br />
*<big><b>Super Fun Hack Days are moved to T3073</b></big><br />
<br />
<br />
*<big><b>Firefox 2 is offically released!!</b></big> - Oct 24 2006<br />
<br />
=Events=<br />
One of the most fun aspects of Club Moz is the fact that we run events (like Super Fun Hack Day)! Come by and get involved!<br />
<br />
Due to some unfortunate events we have had to develop a policy regarding our [[Club Moz:Events:Policy| event policy]]. By attending you accept the policy.<br />
<br />
For a complete list of upcoming Club Moz events, check out our [http://www.google.com/calendar/embed?src=clubmoz%40gmail.com calendar]!<br />
<br />
<br />
==Super Fun Hack Day==<br />
<br />
===Event Agenda===<br />
<br />
'''February 8 '''<br />
* Make sure your User Page is up under "People". This is a place for you to list the projects you're working on and your progress. Other people may use this as a point of reference to who you are. Feel free to take ownership of your user page and the projects you're working on. <br />
* [[Club_Moz#Want_to_work_on_some_cool_stuff.3F_There_are_some_cool_projects_waiting_for_you.. | Wanna work on some cool stuff? There are some projects waiting for you..]]<br />
<br />
<br />
'''February 1''' - Calendar Test Day. Details [http://wiki.mozilla.org/Calendar:Current_QA_TestDay Here]<br />
<br />
===Event Details===<br />
'''Super Fun Hack Day every Thursday'''<br />
*Open to all students no matter your technical background or level. <br />
*Bring your energy and interest and we will help turn that into new abilities and new friends.<br />
*Come by T3073 on the third floor of the TEL building. <br />
*Food and Drinks will be provided after the event. We expect to be starting at around 3:20 pm going until... :)<br />
<br />
<br />
===Super Fun Hack Day Stuff===<br />
* Proposed Flyer ([[User:elichak | Liz Chak]] (elichak) and [[User:moe|Mohammad Tirtashi]] (moe))<br />
<gallery><br />
Image:Flyer.jpg|Hack Day Flyer<br />
</gallery><br />
*[[Hack day Issues|Notes on Hack Day Issues]]<br />
*[http://elichak.wordpress.com/ elichak's log about Super Fun Hack Day]<br />
<br />
<br />
===Issues With Hack day===<br />
<br />
* [[ Hack_day_Issues]]<br />
<br />
==Club Moz planning meetings==<br />
*Open to members of the club - everyone's voice matters<br />
*Date/Time: TBA<br />
*Location: T2091 - Linux Club<br />
<br />
<br />
===Meeting Minutes===<br />
<br />
* [[Club Moz:Meetings/November 9, 2006|November 9, 2006]]<br />
* [[Club Moz:Meetings/November 15, 2006|November 15, 2006]]<br />
* [[Club Moz:Meetings/November 22, 2006|November 22, 2006]]<br />
* [[Club Moz:Meetings/November 29, 2006|November 29, 2006]]<br />
* [[Club Moz:Meetings/January 9, 2006|January 9, 2006]]<br />
<br />
=News=<br />
*The Firefox2 party was a success. <br />
**Here are some [http://www.flickr.com/photos/moebt/sets/72157594346279843/ pictures].<br />
**More [http://www.flickr.com/photos/14311671@N00/ pictures]!<br />
<br />
*Club hangout on irc: irc://irc.mozilla.org/#clubmoz<br />
<br />
<br />
=Members=<br />
List of members still in progress<br />
<br />
Add your name here if you would like to be a member of Club Moz :)<br />
<br />
* [[User:dtolj|Dejan Tolj]] (dtolj)<br />
* [[User:Eldavey|Erin Davey]] (davey_girl)<br />
* [[User:Eor|Eva Or]] (eor)<br />
* [[User:jbmossop|Jeff Mossop]] (JBmossop)<br />
* [[User:Mdsouza|Mark D'Souza]] (mdsouza)<br />
* [[User:melz|Melissa Peh]] (melz)<br />
* [[User:mylau|Michael Lau]] (mylau)<br />
* [[User:moe|Mohammad Tirtashi]] (moe)<br />
* [[User:Paul|Paul Yanchun Gu]] (gpaul)<br />
* [[User:PStD|Paul St-Denis]] (pstdenis)<br />
* [[User:John64|John Ford]] (john64)<br />
* Tiago Moreira (Tiago)<br />
* Sid Kalra (crulshorukh)<br />
* [[User:djhamp-g| david hamp]] (inveigle)<br />
* [[User:jp| justin pacheco]] (jp)<br />
* [[User:robcee|Rob Campbell]], aka robcee, QA Engineer, Mozilla Corp.<br />
* [[User:Gavin|Gavin Sharp]]<br />
* [[User:Shaver|shaver]]<br />
* [[User:backinblakk|Lukas Blakk]] (lsblakk)<br />
* [[User:Saba Naqvi|Saba]] (snaqvi3)</div>Eorhttps://wiki.cdot.senecacollege.ca/w/index.php?title=Club_Moz&diff=10120Club Moz2007-02-08T18:23:05Z<p>Eor: /* <b>Want to work on some cool stuff? There are some cool projects waiting for you..</b> */</p>
<hr />
<div>=Purpose=<br />
<b>To help students get involved in the Mozilla community through its future endeavors in development, testing, support and hacking</b><br />
<br />
This club is open to technical and also non-technical people. If you don't know anything about open source or Mozilla, don't worry, we're here to help you get involved and we promise a good time :)<br />
<br />
<br />
=Committee=<br />
'''President:''' [[User:Themystic|Tom Aratyn]] (mystic)<br />
<br />
'''Vice President:''' Tiago Moreira (Tiago)<br />
<br />
'''Financial Officer:''' [[User:Elichak|Liz Chak]] (elichak)<br />
<br />
'''Events Coordinator:''' [[User:Pcvitori|Philip Vitorino]] (philly)<br />
<br />
'''Promotions Coordinator:''' [[User:Vpmirand|Vanessa Miranda]] (vanessa)<br />
<br />
'''Faculty Advisor:''' [[User:David.humphrey|Dave Humphrey]] (dave or humph)<br />
<br />
<br />
'''Email:''' clubmoz@gmail.com<br />
<br />
=Announcements=<br />
==<b>Want to work on some cool stuff? There are some cool projects waiting for you..</b>==<br />
*<b>If you're interested in any of these projects, speak to [[User:elichak | Liz Chak]] about getting involved</b><br />
*QA Site for more QA details: http://wiki.mozilla.org/Mozilla_QA_Community<br />
*Projects are:<br />
<br />
**<b>Talkback Challenge</b><br />
***Check out this link for detail: <br />
**<b>Data mining of Hendrix data for creating reports of user feedback</b><br />
***To better understand major issues being reported and converting them into new bugs or finding and updating existing ones<br />
<br />
**<b>Litmus Extension</b> <br />
***We wanted to have an extension that would be able to serve users testcases to try and allow them to submit results to http://litmus.mozilla.org. We could expand the feature set of the extension to do a lot of other cool things with Bugzilla and Website Reporter integration... so we need some ideas there. <br />
***If you're interested, you could collaborate with [[User:Djhamp-g | David Hamp-Gonsalves]] to work on this together.<br />
<br />
**<b>QMO Help</b><br />
***Help needed in getting QMO together. If anyone is interested in website design, php hacking, or general graphics work, we can use some help getting QMO into better shape.<br />
<br />
**<b>We are getting ready to ship Firefox 2.0.0.2 and 1.5.0.10</b><br />
***If you're interested in testing, you can run test cases through http://litmus.mozilla.org.<br />
**<b>Do you like hacking scripts or building web apps?</b> <br />
***The Talkback Report Challenge might be a good way to polish those skills of yours<br />
<br />
==<b>Test Days</b>==<br />
* For Calendar, 13:00 UTC on February 9th 2007 to 01:00 UTC on February 10th 2007. http://wiki.mozilla.org/Calendar:Current_QA_TestDay<br />
*For Firefox 1.510 & 2.002 RC1 builds,Friday, February 9, 2007, from 7am - 5pm PST. http://wiki.mozilla.org/Mozilla_QA_Community:Firefox_1510_2002_Community_Test_Day<br />
<br />
==Other==<br />
*<big><b>Super Fun Hack Days are moved to T3073</b></big><br />
<br />
<br />
*<big><b>Firefox 2 is offically released!!</b></big> - Oct 24 2006<br />
<br />
=Events=<br />
One of the most fun aspects of Club Moz is the fact that we run events (like Super Fun Hack Day)! Come by and get involved!<br />
<br />
Due to some unfortunate events we have had to develop a policy regarding our [[Club Moz:Events:Policy| event policy]]. By attending you accept the policy.<br />
<br />
For a complete list of upcoming Club Moz events, check out our [http://www.google.com/calendar/embed?src=clubmoz%40gmail.com calendar]!<br />
<br />
<br />
==Super Fun Hack Day==<br />
<br />
===Event Agenda===<br />
<br />
'''February 8 '''<br />
* Make sure your User Page is up under "People". This is a place for you to list the projects you're working on and your progress. Other people may use this as a point of reference to who you are. Feel free to take ownership of your user page and the projects you're working on. <br />
* [[Club_Moz#Want_to_work_on_some_cool_stuff.3F_There_are_some_cool_projects_waiting_for_you.. | Wanna work on some cool stuff? There are some projects waiting for you..]]<br />
<br />
<br />
'''February 1''' - Calendar Test Day. Details [http://wiki.mozilla.org/Calendar:Current_QA_TestDay Here]<br />
<br />
===Event Details===<br />
'''Super Fun Hack Day every Thursday'''<br />
*Open to all students no matter your technical background or level. <br />
*Bring your energy and interest and we will help turn that into new abilities and new friends.<br />
*Come by T3073 on the third floor of the TEL building. <br />
*Food and Drinks will be provided after the event. We expect to be starting at around 3:20 pm going until... :)<br />
<br />
<br />
===Super Fun Hack Day Stuff===<br />
* Proposed Flyer ([[User:elichak | Liz Chak]] (elichak) and [[User:moe|Mohammad Tirtashi]] (moe))<br />
<gallery><br />
Image:Flyer.jpg|Hack Day Flyer<br />
</gallery><br />
*[[Hack day Issues|Notes on Hack Day Issues]]<br />
*[http://elichak.wordpress.com/ elichak's log about Super Fun Hack Day]<br />
<br />
<br />
===Issues With Hack day===<br />
<br />
* [[ Hack_day_Issues]]<br />
<br />
==Club Moz planning meetings==<br />
*Open to members of the club - everyone's voice matters<br />
*Date/Time: TBA<br />
*Location: T2091 - Linux Club<br />
<br />
<br />
===Meeting Minutes===<br />
<br />
* [[Club Moz:Meetings/November 9, 2006|November 9, 2006]]<br />
* [[Club Moz:Meetings/November 15, 2006|November 15, 2006]]<br />
* [[Club Moz:Meetings/November 22, 2006|November 22, 2006]]<br />
* [[Club Moz:Meetings/November 29, 2006|November 29, 2006]]<br />
* [[Club Moz:Meetings/January 9, 2006|January 9, 2006]]<br />
<br />
=News=<br />
*The Firefox2 party was a success. <br />
**Here are some [http://www.flickr.com/photos/moebt/sets/72157594346279843/ pictures].<br />
**More [http://www.flickr.com/photos/14311671@N00/ pictures]!<br />
<br />
*Club hangout on irc: irc://irc.mozilla.org/#clubmoz<br />
<br />
<br />
=Members=<br />
List of members still in progress<br />
<br />
Add your name here if you would like to be a member of Club Moz :)<br />
<br />
* [[User:dtolj|Dejan Tolj]] (dtolj)<br />
* [[User:Eldavey|Erin Davey]] (davey_girl)<br />
* [[User:Eor|Eva Or]] (eor)<br />
* [[User:jbmossop|Jeff Mossop]] (JBmossop)<br />
* [[User:Mdsouza|Mark D'Souza]] (mdsouza)<br />
* [[User:melz|Melissa Peh]] (melz)<br />
* [[User:mylau|Michael Lau]] (mylau)<br />
* [[User:moe|Mohammad Tirtashi]] (moe)<br />
* [[User:Paul|Paul Yanchun Gu]] (gpaul)<br />
* [[User:PStD|Paul St-Denis]] (pstdenis)<br />
* [[User:John64|John Ford]] (john64)<br />
* Tiago Moreira (Tiago)<br />
* Sid Kalra (crulshorukh)<br />
* [[User:djhamp-g| david hamp]] (inveigle)<br />
* [[User:jp| justin pacheco]] (jp)<br />
* [[User:robcee|Rob Campbell]], aka robcee, QA Engineer, Mozilla Corp.<br />
* [[User:Gavin|Gavin Sharp]]<br />
* [[User:Shaver|shaver]]<br />
* [[User:backinblakk|Lukas Blakk]] (lsblakk)<br />
* [[User:Saba Naqvi|Saba]] (snaqvi3)</div>Eorhttps://wiki.cdot.senecacollege.ca/w/index.php?title=Club_Moz&diff=10081Club Moz2007-02-07T18:07:27Z<p>Eor: /* Members */</p>
<hr />
<div>=Purpose=<br />
<b>To help students get involved in the Mozilla community through its future endeavors in development, testing, support and hacking</b><br />
<br />
This club is open to technical and also non-technical people. If you don't know anything about open source or Mozilla, don't worry, we're here to help you get involved and we promise a good time :)<br />
<br />
<br />
=Committee=<br />
'''President:''' [[User:Themystic|Tom Aratyn]] (mystic)<br />
<br />
'''Vice President:''' Tiago Moreira (Tiago)<br />
<br />
'''Financial Officer:''' [[User:Elichak|Liz Chak]] (elichak)<br />
<br />
'''Events Coordinator:''' [[User:Pcvitori|Philip Vitorino]] (philly)<br />
<br />
'''Promotions Coordinator:''' [[User:Vpmirand|Vanessa Miranda]] (vanessa)<br />
<br />
'''Faculty Advisor:''' [[User:David.humphrey|Dave Humphrey]] (dave or humph)<br />
<br />
<br />
'''Email:''' clubmoz@gmail.com<br />
<br />
=Announcements=<br />
*<big><b>Test Days</b></big><br />
** For Calendar, 13:00 UTC on February 9th 2007 to 01:00 UTC on February 10th 2007. http://wiki.mozilla.org/Calendar:Current_QA_TestDay<br />
**For Firefox 1.510 & 2.002 RC1 builds,Friday, February 9, 2007, from 7am - 5pm PST. http://wiki.mozilla.org/Mozilla_QA_Community:Firefox_1510_2002_Community_Test_Day<br />
<br />
<br />
*Super Fun Hack Days are moved to T3073<br />
<br />
<br />
*<big><b>Firefox 2 is offically released!!</b></big><br />
- Oct 24 2006<br />
<br />
=Events=<br />
One of the most fun aspects of Club Moz is the fact that we run events (like Super Fun Hack Day)! Come by and get involved!<br />
<br />
Due to some unfortunate events we have had to develop a policy regarding our [[Club Moz:Events:Policy| event policy]]. By attending you accept the policy.<br />
<br />
<br />
==Super Fun Hack Day==<br />
<br />
===Event Agenda===<br />
<br />
'''February 1''' - Calendar Test Day. Details [http://wiki.mozilla.org/Calendar:Current_QA_TestDay Here]<br />
<br />
<br />
===Event Details===<br />
'''Super Fun Hack Day every Thursday'''<br />
*Open to all students no matter your technical background or level. <br />
*Bring your energy and interest and we will help turn that into new abilities and new friends.<br />
*Come by T3073 on the third floor of the TEL building. <br />
*Food and Drinks will be provided after the event. We expect to be starting at around 3:20 pm going until... :)<br />
<br />
<br />
===Super Fun Hack Day Stuff===<br />
* Proposed Flyer ([[User:elichak | Liz Chak]] (elichak) and [[User:moe|Mohammad Tirtashi]] (moe))<br />
<gallery><br />
Image:Flyer.jpg|Hack Day Flyer<br />
</gallery><br />
*[[Hack day Issues|Notes on Hack Day Issues]]<br />
*[http://elichak.wordpress.com/ elichak's log about Super Fun Hack Day]<br />
<br />
<br />
===Issues With Hack day===<br />
<br />
* [[ Hack_day_Issues]]<br />
<br />
==Club Moz planning meetings==<br />
*Open to members of the club - everyone's voice matters<br />
*Date/Time: TBA<br />
*Location: T2091 - Linux Club<br />
<br />
<br />
===Meeting Minutes===<br />
<br />
* [[Club Moz:Meetings/November 9, 2006|November 9, 2006]]<br />
* [[Club Moz:Meetings/November 15, 2006|November 15, 2006]]<br />
* [[Club Moz:Meetings/November 22, 2006|November 22, 2006]]<br />
* [[Club Moz:Meetings/November 29, 2006|November 29, 2006]]<br />
* [[Club Moz:Meetings/January 9, 2006|January 9, 2006]]<br />
<br />
=News=<br />
*The Firefox2 party was a success. <br />
**Here are some [http://www.flickr.com/photos/moebt/sets/72157594346279843/ pictures].<br />
**More [http://www.flickr.com/photos/14311671@N00/ pictures]!<br />
<br />
*Club hangout on irc: irc://irc.mozilla.org/#clubmoz<br />
<br />
<br />
=Members=<br />
List of members still in progress<br />
<br />
Add your name here if you would like to be a member of Club Moz :)<br />
<br />
* [[User:dtolj|Dejan Tolj]] (dtolj)<br />
* [[User:Eldavey|Erin Davey]] (davey_girl)<br />
* [[User:Eor|Eva Or]] (eor)<br />
* [[User:jbmossop|Jeff Mossop]] (JBmossop)<br />
* [[User:Mdsouza|Mark D'Souza]] (mdsouza)<br />
* [[User:melz|Melissa Peh]] (melz)<br />
* [[User:mylau|Michael Lau]] (mylau)<br />
* [[User:moe|Mohammad Tirtashi]] (moe)<br />
* [[User:Paul|Paul Yanchun Gu]] (gpaul)<br />
* [[User:PStD|Paul St-Denis]] (pstdenis)<br />
* [[User:John64|John Ford]] (john64)<br />
* Tiago Moreira (Tiago)<br />
* Sid Kalra (crulshorukh)<br />
* [[User:djhamp-g| david hamp]] (inveigle)<br />
* [[User:jp| justin pacheco]] (jp)<br />
* [[User:robcee|Rob Campbell]], aka robcee, QA Engineer, Mozilla Corp.<br />
* [[User:Gavin|Gavin Sharp]]<br />
* [[User:Shaver|shaver]]<br />
* [[User:backinblakk|Lukas Blakk]] (lsblakk)<br />
* [[User:Saba Naqvi|Saba]] (snaqvi3)</div>Eorhttps://wiki.cdot.senecacollege.ca/w/index.php?title=Club_Moz&diff=10080Club Moz2007-02-07T18:05:08Z<p>Eor: /* Announcements */</p>
<hr />
<div>=Purpose=<br />
<b>To help students get involved in the Mozilla community through its future endeavors in development, testing, support and hacking</b><br />
<br />
This club is open to technical and also non-technical people. If you don't know anything about open source or Mozilla, don't worry, we're here to help you get involved and we promise a good time :)<br />
<br />
<br />
=Committee=<br />
'''President:''' [[User:Themystic|Tom Aratyn]] (mystic)<br />
<br />
'''Vice President:''' Tiago Moreira (Tiago)<br />
<br />
'''Financial Officer:''' [[User:Elichak|Liz Chak]] (elichak)<br />
<br />
'''Events Coordinator:''' [[User:Pcvitori|Philip Vitorino]] (philly)<br />
<br />
'''Promotions Coordinator:''' [[User:Vpmirand|Vanessa Miranda]] (vanessa)<br />
<br />
'''Faculty Advisor:''' [[User:David.humphrey|Dave Humphrey]] (dave or humph)<br />
<br />
<br />
'''Email:''' clubmoz@gmail.com<br />
<br />
=Announcements=<br />
*<big><b>Test Days</b></big><br />
** For Calendar, 13:00 UTC on February 9th 2007 to 01:00 UTC on February 10th 2007. http://wiki.mozilla.org/Calendar:Current_QA_TestDay<br />
**For Firefox 1.510 & 2.002 RC1 builds,Friday, February 9, 2007, from 7am - 5pm PST. http://wiki.mozilla.org/Mozilla_QA_Community:Firefox_1510_2002_Community_Test_Day<br />
<br />
<br />
*Super Fun Hack Days are moved to T3073<br />
<br />
<br />
*<big><b>Firefox 2 is offically released!!</b></big><br />
- Oct 24 2006<br />
<br />
=Events=<br />
One of the most fun aspects of Club Moz is the fact that we run events (like Super Fun Hack Day)! Come by and get involved!<br />
<br />
Due to some unfortunate events we have had to develop a policy regarding our [[Club Moz:Events:Policy| event policy]]. By attending you accept the policy.<br />
<br />
<br />
==Super Fun Hack Day==<br />
<br />
===Event Agenda===<br />
<br />
'''February 1''' - Calendar Test Day. Details [http://wiki.mozilla.org/Calendar:Current_QA_TestDay Here]<br />
<br />
<br />
===Event Details===<br />
'''Super Fun Hack Day every Thursday'''<br />
*Open to all students no matter your technical background or level. <br />
*Bring your energy and interest and we will help turn that into new abilities and new friends.<br />
*Come by T3073 on the third floor of the TEL building. <br />
*Food and Drinks will be provided after the event. We expect to be starting at around 3:20 pm going until... :)<br />
<br />
<br />
===Super Fun Hack Day Stuff===<br />
* Proposed Flyer ([[User:elichak | Liz Chak]] (elichak) and [[User:moe|Mohammad Tirtashi]] (moe))<br />
<gallery><br />
Image:Flyer.jpg|Hack Day Flyer<br />
</gallery><br />
*[[Hack day Issues|Notes on Hack Day Issues]]<br />
*[http://elichak.wordpress.com/ elichak's log about Super Fun Hack Day]<br />
<br />
<br />
===Issues With Hack day===<br />
<br />
* [[ Hack_day_Issues]]<br />
<br />
==Club Moz planning meetings==<br />
*Open to members of the club - everyone's voice matters<br />
*Date/Time: TBA<br />
*Location: T2091 - Linux Club<br />
<br />
<br />
===Meeting Minutes===<br />
<br />
* [[Club Moz:Meetings/November 9, 2006|November 9, 2006]]<br />
* [[Club Moz:Meetings/November 15, 2006|November 15, 2006]]<br />
* [[Club Moz:Meetings/November 22, 2006|November 22, 2006]]<br />
* [[Club Moz:Meetings/November 29, 2006|November 29, 2006]]<br />
* [[Club Moz:Meetings/January 9, 2006|January 9, 2006]]<br />
<br />
=News=<br />
*The Firefox2 party was a success. <br />
**Here are some [http://www.flickr.com/photos/moebt/sets/72157594346279843/ pictures].<br />
**More [http://www.flickr.com/photos/14311671@N00/ pictures]!<br />
<br />
*Club hangout on irc: irc://irc.mozilla.org/#clubmoz<br />
<br />
<br />
=Members=<br />
List of members still in progress<br />
<br />
Add your name here if you would like to be a member of Club Moz :)<br />
<br />
* [[User:dtolj|Dejan Tolj]] (dtolj)<br />
* [[User:Eldavey|Erin Davey]] (davey_girl)<br />
* [[User:jbmossop|Jeff Mossop]] (JBmossop)<br />
* [[User:Mdsouza|Mark D'Souza]] (mdsouza)<br />
* [[User:melz|Melissa Peh]] (melz)<br />
* [[User:mylau|Michael Lau]] (mylau)<br />
* [[User:moe|Mohammad Tirtashi]] (moe)<br />
* [[User:Paul|Paul Yanchun Gu]] (gpaul)<br />
* [[User:PStD|Paul St-Denis]] (pstdenis)<br />
* [[User:John64|John Ford]] (john64)<br />
* Tiago Moreira (Tiago)<br />
* Sid Kalra (crulshorukh)<br />
* [[User:djhamp-g| david hamp]] (inveigle)<br />
* [[User:jp| justin pacheco]] (jp)<br />
* [[User:robcee|Rob Campbell]], aka robcee, QA Engineer, Mozilla Corp.<br />
* [[User:Gavin|Gavin Sharp]]<br />
* [[User:Shaver|shaver]]<br />
* [[User:backinblakk|Lukas Blakk]] (lsblakk)<br />
* [[User:Saba Naqvi|Saba]] (snaqvi3)</div>Eorhttps://wiki.cdot.senecacollege.ca/w/index.php?title=Club_Moz&diff=10079Club Moz2007-02-07T18:04:28Z<p>Eor: /* Announcements */</p>
<hr />
<div>=Purpose=<br />
<b>To help students get involved in the Mozilla community through its future endeavors in development, testing, support and hacking</b><br />
<br />
This club is open to technical and also non-technical people. If you don't know anything about open source or Mozilla, don't worry, we're here to help you get involved and we promise a good time :)<br />
<br />
<br />
=Committee=<br />
'''President:''' [[User:Themystic|Tom Aratyn]] (mystic)<br />
<br />
'''Vice President:''' Tiago Moreira (Tiago)<br />
<br />
'''Financial Officer:''' [[User:Elichak|Liz Chak]] (elichak)<br />
<br />
'''Events Coordinator:''' [[User:Pcvitori|Philip Vitorino]] (philly)<br />
<br />
'''Promotions Coordinator:''' [[User:Vpmirand|Vanessa Miranda]] (vanessa)<br />
<br />
'''Faculty Advisor:''' [[User:David.humphrey|Dave Humphrey]] (dave or humph)<br />
<br />
<br />
'''Email:''' clubmoz@gmail.com<br />
<br />
=Announcements=<br />
*<big><b>Test Days</b></big><br />
** For Calendar, 13:00 UTC on February 9th 2007 to 01:00 UTC on February 10th 2007. http://wiki.mozilla.org/Calendar:Current_QA_TestDay<br />
**For Firefox 1.510 & 2.002 RC1 builds,Friday, February 9, 2007, from 7am - 5pm PST. http://wiki.mozilla.org/Mozilla_QA_Community:Firefox_1510_2002_Community_Test_Day<br />
<br />
*Super Fun Hack Days are moved to T3073<br />
<br />
<br />
*<big><b>Firefox 2 is offically released!!</b></big><br />
- Oct 24 2006<br />
<br />
=Events=<br />
One of the most fun aspects of Club Moz is the fact that we run events (like Super Fun Hack Day)! Come by and get involved!<br />
<br />
Due to some unfortunate events we have had to develop a policy regarding our [[Club Moz:Events:Policy| event policy]]. By attending you accept the policy.<br />
<br />
<br />
==Super Fun Hack Day==<br />
<br />
===Event Agenda===<br />
<br />
'''February 1''' - Calendar Test Day. Details [http://wiki.mozilla.org/Calendar:Current_QA_TestDay Here]<br />
<br />
<br />
===Event Details===<br />
'''Super Fun Hack Day every Thursday'''<br />
*Open to all students no matter your technical background or level. <br />
*Bring your energy and interest and we will help turn that into new abilities and new friends.<br />
*Come by T3073 on the third floor of the TEL building. <br />
*Food and Drinks will be provided after the event. We expect to be starting at around 3:20 pm going until... :)<br />
<br />
<br />
===Super Fun Hack Day Stuff===<br />
* Proposed Flyer ([[User:elichak | Liz Chak]] (elichak) and [[User:moe|Mohammad Tirtashi]] (moe))<br />
<gallery><br />
Image:Flyer.jpg|Hack Day Flyer<br />
</gallery><br />
*[[Hack day Issues|Notes on Hack Day Issues]]<br />
*[http://elichak.wordpress.com/ elichak's log about Super Fun Hack Day]<br />
<br />
<br />
===Issues With Hack day===<br />
<br />
* [[ Hack_day_Issues]]<br />
<br />
==Club Moz planning meetings==<br />
*Open to members of the club - everyone's voice matters<br />
*Date/Time: TBA<br />
*Location: T2091 - Linux Club<br />
<br />
<br />
===Meeting Minutes===<br />
<br />
* [[Club Moz:Meetings/November 9, 2006|November 9, 2006]]<br />
* [[Club Moz:Meetings/November 15, 2006|November 15, 2006]]<br />
* [[Club Moz:Meetings/November 22, 2006|November 22, 2006]]<br />
* [[Club Moz:Meetings/November 29, 2006|November 29, 2006]]<br />
* [[Club Moz:Meetings/January 9, 2006|January 9, 2006]]<br />
<br />
=News=<br />
*The Firefox2 party was a success. <br />
**Here are some [http://www.flickr.com/photos/moebt/sets/72157594346279843/ pictures].<br />
**More [http://www.flickr.com/photos/14311671@N00/ pictures]!<br />
<br />
*Club hangout on irc: irc://irc.mozilla.org/#clubmoz<br />
<br />
<br />
=Members=<br />
List of members still in progress<br />
<br />
Add your name here if you would like to be a member of Club Moz :)<br />
<br />
* [[User:dtolj|Dejan Tolj]] (dtolj)<br />
* [[User:Eldavey|Erin Davey]] (davey_girl)<br />
* [[User:jbmossop|Jeff Mossop]] (JBmossop)<br />
* [[User:Mdsouza|Mark D'Souza]] (mdsouza)<br />
* [[User:melz|Melissa Peh]] (melz)<br />
* [[User:mylau|Michael Lau]] (mylau)<br />
* [[User:moe|Mohammad Tirtashi]] (moe)<br />
* [[User:Paul|Paul Yanchun Gu]] (gpaul)<br />
* [[User:PStD|Paul St-Denis]] (pstdenis)<br />
* [[User:John64|John Ford]] (john64)<br />
* Tiago Moreira (Tiago)<br />
* Sid Kalra (crulshorukh)<br />
* [[User:djhamp-g| david hamp]] (inveigle)<br />
* [[User:jp| justin pacheco]] (jp)<br />
* [[User:robcee|Rob Campbell]], aka robcee, QA Engineer, Mozilla Corp.<br />
* [[User:Gavin|Gavin Sharp]]<br />
* [[User:Shaver|shaver]]<br />
* [[User:backinblakk|Lukas Blakk]] (lsblakk)<br />
* [[User:Saba Naqvi|Saba]] (snaqvi3)</div>Eorhttps://wiki.cdot.senecacollege.ca/w/index.php?title=Club_Moz&diff=10078Club Moz2007-02-07T18:03:59Z<p>Eor: /* Announcements */</p>
<hr />
<div>=Purpose=<br />
<b>To help students get involved in the Mozilla community through its future endeavors in development, testing, support and hacking</b><br />
<br />
This club is open to technical and also non-technical people. If you don't know anything about open source or Mozilla, don't worry, we're here to help you get involved and we promise a good time :)<br />
<br />
<br />
=Committee=<br />
'''President:''' [[User:Themystic|Tom Aratyn]] (mystic)<br />
<br />
'''Vice President:''' Tiago Moreira (Tiago)<br />
<br />
'''Financial Officer:''' [[User:Elichak|Liz Chak]] (elichak)<br />
<br />
'''Events Coordinator:''' [[User:Pcvitori|Philip Vitorino]] (philly)<br />
<br />
'''Promotions Coordinator:''' [[User:Vpmirand|Vanessa Miranda]] (vanessa)<br />
<br />
'''Faculty Advisor:''' [[User:David.humphrey|Dave Humphrey]] (dave or humph)<br />
<br />
<br />
'''Email:''' clubmoz@gmail.com<br />
<br />
=Announcements=<br />
*<big><b>Test Days</b></big><br />
- For Calendar, 13:00 UTC on February 9th 2007 to 01:00 UTC on February 10th 2007. http://wiki.mozilla.org/Calendar:Current_QA_TestDay<br />
- For Firefox 1.510 & 2.002 RC1 builds,Friday, February 9, 2007, from 7am - 5pm PST. http://wiki.mozilla.org/Mozilla_QA_Community:Firefox_1510_2002_Community_Test_Day<br />
<br />
*Super Fun Hack Days are moved to T3073<br />
<br />
<br />
*<big><b>Firefox 2 is offically released!!</b></big><br />
- Oct 24 2006<br />
<br />
=Events=<br />
One of the most fun aspects of Club Moz is the fact that we run events (like Super Fun Hack Day)! Come by and get involved!<br />
<br />
Due to some unfortunate events we have had to develop a policy regarding our [[Club Moz:Events:Policy| event policy]]. By attending you accept the policy.<br />
<br />
<br />
==Super Fun Hack Day==<br />
<br />
===Event Agenda===<br />
<br />
'''February 1''' - Calendar Test Day. Details [http://wiki.mozilla.org/Calendar:Current_QA_TestDay Here]<br />
<br />
<br />
===Event Details===<br />
'''Super Fun Hack Day every Thursday'''<br />
*Open to all students no matter your technical background or level. <br />
*Bring your energy and interest and we will help turn that into new abilities and new friends.<br />
*Come by T3073 on the third floor of the TEL building. <br />
*Food and Drinks will be provided after the event. We expect to be starting at around 3:20 pm going until... :)<br />
<br />
<br />
===Super Fun Hack Day Stuff===<br />
* Proposed Flyer ([[User:elichak | Liz Chak]] (elichak) and [[User:moe|Mohammad Tirtashi]] (moe))<br />
<gallery><br />
Image:Flyer.jpg|Hack Day Flyer<br />
</gallery><br />
*[[Hack day Issues|Notes on Hack Day Issues]]<br />
*[http://elichak.wordpress.com/ elichak's log about Super Fun Hack Day]<br />
<br />
<br />
===Issues With Hack day===<br />
<br />
* [[ Hack_day_Issues]]<br />
<br />
==Club Moz planning meetings==<br />
*Open to members of the club - everyone's voice matters<br />
*Date/Time: TBA<br />
*Location: T2091 - Linux Club<br />
<br />
<br />
===Meeting Minutes===<br />
<br />
* [[Club Moz:Meetings/November 9, 2006|November 9, 2006]]<br />
* [[Club Moz:Meetings/November 15, 2006|November 15, 2006]]<br />
* [[Club Moz:Meetings/November 22, 2006|November 22, 2006]]<br />
* [[Club Moz:Meetings/November 29, 2006|November 29, 2006]]<br />
* [[Club Moz:Meetings/January 9, 2006|January 9, 2006]]<br />
<br />
=News=<br />
*The Firefox2 party was a success. <br />
**Here are some [http://www.flickr.com/photos/moebt/sets/72157594346279843/ pictures].<br />
**More [http://www.flickr.com/photos/14311671@N00/ pictures]!<br />
<br />
*Club hangout on irc: irc://irc.mozilla.org/#clubmoz<br />
<br />
<br />
=Members=<br />
List of members still in progress<br />
<br />
Add your name here if you would like to be a member of Club Moz :)<br />
<br />
* [[User:dtolj|Dejan Tolj]] (dtolj)<br />
* [[User:Eldavey|Erin Davey]] (davey_girl)<br />
* [[User:jbmossop|Jeff Mossop]] (JBmossop)<br />
* [[User:Mdsouza|Mark D'Souza]] (mdsouza)<br />
* [[User:melz|Melissa Peh]] (melz)<br />
* [[User:mylau|Michael Lau]] (mylau)<br />
* [[User:moe|Mohammad Tirtashi]] (moe)<br />
* [[User:Paul|Paul Yanchun Gu]] (gpaul)<br />
* [[User:PStD|Paul St-Denis]] (pstdenis)<br />
* [[User:John64|John Ford]] (john64)<br />
* Tiago Moreira (Tiago)<br />
* Sid Kalra (crulshorukh)<br />
* [[User:djhamp-g| david hamp]] (inveigle)<br />
* [[User:jp| justin pacheco]] (jp)<br />
* [[User:robcee|Rob Campbell]], aka robcee, QA Engineer, Mozilla Corp.<br />
* [[User:Gavin|Gavin Sharp]]<br />
* [[User:Shaver|shaver]]<br />
* [[User:backinblakk|Lukas Blakk]] (lsblakk)<br />
* [[User:Saba Naqvi|Saba]] (snaqvi3)</div>Eorhttps://wiki.cdot.senecacollege.ca/w/index.php?title=User:Eor&diff=8745User:Eor2006-12-14T01:39:09Z<p>Eor: /* Other contributed project */</p>
<hr />
<div>== Introduction ==<br />
Hi, All! I am:<br />
<br />
* In BSD 7th Semester student (Started at the very beginning of BSD)<br />
* Working part time as a BSD and CPA Tutor at The Learning Center at Seneca College<br />
* Worked as a QA during my Summer 2006 Coop<br />
* Do not have any experience on Open Source project, but find it interesting. Hopefully, can get more involvement to Open Source by the end of this term.<br />
* Not Geeky in any way, but for some reason being in programming. Usually quiet, but can be talkative at time too.<br />
<br />
== Contact Information ==<br />
:'''Name''': Eva Or<br />
:'''IRC Nick''': eor<br />
:'''Email''': evaor1012@rogers.com<br />
:'''MSN''': evaor1012@hotmail.com<br />
:'''Skype''': N/A<br />
<br />
== Leading Project ==<br />
*[[Calendar_stuff|Calendar Stuff]]<br />
<br />
*Link to Test Day wiki [http://zenit.senecac.on.ca/wiki/index.php/Calendar_TestDay here]<br />
<br />
== Other contributed project ==<br />
*[[Firefox_Performance_Testing_:_A_Python_framework_for_Windows | Performance Testing]]<br />
: I was the first two performance tester before Liz run the performance testing day.<br />
: So I ran through the documentation thoroughly, to make sure it is understandable and I have documented all the detail in the discussion page linked to the performance testing<br />
<br />
*[[Functional_Testing | Functional Testing]]<br />
: I was involve in the Firefox Testday, at first I was only doing it during class. However, I feel the class time is not long enough to make a good contribution, so I went on to test the software for more hours. I stopped in the evening after I got very tired doing more testing. <br />
: liz invited me to join the functional testing project and I will have more involvement on it in the future.<br />
<br />
*[[Simple_Citation | Simple Cititation]]<br />
: For the localization, do translation for chinese traditional(zh-TW) and chinese simplified(zh-CN)<br />
<br />
*[[Mozilla_based_accessibility | Mozilla based accessibility]]<br />
: For this project, I was assigned to search thru about 100 of jingles to find the best 3 for erin to pick and we decide which one to take together. And for the Chinese component, I find pages for her to test, but encountered some difficuit at the beginning and now is solved.<br />
<br />
== Assignment 1 ==<br />
[[Eva_Assignment_1| Assignment 1]]</div>Eorhttps://wiki.cdot.senecacollege.ca/w/index.php?title=User:Eor&diff=8744User:Eor2006-12-14T01:37:42Z<p>Eor: /* Other contributed project */</p>
<hr />
<div>== Introduction ==<br />
Hi, All! I am:<br />
<br />
* In BSD 7th Semester student (Started at the very beginning of BSD)<br />
* Working part time as a BSD and CPA Tutor at The Learning Center at Seneca College<br />
* Worked as a QA during my Summer 2006 Coop<br />
* Do not have any experience on Open Source project, but find it interesting. Hopefully, can get more involvement to Open Source by the end of this term.<br />
* Not Geeky in any way, but for some reason being in programming. Usually quiet, but can be talkative at time too.<br />
<br />
== Contact Information ==<br />
:'''Name''': Eva Or<br />
:'''IRC Nick''': eor<br />
:'''Email''': evaor1012@rogers.com<br />
:'''MSN''': evaor1012@hotmail.com<br />
:'''Skype''': N/A<br />
<br />
== Leading Project ==<br />
*[[Calendar_stuff|Calendar Stuff]]<br />
<br />
*Link to Test Day wiki [http://zenit.senecac.on.ca/wiki/index.php/Calendar_TestDay here]<br />
<br />
== Other contributed project ==<br />
*[[Firefox_Performance_Testing_:_A_Python_framework_for_Windows | Performance Testing]]<br />
: I was the first two performance tester before Liz run the performance testing day.<br />
: So I ran through the documentation thoroughly, to make sure it is understandable and I have documented all the detail in the discussion page linked to the performance testing<br />
<br />
*[[Functional_Testing | Functional Testing]]<br />
: I was involve in the Firefox Testday, at first I was only doing it during class. However, I feel the class time is not long enough to make a good contribution, so I went on to test the software for more hours. I stopped in the evening after I got very tired doing more testing. <br />
: liz invited me to join the functional testing project and I will have more involvement on it in the future.<br />
<br />
*[[Simple_Citation Simple | Cititation]]<br />
: For the localization, do translation for chinese traditional(zh-TW) and chinese simplified(zh-CN)<br />
<br />
*[[Mozilla_based_accessibility | Mozilla based accessibility]]<br />
: For this project, I was assigned to search thru about 100 of jingles to find the best 3 for erin to pick and we decide which one to take together. And for the Chinese component, I find pages for her to test, but encountered some difficuit at the beginning and now is solved.<br />
<br />
== Assignment 1 ==<br />
[[Eva_Assignment_1| Assignment 1]]</div>Eorhttps://wiki.cdot.senecacollege.ca/w/index.php?title=User:Eor&diff=7633User:Eor2006-12-09T00:41:51Z<p>Eor: /* Other contributed project */</p>
<hr />
<div>== Introduction ==<br />
Hi, All! I am:<br />
<br />
* In BSD 7th Semester student (Started at the very beginning of BSD)<br />
* Working part time as a BSD and CPA Tutor at The Learning Center at Seneca College<br />
* Worked as a QA during my Summer 2006 Coop<br />
* Do not have any experience on Open Source project, but find it interesting. Hopefully, can get more involvement to Open Source by the end of this term.<br />
* Not Geeky in any way, but for some reason being in programming. Usually quiet, but can be talkative at time too.<br />
<br />
== Contact Information ==<br />
:'''Name''': Eva Or<br />
:'''IRC Nick''': eor<br />
:'''Email''': evaor1012@rogers.com<br />
:'''MSN''': evaor1012@hotmail.com<br />
:'''Skype''': N/A<br />
<br />
== Leading Project ==<br />
*[[Calendar_stuff|Calendar Stuff]]<br />
<br />
*Link to Test Day wiki [http://zenit.senecac.on.ca/wiki/index.php/Calendar_TestDay here]<br />
<br />
== Other contributed project ==<br />
*[http://zenit.senecac.on.ca/wiki/index.php/Firefox_Performance_Testing_:_A_Python_framework_for_Windows Performance Testing]<br />
: I was the first two performance tester before Liz run the performance testing day.<br />
: So I ran through the documentation thoroughly, to make sure it is understandable and I have documented all the detail in the discussion page linked to the performance testing<br />
<br />
*[http://zenit.senecac.on.ca/wiki/index.php/Functional_Testing Functional Testing]<br />
: I was involve in the Firefox Testday, at first I was only doing it during class. However, I feel the class time is not long enough to make a good contribution, so I went on to test the software for more hours. I stopped in the evening after I got very tired doing more testing. <br />
: liz invited me to join the functional testing project and I will have more involvement on it in the future.<br />
<br />
*[http://zenit.senecac.on.ca/wiki/index.php/Simple_Citation Simple Cititation]<br />
: For the localization, do translation for chinese traditional(zh-TW) and chinese simplified(zh-CN)<br />
<br />
== Assignment 1 ==<br />
[[Eva_Assignment_1| Assignment 1]]</div>Eorhttps://wiki.cdot.senecacollege.ca/w/index.php?title=User:Eor&diff=7407User:Eor2006-12-06T17:27:21Z<p>Eor: /* Other contributed project */</p>
<hr />
<div>== Introduction ==<br />
Hi, All! I am:<br />
<br />
* In BSD 7th Semester student (Started at the very beginning of BSD)<br />
* Working part time as a BSD and CPA Tutor at The Learning Center at Seneca College<br />
* Worked as a QA during my Summer 2006 Coop<br />
* Do not have any experience on Open Source project, but find it interesting. Hopefully, can get more involvement to Open Source by the end of this term.<br />
* Not Geeky in any way, but for some reason being in programming. Usually quiet, but can be talkative at time too.<br />
<br />
== Contact Information ==<br />
:'''Name''': Eva Or<br />
:'''IRC Nick''': eor<br />
:'''Email''': evaor1012@rogers.com<br />
:'''MSN''': evaor1012@hotmail.com<br />
:'''Skype''': N/A<br />
<br />
== Leading Project ==<br />
*[[Calendar_stuff|Calendar Stuff]]<br />
<br />
*Link to Test Day wiki [http://zenit.senecac.on.ca/wiki/index.php/Calendar_TestDay here]<br />
<br />
== Other contributed project ==<br />
*[http://zenit.senecac.on.ca/wiki/index.php/Firefox_Performance_Testing_:_A_Python_framework_for_Windows Performance Testing]<br />
: I was the first two performance tester before Liz run the performance testing day.<br />
: So I ran through the documentation thoroughly, to make sure it is understandable and I have documented all the detail in the discussion page linked to the performance testing<br />
<br />
*[http://zenit.senecac.on.ca/wiki/index.php/Functional_Testing Functional Testing]<br />
: I was involve in the Firefox Testday, at first I was only doing it during class. However, I feel the class time is not long enough to make a good contribution, so I went on to test the software for more hours. I stopped in the evening after I got very tired doing more testing. <br />
: liz invited me to join the functional testing project and I will have more involvement on it in the future.<br />
<br />
*[http://zenit.senecac.on.ca/wiki/index.php/Simple_Citation Simple Cititation]<br />
: Doing a chinese translation for this project<br />
<br />
== Assignment 1 ==<br />
[[Eva_Assignment_1| Assignment 1]]</div>Eorhttps://wiki.cdot.senecacollege.ca/w/index.php?title=User:Eor&diff=7404User:Eor2006-12-06T17:25:05Z<p>Eor: /* Other contributed project */</p>
<hr />
<div>== Introduction ==<br />
Hi, All! I am:<br />
<br />
* In BSD 7th Semester student (Started at the very beginning of BSD)<br />
* Working part time as a BSD and CPA Tutor at The Learning Center at Seneca College<br />
* Worked as a QA during my Summer 2006 Coop<br />
* Do not have any experience on Open Source project, but find it interesting. Hopefully, can get more involvement to Open Source by the end of this term.<br />
* Not Geeky in any way, but for some reason being in programming. Usually quiet, but can be talkative at time too.<br />
<br />
== Contact Information ==<br />
:'''Name''': Eva Or<br />
:'''IRC Nick''': eor<br />
:'''Email''': evaor1012@rogers.com<br />
:'''MSN''': evaor1012@hotmail.com<br />
:'''Skype''': N/A<br />
<br />
== Leading Project ==<br />
*[[Calendar_stuff|Calendar Stuff]]<br />
<br />
*Link to Test Day wiki [http://zenit.senecac.on.ca/wiki/index.php/Calendar_TestDay here]<br />
<br />
== Other contributed project ==<br />
*[Performance Testing]<br />
: I was the first two performance tester before Liz run the performance testing day.<br />
: So I ran through the documentation thoroughly, to make sure it is understandable and I have documented all the detail in the discussion page linked to the performance testing<br />
<br />
*[Functional Testing]<br />
: I was involve in the Firefox Testday, at first I was only doing it during class. However, I feel the class time is not long enough to make a good contribution, so I went on to test the software for more hours. I stopped in the evening after I got very tired doing more testing. <br />
: liz invited me to join the functional testing project and I will have more involvement on it in the future.<br />
<br />
*[Simple Cititation]<br />
: Doing a chinese translation for this project<br />
<br />
== Assignment 1 ==<br />
[[Eva_Assignment_1| Assignment 1]]</div>Eorhttps://wiki.cdot.senecacollege.ca/w/index.php?title=User:Eor&diff=7398User:Eor2006-12-06T17:20:44Z<p>Eor: /* Project */</p>
<hr />
<div>== Introduction ==<br />
Hi, All! I am:<br />
<br />
* In BSD 7th Semester student (Started at the very beginning of BSD)<br />
* Working part time as a BSD and CPA Tutor at The Learning Center at Seneca College<br />
* Worked as a QA during my Summer 2006 Coop<br />
* Do not have any experience on Open Source project, but find it interesting. Hopefully, can get more involvement to Open Source by the end of this term.<br />
* Not Geeky in any way, but for some reason being in programming. Usually quiet, but can be talkative at time too.<br />
<br />
== Contact Information ==<br />
:'''Name''': Eva Or<br />
:'''IRC Nick''': eor<br />
:'''Email''': evaor1012@rogers.com<br />
:'''MSN''': evaor1012@hotmail.com<br />
:'''Skype''': N/A<br />
<br />
== Leading Project ==<br />
*[[Calendar_stuff|Calendar Stuff]]<br />
<br />
*Link to Test Day wiki [http://zenit.senecac.on.ca/wiki/index.php/Calendar_TestDay here]<br />
<br />
== Other contributed project ==<br />
*[Performance Testing]<br />
: I was the first two performance tester before Liz run the performance testing day.<br />
: So I ran through the documentation thoroughly, to make sure it is understandable and I have documented all the detail in the discussion page linked to the performance testing<br />
<br />
*[Functional Testing]<br />
: <br />
*[Simple Cititation]<br />
<br />
== Assignment 1 ==<br />
[[Eva_Assignment_1| Assignment 1]]</div>Eorhttps://wiki.cdot.senecacollege.ca/w/index.php?title=User:Eor&diff=7176User:Eor2006-12-01T15:13:33Z<p>Eor: /* Project */</p>
<hr />
<div>== Introduction ==<br />
Hi, All! I am:<br />
<br />
* In BSD 7th Semester student (Started at the very beginning of BSD)<br />
* Working part time as a BSD and CPA Tutor at The Learning Center at Seneca College<br />
* Worked as a QA during my Summer 2006 Coop<br />
* Do not have any experience on Open Source project, but find it interesting. Hopefully, can get more involvement to Open Source by the end of this term.<br />
* Not Geeky in any way, but for some reason being in programming. Usually quiet, but can be talkative at time too.<br />
<br />
== Contact Information ==<br />
:'''Name''': Eva Or<br />
:'''IRC Nick''': eor<br />
:'''Email''': evaor1012@rogers.com<br />
:'''MSN''': evaor1012@hotmail.com<br />
:'''Skype''': N/A<br />
<br />
== Project ==<br />
*Project Leader in [[Calendar_stuff|Calendar Stuff]]<br />
<br />
<br />
*Link to Test Day wiki [http://zenit.senecac.on.ca/wiki/index.php/Calendar_TestDay here]<br />
<br />
== Assignment 1 ==<br />
[[Eva_Assignment_1| Assignment 1]]</div>Eorhttps://wiki.cdot.senecacollege.ca/w/index.php?title=User:Eor&diff=7175User:Eor2006-12-01T15:04:12Z<p>Eor: /* Project */</p>
<hr />
<div>== Introduction ==<br />
Hi, All! I am:<br />
<br />
* In BSD 7th Semester student (Started at the very beginning of BSD)<br />
* Working part time as a BSD and CPA Tutor at The Learning Center at Seneca College<br />
* Worked as a QA during my Summer 2006 Coop<br />
* Do not have any experience on Open Source project, but find it interesting. Hopefully, can get more involvement to Open Source by the end of this term.<br />
* Not Geeky in any way, but for some reason being in programming. Usually quiet, but can be talkative at time too.<br />
<br />
== Contact Information ==<br />
:'''Name''': Eva Or<br />
:'''IRC Nick''': eor<br />
:'''Email''': evaor1012@rogers.com<br />
:'''MSN''': evaor1012@hotmail.com<br />
:'''Skype''': N/A<br />
<br />
== Project ==<br />
Project Leader in [[Calendar_stuff|Calendar Stuff]]<br />
Link to Test Day wiki [http://zenit.senecac.on.ca/wiki/index.php/Calendar_TestDay here]<br />
<br />
== Assignment 1 ==<br />
[[Eva_Assignment_1| Assignment 1]]</div>Eorhttps://wiki.cdot.senecacollege.ca/w/index.php?title=Mozilla.dev.apps.thunderbird&diff=7153Mozilla.dev.apps.thunderbird2006-12-01T04:07:01Z<p>Eor: /* Weekly Summaries */</p>
<hr />
<div>== Newsgroup ==<br />
<br />
[http://groups.google.com/group/mozilla.dev.apps.thunderbird?lnk=srg&hl=en mozilla.dev.apps.thunderbird]<br />
<br />
== Authors ==<br />
<br />
# [[User:eor|Eva Or]]<br />
# [[User:melz|Melissa Peh]]<br />
<br />
== Weekly Summaries ==<br />
<br />
# [http://developer.mozilla.org/en/docs/Newsgroup_summaries:mozilla-dev-apps-thunderbird:2006-09-29 Friday September 29, 2006]<br />
# [http://developer.mozilla.org/en/docs/Newsgroup_summaries:mozilla-dev-apps-thunderbird:2006-10-06 Friday October 6, 2006]<br />
# [http://developer.mozilla.org/en/docs/Newsgroup_summaries:mozilla-dev-apps-thunderbird:2006-10-13 Friday October 13, 2006]<br />
# [http://developer.mozilla.org/en/docs/Newsgroup_summaries:mozilla-dev-apps-thunderbird:2006-10-20 Friday October 20, 2006]<br />
# [http://developer.mozilla.org/en/docs/Newsgroup_summaries:mozilla-dev-apps-thunderbird:2006-10-27 Friday October 27, 2006]<br />
# [http://developer.mozilla.org/en/docs/Newsgroup_summaries:mozilla-dev-apps-thunderbird:2006-11-03 Friday November 03, 2006]<br />
# [http://developer.mozilla.org/en/docs/Newsgroup_summaries:mozilla-dev-apps-thunderbird:2006-11-10 Friday November 10, 2006]<br />
# [http://developer.mozilla.org/en/docs/Newsgroup_summaries:mozilla-dev-apps-thunderbird:2006-11-17 Friday November 17, 2006]<br />
# [http://developer.mozilla.org/en/docs/Newsgroup_summaries:mozilla-dev-apps-thunderbird:2006-11-24 Friday November 24, 2006]<br />
# [http://developer.mozilla.org/en/docs/Newsgroup_summaries:mozilla-dev-apps-thunderbird:2006-12-01 Friday December 01, 2006]<br />
# [[thunderbirdnews_01122006 |Friday December 08, 2006]]<br />
# ...<br />
<br />
== FAQ ==<br />
<br />
1. How do I create my summary page?<br />
<br />
Like this!<br />
<br />
2. Should I put the FAQ questions/answers in the summaries?<br />
<br />
No. Put them in a single place (here), instead of in the summaries.</div>Eorhttps://wiki.cdot.senecacollege.ca/w/index.php?title=Mozilla.dev.apps.thunderbird&diff=7152Mozilla.dev.apps.thunderbird2006-12-01T04:06:49Z<p>Eor: /* Weekly Summaries */</p>
<hr />
<div>== Newsgroup ==<br />
<br />
[http://groups.google.com/group/mozilla.dev.apps.thunderbird?lnk=srg&hl=en mozilla.dev.apps.thunderbird]<br />
<br />
== Authors ==<br />
<br />
# [[User:eor|Eva Or]]<br />
# [[User:melz|Melissa Peh]]<br />
<br />
== Weekly Summaries ==<br />
<br />
# [http://developer.mozilla.org/en/docs/Newsgroup_summaries:mozilla-dev-apps-thunderbird:2006-09-29 Friday September 29, 2006]<br />
# [http://developer.mozilla.org/en/docs/Newsgroup_summaries:mozilla-dev-apps-thunderbird:2006-10-06 Friday October 6, 2006]<br />
# [http://developer.mozilla.org/en/docs/Newsgroup_summaries:mozilla-dev-apps-thunderbird:2006-10-13 Friday October 13, 2006]<br />
# [http://developer.mozilla.org/en/docs/Newsgroup_summaries:mozilla-dev-apps-thunderbird:2006-10-20 Friday October 20, 2006]<br />
# [http://developer.mozilla.org/en/docs/Newsgroup_summaries:mozilla-dev-apps-thunderbird:2006-10-27 Friday October 27, 2006]<br />
# [http://developer.mozilla.org/en/docs/Newsgroup_summaries:mozilla-dev-apps-thunderbird:2006-11-03 Friday November 03, 2006]<br />
# [http://developer.mozilla.org/en/docs/Newsgroup_summaries:mozilla-dev-apps-thunderbird:2006-11-10 Friday November 10, 2006]<br />
# [http://developer.mozilla.org/en/docs/Newsgroup_summaries:mozilla-dev-apps-thunderbird:2006-11-17 Friday November 17, 2006]<br />
# [http://developer.mozilla.org/en/docs/Newsgroup_summaries:mozilla-dev-apps-thunderbird:2006-11-24 Friday November 24, 2006]<br />
# [http://developer.mozilla.org/en/docs/Newsgroup_summaries:mozilla-dev-apps-thunderbird:2006-12-01Friday December 01, 2006]<br />
# [[thunderbirdnews_01122006 |Friday December 08, 2006]]<br />
# ...<br />
<br />
== FAQ ==<br />
<br />
1. How do I create my summary page?<br />
<br />
Like this!<br />
<br />
2. Should I put the FAQ questions/answers in the summaries?<br />
<br />
No. Put them in a single place (here), instead of in the summaries.</div>Eorhttps://wiki.cdot.senecacollege.ca/w/index.php?title=November_29,_2006_Test_Day/List_of_participants&diff=6988November 29, 2006 Test Day/List of participants2006-11-29T17:26:56Z<p>Eor: /* Test day participants */</p>
<hr />
<div>=Test day participants=<br />
<br />
*[[User:Mylau | Mike Lau]]<br />
*[[User:elichak | Liz Chak]]<br />
*[[User:Sminchel | Sara Minchella]]<br />
*[[User:eor | Eva Or]]</div>Eorhttps://wiki.cdot.senecacollege.ca/w/index.php?title=Talk:Firefox_Performance_Testing_:_A_Python_framework_for_Windows_Documentation&diff=6980Talk:Firefox Performance Testing : A Python framework for Windows Documentation2006-11-29T17:17:22Z<p>Eor: </p>
<hr />
<div>Eva Comment on the documentation<br />
*Do I need to read the Readme.txt by Annie Sullivan? It didn’t specify? Are you putting an assumption there? If you are not assuming the user already read the text file, tell them to read it first.<br />
<br />
*“The scripts all run from Python 2.4. You will need the windows version (not the cygwin version).” When I clicked on the link, it sent me to download right away. Should I be testing this using IE instead? I was wondering why you make that notice when I don’t even have to pick. If you are worry other people want to find their download and make sure that they got the right version. Specify that too. <br />
<br />
*???For Python Win32 Extensions installation, I noticed this is an extension for Python 2.4 that I downloaded earlier. So does it has to be located in the same directory as the Python 2.4? Does the installer check rather or not u have the python already? If it check, so is that mean it will put the extension in where the python is for sure? I just want to make sure these. If those thing are not sure, I think you might want to consider telling the user to make sure the extension is located here Python 2.4 is. <br />
<br />
*For the Config, I think you should tell he user to GO TO those path to see if the necessary item exists with the same path or not. If not Fix the path. For example, I have a PerformanceTesting directory in between mozilla and testing directory. In my case, I either remove the PerformanceTesting directory or add PermanceTesting to my path.<br />
<br />
*CAUTION: This is where I hit the part I must ask you question to keep going<br />
::For firefox: C:\Program Files\Mozilla Firefox 2 Beta 1\firefox.exe<br />
::in the config.yaml. I do not have Mozilla Firefox 2 Beta 1, I only have Mozilla Firefox. In that case, should I change my path or should I download the version you have. In your instruction you just said check that your firefox path is right. You didn’t say what to do if it is not right.<br />
<br />
*Instruction 5. didn’t mention use what to run the run_test.py file? Cmd or cygwin?<br />
*How long the after you run the test should be mention. 10 – 15mins depends on the processor speed. <br />
<br />
*In your page, it didn’t mention how to handle error or problem encounter, if you have mentioned this in separate page, aren’t you suppose to have a link somewhere for that? Because if I got that problem I will not be able to continue and I might not know what to do to finish the performance testing.</div>Eorhttps://wiki.cdot.senecacollege.ca/w/index.php?title=Talk:Firefox_Performance_Testing_:_A_Python_framework_for_Windows_Documentation&diff=6979Talk:Firefox Performance Testing : A Python framework for Windows Documentation2006-11-29T17:17:07Z<p>Eor: </p>
<hr />
<div>Eva Comment on the documentation<br />
*Do I need to read the Readme.txt by Annie Sullivan? It didn’t specify? Are you putting an assumption there? If you are not assuming the user already read the text file, tell them to read it first.<br />
<br />
*“The scripts all run from Python 2.4. You will need the windows version (not the cygwin version).” When I clicked on the link, it sent me to download right away. Should I be testing this using IE instead? I was wondering why you make that notice when I don’t even have to pick. If you are worry other people want to find their download and make sure that they got the right version. Specify that too. <br />
<br />
*???For Python Win32 Extensions installation, I noticed this is an extension for Python 2.4 that I downloaded earlier. So does it has to be located in the same directory as the Python 2.4? Does the installer check rather or not u have the python already? If it check, so is that mean it will put the extension in where the python is for sure? I just want to make sure these. If those thing are not sure, I think you might want to consider telling the user to make sure the extension is located here Python 2.4 is. <br />
<br />
*For the Config, I think you should tell he user to GO TO those path to see if the necessary item exists with the same path or not. If not Fix the path. For example, I have a PerformanceTesting directory in between mozilla and testing directory. In my case, I either remove the PerformanceTesting directory or add PermanceTesting to my path.<br />
<br />
*CAUTION: This is where I hit the part I must ask you question to keep going<br />
::For firefox: C:\Program Files\Mozilla Firefox 2 Beta 1\firefox.exe<br />
in the config.yaml. I do not have Mozilla Firefox 2 Beta 1, I only have Mozilla Firefox. In that case, should I change my path or should I download the version you have. In your instruction you just said check that your firefox path is right. You didn’t say what to do if it is not right.<br />
<br />
*Instruction 5. didn’t mention use what to run the run_test.py file? Cmd or cygwin?<br />
*How long the after you run the test should be mention. 10 – 15mins depends on the processor speed. <br />
<br />
*In your page, it didn’t mention how to handle error or problem encounter, if you have mentioned this in separate page, aren’t you suppose to have a link somewhere for that? Because if I got that problem I will not be able to continue and I might not know what to do to finish the performance testing.</div>Eorhttps://wiki.cdot.senecacollege.ca/w/index.php?title=Talk:Firefox_Performance_Testing_:_A_Python_framework_for_Windows_Documentation&diff=6976Talk:Firefox Performance Testing : A Python framework for Windows Documentation2006-11-29T17:16:33Z<p>Eor: </p>
<hr />
<div>Eva Comment on the documentation<br />
*Do I need to read the Readme.txt by Annie Sullivan? It didn’t specify? Are you putting an assumption there? If you are not assuming the user already read the text file, tell them to read it first.<br />
<br />
*“The scripts all run from Python 2.4. You will need the windows version (not the cygwin version).” When I clicked on the link, it sent me to download right away. Should I be testing this using IE instead? I was wondering why you make that notice when I don’t even have to pick. If you are worry other people want to find their download and make sure that they got the right version. Specify that too. <br />
<br />
*???For Python Win32 Extensions installation, I noticed this is an extension for Python 2.4 that I downloaded earlier. So does it has to be located in the same directory as the Python 2.4? Does the installer check rather or not u have the python already? If it check, so is that mean it will put the extension in where the python is for sure? I just want to make sure these. If those thing are not sure, I think you might want to consider telling the user to make sure the extension is located here Python 2.4 is. <br />
<br />
*For the Config, I think you should tell he user to GO TO those path to see if the necessary item exists with the same path or not. If not Fix the path. For example, I have a PerformanceTesting directory in between mozilla and testing directory. In my case, I either remove the PerformanceTesting directory or add PermanceTesting to my path.<br />
<br />
*CAUTION: This is where I hit the part I must ask you question to keep going<br />
For firefox: C:\Program Files\Mozilla Firefox 2 Beta 1\firefox.exe<br />
in the config.yaml. I do not have Mozilla Firefox 2 Beta 1, I only have Mozilla Firefox. In that case, should I change my path or should I download the version you have. In your instruction you just said check that your firefox path is right. You didn’t say what to do if it is not right.<br />
<br />
*Instruction 5. didn’t mention use what to run the run_test.py file? Cmd or cygwin?<br />
*How long the after you run the test should be mention. 10 – 15mins depends on the processor speed. <br />
<br />
*In your page, it didn’t mention how to handle error or problem encounter, if you have mentioned this in separate page, aren’t you suppose to have a link somewhere for that? Because if I got that problem I will not be able to continue and I might not know what to do to finish the performance testing.</div>Eorhttps://wiki.cdot.senecacollege.ca/w/index.php?title=Thunderbird_TestDay&diff=6520Thunderbird TestDay2006-11-24T14:10:28Z<p>Eor: /* Preparation */</p>
<hr />
<div>[[Calendar_stuff | Back to Calendar project page]]<br />
<br />
== Time and Location ==<br />
<br />
Friday, Dec 1, 2006 at 11:40 EST at Rm???. <br />
<br />
Duration : 2 hours<br />
<br />
== Preparation ==<br />
<br />
Everyone who want to contribute to this project must sign up for an Bugzilla account and email your user id to Eva at yeor@learn.senecac.on.ca 2 days priors to the event. This is for the Calendar QA's to assign us the Canconfirm privilege. <br />
<br />
This event host as a competition, the calendar QA team will announce a winner who contributes the most to this event. Prize will be given to the winner. <br />
<br />
Hence, how can you prepare yourself for this event? First of all, you will need to get familar with Bugzilla. We will not be using litmus in this event. This [http://developer.mozilla.org/en/docs/What_to_do_and_what_not_to_do_in_Bugzilla link] is a documentation on what to do an what not to do in bugzilla.<br />
<br />
Calendar QA goal is to clean out the bugzilla backlog so new functionality can be test soon. Therefore, they need to:<br />
<br />
::* Confirm unconfirmed bugs - ensure that the bugs are reproducible and not duplicates of known issues. A documented guide is provide in this [http://www.mozilla.org/quality/help/unconfirmed.html link].<br />
<br />
::* Verify existing fixed - ensure that the fixes did fix the problem in the bug report and did not cause other regressions. In this case, you need to how the find the bugs that is fixed and how to change its status after you verified it.<br />
<br />
::* Investigate on defects that are flagged as QAWanted. provide more details, analysis, and clearer or simpler steps to reproduce the issue.<br />
<br />
[http://wiki.mozilla.org/Calendar:QA_TestDay:2006-10-31#Testing_Instructions Here] is a previous Calendar Test Day example</div>Eorhttps://wiki.cdot.senecacollege.ca/w/index.php?title=Thunderbird_TestDay&diff=6513Thunderbird TestDay2006-11-24T05:12:14Z<p>Eor: /* Time and Location */</p>
<hr />
<div>[[Calendar_stuff | Back to Calendar project page]]<br />
<br />
== Time and Location ==<br />
<br />
Friday, Dec 1, 2006 at 11:40 EST at Rm???. <br />
<br />
Duration : 2 hours<br />
<br />
== Preparation ==<br />
<br />
Everyone who want to contribute to this project must sign up for an Bugzilla account and email your user id to Eva at yeor@learn.senecac.on.ca 2 days priors to the event. <br />
<br />
This event host as a competition, the calendar QA team will announce a winner who contributes the most to this event. Prize will be given to the winner. <br />
<br />
Hence, how can you prepare yourself for this event? First of all, you will need to get familar with Bugzilla. We will not be using litmus in this event. This [http://developer.mozilla.org/en/docs/What_to_do_and_what_not_to_do_in_Bugzilla link] is a documentation on what to do an what not to do in bugzilla.<br />
<br />
Calendar QA goal is to clean out the bugzilla backlog so new functionality can be test soon. Therefore, they need to:<br />
<br />
::* Confirm unconfirmed bugs - ensure that the bugs are reproducible and not duplicates of known issues. A documented guide is provide in this [http://www.mozilla.org/quality/help/unconfirmed.html link].<br />
<br />
::* Verify existing fixed - ensure that the fixes did fix the problem in the bug report and did not cause other regressions. In this case, you need to how the find the bugs that is fixed and how to change its status after you verified it.<br />
<br />
::* Investigate on defects that are flagged as QAWanted. provide more details, analysis, and clearer or simpler steps to reproduce the issue.<br />
<br />
[http://wiki.mozilla.org/Calendar:QA_TestDay:2006-10-31#Testing_Instructions Here] is a previous Calendar Test Day example</div>Eorhttps://wiki.cdot.senecacollege.ca/w/index.php?title=Thunderbird_TestDay&diff=6512Thunderbird TestDay2006-11-24T05:11:42Z<p>Eor: </p>
<hr />
<div>[[Calendar_stuff | Back to Calendar project page]]<br />
<br />
== Time and Location ==<br />
<br />
Friday, Dec 1, 2006 at 11:40 EST at Rm. <br />
<br />
Duration : 2 hours<br />
<br />
<br />
== Preparation ==<br />
<br />
Everyone who want to contribute to this project must sign up for an Bugzilla account and email your user id to Eva at yeor@learn.senecac.on.ca 2 days priors to the event. <br />
<br />
This event host as a competition, the calendar QA team will announce a winner who contributes the most to this event. Prize will be given to the winner. <br />
<br />
Hence, how can you prepare yourself for this event? First of all, you will need to get familar with Bugzilla. We will not be using litmus in this event. This [http://developer.mozilla.org/en/docs/What_to_do_and_what_not_to_do_in_Bugzilla link] is a documentation on what to do an what not to do in bugzilla.<br />
<br />
Calendar QA goal is to clean out the bugzilla backlog so new functionality can be test soon. Therefore, they need to:<br />
<br />
::* Confirm unconfirmed bugs - ensure that the bugs are reproducible and not duplicates of known issues. A documented guide is provide in this [http://www.mozilla.org/quality/help/unconfirmed.html link].<br />
<br />
::* Verify existing fixed - ensure that the fixes did fix the problem in the bug report and did not cause other regressions. In this case, you need to how the find the bugs that is fixed and how to change its status after you verified it.<br />
<br />
::* Investigate on defects that are flagged as QAWanted. provide more details, analysis, and clearer or simpler steps to reproduce the issue.<br />
<br />
[http://wiki.mozilla.org/Calendar:QA_TestDay:2006-10-31#Testing_Instructions Here] is a previous Calendar Test Day example</div>Eorhttps://wiki.cdot.senecacollege.ca/w/index.php?title=TB_TestDay&diff=6508TB TestDay2006-11-24T04:28:57Z<p>Eor: </p>
<hr />
<div>[[Calendar_stuff | Back to Calendar project page]]<br />
== Thunderbird Test Day ==<br />
<br />
Thunderbird Test Day<br />
<br />
== Time and Location ==<br />
<br />
Friday, Dec 1, 2006 at 11:40 EST at Rm. <br />
<br />
Duration : 2 hours<br />
<br />
<br />
== Project Leader(s) ==</div>Eorhttps://wiki.cdot.senecacollege.ca/w/index.php?title=TB_TestDay&diff=6507TB TestDay2006-11-24T04:19:06Z<p>Eor: </p>
<hr />
<div>[[Calendar_stuff | Back to Calendar project page]<br />
== Thunderbird Test Day ==<br />
<br />
Thunderbird Test Day<br />
<br />
== Time and Location ==<br />
<br />
Friday, Dec 1, 2006 at 11:40 EST at Rm. <br />
<br />
Duration : 2 hours<br />
<br />
<br />
== Project Leader(s) ==</div>Eorhttps://wiki.cdot.senecacollege.ca/w/index.php?title=Mozilla.dev.apps.thunderbird&diff=5883Mozilla.dev.apps.thunderbird2006-11-03T19:11:48Z<p>Eor: /* Weekly Summaries */</p>
<hr />
<div>== Newsgroup ==<br />
<br />
[http://groups.google.com/group/mozilla.dev.apps.thunderbird?lnk=srg&hl=en mozilla.dev.apps.thunderbird]<br />
<br />
== Authors ==<br />
<br />
# [[User:eor|Eva Or]]<br />
# [[User:melz|Melissa Peh]]<br />
<br />
== Weekly Summaries ==<br />
<br />
# [http://developer.mozilla.org/en/docs/Newsgroup_summaries:mozilla-dev-apps-thunderbird:2006-09-29 Friday September 29, 2006]<br />
# [http://developer.mozilla.org/en/docs/Newsgroup_summaries:mozilla-dev-apps-thunderbird:2006-10-06 Friday October 6, 2006]<br />
# [http://developer.mozilla.org/en/docs/Newsgroup_summaries:mozilla-dev-apps-thunderbird:2006-10-13 Friday October 13, 2006]<br />
# [http://developer.mozilla.org/en/docs/Newsgroup_summaries:mozilla-dev-apps-thunderbird:2006-10-20 Friday October 20, 2006]<br />
# [http://developer.mozilla.org/en/docs/Newsgroup_summaries:mozilla-dev-apps-thunderbird:2006-10-27 Friday October 27, 2006]<br />
# [http://developer.mozilla.org/en/docs/Newsgroup_summaries:mozilla-dev-apps-thunderbird:2006-11-03#Discussions Friday November 03, 2006]<br />
# [[thunderbirdnews_03112006 |Friday November 10, 2006]]<br />
# [[thunderbirdnews_10112006 |Friday November 17, 2006]]<br />
# [[thunderbirdnews_17112006 |Friday November 24, 2006]]<br />
# [[thunderbirdnews_24112006 |Friday December 01, 2006]]<br />
# [[thunderbirdnews_01122006 |Friday December 08, 2006]]<br />
# ...<br />
<br />
== FAQ ==<br />
<br />
1. How do I create my summary page?<br />
<br />
Like this!<br />
<br />
2. Should I put the FAQ questions/answers in the summaries?<br />
<br />
No. Put them in a single place (here), instead of in the summaries.</div>Eorhttps://wiki.cdot.senecacollege.ca/w/index.php?title=Mozilla.dev.apps.thunderbird&diff=5882Mozilla.dev.apps.thunderbird2006-11-03T19:11:29Z<p>Eor: /* Weekly Summaries */</p>
<hr />
<div>== Newsgroup ==<br />
<br />
[http://groups.google.com/group/mozilla.dev.apps.thunderbird?lnk=srg&hl=en mozilla.dev.apps.thunderbird]<br />
<br />
== Authors ==<br />
<br />
# [[User:eor|Eva Or]]<br />
# [[User:melz|Melissa Peh]]<br />
<br />
== Weekly Summaries ==<br />
<br />
# [http://developer.mozilla.org/en/docs/Newsgroup_summaries:mozilla-dev-apps-thunderbird:2006-09-29 Friday September 29, 2006]<br />
# [http://developer.mozilla.org/en/docs/Newsgroup_summaries:mozilla-dev-apps-thunderbird:2006-10-06 Friday October 6, 2006]<br />
# [http://developer.mozilla.org/en/docs/Newsgroup_summaries:mozilla-dev-apps-thunderbird:2006-10-13 Friday October 13, 2006]<br />
# [http://developer.mozilla.org/en/docs/Newsgroup_summaries:mozilla-dev-apps-thunderbird:2006-10-20 Friday October 20, 2006]<br />
# [http://developer.mozilla.org/en/docs/Newsgroup_summaries:mozilla-dev-apps-thunderbird:2006-10-27 Friday October 27, 2006]<br />
# [[http://developer.mozilla.org/en/docs/Newsgroup_summaries:mozilla-dev-apps-thunderbird:2006-11-03#Discussions Friday November 03, 2006]]<br />
# [[thunderbirdnews_03112006 |Friday November 10, 2006]]<br />
# [[thunderbirdnews_10112006 |Friday November 17, 2006]]<br />
# [[thunderbirdnews_17112006 |Friday November 24, 2006]]<br />
# [[thunderbirdnews_24112006 |Friday December 01, 2006]]<br />
# [[thunderbirdnews_01122006 |Friday December 08, 2006]]<br />
# ...<br />
<br />
== FAQ ==<br />
<br />
1. How do I create my summary page?<br />
<br />
Like this!<br />
<br />
2. Should I put the FAQ questions/answers in the summaries?<br />
<br />
No. Put them in a single place (here), instead of in the summaries.</div>Eorhttps://wiki.cdot.senecacollege.ca/w/index.php?title=Mozilla.dev.apps.thunderbird&diff=5464Mozilla.dev.apps.thunderbird2006-10-21T02:51:50Z<p>Eor: /* Weekly Summaries */</p>
<hr />
<div>== Newsgroup ==<br />
<br />
[http://groups.google.com/group/mozilla.dev.apps.thunderbird?lnk=srg&hl=en mozilla.dev.apps.thunderbird]<br />
<br />
== Authors ==<br />
<br />
# [[User:eor|Eva Or]]<br />
# [[User:melz|Melissa Peh]]<br />
<br />
== Weekly Summaries ==<br />
<br />
# [http://developer.mozilla.org/en/docs/Newsgroup_summaries:mozilla-dev-apps-thunderbird:2006-09-29 Friday September 29, 2006]<br />
# [http://developer.mozilla.org/en/docs/Newsgroup_summaries:mozilla-dev-apps-thunderbird:2006-10-06 Friday October 6, 2006]<br />
# [http://developer.mozilla.org/en/docs/Newsgroup_summaries:mozilla-dev-apps-thunderbird:2006-10-13 Friday October 13, 2006]<br />
# [http://developer.mozilla.org/en/docs/Newsgroup_summaries:mozilla-dev-apps-thunderbird:2006-10-20#Summary:_mozilla.dev.apps.thunderbird_-_October_14-20.2C_2006 Friday October 20, 2006]<br />
# [[thunderbirdnews_20102006 |Friday October 27, 2006]]<br />
# [[thunderbirdnews_27102006 |Friday November 03, 2006]]<br />
# [[thunderbirdnews_03112006 |Friday November 10, 2006]]<br />
# [[thunderbirdnews_10112006 |Friday November 17, 2006]]<br />
# [[thunderbirdnews_17112006 |Friday November 24, 2006]]<br />
# [[thunderbirdnews_24112006 |Friday December 01, 2006]]<br />
# [[thunderbirdnews_01122006 |Friday December 08, 2006]]<br />
# ...<br />
<br />
== FAQ ==<br />
<br />
1. How do I create my summary page?<br />
<br />
Like this!<br />
<br />
2. Should I put the FAQ questions/answers in the summaries?<br />
<br />
No. Put them in a single place (here), instead of in the summaries.</div>Eorhttps://wiki.cdot.senecacollege.ca/w/index.php?title=Mozilla.dev.apps.thunderbird&diff=5192Mozilla.dev.apps.thunderbird2006-10-13T16:12:37Z<p>Eor: /* Weekly Summaries */</p>
<hr />
<div>== Newsgroup ==<br />
<br />
[http://groups.google.com/group/mozilla.dev.apps.thunderbird?lnk=srg&hl=en mozilla.dev.apps.thunderbird]<br />
<br />
== Authors ==<br />
<br />
# [[User:eor|Eva Or]]<br />
# [[User:melz|Melissa Peh]]<br />
<br />
== Weekly Summaries ==<br />
<br />
# [http://developer.mozilla.org/en/docs/Newsgroup_summaries:mozilla-dev-apps-thunderbird:2006-09-29 Friday September 29, 2006]<br />
# [http://developer.mozilla.org/en/docs/Newsgroup_summaries:mozilla-dev-apps-thunderbird:2006-10-06 Friday October 6, 2006]<br />
# [http://developer.mozilla.org/en/docs/Newsgroup_summaries:mozilla-dev-apps-thunderbird:2006-10-13 Friday October 13, 2006]<br />
# [[thunderbirdnews_13102006 |Friday October 20, 2006]]<br />
# [[thunderbirdnews_20102006 |Friday October 27, 2006]]<br />
# [[thunderbirdnews_27102006 |Friday November 03, 2006]]<br />
# [[thunderbirdnews_03112006 |Friday November 10, 2006]]<br />
# [[thunderbirdnews_10112006 |Friday November 17, 2006]]<br />
# [[thunderbirdnews_17112006 |Friday November 24, 2006]]<br />
# [[thunderbirdnews_24112006 |Friday December 01, 2006]]<br />
# [[thunderbirdnews_01122006 |Friday December 08, 2006]]<br />
# ...<br />
<br />
== FAQ ==<br />
<br />
1. How do I create my summary page?<br />
<br />
Like this!<br />
<br />
2. Should I put the FAQ questions/answers in the summaries?<br />
<br />
No. Put them in a single place (here), instead of in the summaries.</div>Eorhttps://wiki.cdot.senecacollege.ca/w/index.php?title=Mozilla.dev.apps.thunderbird&diff=5191Mozilla.dev.apps.thunderbird2006-10-13T16:12:16Z<p>Eor: /* Weekly Summaries */</p>
<hr />
<div>== Newsgroup ==<br />
<br />
[http://groups.google.com/group/mozilla.dev.apps.thunderbird?lnk=srg&hl=en mozilla.dev.apps.thunderbird]<br />
<br />
== Authors ==<br />
<br />
# [[User:eor|Eva Or]]<br />
# [[User:melz|Melissa Peh]]<br />
<br />
== Weekly Summaries ==<br />
<br />
# [http://developer.mozilla.org/en/docs/Newsgroup_summaries:mozilla-dev-apps-thunderbird:2006-09-29 Friday September 29, 2006]<br />
# [http://developer.mozilla.org/en/docs/Newsgroup_summaries:mozilla-dev-apps-thunderbird:2006-10-06 Friday October 6, 2006]<br />
# [http://developer.mozilla.org/en/docs/Newsgroup_summaries:mozilla-dev-apps-thunderbird:2006-10-13 Friday October 6, 2006]<br />
# [[thunderbirdnews_13102006 |Friday October 20, 2006]]<br />
# [[thunderbirdnews_20102006 |Friday October 27, 2006]]<br />
# [[thunderbirdnews_27102006 |Friday November 03, 2006]]<br />
# [[thunderbirdnews_03112006 |Friday November 10, 2006]]<br />
# [[thunderbirdnews_10112006 |Friday November 17, 2006]]<br />
# [[thunderbirdnews_17112006 |Friday November 24, 2006]]<br />
# [[thunderbirdnews_24112006 |Friday December 01, 2006]]<br />
# [[thunderbirdnews_01122006 |Friday December 08, 2006]]<br />
# ...<br />
<br />
== FAQ ==<br />
<br />
1. How do I create my summary page?<br />
<br />
Like this!<br />
<br />
2. Should I put the FAQ questions/answers in the summaries?<br />
<br />
No. Put them in a single place (here), instead of in the summaries.</div>Eorhttps://wiki.cdot.senecacollege.ca/w/index.php?title=Mozilla.dev.apps.thunderbird&diff=4817Mozilla.dev.apps.thunderbird2006-10-06T14:59:03Z<p>Eor: /* Weekly Summaries */</p>
<hr />
<div>== Newsgroup ==<br />
<br />
[http://groups.google.com/group/mozilla.dev.apps.thunderbird?lnk=srg&hl=en mozilla.dev.apps.thunderbird]<br />
<br />
== Authors ==<br />
<br />
# [[User:eor|Eva Or]]<br />
# [[User:melz|Melissa Peh]]<br />
<br />
== Weekly Summaries ==<br />
<br />
'''NOTE''': these should be turned into links to separate pages.<br />
<br />
# [http://developer.mozilla.org/en/docs/Newsgroup_summaries:mozilla-dev-apps-thunderbird:2006-09-29 Friday September 22, 2006]<br />
# [http://developer.mozilla.org/en/docs/Newsgroup_summaries:mozilla-dev-apps-thunderbird:2006-10-06 Friday September 29, 2006]<br />
# [[thunderbirdnews_06102006 |Friday October 6, 2006]]<br />
# [[thunderbirdnews_13102006 |Friday October 13, 2006]]<br />
# [[thunderbirdnews_20102006 |Friday October 20, 2006]]<br />
# [[thunderbirdnews_27102006 |Friday October 27, 2006]]<br />
# [[thunderbirdnews_03112006 |Friday November 03, 2006]]<br />
# [[thunderbirdnews_10112006 |Friday November 10, 2006]]<br />
# [[thunderbirdnews_17112006 |Friday November 17, 2006]]<br />
# [[thunderbirdnews_24112006 |Friday November 24, 2006]]<br />
# [[thunderbirdnews_01122006 |Friday December 01, 2006]]<br />
# [[thunderbirdnews_08122006 |Friday December 08, 2006]]<br />
# ...<br />
<br />
== FAQ ==<br />
<br />
1. How do I create my summary page?<br />
<br />
Like this!<br />
<br />
2. Should I put the FAQ questions/answers in the summaries?<br />
<br />
No. Put them in a single place (here), instead of in the summaries.</div>Eorhttps://wiki.cdot.senecacollege.ca/w/index.php?title=Chrome&diff=4811Chrome2006-10-06T14:41:39Z<p>Eor: </p>
<hr />
<div>=What is Chrome?=<br />
In a nutshell, Chrome is the user interface of Mozilla products. The user interface is composed mostly of [[XUL]], [[XBL]], CSS, and JS files. (You can make changes to these files without needing to recompile the Mozilla project you're working on - which is an enormous timesaver, especially for people who are just starting out on Mozilla-based development). <br />
<br />
If you look in the chrome subdirectory of your installation, you'll find .jar files - these contain the chrome files that make up the user interface. These jar files are actually just ZIP archives. Extensions are (usually) chrome applets. 90% of an [http://developer.mozilla.org/en/docs/Extensions extension], typically is chrome. <br />
<br />
In the XUL world, Chrome is the top level window which contains groups of UI elements of various types. Example of chrome are the browser window and dialog window. The chrome obtains its UI description from four types of providers: <br />
<br />
* Content provider<br />
::Provides the skeleton, i.e., the menus, command buttons<br />
* Skin provider<br />
::Supplies the look-and-feel of the chrome<br />
* Platform provider<br />
::Gives platform dependent UI description<br />
* Locale provider<br />
::Offers the language and culture sensitive resources<br />
<br />
=Chrome in depth=<br />
<br />
==Chrome URLs==<br />
To maximize the flexibility, Mozilla introduces a new technology called "Configurable Chrome" (Refer to [http://www.mozilla.org/xpfe/ConfigChromeSpec.html Configurable Chrome] by Benjamin Smedberg <benjamin@smedbergs.us>). A XUL file can be written in such a fashion that its chrome description comes from a mixture of physical sources, either locally, remotely, or a combination of both. An end user may customize her/his configuration to pick up any of the source type from his favor chrome providers.<br />
<br />
To achieve this, chrome type URLs must be used to reference external sources; such as CSS files and JavaScript files. A Chrome URL points to a file registered within the Mozilla product (it could be e-mail, calendar, browser etc.)<br />
<br />
The general form of chrome URLs look like this [Refer to [http://xulplanet.com/tutorials/xultu/chromeurl.html XULPlanet - The Chrome URL] for more details]:<br />
<br />
<pre>chrome://WindowType/ProviderType/[ProviderName/]</pre><br />
<br />
*The "WindowType" is the window type of the chrome. Possible values are "navigator", "messenger", etc. The "ProviderType" is one of the four providers: content, skin, platform, or locale. Examples of the provider names, "ProviderName", are Mozilla, Mozillazine, xyzOrg, myISP, and etc. (Refer to [http://www.mozilla.org/projects/intl/iuc15/paper/iuc15xul.html XUL - Creating Localizable XML GUI] for illustrations).<br />
<br />
==Chrome Registry==<br />
This aspect requires sufficient understanding of Chrome.<br />
<br />
Acoording to WierdAl (#developers), Firefox uses the toolkit approach: [http://developer.mozilla.org/en/docs/chrome.manifest Chrome Registration - MDC] whereas SeaMonkey uses the old way (xpfe).<br />
<br />
<br />
==Code Registry Example==<br />
<pre><br />
1. content necko jar:comm.jar!/content/necko/ xpcnativewrappers=yes<br />
2. locale necko en-US jar:en-US.jar!/locale/en-US/necko/<br />
3. content xbl-marquee jar:comm.jar!/content/xbl-marquee/<br />
4. content pipnss jar:pipnss.jar!/content/pipnss/<br />
5. locale pipnss en-US jar:en-US.jar!/locale/en-US/pipnss/<br />
6. # Firefox-only<br />
7. overlay chrome://browser/content/pageInfo.xul chrome://pippki/content/PageInfoOverlay.xul application={ec8030f7-c20a-464f-9b0e-13a3a9e97384}<br />
8. overlay chrome://communicator/content/pref/preftree.xul chrome://pippki/content/PrefOverlay.xul<br />
9. overlay chrome://navigator/content/pageInfo.xul chrome://pippki/content/PageInfoOverlay.xul application=seamonkey@applications.mozilla.org<br />
10. content pippki jar:pippki.jar!/content/pippki/ xpcnativewrappers=yes<br />
11. locale pippki en-US jar:en-US.jar!/locale/en-US/pippki/<br />
12. content global-platform jar:toolkit.jar!/content/global-platform/ platform<br />
13. skin global classic/1.0 jar:classic.jar!/skin/classic/global/<br />
14. override chrome://global/content/netError.xhtml jar:embedder.jar!/global/content/netError.xhtml<br />
15. content inspector jar:inspector.jar!/content/inspector/ xpcnativewrappers=no<br />
</pre><br />
<br />
*Line 1: <pre>content packagename uri/to/files/ [flags]</pre><br />
**This code will register the package called necko when resolving the URL jar:comm.jar!/content/necko/ with the xpcnativewrappers flag on <br />
<br />
<br />
*Line 5: <pre>locale packagename localename uri/to/files/ [flags]</pre><br />
**This code will register a locale package called pinpnss with the localename en-US when resolving the URL jar:en-US.jar!/locale/en-US/pipnss/<br />
**NOTE: If there are more than one locale file register for the package, chrome will select the best-fit locale for the URL.<br />
<br />
<br />
*Line 6: <pre># this line is a comment - you can put whatever you want here</pre><br />
**To comment your code, put '#' in the beginning of the line.<br />
<br />
<br />
*Line 7: <pre>overlay chrome://URI-to-be-overlayed chrome://overlay-URI [flags]</pre><br />
**The prupose of this code is to overlaying one chrome on top of the other. The application={ec8030f7-c20a-464f-9b0e-13a3a9e97384} is a flag that specific which application will have this overlay.<br />
<br />
<br />
*Line 13: <pre>skin packagename skinname uri/to/files/ [flags]</pre><br />
**This will register a skin package gobal with the skinname classic/1.0 when resolving the URL jar:classic.jar!/skin/classic/global/<br />
**NOTE: If more than one skin register for the package, chrome will select the best-fit skin for the URL.<br />
<br />
<br />
*Line 14: <pre>override chrome://package/type/original-uri.whatever new-resolved-URI [flags]</pre><br />
**The purpose of this is to override a chrome file provided by the application or XULRunner with a new extension or embedder.<br />
<br />
<br />
<br />
=Additional Info=<br />
<br />
==Starting Out==<br />
WierdAl in #developers said he started doing the development work by obtaining [http://www.gerv.net/software/patch-maker Gerv's Patch Maker] and looking in Bugzilla for a bug with the words "good first bug" in the Status Whiteboard. WierdAl also has a blog on his development: <br />
*[http://weblogs.mozillazine.org/weirdal/archives/cat_xul_widgets.html Burning Chrome: XUL Widgets Archives]<br />
*[http://weblogs.mozillazine.org/weirdal/archives/cat_xul_xbl_js_and_dom.html Burning Chrome: XUL, XBL, JS and DOM Archives]<br />
<br />
== Chrome Tutorials==<br />
Here are tutorials on how to create user interface parts using Chrome:<br />
*[http://developer.mozilla.org/en/docs/Creating_a_Skin_for_Mozilla:Getting_Started Create a skin for Mozilla]<br />
*[http://developer.mozilla.org/en/docs/Working_with_windows_in_chrome_code Working with windows in Chrome Code]<br />
*[http://developer.mozilla.org/en/docs/Creating_toolbar_buttons Create toolbar buttons]<br />
*[http://developer.mozilla.org/en/docs/Creating_a_Firefox_sidebar Create a Firefox sidebar]<br />
*[http://developer.mozilla.org/en/docs/XUL_Tutorial:Creating_a_Window XULTutorial: Creating a Window - MDC]<br />
*[http://www.g4tv.com/screensavers/features/41046/Create_a_Mozilla_Extension_pg3.html Create a Mozilla Extension]<br />
*[http://www.mozilla.org/unix/customizing.html Customizing Mozilla]<br />
<br />
=Resources=<br />
WierdAl in #developers<br />
<br />
[http://www.mozilla.org/projects/intl/iuc15/paper/iuc15xul.html XUL - Creating Localizable XML GUI]<br />
<br />
[http://www.mozilla.org/xpfe/ConfigChromeSpec.html Configurable Chrome ]&nbsp;&nbsp; by Benjamin Smedberg <benjamin@smedbergs.us><br />
<br />
[http://developer.mozilla.org/en/docs/Chrome_Registration Chrome Registration]<br />
<br />
http://www.mozilla.org/support/firefox/tips<br />
<br />
[http://www.xulplanet.com/tutorials/xultu/intro.html 1.1 Introduction]</div>Eorhttps://wiki.cdot.senecacollege.ca/w/index.php?title=Chrome&diff=4809Chrome2006-10-06T14:40:27Z<p>Eor: /* Chrome Registry */</p>
<hr />
<div>=What is Chrome?=<br />
In a nutshell, Chrome is the user interface of Mozilla products. The user interface is composed mostly of [[XUL]], [[XBL]], CSS, and JS files. (You can make changes to these files without needing to recompile the Mozilla project you're working on - which is an enormous timesaver, especially for people who are just starting out on Mozilla-based development). <br />
<br />
If you look in the chrome subdirectory of your installation, you'll find .jar files - these contain the chrome files that make up the user interface. These jar files are actually just ZIP archives. Extensions are (usually) chrome applets. 90% of an [http://developer.mozilla.org/en/docs/Extensions extension], typically is chrome. <br />
<br />
In the XUL world, Chrome is the top level window which contains groups of UI elements of various types. Example of chrome are the browser window and dialog window. The chrome obtains its UI description from four types of providers: <br />
<br />
* Content provider<br />
::Provides the skeleton, i.e., the menus, command buttons<br />
* Skin provider<br />
::Supplies the look-and-feel of the chrome<br />
* Platform provider<br />
::Gives platform dependent UI description<br />
* Locale provider<br />
::Offers the language and culture sensitive resources<br />
<br />
=Chrome in depth=<br />
<br />
==Chrome URLs==<br />
To maximize the flexibility, Mozilla introduces a new technology called "Configurable Chrome" (Refer to [http://www.mozilla.org/xpfe/ConfigChromeSpec.html Configurable Chrome] by Benjamin Smedberg <benjamin@smedbergs.us>). A XUL file can be written in such a fashion that its chrome description comes from a mixture of physical sources, either locally, remotely, or a combination of both. An end user may customize her/his configuration to pick up any of the source type from his favor chrome providers.<br />
<br />
To achieve this, chrome type URLs must be used to reference external sources; such as CSS files and JavaScript files. A Chrome URL points to a file registered within the Mozilla product (it could be e-mail, calendar, browser etc.)<br />
<br />
The general form of chrome URLs look like this [Refer to [http://xulplanet.com/tutorials/xultu/chromeurl.html XULPlanet - The Chrome URL] for more details]:<br />
<br />
<pre>chrome://WindowType/ProviderType/[ProviderName/]</pre><br />
<br />
*The "WindowType" is the window type of the chrome. Possible values are "navigator", "messenger", etc. The "ProviderType" is one of the four providers: content, skin, platform, or locale. Examples of the provider names, "ProviderName", are Mozilla, Mozillazine, xyzOrg, myISP, and etc. (Refer to [http://www.mozilla.org/projects/intl/iuc15/paper/iuc15xul.html XUL - Creating Localizable XML GUI] for illustrations).<br />
<br />
==Chrome Registry==<br />
This aspect requires sufficient understanding of Chrome.<br />
<br />
Acoording to WierdAl (#developers), Firefox uses the toolkit approach: [http://developer.mozilla.org/en/docs/chrome.manifest Chrome Registration - MDC] whereas SeaMonkey uses the old way (xpfe).<br />
<br />
<br />
==Code Registry Example==<br />
<pre><br />
1. content necko jar:comm.jar!/content/necko/ xpcnativewrappers=yes<br />
2. locale necko en-US jar:en-US.jar!/locale/en-US/necko/<br />
3. content xbl-marquee jar:comm.jar!/content/xbl-marquee/<br />
4. content pipnss jar:pipnss.jar!/content/pipnss/<br />
5. locale pipnss en-US jar:en-US.jar!/locale/en-US/pipnss/<br />
6. # Firefox-only<br />
7. overlay chrome://browser/content/pageInfo.xul chrome://pippki/content/PageInfoOverlay.xul application={ec8030f7-c20a-464f-9b0e-13a3a9e97384}<br />
8. overlay chrome://communicator/content/pref/preftree.xul chrome://pippki/content/PrefOverlay.xul<br />
9. overlay chrome://navigator/content/pageInfo.xul chrome://pippki/content/PageInfoOverlay.xul application=seamonkey@applications.mozilla.org<br />
10. content pippki jar:pippki.jar!/content/pippki/ xpcnativewrappers=yes<br />
11. locale pippki en-US jar:en-US.jar!/locale/en-US/pippki/<br />
12. content global-platform jar:toolkit.jar!/content/global-platform/ platform<br />
13. skin global classic/1.0 jar:classic.jar!/skin/classic/global/<br />
14. override chrome://global/content/netError.xhtml jar:embedder.jar!/global/content/netError.xhtml<br />
15. content inspector jar:inspector.jar!/content/inspector/ xpcnativewrappers=no<br />
</pre><br />
<br />
*Line 1: <pre>content packagename uri/to/files/ [flags]</pre><br />
**This code will register the package called necko when resolving the URL jar:comm.jar!/content/necko/ with the xpcnativewrappers flag on <br />
<br />
<br />
*Line 5: <pre>locale packagename localename uri/to/files/ [flags]</pre><br />
**This code will register a locale package called pinpnss with the localename en-US when resolving the URL jar:en-US.jar!/locale/en-US/pipnss/<br />
**NOTE: If there are more than one locale file register for the package, chrome will select the best-fit locale for the URL.<br />
<br />
<br />
*Line 6: <pre># this line is a comment - you can put whatever you want here</pre><br />
**To comment your code, put '#' in the beginning of the line.<br />
<br />
<br />
*Line 7: <pre>overlay chrome://URI-to-be-overlayed chrome://overlay-URI [flags]</pre><br />
**The prupose of this code is to overlaying one chrome on top of the other. The application={ec8030f7-c20a-464f-9b0e-13a3a9e97384} is a flag that specific which application will have this overlay.<br />
<br />
<br />
*Line 13: <pre>skin packagename skinname uri/to/files/ [flags]</pre><br />
**This will register a skin package gobal with the skinname classic/1.0 when resolving the URL jar:classic.jar!/skin/classic/global/<br />
**NOTE: If more than one skin register for the package, chrome will select the best-fit skin for the URL.<br />
<br />
<br />
*Line 14: <pre>override chrome://package/type/original-uri.whatever new-resolved-URI [flags]</pre><br />
**The purpose of this is to override a chrome file provided by the application or XULRunner with a new extension or embedder.<br />
<br />
=Additional Info=<br />
<br />
<br />
<br />
==Starting Out==<br />
WierdAl in #developers said he started doing the development work by obtaining [http://www.gerv.net/software/patch-maker Gerv's Patch Maker] and looking in Bugzilla for a bug with the words "good first bug" in the Status Whiteboard. WierdAl also has a blog on his development: <br />
*[http://weblogs.mozillazine.org/weirdal/archives/cat_xul_widgets.html Burning Chrome: XUL Widgets Archives]<br />
*[http://weblogs.mozillazine.org/weirdal/archives/cat_xul_xbl_js_and_dom.html Burning Chrome: XUL, XBL, JS and DOM Archives]<br />
<br />
== Chrome Tutorials==<br />
Here are tutorials on how to create user interface parts using Chrome:<br />
*[http://developer.mozilla.org/en/docs/Creating_a_Skin_for_Mozilla:Getting_Started Create a skin for Mozilla]<br />
*[http://developer.mozilla.org/en/docs/Working_with_windows_in_chrome_code Working with windows in Chrome Code]<br />
*[http://developer.mozilla.org/en/docs/Creating_toolbar_buttons Create toolbar buttons]<br />
*[http://developer.mozilla.org/en/docs/Creating_a_Firefox_sidebar Create a Firefox sidebar]<br />
*[http://developer.mozilla.org/en/docs/XUL_Tutorial:Creating_a_Window XULTutorial: Creating a Window - MDC]<br />
*[http://www.g4tv.com/screensavers/features/41046/Create_a_Mozilla_Extension_pg3.html Create a Mozilla Extension]<br />
*[http://www.mozilla.org/unix/customizing.html Customizing Mozilla]<br />
<br />
=Resources=<br />
WierdAl in #developers<br />
<br />
[http://www.mozilla.org/projects/intl/iuc15/paper/iuc15xul.html XUL - Creating Localizable XML GUI]<br />
<br />
[http://www.mozilla.org/xpfe/ConfigChromeSpec.html Configurable Chrome ]&nbsp;&nbsp; by Benjamin Smedberg <benjamin@smedbergs.us><br />
<br />
[http://developer.mozilla.org/en/docs/Chrome_Registration Chrome Registration]<br />
<br />
http://www.mozilla.org/support/firefox/tips<br />
<br />
[http://www.xulplanet.com/tutorials/xultu/intro.html 1.1 Introduction]</div>Eorhttps://wiki.cdot.senecacollege.ca/w/index.php?title=Chrome&diff=4808Chrome2006-10-06T14:40:14Z<p>Eor: /* Code Registry Example */</p>
<hr />
<div>=What is Chrome?=<br />
In a nutshell, Chrome is the user interface of Mozilla products. The user interface is composed mostly of [[XUL]], [[XBL]], CSS, and JS files. (You can make changes to these files without needing to recompile the Mozilla project you're working on - which is an enormous timesaver, especially for people who are just starting out on Mozilla-based development). <br />
<br />
If you look in the chrome subdirectory of your installation, you'll find .jar files - these contain the chrome files that make up the user interface. These jar files are actually just ZIP archives. Extensions are (usually) chrome applets. 90% of an [http://developer.mozilla.org/en/docs/Extensions extension], typically is chrome. <br />
<br />
In the XUL world, Chrome is the top level window which contains groups of UI elements of various types. Example of chrome are the browser window and dialog window. The chrome obtains its UI description from four types of providers: <br />
<br />
* Content provider<br />
::Provides the skeleton, i.e., the menus, command buttons<br />
* Skin provider<br />
::Supplies the look-and-feel of the chrome<br />
* Platform provider<br />
::Gives platform dependent UI description<br />
* Locale provider<br />
::Offers the language and culture sensitive resources<br />
<br />
=Chrome in depth=<br />
<br />
==Chrome URLs==<br />
To maximize the flexibility, Mozilla introduces a new technology called "Configurable Chrome" (Refer to [http://www.mozilla.org/xpfe/ConfigChromeSpec.html Configurable Chrome] by Benjamin Smedberg <benjamin@smedbergs.us>). A XUL file can be written in such a fashion that its chrome description comes from a mixture of physical sources, either locally, remotely, or a combination of both. An end user may customize her/his configuration to pick up any of the source type from his favor chrome providers.<br />
<br />
To achieve this, chrome type URLs must be used to reference external sources; such as CSS files and JavaScript files. A Chrome URL points to a file registered within the Mozilla product (it could be e-mail, calendar, browser etc.)<br />
<br />
The general form of chrome URLs look like this [Refer to [http://xulplanet.com/tutorials/xultu/chromeurl.html XULPlanet - The Chrome URL] for more details]:<br />
<br />
<pre>chrome://WindowType/ProviderType/[ProviderName/]</pre><br />
<br />
*The "WindowType" is the window type of the chrome. Possible values are "navigator", "messenger", etc. The "ProviderType" is one of the four providers: content, skin, platform, or locale. Examples of the provider names, "ProviderName", are Mozilla, Mozillazine, xyzOrg, myISP, and etc. (Refer to [http://www.mozilla.org/projects/intl/iuc15/paper/iuc15xul.html XUL - Creating Localizable XML GUI] for illustrations).<br />
<br />
==Chrome Registry==<br />
This aspect requires sufficient understanding of Chrome.<br />
<br />
Acoording to WierdAl (#developers), Firefox uses the toolkit approach: [http://developer.mozilla.org/en/docs/chrome.manifest Chrome Registration - MDC] whereas SeaMonkey uses the old way (xpfe).<br />
<br />
=Additional Info=<br />
<br />
<br />
<br />
==Starting Out==<br />
WierdAl in #developers said he started doing the development work by obtaining [http://www.gerv.net/software/patch-maker Gerv's Patch Maker] and looking in Bugzilla for a bug with the words "good first bug" in the Status Whiteboard. WierdAl also has a blog on his development: <br />
*[http://weblogs.mozillazine.org/weirdal/archives/cat_xul_widgets.html Burning Chrome: XUL Widgets Archives]<br />
*[http://weblogs.mozillazine.org/weirdal/archives/cat_xul_xbl_js_and_dom.html Burning Chrome: XUL, XBL, JS and DOM Archives]<br />
<br />
== Chrome Tutorials==<br />
Here are tutorials on how to create user interface parts using Chrome:<br />
*[http://developer.mozilla.org/en/docs/Creating_a_Skin_for_Mozilla:Getting_Started Create a skin for Mozilla]<br />
*[http://developer.mozilla.org/en/docs/Working_with_windows_in_chrome_code Working with windows in Chrome Code]<br />
*[http://developer.mozilla.org/en/docs/Creating_toolbar_buttons Create toolbar buttons]<br />
*[http://developer.mozilla.org/en/docs/Creating_a_Firefox_sidebar Create a Firefox sidebar]<br />
*[http://developer.mozilla.org/en/docs/XUL_Tutorial:Creating_a_Window XULTutorial: Creating a Window - MDC]<br />
*[http://www.g4tv.com/screensavers/features/41046/Create_a_Mozilla_Extension_pg3.html Create a Mozilla Extension]<br />
*[http://www.mozilla.org/unix/customizing.html Customizing Mozilla]<br />
<br />
=Resources=<br />
WierdAl in #developers<br />
<br />
[http://www.mozilla.org/projects/intl/iuc15/paper/iuc15xul.html XUL - Creating Localizable XML GUI]<br />
<br />
[http://www.mozilla.org/xpfe/ConfigChromeSpec.html Configurable Chrome ]&nbsp;&nbsp; by Benjamin Smedberg <benjamin@smedbergs.us><br />
<br />
[http://developer.mozilla.org/en/docs/Chrome_Registration Chrome Registration]<br />
<br />
http://www.mozilla.org/support/firefox/tips<br />
<br />
[http://www.xulplanet.com/tutorials/xultu/intro.html 1.1 Introduction]</div>Eorhttps://wiki.cdot.senecacollege.ca/w/index.php?title=Chrome&diff=4807Chrome2006-10-06T14:33:18Z<p>Eor: /* Additional Info */</p>
<hr />
<div>=What is Chrome?=<br />
In a nutshell, Chrome is the user interface of Mozilla products. The user interface is composed mostly of [[XUL]], [[XBL]], CSS, and JS files. (You can make changes to these files without needing to recompile the Mozilla project you're working on - which is an enormous timesaver, especially for people who are just starting out on Mozilla-based development). <br />
<br />
If you look in the chrome subdirectory of your installation, you'll find .jar files - these contain the chrome files that make up the user interface. These jar files are actually just ZIP archives. Extensions are (usually) chrome applets. 90% of an [http://developer.mozilla.org/en/docs/Extensions extension], typically is chrome. <br />
<br />
In the XUL world, Chrome is the top level window which contains groups of UI elements of various types. Example of chrome are the browser window and dialog window. The chrome obtains its UI description from four types of providers: <br />
<br />
* Content provider<br />
::Provides the skeleton, i.e., the menus, command buttons<br />
* Skin provider<br />
::Supplies the look-and-feel of the chrome<br />
* Platform provider<br />
::Gives platform dependent UI description<br />
* Locale provider<br />
::Offers the language and culture sensitive resources<br />
<br />
=Chrome in depth=<br />
<br />
==Chrome URLs==<br />
To maximize the flexibility, Mozilla introduces a new technology called "Configurable Chrome" (Refer to [http://www.mozilla.org/xpfe/ConfigChromeSpec.html Configurable Chrome] by Benjamin Smedberg <benjamin@smedbergs.us>). A XUL file can be written in such a fashion that its chrome description comes from a mixture of physical sources, either locally, remotely, or a combination of both. An end user may customize her/his configuration to pick up any of the source type from his favor chrome providers.<br />
<br />
To achieve this, chrome type URLs must be used to reference external sources; such as CSS files and JavaScript files. A Chrome URL points to a file registered within the Mozilla product (it could be e-mail, calendar, browser etc.)<br />
<br />
The general form of chrome URLs look like this [Refer to [http://xulplanet.com/tutorials/xultu/chromeurl.html XULPlanet - The Chrome URL] for more details]:<br />
<br />
<pre>chrome://WindowType/ProviderType/[ProviderName/]</pre><br />
<br />
*The "WindowType" is the window type of the chrome. Possible values are "navigator", "messenger", etc. The "ProviderType" is one of the four providers: content, skin, platform, or locale. Examples of the provider names, "ProviderName", are Mozilla, Mozillazine, xyzOrg, myISP, and etc. (Refer to [http://www.mozilla.org/projects/intl/iuc15/paper/iuc15xul.html XUL - Creating Localizable XML GUI] for illustrations).<br />
<br />
==Chrome Registry==<br />
This aspect requires sufficient understanding of Chrome.<br />
<br />
Acoording to WierdAl (#developers), Firefox uses the toolkit approach: [http://developer.mozilla.org/en/docs/chrome.manifest Chrome Registration - MDC] whereas SeaMonkey uses the old way (xpfe).<br />
<br />
=Additional Info=<br />
<br />
==Code Registry Example==<br />
<pre><br />
1. content necko jar:comm.jar!/content/necko/ xpcnativewrappers=yes<br />
2. locale necko en-US jar:en-US.jar!/locale/en-US/necko/<br />
3. content xbl-marquee jar:comm.jar!/content/xbl-marquee/<br />
4. content pipnss jar:pipnss.jar!/content/pipnss/<br />
5. locale pipnss en-US jar:en-US.jar!/locale/en-US/pipnss/<br />
6. # Firefox-only<br />
7. overlay chrome://browser/content/pageInfo.xul chrome://pippki/content/PageInfoOverlay.xul application={ec8030f7-c20a-464f-9b0e-13a3a9e97384}<br />
8. overlay chrome://communicator/content/pref/preftree.xul chrome://pippki/content/PrefOverlay.xul<br />
9. overlay chrome://navigator/content/pageInfo.xul chrome://pippki/content/PageInfoOverlay.xul application=seamonkey@applications.mozilla.org<br />
10. content pippki jar:pippki.jar!/content/pippki/ xpcnativewrappers=yes<br />
11. locale pippki en-US jar:en-US.jar!/locale/en-US/pippki/<br />
12. content global-platform jar:toolkit.jar!/content/global-platform/ platform<br />
13. skin global classic/1.0 jar:classic.jar!/skin/classic/global/<br />
14. override chrome://global/content/netError.xhtml jar:embedder.jar!/global/content/netError.xhtml<br />
15. content inspector jar:inspector.jar!/content/inspector/ xpcnativewrappers=no<br />
</pre><br />
<br />
*Line 1: <pre>content packagename uri/to/files/ [flags]</pre><br />
**This code will register the package called necko when resolving the URL jar:comm.jar!/content/necko/ with the xpcnativewrappers flag on <br />
<br />
<br />
*Line 5: <pre>locale packagename localename uri/to/files/ [flags]</pre><br />
**This code will register a locale package called pinpnss with the localename en-US when resolving the URL jar:en-US.jar!/locale/en-US/pipnss/<br />
**NOTE: If there are more than one locale file register for the package, chrome will select the best-fit locale for the URL.<br />
<br />
<br />
*Line 6: <pre># this line is a comment - you can put whatever you want here</pre><br />
**To comment your code, put '#' in the beginning of the line.<br />
<br />
<br />
*Line 7: <pre>overlay chrome://URI-to-be-overlayed chrome://overlay-URI [flags]</pre><br />
**The prupose of this code is to overlaying one chrome on top of the other. The application={ec8030f7-c20a-464f-9b0e-13a3a9e97384} is a flag that specific which application will have this overlay.<br />
<br />
<br />
*Line 13: <pre>skin packagename skinname uri/to/files/ [flags]</pre><br />
**This will register a skin package gobal with the skinname classic/1.0 when resolving the URL jar:classic.jar!/skin/classic/global/<br />
**NOTE: If more than one skin register for the package, chrome will select the best-fit skin for the URL.<br />
<br />
<br />
*Line 14: <pre>override chrome://package/type/original-uri.whatever new-resolved-URI [flags]</pre><br />
**The purpose of this is to override a chrome file provided by the application or XULRunner with a new extension or embedder.<br />
<br />
<br />
==Starting Out==<br />
WierdAl in #developers said he started doing the development work by obtaining [http://www.gerv.net/software/patch-maker Gerv's Patch Maker] and looking in Bugzilla for a bug with the words "good first bug" in the Status Whiteboard. WierdAl also has a blog on his development: <br />
*[http://weblogs.mozillazine.org/weirdal/archives/cat_xul_widgets.html Burning Chrome: XUL Widgets Archives]<br />
*[http://weblogs.mozillazine.org/weirdal/archives/cat_xul_xbl_js_and_dom.html Burning Chrome: XUL, XBL, JS and DOM Archives]<br />
<br />
== Chrome Tutorials==<br />
Here are tutorials on how to create user interface parts using Chrome:<br />
*[http://developer.mozilla.org/en/docs/Creating_a_Skin_for_Mozilla:Getting_Started Create a skin for Mozilla]<br />
*[http://developer.mozilla.org/en/docs/Working_with_windows_in_chrome_code Working with windows in Chrome Code]<br />
*[http://developer.mozilla.org/en/docs/Creating_toolbar_buttons Create toolbar buttons]<br />
*[http://developer.mozilla.org/en/docs/Creating_a_Firefox_sidebar Create a Firefox sidebar]<br />
*[http://developer.mozilla.org/en/docs/XUL_Tutorial:Creating_a_Window XULTutorial: Creating a Window - MDC]<br />
*[http://www.g4tv.com/screensavers/features/41046/Create_a_Mozilla_Extension_pg3.html Create a Mozilla Extension]<br />
*[http://www.mozilla.org/unix/customizing.html Customizing Mozilla]<br />
<br />
=Resources=<br />
WierdAl in #developers<br />
<br />
[http://www.mozilla.org/projects/intl/iuc15/paper/iuc15xul.html XUL - Creating Localizable XML GUI]<br />
<br />
[http://www.mozilla.org/xpfe/ConfigChromeSpec.html Configurable Chrome ]&nbsp;&nbsp; by Benjamin Smedberg <benjamin@smedbergs.us><br />
<br />
[http://developer.mozilla.org/en/docs/Chrome_Registration Chrome Registration]<br />
<br />
http://www.mozilla.org/support/firefox/tips<br />
<br />
[http://www.xulplanet.com/tutorials/xultu/intro.html 1.1 Introduction]</div>Eorhttps://wiki.cdot.senecacollege.ca/w/index.php?title=Chrome&diff=4804Chrome2006-10-06T13:51:24Z<p>Eor: /* Additional Info */</p>
<hr />
<div>=What is Chrome?=<br />
In a nutshell, Chrome is the user interface of Mozilla products. The user interface is composed mostly of [[XUL]], [[XBL]], CSS, and JS files. (You can make changes to these files without needing to recompile the Mozilla project you're working on - which is an enormous timesaver, especially for people who are just starting out on Mozilla-based development). <br />
<br />
If you look in the chrome subdirectory of your installation, you'll find .jar files - these contain the chrome files that make up the user interface. These jar files are actually just ZIP archives. Extensions are (usually) chrome applets. 90% of an [http://developer.mozilla.org/en/docs/Extensions extension], typically is chrome. <br />
<br />
In the XUL world, Chrome is the top level window which contains groups of UI elements of various types. Example of chrome are the browser window and dialog window. The chrome obtains its UI description from four types of providers: <br />
<br />
* Content provider<br />
::Provides the skeleton, i.e., the menus, command buttons<br />
* Skin provider<br />
::Supplies the look-and-feel of the chrome<br />
* Platform provider<br />
::Gives platform dependent UI description<br />
* Locale provider<br />
::Offers the language and culture sensitive resources<br />
<br />
=Chrome in depth=<br />
<br />
==Chrome URLs==<br />
To maximize the flexibility, Mozilla introduces a new technology called "Configurable Chrome" (Refer to [http://www.mozilla.org/xpfe/ConfigChromeSpec.html Configurable Chrome] by Benjamin Smedberg <benjamin@smedbergs.us>). A XUL file can be written in such a fashion that its chrome description comes from a mixture of physical sources, either locally, remotely, or a combination of both. An end user may customize her/his configuration to pick up any of the source type from his favor chrome providers.<br />
<br />
To achieve this, chrome type URLs must be used to reference external sources; such as CSS files and JavaScript files. A Chrome URL points to a file registered within the Mozilla product (it could be e-mail, calendar, browser etc.)<br />
<br />
The general form of chrome URLs look like this [Refer to [http://xulplanet.com/tutorials/xultu/chromeurl.html XULPlanet - The Chrome URL] for more details]:<br />
<br />
<pre>chrome://WindowType/ProviderType/[ProviderName/]</pre><br />
<br />
*The "WindowType" is the window type of the chrome. Possible values are "navigator", "messenger", etc. The "ProviderType" is one of the four providers: content, skin, platform, or locale. Examples of the provider names, "ProviderName", are Mozilla, Mozillazine, xyzOrg, myISP, and etc. (Refer to [http://www.mozilla.org/projects/intl/iuc15/paper/iuc15xul.html XUL - Creating Localizable XML GUI] for illustrations).<br />
<br />
==Chrome Registry==<br />
This aspect requires sufficient understanding of Chrome.<br />
<br />
Acoording to WierdAl (#developers), Firefox uses the toolkit approach: [http://developer.mozilla.org/en/docs/chrome.manifest Chrome Registration - MDC] whereas SeaMonkey uses the old way (xpfe).<br />
<br />
=Additional Info=<br />
<br />
==Code Example==<br />
<pre><br />
1. content necko jar:comm.jar!/content/necko/ xpcnativewrappers=yes<br />
2. locale necko en-US jar:en-US.jar!/locale/en-US/necko/<br />
3. content xbl-marquee jar:comm.jar!/content/xbl-marquee/<br />
4. content pipnss jar:pipnss.jar!/content/pipnss/<br />
5. locale pipnss en-US jar:en-US.jar!/locale/en-US/pipnss/<br />
6. # Firefox-only<br />
7. overlay chrome://browser/content/pageInfo.xul chrome://pippki/content/PageInfoOverlay.xul application={ec8030f7-c20a-464f-9b0e-13a3a9e97384}<br />
8. overlay chrome://communicator/content/pref/preftree.xul chrome://pippki/content/PrefOverlay.xul<br />
9. overlay chrome://navigator/content/pageInfo.xul chrome://pippki/content/PageInfoOverlay.xul application=seamonkey@applications.mozilla.org<br />
10. content pippki jar:pippki.jar!/content/pippki/ xpcnativewrappers=yes<br />
11. locale pippki en-US jar:en-US.jar!/locale/en-US/pippki/<br />
12. content global-platform jar:toolkit.jar!/content/global-platform/ platform<br />
13. skin global classic/1.0 jar:classic.jar!/skin/classic/global/<br />
14. override chrome://global/content/netError.xhtml jar:embedder.jar!/global/content/netError.xhtml<br />
15. content inspector jar:inspector.jar!/content/inspector/ xpcnativewrappers=no<br />
</pre><br />
<br />
*Line 1: <pre>content packagename uri/to/files/ [flags]</pre><br />
**This code will register the package called necko when resolving the URL jar:comm.jar!/content/necko/ with the xpcnativewrappers flag on <br />
<br />
<br />
*Line 5: <pre>locale packagename localename uri/to/files/ [flags]</pre><br />
**This code will register a locale package called pinpnss with the localename en-US when resolving the URL jar:en-US.jar!/locale/en-US/pipnss/<br />
**NOTE: If there are more than one locale file register for the package, chrome will select the best-fit locale for the URL.<br />
<br />
<br />
*Line 6: <pre># this line is a comment - you can put whatever you want here</pre><br />
**To comment your code, put '#' in the beginning of the line.<br />
<br />
<br />
*Line 7: <pre>overlay chrome://URI-to-be-overlayed chrome://overlay-URI [flags]</pre><br />
**The prupose of this code is to overlaying one chrome on top of the other. The application={ec8030f7-c20a-464f-9b0e-13a3a9e97384} is a flag that specific which application will have this overlay.<br />
<br />
<br />
*Line 13: <pre>skin packagename skinname uri/to/files/ [flags]</pre><br />
**This will register a skin package gobal with the skinname classic/1.0 when resolving the URL jar:classic.jar!/skin/classic/global/<br />
**NOTE: If more than one skin register for the package, chrome will select the best-fit skin for the URL.<br />
<br />
<br />
*Line 14: <pre>override chrome://package/type/original-uri.whatever new-resolved-URI [flags]</pre><br />
**The purpose of this is to override a chrome file provided by the application or XULRunner with a new extension or embedder.<br />
<br />
<br />
==Starting Out==<br />
WierdAl in #developers said he started doing the development work by obtaining [http://www.gerv.net/software/patch-maker Gerv's Patch Maker] and looking in Bugzilla for a bug with the words "good first bug" in the Status Whiteboard. WierdAl also has a blog on his development: <br />
*[http://weblogs.mozillazine.org/weirdal/archives/cat_xul_widgets.html Burning Chrome: XUL Widgets Archives]<br />
*[http://weblogs.mozillazine.org/weirdal/archives/cat_xul_xbl_js_and_dom.html Burning Chrome: XUL, XBL, JS and DOM Archives]<br />
<br />
== Chrome Tutorials==<br />
Here are tutorials on how to create user interface parts using Chrome:<br />
*[http://developer.mozilla.org/en/docs/Creating_a_Skin_for_Mozilla:Getting_Started Create a skin for Mozilla]<br />
*[http://developer.mozilla.org/en/docs/Working_with_windows_in_chrome_code Working with windows in Chrome Code]<br />
*[http://developer.mozilla.org/en/docs/Creating_toolbar_buttons Create toolbar buttons]<br />
*[http://developer.mozilla.org/en/docs/Creating_a_Firefox_sidebar Create a Firefox sidebar]<br />
*[http://developer.mozilla.org/en/docs/XUL_Tutorial:Creating_a_Window XULTutorial: Creating a Window - MDC]<br />
*[http://www.g4tv.com/screensavers/features/41046/Create_a_Mozilla_Extension_pg3.html Create a Mozilla Extension]<br />
*[http://www.mozilla.org/unix/customizing.html Customizing Mozilla]<br />
<br />
=Resources=<br />
WierdAl in #developers<br />
<br />
[http://www.mozilla.org/projects/intl/iuc15/paper/iuc15xul.html XUL - Creating Localizable XML GUI]<br />
<br />
[http://www.mozilla.org/xpfe/ConfigChromeSpec.html Configurable Chrome ]&nbsp;&nbsp; by Benjamin Smedberg <benjamin@smedbergs.us><br />
<br />
[http://developer.mozilla.org/en/docs/Chrome_Registration Chrome Registration]<br />
<br />
http://www.mozilla.org/support/firefox/tips<br />
<br />
[http://www.xulplanet.com/tutorials/xultu/intro.html 1.1 Introduction]</div>Eorhttps://wiki.cdot.senecacollege.ca/w/index.php?title=Chrome&diff=4803Chrome2006-10-06T13:51:01Z<p>Eor: /* Additional Info */</p>
<hr />
<div>=What is Chrome?=<br />
In a nutshell, Chrome is the user interface of Mozilla products. The user interface is composed mostly of [[XUL]], [[XBL]], CSS, and JS files. (You can make changes to these files without needing to recompile the Mozilla project you're working on - which is an enormous timesaver, especially for people who are just starting out on Mozilla-based development). <br />
<br />
If you look in the chrome subdirectory of your installation, you'll find .jar files - these contain the chrome files that make up the user interface. These jar files are actually just ZIP archives. Extensions are (usually) chrome applets. 90% of an [http://developer.mozilla.org/en/docs/Extensions extension], typically is chrome. <br />
<br />
In the XUL world, Chrome is the top level window which contains groups of UI elements of various types. Example of chrome are the browser window and dialog window. The chrome obtains its UI description from four types of providers: <br />
<br />
* Content provider<br />
::Provides the skeleton, i.e., the menus, command buttons<br />
* Skin provider<br />
::Supplies the look-and-feel of the chrome<br />
* Platform provider<br />
::Gives platform dependent UI description<br />
* Locale provider<br />
::Offers the language and culture sensitive resources<br />
<br />
=Chrome in depth=<br />
<br />
==Chrome URLs==<br />
To maximize the flexibility, Mozilla introduces a new technology called "Configurable Chrome" (Refer to [http://www.mozilla.org/xpfe/ConfigChromeSpec.html Configurable Chrome] by Benjamin Smedberg <benjamin@smedbergs.us>). A XUL file can be written in such a fashion that its chrome description comes from a mixture of physical sources, either locally, remotely, or a combination of both. An end user may customize her/his configuration to pick up any of the source type from his favor chrome providers.<br />
<br />
To achieve this, chrome type URLs must be used to reference external sources; such as CSS files and JavaScript files. A Chrome URL points to a file registered within the Mozilla product (it could be e-mail, calendar, browser etc.)<br />
<br />
The general form of chrome URLs look like this [Refer to [http://xulplanet.com/tutorials/xultu/chromeurl.html XULPlanet - The Chrome URL] for more details]:<br />
<br />
<pre>chrome://WindowType/ProviderType/[ProviderName/]</pre><br />
<br />
*The "WindowType" is the window type of the chrome. Possible values are "navigator", "messenger", etc. The "ProviderType" is one of the four providers: content, skin, platform, or locale. Examples of the provider names, "ProviderName", are Mozilla, Mozillazine, xyzOrg, myISP, and etc. (Refer to [http://www.mozilla.org/projects/intl/iuc15/paper/iuc15xul.html XUL - Creating Localizable XML GUI] for illustrations).<br />
<br />
==Chrome Registry==<br />
This aspect requires sufficient understanding of Chrome.<br />
<br />
Acoording to WierdAl (#developers), Firefox uses the toolkit approach: [http://developer.mozilla.org/en/docs/chrome.manifest Chrome Registration - MDC] whereas SeaMonkey uses the old way (xpfe).<br />
<br />
=Additional Info=<br />
<br />
==Code Example==<br />
<pre><br />
1. content necko jar:comm.jar!/content/necko/ xpcnativewrappers=yes<br />
2. locale necko en-US jar:en-US.jar!/locale/en-US/necko/<br />
3. content xbl-marquee jar:comm.jar!/content/xbl-marquee/<br />
4. content pipnss jar:pipnss.jar!/content/pipnss/<br />
5. locale pipnss en-US jar:en-US.jar!/locale/en-US/pipnss/<br />
6. # Firefox-only<br />
7. overlay chrome://browser/content/pageInfo.xul chrome://pippki/content/PageInfoOverlay.xul application={ec8030f7-c20a-464f-9b0e-13a3a9e97384}<br />
8. overlay chrome://communicator/content/pref/preftree.xul chrome://pippki/content/PrefOverlay.xul<br />
9. overlay chrome://navigator/content/pageInfo.xul chrome://pippki/content/PageInfoOverlay.xul application=seamonkey@applications.mozilla.org<br />
10. content pippki jar:pippki.jar!/content/pippki/ xpcnativewrappers=yes<br />
11. locale pippki en-US jar:en-US.jar!/locale/en-US/pippki/<br />
12. content global-platform jar:toolkit.jar!/content/global-platform/ platform<br />
13. skin global classic/1.0 jar:classic.jar!/skin/classic/global/<br />
14. override chrome://global/content/netError.xhtml jar:embedder.jar!/global/content/netError.xhtml<br />
15. content inspector jar:inspector.jar!/content/inspector/ xpcnativewrappers=no<br />
</pre><br />
<br />
*Line 1: <pre>content packagename uri/to/files/ [flags]</pre><br />
**This code will register the package called necko when resolving the URL jar:comm.jar!/content/necko/ with the xpcnativewrappers flag on <br />
<br />
*Line 5: <pre>locale packagename localename uri/to/files/ [flags]</pre><br />
**This code will register a locale package called pinpnss with the localename en-US when resolving the URL jar:en-US.jar!/locale/en-US/pipnss/<br />
**NOTE: If there are more than one locale file register for the package, chrome will select the best-fit locale for the URL.<br />
<br />
<br />
*Line 6: <pre># this line is a comment - you can put whatever you want here</pre><br />
**To comment your code, put '#' in the beginning of the line.<br />
<br />
<br />
*Line 7: <pre>overlay chrome://URI-to-be-overlayed chrome://overlay-URI [flags]</pre><br />
**The prupose of this code is to overlaying one chrome on top of the other. The application={ec8030f7-c20a-464f-9b0e-13a3a9e97384} is a flag that specific which application will have this overlay.<br />
<br />
<br />
*Line 13: <pre>skin packagename skinname uri/to/files/ [flags]</pre><br />
**This will register a skin package gobal with the skinname classic/1.0 when resolving the URL jar:classic.jar!/skin/classic/global/<br />
**NOTE: If more than one skin register for the package, chrome will select the best-fit skin for the URL.<br />
<br />
<br />
*Line 14: <pre>override chrome://package/type/original-uri.whatever new-resolved-URI [flags]</pre><br />
**The purpose of this is to override a chrome file provided by the application or XULRunner with a new extension or embedder.<br />
<br />
<br />
==Starting Out==<br />
WierdAl in #developers said he started doing the development work by obtaining [http://www.gerv.net/software/patch-maker Gerv's Patch Maker] and looking in Bugzilla for a bug with the words "good first bug" in the Status Whiteboard. WierdAl also has a blog on his development: <br />
*[http://weblogs.mozillazine.org/weirdal/archives/cat_xul_widgets.html Burning Chrome: XUL Widgets Archives]<br />
*[http://weblogs.mozillazine.org/weirdal/archives/cat_xul_xbl_js_and_dom.html Burning Chrome: XUL, XBL, JS and DOM Archives]<br />
<br />
== Chrome Tutorials==<br />
Here are tutorials on how to create user interface parts using Chrome:<br />
*[http://developer.mozilla.org/en/docs/Creating_a_Skin_for_Mozilla:Getting_Started Create a skin for Mozilla]<br />
*[http://developer.mozilla.org/en/docs/Working_with_windows_in_chrome_code Working with windows in Chrome Code]<br />
*[http://developer.mozilla.org/en/docs/Creating_toolbar_buttons Create toolbar buttons]<br />
*[http://developer.mozilla.org/en/docs/Creating_a_Firefox_sidebar Create a Firefox sidebar]<br />
*[http://developer.mozilla.org/en/docs/XUL_Tutorial:Creating_a_Window XULTutorial: Creating a Window - MDC]<br />
*[http://www.g4tv.com/screensavers/features/41046/Create_a_Mozilla_Extension_pg3.html Create a Mozilla Extension]<br />
*[http://www.mozilla.org/unix/customizing.html Customizing Mozilla]<br />
<br />
=Resources=<br />
WierdAl in #developers<br />
<br />
[http://www.mozilla.org/projects/intl/iuc15/paper/iuc15xul.html XUL - Creating Localizable XML GUI]<br />
<br />
[http://www.mozilla.org/xpfe/ConfigChromeSpec.html Configurable Chrome ]&nbsp;&nbsp; by Benjamin Smedberg <benjamin@smedbergs.us><br />
<br />
[http://developer.mozilla.org/en/docs/Chrome_Registration Chrome Registration]<br />
<br />
http://www.mozilla.org/support/firefox/tips<br />
<br />
[http://www.xulplanet.com/tutorials/xultu/intro.html 1.1 Introduction]</div>Eorhttps://wiki.cdot.senecacollege.ca/w/index.php?title=Chrome&diff=4802Chrome2006-10-06T13:46:09Z<p>Eor: /* Additional Info */</p>
<hr />
<div>=What is Chrome?=<br />
In a nutshell, Chrome is the user interface of Mozilla products. The user interface is composed mostly of [[XUL]], [[XBL]], CSS, and JS files. (You can make changes to these files without needing to recompile the Mozilla project you're working on - which is an enormous timesaver, especially for people who are just starting out on Mozilla-based development). <br />
<br />
If you look in the chrome subdirectory of your installation, you'll find .jar files - these contain the chrome files that make up the user interface. These jar files are actually just ZIP archives. Extensions are (usually) chrome applets. 90% of an [http://developer.mozilla.org/en/docs/Extensions extension], typically is chrome. <br />
<br />
In the XUL world, Chrome is the top level window which contains groups of UI elements of various types. Example of chrome are the browser window and dialog window. The chrome obtains its UI description from four types of providers: <br />
<br />
* Content provider<br />
::Provides the skeleton, i.e., the menus, command buttons<br />
* Skin provider<br />
::Supplies the look-and-feel of the chrome<br />
* Platform provider<br />
::Gives platform dependent UI description<br />
* Locale provider<br />
::Offers the language and culture sensitive resources<br />
<br />
=Chrome in depth=<br />
<br />
==Chrome URLs==<br />
To maximize the flexibility, Mozilla introduces a new technology called "Configurable Chrome" (Refer to [http://www.mozilla.org/xpfe/ConfigChromeSpec.html Configurable Chrome] by Benjamin Smedberg <benjamin@smedbergs.us>). A XUL file can be written in such a fashion that its chrome description comes from a mixture of physical sources, either locally, remotely, or a combination of both. An end user may customize her/his configuration to pick up any of the source type from his favor chrome providers.<br />
<br />
To achieve this, chrome type URLs must be used to reference external sources; such as CSS files and JavaScript files. A Chrome URL points to a file registered within the Mozilla product (it could be e-mail, calendar, browser etc.)<br />
<br />
The general form of chrome URLs look like this [Refer to [http://xulplanet.com/tutorials/xultu/chromeurl.html XULPlanet - The Chrome URL] for more details]:<br />
<br />
<pre>chrome://WindowType/ProviderType/[ProviderName/]</pre><br />
<br />
*The "WindowType" is the window type of the chrome. Possible values are "navigator", "messenger", etc. The "ProviderType" is one of the four providers: content, skin, platform, or locale. Examples of the provider names, "ProviderName", are Mozilla, Mozillazine, xyzOrg, myISP, and etc. (Refer to [http://www.mozilla.org/projects/intl/iuc15/paper/iuc15xul.html XUL - Creating Localizable XML GUI] for illustrations).<br />
<br />
==Chrome Registry==<br />
This aspect requires sufficient understanding of Chrome.<br />
<br />
Acoording to WierdAl (#developers), Firefox uses the toolkit approach: [http://developer.mozilla.org/en/docs/chrome.manifest Chrome Registration - MDC] whereas SeaMonkey uses the old way (xpfe).<br />
<br />
=Additional Info=<br />
<br />
==Code Example==<br />
<pre><br />
1. content necko jar:comm.jar!/content/necko/ xpcnativewrappers=yes<br />
2. locale necko en-US jar:en-US.jar!/locale/en-US/necko/<br />
3. content xbl-marquee jar:comm.jar!/content/xbl-marquee/<br />
4. content pipnss jar:pipnss.jar!/content/pipnss/<br />
5. locale pipnss en-US jar:en-US.jar!/locale/en-US/pipnss/<br />
6. # Firefox-only<br />
7. overlay chrome://browser/content/pageInfo.xul chrome://pippki/content/PageInfoOverlay.xul application={ec8030f7-c20a-464f-9b0e-13a3a9e97384}<br />
8. overlay chrome://communicator/content/pref/preftree.xul chrome://pippki/content/PrefOverlay.xul<br />
9. overlay chrome://navigator/content/pageInfo.xul chrome://pippki/content/PageInfoOverlay.xul application=seamonkey@applications.mozilla.org<br />
10. content pippki jar:pippki.jar!/content/pippki/ xpcnativewrappers=yes<br />
11. locale pippki en-US jar:en-US.jar!/locale/en-US/pippki/<br />
12. content global-platform jar:toolkit.jar!/content/global-platform/ platform<br />
13. skin global classic/1.0 jar:classic.jar!/skin/classic/global/<br />
14. override chrome://global/content/netError.xhtml jar:embedder.jar!/global/content/netError.xhtml<br />
15. content inspector jar:inspector.jar!/content/inspector/ xpcnativewrappers=no<br />
</pre><br />
<br />
*Line 1: <pre>content packagename uri/to/files/ [flags]</pre><br />
**This code will register the package called necko when resolving the URL jar:comm.jar!/content/necko/ xpcnativewrappers=yes<br />
<br />
<br />
*Line 5: <pre>locale packagename localename uri/to/files/ [flags]</pre><br />
**This code will register a locale package called pinpnss with the localename en-US when resolving the URL jar:en-US.jar!/locale/en-US/pipnss/<br />
**NOTE: If there are more than one locale file register for the package, chrome will select the best-fit locale for the URL.<br />
<br />
<br />
*Line 6: <pre># this line is a comment - you can put whatever you want here</pre><br />
**To comment your code, put '#' in the beginning of the line.<br />
<br />
<br />
*Line 7: <pre>overlay chrome://URI-to-be-overlayed chrome://overlay-URI [flags]</pre><br />
**The prupose of this code is to overlaying one chrome on top of the other.<br />
<br />
<br />
*Line 13: <pre>skin packagename skinname uri/to/files/ [flags]</pre><br />
**This will register a skin package gobal with the skinname classic/1.0 when resolving the URL jar:classic.jar!/skin/classic/global/<br />
**NOTE: If more than one skin register for the package, chrome will select the best-fit skin for the URL.<br />
<br />
<br />
*Line 14: <pre>override chrome://package/type/original-uri.whatever new-resolved-URI [flags]</pre><br />
**The purpose of this is to override a chrome file provided by the application or XULRunner with a new extension or embedder.<br />
<br />
==Starting Out==<br />
WierdAl in #developers said he started doing the development work by obtaining [http://www.gerv.net/software/patch-maker Gerv's Patch Maker] and looking in Bugzilla for a bug with the words "good first bug" in the Status Whiteboard. WierdAl also has a blog on his development: <br />
*[http://weblogs.mozillazine.org/weirdal/archives/cat_xul_widgets.html Burning Chrome: XUL Widgets Archives]<br />
*[http://weblogs.mozillazine.org/weirdal/archives/cat_xul_xbl_js_and_dom.html Burning Chrome: XUL, XBL, JS and DOM Archives]<br />
<br />
== Chrome Tutorials==<br />
Here are tutorials on how to create user interface parts using Chrome:<br />
*[http://developer.mozilla.org/en/docs/Creating_a_Skin_for_Mozilla:Getting_Started Create a skin for Mozilla]<br />
*[http://developer.mozilla.org/en/docs/Working_with_windows_in_chrome_code Working with windows in Chrome Code]<br />
*[http://developer.mozilla.org/en/docs/Creating_toolbar_buttons Create toolbar buttons]<br />
*[http://developer.mozilla.org/en/docs/Creating_a_Firefox_sidebar Create a Firefox sidebar]<br />
*[http://developer.mozilla.org/en/docs/XUL_Tutorial:Creating_a_Window XULTutorial: Creating a Window - MDC]<br />
*[http://www.g4tv.com/screensavers/features/41046/Create_a_Mozilla_Extension_pg3.html Create a Mozilla Extension]<br />
*[http://www.mozilla.org/unix/customizing.html Customizing Mozilla]<br />
<br />
=Resources=<br />
WierdAl in #developers<br />
<br />
[http://www.mozilla.org/projects/intl/iuc15/paper/iuc15xul.html XUL - Creating Localizable XML GUI]<br />
<br />
[http://www.mozilla.org/xpfe/ConfigChromeSpec.html Configurable Chrome ]&nbsp;&nbsp; by Benjamin Smedberg <benjamin@smedbergs.us><br />
<br />
[http://developer.mozilla.org/en/docs/Chrome_Registration Chrome Registration]<br />
<br />
http://www.mozilla.org/support/firefox/tips<br />
<br />
[http://www.xulplanet.com/tutorials/xultu/intro.html 1.1 Introduction]</div>Eorhttps://wiki.cdot.senecacollege.ca/w/index.php?title=Chrome&diff=4801Chrome2006-10-06T13:44:41Z<p>Eor: /* Code Example */</p>
<hr />
<div>=What is Chrome?=<br />
In a nutshell, Chrome is the user interface of Mozilla products. The user interface is composed mostly of [[XUL]], [[XBL]], CSS, and JS files. (You can make changes to these files without needing to recompile the Mozilla project you're working on - which is an enormous timesaver, especially for people who are just starting out on Mozilla-based development). <br />
<br />
If you look in the chrome subdirectory of your installation, you'll find .jar files - these contain the chrome files that make up the user interface. These jar files are actually just ZIP archives. Extensions are (usually) chrome applets. 90% of an [http://developer.mozilla.org/en/docs/Extensions extension], typically is chrome. <br />
<br />
In the XUL world, Chrome is the top level window which contains groups of UI elements of various types. Example of chrome are the browser window and dialog window. The chrome obtains its UI description from four types of providers: <br />
<br />
* Content provider<br />
::Provides the skeleton, i.e., the menus, command buttons<br />
* Skin provider<br />
::Supplies the look-and-feel of the chrome<br />
* Platform provider<br />
::Gives platform dependent UI description<br />
* Locale provider<br />
::Offers the language and culture sensitive resources<br />
<br />
=Chrome in depth=<br />
<br />
==Chrome URLs==<br />
To maximize the flexibility, Mozilla introduces a new technology called "Configurable Chrome" (Refer to [http://www.mozilla.org/xpfe/ConfigChromeSpec.html Configurable Chrome] by Benjamin Smedberg <benjamin@smedbergs.us>). A XUL file can be written in such a fashion that its chrome description comes from a mixture of physical sources, either locally, remotely, or a combination of both. An end user may customize her/his configuration to pick up any of the source type from his favor chrome providers.<br />
<br />
To achieve this, chrome type URLs must be used to reference external sources; such as CSS files and JavaScript files. A Chrome URL points to a file registered within the Mozilla product (it could be e-mail, calendar, browser etc.)<br />
<br />
The general form of chrome URLs look like this [Refer to [http://xulplanet.com/tutorials/xultu/chromeurl.html XULPlanet - The Chrome URL] for more details]:<br />
<br />
<pre>chrome://WindowType/ProviderType/[ProviderName/]</pre><br />
<br />
*The "WindowType" is the window type of the chrome. Possible values are "navigator", "messenger", etc. The "ProviderType" is one of the four providers: content, skin, platform, or locale. Examples of the provider names, "ProviderName", are Mozilla, Mozillazine, xyzOrg, myISP, and etc. (Refer to [http://www.mozilla.org/projects/intl/iuc15/paper/iuc15xul.html XUL - Creating Localizable XML GUI] for illustrations).<br />
<br />
==Chrome Registry==<br />
This aspect requires sufficient understanding of Chrome.<br />
<br />
Acoording to WierdAl (#developers), Firefox uses the toolkit approach: [http://developer.mozilla.org/en/docs/chrome.manifest Chrome Registration - MDC] whereas SeaMonkey uses the old way (xpfe).<br />
<br />
=Additional Info=<br />
<br />
==Code Example==<br />
<pre><br />
1. content necko jar:comm.jar!/content/necko/ xpcnativewrappers=yes<br />
2. locale necko en-US jar:en-US.jar!/locale/en-US/necko/<br />
3. content xbl-marquee jar:comm.jar!/content/xbl-marquee/<br />
4. content pipnss jar:pipnss.jar!/content/pipnss/<br />
5. locale pipnss en-US jar:en-US.jar!/locale/en-US/pipnss/<br />
6. # Firefox-only<br />
7. overlay chrome://browser/content/pageInfo.xul chrome://pippki/content/PageInfoOverlay.xul application={ec8030f7-c20a-464f-9b0e-13a3a9e97384}<br />
8. overlay chrome://communicator/content/pref/preftree.xul chrome://pippki/content/PrefOverlay.xul<br />
9. overlay chrome://navigator/content/pageInfo.xul chrome://pippki/content/PageInfoOverlay.xul application=seamonkey@applications.mozilla.org<br />
10. content pippki jar:pippki.jar!/content/pippki/ xpcnativewrappers=yes<br />
11. locale pippki en-US jar:en-US.jar!/locale/en-US/pippki/<br />
12. content global-platform jar:toolkit.jar!/content/global-platform/ platform<br />
13. skin global classic/1.0 jar:classic.jar!/skin/classic/global/<br />
14. override chrome://global/content/netError.xhtml jar:embedder.jar!/global/content/netError.xhtml<br />
15. content inspector jar:inspector.jar!/content/inspector/ xpcnativewrappers=no<br />
</pre><br />
<br />
*Line 1: <pre>content packagename uri/to/files/ [flags]</pre><br />
**This code will register the package called necko when resolving the URL jar:comm.jar!/content/necko/ xpcnativewrappers=yes<br />
<br />
<br />
*Line 5: <color=blue>locale packagename localename uri/to/files/ [flags]</color><br />
**This code will register a locale package called pinpnss with the localename en-US when resolving the URL jar:en-US.jar!/locale/en-US/pipnss/<br />
**NOTE: If there are more than one locale file register for the package, chrome will select the best-fit locale for the URL.<br />
<br />
<br />
*Line 6: # this line is a comment - you can put whatever you want here<br />
**To comment your code, put '#' in the beginning of the line.<br />
<br />
<br />
*Line 7: overlay chrome://URI-to-be-overlayed chrome://overlay-URI [flags]<br />
**The prupose of this code is to overlaying one chrome on top of the other.<br />
<br />
<br />
*Line 13: skin packagename skinname uri/to/files/ [flags]<br />
**This will register a skin package gobal with the skinname classic/1.0 when resolving the URL jar:classic.jar!/skin/classic/global/<br />
**NOTE: If more than one skin register for the package, chrome will select the best-fit skin for the URL.<br />
<br />
<br />
*Line 14: override chrome://package/type/original-uri.whatever new-resolved-URI [flags]<br />
**The purpose of this is to override a chrome file provided by the application or XULRunner with a new extension or embedder.<br />
<br />
==Starting Out==<br />
WierdAl in #developers said he started doing the development work by obtaining [http://www.gerv.net/software/patch-maker Gerv's Patch Maker] and looking in Bugzilla for a bug with the words "good first bug" in the Status Whiteboard. WierdAl also has a blog on his development: <br />
*[http://weblogs.mozillazine.org/weirdal/archives/cat_xul_widgets.html Burning Chrome: XUL Widgets Archives]<br />
*[http://weblogs.mozillazine.org/weirdal/archives/cat_xul_xbl_js_and_dom.html Burning Chrome: XUL, XBL, JS and DOM Archives]<br />
<br />
== Chrome Tutorials==<br />
Here are tutorials on how to create user interface parts using Chrome:<br />
*[http://developer.mozilla.org/en/docs/Creating_a_Skin_for_Mozilla:Getting_Started Create a skin for Mozilla]<br />
*[http://developer.mozilla.org/en/docs/Working_with_windows_in_chrome_code Working with windows in Chrome Code]<br />
*[http://developer.mozilla.org/en/docs/Creating_toolbar_buttons Create toolbar buttons]<br />
*[http://developer.mozilla.org/en/docs/Creating_a_Firefox_sidebar Create a Firefox sidebar]<br />
*[http://developer.mozilla.org/en/docs/XUL_Tutorial:Creating_a_Window XULTutorial: Creating a Window - MDC]<br />
*[http://www.g4tv.com/screensavers/features/41046/Create_a_Mozilla_Extension_pg3.html Create a Mozilla Extension]<br />
*[http://www.mozilla.org/unix/customizing.html Customizing Mozilla]<br />
<br />
=Resources=<br />
WierdAl in #developers<br />
<br />
[http://www.mozilla.org/projects/intl/iuc15/paper/iuc15xul.html XUL - Creating Localizable XML GUI]<br />
<br />
[http://www.mozilla.org/xpfe/ConfigChromeSpec.html Configurable Chrome ]&nbsp;&nbsp; by Benjamin Smedberg <benjamin@smedbergs.us><br />
<br />
[http://developer.mozilla.org/en/docs/Chrome_Registration Chrome Registration]<br />
<br />
http://www.mozilla.org/support/firefox/tips<br />
<br />
[http://www.xulplanet.com/tutorials/xultu/intro.html 1.1 Introduction]</div>Eorhttps://wiki.cdot.senecacollege.ca/w/index.php?title=Chrome&diff=4798Chrome2006-10-06T13:44:10Z<p>Eor: /* Code Example */</p>
<hr />
<div>=What is Chrome?=<br />
In a nutshell, Chrome is the user interface of Mozilla products. The user interface is composed mostly of [[XUL]], [[XBL]], CSS, and JS files. (You can make changes to these files without needing to recompile the Mozilla project you're working on - which is an enormous timesaver, especially for people who are just starting out on Mozilla-based development). <br />
<br />
If you look in the chrome subdirectory of your installation, you'll find .jar files - these contain the chrome files that make up the user interface. These jar files are actually just ZIP archives. Extensions are (usually) chrome applets. 90% of an [http://developer.mozilla.org/en/docs/Extensions extension], typically is chrome. <br />
<br />
In the XUL world, Chrome is the top level window which contains groups of UI elements of various types. Example of chrome are the browser window and dialog window. The chrome obtains its UI description from four types of providers: <br />
<br />
* Content provider<br />
::Provides the skeleton, i.e., the menus, command buttons<br />
* Skin provider<br />
::Supplies the look-and-feel of the chrome<br />
* Platform provider<br />
::Gives platform dependent UI description<br />
* Locale provider<br />
::Offers the language and culture sensitive resources<br />
<br />
=Chrome in depth=<br />
<br />
==Chrome URLs==<br />
To maximize the flexibility, Mozilla introduces a new technology called "Configurable Chrome" (Refer to [http://www.mozilla.org/xpfe/ConfigChromeSpec.html Configurable Chrome] by Benjamin Smedberg <benjamin@smedbergs.us>). A XUL file can be written in such a fashion that its chrome description comes from a mixture of physical sources, either locally, remotely, or a combination of both. An end user may customize her/his configuration to pick up any of the source type from his favor chrome providers.<br />
<br />
To achieve this, chrome type URLs must be used to reference external sources; such as CSS files and JavaScript files. A Chrome URL points to a file registered within the Mozilla product (it could be e-mail, calendar, browser etc.)<br />
<br />
The general form of chrome URLs look like this [Refer to [http://xulplanet.com/tutorials/xultu/chromeurl.html XULPlanet - The Chrome URL] for more details]:<br />
<br />
<pre>chrome://WindowType/ProviderType/[ProviderName/]</pre><br />
<br />
*The "WindowType" is the window type of the chrome. Possible values are "navigator", "messenger", etc. The "ProviderType" is one of the four providers: content, skin, platform, or locale. Examples of the provider names, "ProviderName", are Mozilla, Mozillazine, xyzOrg, myISP, and etc. (Refer to [http://www.mozilla.org/projects/intl/iuc15/paper/iuc15xul.html XUL - Creating Localizable XML GUI] for illustrations).<br />
<br />
==Chrome Registry==<br />
This aspect requires sufficient understanding of Chrome.<br />
<br />
Acoording to WierdAl (#developers), Firefox uses the toolkit approach: [http://developer.mozilla.org/en/docs/chrome.manifest Chrome Registration - MDC] whereas SeaMonkey uses the old way (xpfe).<br />
<br />
=Additional Info=<br />
<br />
==Code Example==<br />
<pre><br />
1. content necko jar:comm.jar!/content/necko/ xpcnativewrappers=yes<br />
2. locale necko en-US jar:en-US.jar!/locale/en-US/necko/<br />
3. content xbl-marquee jar:comm.jar!/content/xbl-marquee/<br />
4. content pipnss jar:pipnss.jar!/content/pipnss/<br />
5. locale pipnss en-US jar:en-US.jar!/locale/en-US/pipnss/<br />
6. # Firefox-only<br />
7. overlay chrome://browser/content/pageInfo.xul chrome://pippki/content/PageInfoOverlay.xul application={ec8030f7-c20a-464f-9b0e-13a3a9e97384}<br />
8. overlay chrome://communicator/content/pref/preftree.xul chrome://pippki/content/PrefOverlay.xul<br />
9. overlay chrome://navigator/content/pageInfo.xul chrome://pippki/content/PageInfoOverlay.xul application=seamonkey@applications.mozilla.org<br />
10. content pippki jar:pippki.jar!/content/pippki/ xpcnativewrappers=yes<br />
11. locale pippki en-US jar:en-US.jar!/locale/en-US/pippki/<br />
12. content global-platform jar:toolkit.jar!/content/global-platform/ platform<br />
13. skin global classic/1.0 jar:classic.jar!/skin/classic/global/<br />
14. override chrome://global/content/netError.xhtml jar:embedder.jar!/global/content/netError.xhtml<br />
15. content inspector jar:inspector.jar!/content/inspector/ xpcnativewrappers=no<br />
</pre><br />
<br />
*Line 1: <pre>content packagename uri/to/files/ [flags]</pre><br />
**This code will register the package called necko when resolving the URL jar:comm.jar!/content/necko/ xpcnativewrappers=yes<br />
<br />
<br />
*Line 5: <color blue>locale packagename localename uri/to/files/ [flags]</color><br />
**This code will register a locale package called pinpnss with the localename en-US when resolving the URL jar:en-US.jar!/locale/en-US/pipnss/<br />
**NOTE: If there are more than one locale file register for the package, chrome will select the best-fit locale for the URL.<br />
<br />
<br />
*Line 6: # this line is a comment - you can put whatever you want here<br />
**To comment your code, put '#' in the beginning of the line.<br />
<br />
<br />
*Line 7: overlay chrome://URI-to-be-overlayed chrome://overlay-URI [flags]<br />
**The prupose of this code is to overlaying one chrome on top of the other.<br />
<br />
<br />
*Line 13: skin packagename skinname uri/to/files/ [flags]<br />
**This will register a skin package gobal with the skinname classic/1.0 when resolving the URL jar:classic.jar!/skin/classic/global/<br />
**NOTE: If more than one skin register for the package, chrome will select the best-fit skin for the URL.<br />
<br />
<br />
*Line 14: override chrome://package/type/original-uri.whatever new-resolved-URI [flags]<br />
**The purpose of this is to override a chrome file provided by the application or XULRunner with a new extension or embedder.<br />
<br />
==Starting Out==<br />
WierdAl in #developers said he started doing the development work by obtaining [http://www.gerv.net/software/patch-maker Gerv's Patch Maker] and looking in Bugzilla for a bug with the words "good first bug" in the Status Whiteboard. WierdAl also has a blog on his development: <br />
*[http://weblogs.mozillazine.org/weirdal/archives/cat_xul_widgets.html Burning Chrome: XUL Widgets Archives]<br />
*[http://weblogs.mozillazine.org/weirdal/archives/cat_xul_xbl_js_and_dom.html Burning Chrome: XUL, XBL, JS and DOM Archives]<br />
<br />
== Chrome Tutorials==<br />
Here are tutorials on how to create user interface parts using Chrome:<br />
*[http://developer.mozilla.org/en/docs/Creating_a_Skin_for_Mozilla:Getting_Started Create a skin for Mozilla]<br />
*[http://developer.mozilla.org/en/docs/Working_with_windows_in_chrome_code Working with windows in Chrome Code]<br />
*[http://developer.mozilla.org/en/docs/Creating_toolbar_buttons Create toolbar buttons]<br />
*[http://developer.mozilla.org/en/docs/Creating_a_Firefox_sidebar Create a Firefox sidebar]<br />
*[http://developer.mozilla.org/en/docs/XUL_Tutorial:Creating_a_Window XULTutorial: Creating a Window - MDC]<br />
*[http://www.g4tv.com/screensavers/features/41046/Create_a_Mozilla_Extension_pg3.html Create a Mozilla Extension]<br />
*[http://www.mozilla.org/unix/customizing.html Customizing Mozilla]<br />
<br />
=Resources=<br />
WierdAl in #developers<br />
<br />
[http://www.mozilla.org/projects/intl/iuc15/paper/iuc15xul.html XUL - Creating Localizable XML GUI]<br />
<br />
[http://www.mozilla.org/xpfe/ConfigChromeSpec.html Configurable Chrome ]&nbsp;&nbsp; by Benjamin Smedberg <benjamin@smedbergs.us><br />
<br />
[http://developer.mozilla.org/en/docs/Chrome_Registration Chrome Registration]<br />
<br />
http://www.mozilla.org/support/firefox/tips<br />
<br />
[http://www.xulplanet.com/tutorials/xultu/intro.html 1.1 Introduction]</div>Eor