https://wiki.mozilla.org/api.php?action=feedcontributions&user=Jgoulie&feedformat=atomMozillaWiki - User contributions [en]2024-03-29T05:29:54ZUser contributionsMediaWiki 1.27.4https://wiki.mozilla.org/index.php?title=Contribute/Recruiting&diff=407973Contribute/Recruiting2012-03-15T01:02:52Z<p>Jgoulie: /* Support Recruitment Activities */</p>
<hr />
<div>=Stewards=<br />
<br />
Vivien Jin and Kimber Schlegelmilch <br><br />
Please note that this plan is mainly for College Recruiting<br />
<br />
=Identify Community=<br />
<br />
Paid Staff on the University Recruiting Team: Kimber, Jill, and Vivien<br><br />
Volunteers: our intern alumni<br />
<br />
=Define Contribution Opportunities=<br />
<br />
Please note that the opportunities offered by the University Recruiting Team will be seasonal, mostly happening between September and March, with a much stronger need in the Fall. <br><br />
<br />
==Support Recruitment Activities==<br />
1. Intern Alumni or Student Rep: up to 4 positions available to build Mozilla presence at new universities (Oxford, Cambridge, INSA Lyon, and University Politehnica of Bucharest). <br><br />
2. Mozilla Evangelists: We would love contributors to help host workshops, take on the role of technical evangelists during campus events, facilitate tech talks at universities, act as a mentor for university capstone projects, GSoC (Mozilla based GSoC projects), and attend career fairs with us. Ideally, we would need contributors with a deep knowledge of Mozilla technologies who also understand our recruiting needs and can speak knowledgeably about our various teams and projects. <br><br />
3. Mozilla Reps: help us identify new talent at conferences and hackathons, and help identify key rigorous courses at the university level<br><br />
<br />
==Strengthen our online presence==<br />
1. We need one Web Developer (perhaps a Web Designer) to give college.mozilla.org a new look<br><br />
2. We need one web Administrator to maintain our web content and keep it interactive (bug of the month, algorithms problems, organize online competing events)<br />
<br />
=Map Contribution Paths=<br />
<br />
Q: Are there clearly understood steps someone can follow to go from knowing nothing about your project to successfully contributing?<br />
<br />
Not at the moment, but we would love to include the Students Rep Program to promote Mozilla on a wider range of campuses. Ideally, those students will be somewhat technical and could help us organizing events at their respective universities. <br />
<br />
Until now, we've been relying on our full-time employees to sign up for tech talks and career fairs, but we understand that our engineers get extremely busy. <br />
<br />
- come up with a list of bugs per team that would be ideal for new students to work on. In short, how can we encourage students with prior technical expertise to take part in the project?<br><br />
- create some sort of process for new contributors to get up to speed with our college recruiting needs<br />
<br />
<br />
<br />
Suggestion: In addition to just documenting these steps, look for a simple 5-minute task that someone can take to get started (for example, signing up for Bugzilla if they are interested in coding) and also figure out where in the process you can add a mentor to help people.<br />
<br />
=Establish Goals and Metrics=<br />
<br />
Q: Can you measure participation or contributors today? If so, what metrics can you track? What goal or metric would you like to achieve for Q1? Alternatively, what metrics would you like to get in place for Q1?<br />
<br />
We don't have any external participation for our team at this point. <br />
<br />
Goals for Q1:<br />
1) Start collaborating with Student Reps on our various campus events (career fairs, hackathons, and so on)<br><br />
2) Identify what opportunities would be available for the Student Reps<br><br />
3) Identify location of potential contributors<br><br />
4) Solidify our college recruiting strategy for Fall '12 (career fairs, events, workshops)<br><br />
5) Identify Student Reps for our tier1 universities<br><br />
6) Recruit potential new Student Reps in the various open source clubs (see list from Vivien)<br><br><br />
<br />
<br />
<br />
Suggestion: Write down what you think would be helpful to track even if it isn't possible to get that data today. We'll work on implementing dashboards when we know what data we want.</div>Jgouliehttps://wiki.mozilla.org/index.php?title=Contribute/Recruiting&diff=407971Contribute/Recruiting2012-03-15T00:56:33Z<p>Jgoulie: /* Define Contribution Opportunities */</p>
<hr />
<div>=Stewards=<br />
<br />
Vivien Jin and Kimber Schlegelmilch <br><br />
Please note that this plan is mainly for College Recruiting<br />
<br />
=Identify Community=<br />
<br />
Paid Staff on the University Recruiting Team: Kimber, Jill, and Vivien<br><br />
Volunteers: our intern alumni<br />
<br />
=Define Contribution Opportunities=<br />
<br />
Please note that the opportunities offered by the University Recruiting Team will be seasonal, mostly happening between September and March, with a much stronger need in the Fall. <br><br />
<br />
==Support Recruitment Activities==<br />
1. Intern Alumni or Student Rep: up to 4 positions available to build Mozilla presence at new universities (Oxford, Cambridge, INSA Lyon, and University Politehnica of Bucharest). <br><br />
2. Mozilla Evangelists: We would love contributors to help hosting workshops, play the role of evangelists during campus events, hold tech talks at universities, act as a mentor for capstone projects, GSoC (Mozilla based GSoC projects), and attend career fairs with us. Ideally, we would need contributors with a deep knowledge of Mozilla technologies who also understand our recruiting needs and could speak about our various teams and projects. <br><br />
3. Mozilla Reps: help us identify new talent at conferences, hackathons, and strong CS talent<br><br />
<br />
==Strengthen our online presence==<br />
1. We need one Web Developer (perhaps a Web Designer) to give college.mozilla.org a new look<br><br />
2. We need one web Administrator to maintain our web content and keep it interactive (bug of the month, algorithms problems, organize online competing events)<br />
<br />
=Map Contribution Paths=<br />
<br />
Q: Are there clearly understood steps someone can follow to go from knowing nothing about your project to successfully contributing?<br />
<br />
Not at the moment, but we would love to include the Students Rep Program to promote Mozilla on a wider range of campuses. Ideally, those students will be somewhat technical and could help us organizing events at their respective universities. <br />
<br />
Until now, we've been relying on our full-time employees to sign up for tech talks and career fairs, but we understand that our engineers get extremely busy. <br />
<br />
- come up with a list of bugs per team that would be ideal for new students to work on. In short, how can we encourage students with prior technical expertise to take part in the project?<br><br />
- create some sort of process for new contributors to get up to speed with our college recruiting needs<br />
<br />
<br />
<br />
Suggestion: In addition to just documenting these steps, look for a simple 5-minute task that someone can take to get started (for example, signing up for Bugzilla if they are interested in coding) and also figure out where in the process you can add a mentor to help people.<br />
<br />
=Establish Goals and Metrics=<br />
<br />
Q: Can you measure participation or contributors today? If so, what metrics can you track? What goal or metric would you like to achieve for Q1? Alternatively, what metrics would you like to get in place for Q1?<br />
<br />
We don't have any external participation for our team at this point. <br />
<br />
Goals for Q1:<br />
1) Start collaborating with Student Reps on our various campus events (career fairs, hackathons, and so on)<br><br />
2) Identify what opportunities would be available for the Student Reps<br><br />
3) Identify location of potential contributors<br><br />
4) Solidify our college recruiting strategy for Fall '12 (career fairs, events, workshops)<br><br />
5) Identify Student Reps for our tier1 universities<br><br />
6) Recruit potential new Student Reps in the various open source clubs (see list from Vivien)<br><br><br />
<br />
<br />
<br />
Suggestion: Write down what you think would be helpful to track even if it isn't possible to get that data today. We'll work on implementing dashboards when we know what data we want.</div>Jgouliehttps://wiki.mozilla.org/index.php?title=Contribute/Recruiting&diff=407970Contribute/Recruiting2012-03-15T00:55:58Z<p>Jgoulie: /* Define Contribution Opportunities */</p>
<hr />
<div>=Stewards=<br />
<br />
Vivien Jin and Kimber Schlegelmilch <br><br />
Please note that this plan is mainly for College Recruiting<br />
<br />
=Identify Community=<br />
<br />
Paid Staff on the University Recruiting Team: Kimber, Jill, and Vivien<br><br />
Volunteers: our intern alumni<br />
<br />
=Define Contribution Opportunities=<br />
<br />
Please note that the opportunities offered by the University Recruiting Team will be seasonal, mostly happening between September and March, with a much stronger need in the Fall. <br><br />
<br />
==Support Recruitment Activities==<br />
1. Intern Alumni or Student Rep: up to 4 positions available to build Mozilla presence at new universities (Oxford, Cambridge, INSA Lyon, and University Politehnica of Bucharest). <br><br />
2. Mozilla Evangelists: We would love contributors to help hosting workshops, play the role of evangelists during campus events, hold tech talks at universities, act as a mentor for capstone projects, GSoC (Mozilla based GSoC projects), and attend career fairs with us. Ideally, we would need contributors with a deep knowledge of Mozilla technologies who also understand our recruiting needs and could speak about our various teams and projects. <br><br />
3. Mozilla Reps: help us identify new talent at conferences, hackathons, and strong CS talent<br><br><br />
<br />
<br />
==Strengthen our online presence==<br />
1. We need one Web Developer (perhaps a Web Designer) to give college.mozilla.org a new look <br />
2. We need one web Administrator to maintain our web content and keep it interactive (bug of the month, algorithms problems, organize online competing events)<br />
<br />
=Map Contribution Paths=<br />
<br />
Q: Are there clearly understood steps someone can follow to go from knowing nothing about your project to successfully contributing?<br />
<br />
Not at the moment, but we would love to include the Students Rep Program to promote Mozilla on a wider range of campuses. Ideally, those students will be somewhat technical and could help us organizing events at their respective universities. <br />
<br />
Until now, we've been relying on our full-time employees to sign up for tech talks and career fairs, but we understand that our engineers get extremely busy. <br />
<br />
- come up with a list of bugs per team that would be ideal for new students to work on. In short, how can we encourage students with prior technical expertise to take part in the project?<br><br />
- create some sort of process for new contributors to get up to speed with our college recruiting needs<br />
<br />
<br />
<br />
Suggestion: In addition to just documenting these steps, look for a simple 5-minute task that someone can take to get started (for example, signing up for Bugzilla if they are interested in coding) and also figure out where in the process you can add a mentor to help people.<br />
<br />
=Establish Goals and Metrics=<br />
<br />
Q: Can you measure participation or contributors today? If so, what metrics can you track? What goal or metric would you like to achieve for Q1? Alternatively, what metrics would you like to get in place for Q1?<br />
<br />
We don't have any external participation for our team at this point. <br />
<br />
Goals for Q1:<br />
1) Start collaborating with Student Reps on our various campus events (career fairs, hackathons, and so on)<br><br />
2) Identify what opportunities would be available for the Student Reps<br><br />
3) Identify location of potential contributors<br><br />
4) Solidify our college recruiting strategy for Fall '12 (career fairs, events, workshops)<br><br />
5) Identify Student Reps for our tier1 universities<br><br />
6) Recruit potential new Student Reps in the various open source clubs (see list from Vivien)<br><br><br />
<br />
<br />
<br />
Suggestion: Write down what you think would be helpful to track even if it isn't possible to get that data today. We'll work on implementing dashboards when we know what data we want.</div>Jgouliehttps://wiki.mozilla.org/index.php?title=Contribute/Recruiting&diff=407960Contribute/Recruiting2012-03-15T00:31:30Z<p>Jgoulie: /* Identify Community */</p>
<hr />
<div>=Stewards=<br />
<br />
Vivien Jin and Kimber Schlegelmilch <br><br />
Please note that this plan is mainly for College Recruiting<br />
<br />
=Identify Community=<br />
<br />
Paid Staff on the University Recruiting Team: Kimber, Jill, and Vivien<br><br />
Volunteers: our intern alumni<br />
<br />
=Define Contribution Opportunities=<br />
<br />
Q: Can you point someone interested in contributing to your project to a list of available contribution opportunities?<br />
<br />
A: The opportunities will be seasonal, mostly happening between September and March, with a much stronger need in the Fall. <br />
We would love contributors to help hosting workshops, play the role of evangelists during campus events, hold tech talks at universities, act as a mentor for capstone projects, GSoC (Mozilla based GSoC projects), and attend career fairs with us. Ideally, we would need contributors with a deep knowledge of Mozilla technologies who also understand our recruiting needs and could speak about our various teams and projects. <br />
<br />
Attend conferences + interview <br />
- <br />
<br />
Suggestion: Look at what your team's needs are and what gaps you have in staffing to come up with a list of contribution opportunities. Capture those on a wiki page, in bugs, as role descriptions in Jobvite or whatever makes sense for your community.<br />
<br />
=Map Contribution Paths=<br />
<br />
Q: Are there clearly understood steps someone can follow to go from knowing nothing about your project to successfully contributing?<br />
<br />
Not at the moment, but we would love to include the Students Rep Program to promote Mozilla on a wider range of campuses. Ideally, those students will be somewhat technical and could help us organizing events at their respective universities. <br />
<br />
Until now, we've been relying on our full-time employees to sign up for tech talks and career fairs, but we understand that our engineers get extremely busy. <br />
<br />
- come up with a list of bugs per team that would be ideal for new students to work on. In short, how can we encourage students with prior technical expertise to take part in the project?<br><br />
- create some sort of process for new contributors to get up to speed with our college recruiting needs<br />
<br />
<br />
<br />
Suggestion: In addition to just documenting these steps, look for a simple 5-minute task that someone can take to get started (for example, signing up for Bugzilla if they are interested in coding) and also figure out where in the process you can add a mentor to help people.<br />
<br />
=Establish Goals and Metrics=<br />
<br />
Q: Can you measure participation or contributors today? If so, what metrics can you track? What goal or metric would you like to achieve for Q1? Alternatively, what metrics would you like to get in place for Q1?<br />
<br />
We don't have any external participation for our team at this point. <br />
<br />
Goals for Q1:<br />
1) Start collaborating with Student Reps on our various campus events (career fairs, hackathons, and so on)<br><br />
2) Identify what opportunities would be available for the Student Reps<br><br />
3) Identify location of potential contributors<br><br />
4) Solidify our college recruiting strategy for Fall '12 (career fairs, events, workshops)<br><br />
5) Identify Student Reps for our tier1 universities<br><br />
6) Recruit potential new Student Reps in the various open source clubs (see list from Vivien)<br><br><br />
<br />
<br />
<br />
Suggestion: Write down what you think would be helpful to track even if it isn't possible to get that data today. We'll work on implementing dashboards when we know what data we want.</div>Jgouliehttps://wiki.mozilla.org/index.php?title=Contribute/Recruiting&diff=407959Contribute/Recruiting2012-03-15T00:31:14Z<p>Jgoulie: /* Identify Community */</p>
<hr />
<div>=Stewards=<br />
<br />
Vivien Jin and Kimber Schlegelmilch <br><br />
Please note that this plan is mainly for College Recruiting<br />
<br />
=Identify Community=<br />
<br />
Paid Staff on the University Recruiting Team: Kimber, Jill, and Vivien<br />
Volunteers: our intern alumni<br />
<br />
=Define Contribution Opportunities=<br />
<br />
Q: Can you point someone interested in contributing to your project to a list of available contribution opportunities?<br />
<br />
A: The opportunities will be seasonal, mostly happening between September and March, with a much stronger need in the Fall. <br />
We would love contributors to help hosting workshops, play the role of evangelists during campus events, hold tech talks at universities, act as a mentor for capstone projects, GSoC (Mozilla based GSoC projects), and attend career fairs with us. Ideally, we would need contributors with a deep knowledge of Mozilla technologies who also understand our recruiting needs and could speak about our various teams and projects. <br />
<br />
Attend conferences + interview <br />
- <br />
<br />
Suggestion: Look at what your team's needs are and what gaps you have in staffing to come up with a list of contribution opportunities. Capture those on a wiki page, in bugs, as role descriptions in Jobvite or whatever makes sense for your community.<br />
<br />
=Map Contribution Paths=<br />
<br />
Q: Are there clearly understood steps someone can follow to go from knowing nothing about your project to successfully contributing?<br />
<br />
Not at the moment, but we would love to include the Students Rep Program to promote Mozilla on a wider range of campuses. Ideally, those students will be somewhat technical and could help us organizing events at their respective universities. <br />
<br />
Until now, we've been relying on our full-time employees to sign up for tech talks and career fairs, but we understand that our engineers get extremely busy. <br />
<br />
- come up with a list of bugs per team that would be ideal for new students to work on. In short, how can we encourage students with prior technical expertise to take part in the project?<br><br />
- create some sort of process for new contributors to get up to speed with our college recruiting needs<br />
<br />
<br />
<br />
Suggestion: In addition to just documenting these steps, look for a simple 5-minute task that someone can take to get started (for example, signing up for Bugzilla if they are interested in coding) and also figure out where in the process you can add a mentor to help people.<br />
<br />
=Establish Goals and Metrics=<br />
<br />
Q: Can you measure participation or contributors today? If so, what metrics can you track? What goal or metric would you like to achieve for Q1? Alternatively, what metrics would you like to get in place for Q1?<br />
<br />
We don't have any external participation for our team at this point. <br />
<br />
Goals for Q1:<br />
1) Start collaborating with Student Reps on our various campus events (career fairs, hackathons, and so on)<br><br />
2) Identify what opportunities would be available for the Student Reps<br><br />
3) Identify location of potential contributors<br><br />
4) Solidify our college recruiting strategy for Fall '12 (career fairs, events, workshops)<br><br />
5) Identify Student Reps for our tier1 universities<br><br />
6) Recruit potential new Student Reps in the various open source clubs (see list from Vivien)<br><br><br />
<br />
<br />
<br />
Suggestion: Write down what you think would be helpful to track even if it isn't possible to get that data today. We'll work on implementing dashboards when we know what data we want.</div>Jgouliehttps://wiki.mozilla.org/index.php?title=Contribute/Recruiting&diff=404754Contribute/Recruiting2012-03-06T21:32:36Z<p>Jgoulie: /* Establish Goals and Metrics */</p>
<hr />
<div>=Steward=<br />
<br />
Julie Deroche <br><br />
Please note that this plan is mainly for College Recruiting<br />
<br />
=Identify Community=<br />
<br />
Q: Can you identify all of the contributors on your team (both paid-staff and volunteer-staff)?<br />
<br />
A: At this point, we don't have contributors in College Recruiting, but we could use help from contributors with the Capstone Projects, career fairs and some other students-run events, such as school hackathons. <br />
<br />
Suggestion: Use the [http://www.mozillians.org mozillians.org contributor directory] to help. Communicate through your team's channels and encourage people to sign up and group themselves with a common team tag. If you assign a group tag to all contributors on your project, the [https://metrics.mozilla.com/pentaho/content/pentaho-cdf-dd/Render?solution=metrics2&path=mozillians&file=mozillians.wcdf Mozillians dashboard] will track the size of that group and will also allow you to easily export the contact information for group members. You can export these contacts to ensure all your contributors are signed up.<br />
<br />
=Define Contribution Opportunities=<br />
<br />
Q: Can you point someone interested in contributing to your project to a list of available contribution opportunities?<br />
<br />
A: The opportunities will be seasonal, mostly happening between September and March, with a much stronger need in the Fall. <br />
We would love contributors to help hosting workshops, play the role of evangelists during campus events, hold tech talks at universities, act as a mentor for capstone projects, GSoC (Mozilla based GSoC projects), and attend career fairs with us. Ideally, we would need contributors with a deep knowledge of Mozilla technologies who also understand our recruiting needs and could speak about our various teams and projects. <br />
<br />
Attend conferences + interview <br />
- <br />
<br />
Suggestion: Look at what your team's needs are and what gaps you have in staffing to come up with a list of contribution opportunities. Capture those on a wiki page, in bugs, as role descriptions in Jobvite or whatever makes sense for your community.<br />
<br />
=Map Contribution Paths=<br />
<br />
Q: Are there clearly understood steps someone can follow to go from knowing nothing about your project to successfully contributing?<br />
<br />
Not at the moment, but we would love to include the Students Rep Program to promote Mozilla on a wider range of campuses. Ideally, those students will be somewhat technical and could help us organizing events at their respective universities. <br />
<br />
Until now, we've been relying on our full-time employees to sign up for tech talks and career fairs, but we understand that our engineers get extremely busy. <br />
<br />
- come up with a list of bugs per team that would be ideal for new students to work on. In short, how can we encourage students with prior technical expertise to take part in the project?<br><br />
- create some sort of process for new contributors to get up to speed with our college recruiting needs<br />
<br />
<br />
<br />
Suggestion: In addition to just documenting these steps, look for a simple 5-minute task that someone can take to get started (for example, signing up for Bugzilla if they are interested in coding) and also figure out where in the process you can add a mentor to help people.<br />
<br />
=Establish Goals and Metrics=<br />
<br />
Q: Can you measure participation or contributors today? If so, what metrics can you track? What goal or metric would you like to achieve for Q1? Alternatively, what metrics would you like to get in place for Q1?<br />
<br />
We don't have any external participation for our team at this point. <br />
<br />
Goals for Q1:<br />
1) Start collaborating with Student Reps on our various campus events (career fairs, hackathons, and so on)<br><br />
2) Identify what opportunities would be available for the Student Reps<br><br />
3) Identify location of potential contributors<br><br />
4) Solidify our college recruiting strategy for Fall '12 (career fairs, events, workshops)<br><br />
5) Identify Student Reps for our tier1 universities<br><br />
6) Recruit potential new Student Reps in the various open source clubs (see list from Vivien)<br><br><br />
<br />
<br />
<br />
Suggestion: Write down what you think would be helpful to track even if it isn't possible to get that data today. We'll work on implementing dashboards when we know what data we want.</div>Jgouliehttps://wiki.mozilla.org/index.php?title=Contribute/Recruiting&diff=402033Contribute/Recruiting2012-02-28T21:50:58Z<p>Jgoulie: /* Establish Goals and Metrics */</p>
<hr />
<div>=Steward=<br />
<br />
Julie Deroche <br><br />
Please note that this plan is mainly for College Recruiting<br />
<br />
=Identify Community=<br />
<br />
Q: Can you identify all of the contributors on your team (both paid-staff and volunteer-staff)?<br />
<br />
A: At this point, we don't have contributors in College Recruiting, but we could use help from contributors with the Capstone Projects, career fairs and some other students-run events, such as school hackathons. <br />
<br />
Suggestion: Use the [http://www.mozillians.org mozillians.org contributor directory] to help. Communicate through your team's channels and encourage people to sign up and group themselves with a common team tag. If you assign a group tag to all contributors on your project, the [https://metrics.mozilla.com/pentaho/content/pentaho-cdf-dd/Render?solution=metrics2&path=mozillians&file=mozillians.wcdf Mozillians dashboard] will track the size of that group and will also allow you to easily export the contact information for group members. You can export these contacts to ensure all your contributors are signed up.<br />
<br />
=Define Contribution Opportunities=<br />
<br />
Q: Can you point someone interested in contributing to your project to a list of available contribution opportunities?<br />
<br />
A: The opportunities will be seasonal, mostly happening between September and March, with a much stronger need in the Fall. <br />
We would love contributors to help hosting workshops, play the role of evangelists during campus events, hold tech talks at universities, act as a mentor for capstone projects, GSoC (Mozilla based GSoC projects), and attend career fairs with us. Ideally, we would need contributors with a deep knowledge of Mozilla technologies who also understand our recruiting needs and could speak about our various teams and projects. <br />
<br />
Attend conferences + interview <br />
- <br />
<br />
Suggestion: Look at what your team's needs are and what gaps you have in staffing to come up with a list of contribution opportunities. Capture those on a wiki page, in bugs, as role descriptions in Jobvite or whatever makes sense for your community.<br />
<br />
=Map Contribution Paths=<br />
<br />
Q: Are there clearly understood steps someone can follow to go from knowing nothing about your project to successfully contributing?<br />
<br />
Not at the moment, but we would love to include the Students Rep Program to promote Mozilla on a wider range of campuses. Ideally, those students will be somewhat technical and could help us organizing events at their respective universities. <br />
<br />
Until now, we've been relying on our full-time employees to sign up for tech talks and career fairs, but we understand that our engineers get extremely busy. <br />
<br />
- come up with a list of bugs per team that would be ideal for new students to work on. In short, how can we encourage students with prior technical expertise to take part in the project?<br><br />
- create some sort of process for new contributors to get up to speed with our college recruiting needs<br />
<br />
<br />
<br />
Suggestion: In addition to just documenting these steps, look for a simple 5-minute task that someone can take to get started (for example, signing up for Bugzilla if they are interested in coding) and also figure out where in the process you can add a mentor to help people.<br />
<br />
=Establish Goals and Metrics=<br />
<br />
Q: Can you measure participation or contributors today? If so, what metrics can you track? What goal or metric would you like to achieve for Q1? Alternatively, what metrics would you like to get in place for Q1?<br />
<br />
We don't have any external participation for our team at this point. <br />
<br />
Goals for Q1:<br />
1) Start collaborating with Student Reps on our various campus events (career fairs, hackathons, and so on)<br />
2) Identify what opportunities would be available for the Student Reps<br />
3) Identify location of potential contributors<br />
4) Solidify our college recruiting strategy for Fall '12 (career fairs, events, workshops)<br />
5) Identify Student Reps for our tier1 universities<br />
6) Recruit potential new Student Reps in the various open source clubs (see list from Vivien)<br />
<br />
<br />
<br />
Suggestion: Write down what you think would be helpful to track even if it isn't possible to get that data today. We'll work on implementing dashboards when we know what data we want.</div>Jgouliehttps://wiki.mozilla.org/index.php?title=Contribute/Recruiting&diff=402011Contribute/Recruiting2012-02-28T21:20:22Z<p>Jgoulie: /* Map Contribution Paths */</p>
<hr />
<div>=Steward=<br />
<br />
Julie Deroche <br><br />
Please note that this plan is mainly for College Recruiting<br />
<br />
=Identify Community=<br />
<br />
Q: Can you identify all of the contributors on your team (both paid-staff and volunteer-staff)?<br />
<br />
A: At this point, we don't have contributors in College Recruiting, but we could use help from contributors with the Capstone Projects, career fairs and some other students-run events, such as school hackathons. <br />
<br />
Suggestion: Use the [http://www.mozillians.org mozillians.org contributor directory] to help. Communicate through your team's channels and encourage people to sign up and group themselves with a common team tag. If you assign a group tag to all contributors on your project, the [https://metrics.mozilla.com/pentaho/content/pentaho-cdf-dd/Render?solution=metrics2&path=mozillians&file=mozillians.wcdf Mozillians dashboard] will track the size of that group and will also allow you to easily export the contact information for group members. You can export these contacts to ensure all your contributors are signed up.<br />
<br />
=Define Contribution Opportunities=<br />
<br />
Q: Can you point someone interested in contributing to your project to a list of available contribution opportunities?<br />
<br />
A: The opportunities will be seasonal, mostly happening between September and March, with a much stronger need in the Fall. <br />
We would love contributors to help hosting workshops, play the role of evangelists during campus events, hold tech talks at universities, act as a mentor for capstone projects, GSoC (Mozilla based GSoC projects), and attend career fairs with us. Ideally, we would need contributors with a deep knowledge of Mozilla technologies who also understand our recruiting needs and could speak about our various teams and projects. <br />
<br />
Attend conferences + interview <br />
- <br />
<br />
Suggestion: Look at what your team's needs are and what gaps you have in staffing to come up with a list of contribution opportunities. Capture those on a wiki page, in bugs, as role descriptions in Jobvite or whatever makes sense for your community.<br />
<br />
=Map Contribution Paths=<br />
<br />
Q: Are there clearly understood steps someone can follow to go from knowing nothing about your project to successfully contributing?<br />
<br />
Not at the moment, but we would love to include the Students Rep Program to promote Mozilla on a wider range of campuses. Ideally, those students will be somewhat technical and could help us organizing events at their respective universities. <br />
<br />
Until now, we've been relying on our full-time employees to sign up for tech talks and career fairs, but we understand that our engineers get extremely busy. <br />
<br />
- come up with a list of bugs per team that would be ideal for new students to work on. In short, how can we encourage students with prior technical expertise to take part in the project?<br><br />
- create some sort of process for new contributors to get up to speed with our college recruiting needs<br />
<br />
<br />
<br />
Suggestion: In addition to just documenting these steps, look for a simple 5-minute task that someone can take to get started (for example, signing up for Bugzilla if they are interested in coding) and also figure out where in the process you can add a mentor to help people.<br />
<br />
=Establish Goals and Metrics=<br />
<br />
Q: Can you measure participation or contributors today? If so, what metrics can you track? What goal or metric would you like to achieve for Q1? Alternatively, what metrics would you like to get in place for Q1?<br />
<br />
A: Participation is only measured internally at this point, and we look at who in the organization supports our various events. <br />
<br />
A: College Recruiting has two main goals to involve the contributor community:<br />
<br />
1) Define great contributor mentor for Capstone project<br><br />
2) Engage contributors to represent Mozilla at career fairs or college events<br />
<br />
Suggestion: Write down what you think would be helpful to track even if it isn't possible to get that data today. We'll work on implementing dashboards when we know what data we want.</div>Jgouliehttps://wiki.mozilla.org/index.php?title=Contribute/Recruiting&diff=402010Contribute/Recruiting2012-02-28T21:19:59Z<p>Jgoulie: /* Map Contribution Paths */</p>
<hr />
<div>=Steward=<br />
<br />
Julie Deroche <br><br />
Please note that this plan is mainly for College Recruiting<br />
<br />
=Identify Community=<br />
<br />
Q: Can you identify all of the contributors on your team (both paid-staff and volunteer-staff)?<br />
<br />
A: At this point, we don't have contributors in College Recruiting, but we could use help from contributors with the Capstone Projects, career fairs and some other students-run events, such as school hackathons. <br />
<br />
Suggestion: Use the [http://www.mozillians.org mozillians.org contributor directory] to help. Communicate through your team's channels and encourage people to sign up and group themselves with a common team tag. If you assign a group tag to all contributors on your project, the [https://metrics.mozilla.com/pentaho/content/pentaho-cdf-dd/Render?solution=metrics2&path=mozillians&file=mozillians.wcdf Mozillians dashboard] will track the size of that group and will also allow you to easily export the contact information for group members. You can export these contacts to ensure all your contributors are signed up.<br />
<br />
=Define Contribution Opportunities=<br />
<br />
Q: Can you point someone interested in contributing to your project to a list of available contribution opportunities?<br />
<br />
A: The opportunities will be seasonal, mostly happening between September and March, with a much stronger need in the Fall. <br />
We would love contributors to help hosting workshops, play the role of evangelists during campus events, hold tech talks at universities, act as a mentor for capstone projects, GSoC (Mozilla based GSoC projects), and attend career fairs with us. Ideally, we would need contributors with a deep knowledge of Mozilla technologies who also understand our recruiting needs and could speak about our various teams and projects. <br />
<br />
Attend conferences + interview <br />
- <br />
<br />
Suggestion: Look at what your team's needs are and what gaps you have in staffing to come up with a list of contribution opportunities. Capture those on a wiki page, in bugs, as role descriptions in Jobvite or whatever makes sense for your community.<br />
<br />
=Map Contribution Paths=<br />
<br />
Q: Are there clearly understood steps someone can follow to go from knowing nothing about your project to successfully contributing?<br />
<br />
Not at the moment, but we would love to include the Students Rep Program to promote Mozilla on a wider range of campuses. Ideally, those students will be somewhat technical and could help us organizing events at their respective universities. <br />
<br />
Until now, we've been relying on our full-time employees to sign up for tech talks and career fairs, but we understand that our engineers get extremely busy. <br />
<br />
- come up with a list of bugs per team that would be ideal for new students to work on. In short, how can we encourage students with prior technical expertise to take part in the project?<br />
- create some sort of process for new contributors to get up to speed with our college recruiting needs<br />
<br />
<br />
<br />
Suggestion: In addition to just documenting these steps, look for a simple 5-minute task that someone can take to get started (for example, signing up for Bugzilla if they are interested in coding) and also figure out where in the process you can add a mentor to help people.<br />
<br />
=Establish Goals and Metrics=<br />
<br />
Q: Can you measure participation or contributors today? If so, what metrics can you track? What goal or metric would you like to achieve for Q1? Alternatively, what metrics would you like to get in place for Q1?<br />
<br />
A: Participation is only measured internally at this point, and we look at who in the organization supports our various events. <br />
<br />
A: College Recruiting has two main goals to involve the contributor community:<br />
<br />
1) Define great contributor mentor for Capstone project<br><br />
2) Engage contributors to represent Mozilla at career fairs or college events<br />
<br />
Suggestion: Write down what you think would be helpful to track even if it isn't possible to get that data today. We'll work on implementing dashboards when we know what data we want.</div>Jgouliehttps://wiki.mozilla.org/index.php?title=Contribute/Recruiting&diff=401999Contribute/Recruiting2012-02-28T21:11:38Z<p>Jgoulie: /* Define Contribution Opportunities */</p>
<hr />
<div>=Steward=<br />
<br />
Julie Deroche <br><br />
Please note that this plan is mainly for College Recruiting<br />
<br />
=Identify Community=<br />
<br />
Q: Can you identify all of the contributors on your team (both paid-staff and volunteer-staff)?<br />
<br />
A: At this point, we don't have contributors in College Recruiting, but we could use help from contributors with the Capstone Projects, career fairs and some other students-run events, such as school hackathons. <br />
<br />
Suggestion: Use the [http://www.mozillians.org mozillians.org contributor directory] to help. Communicate through your team's channels and encourage people to sign up and group themselves with a common team tag. If you assign a group tag to all contributors on your project, the [https://metrics.mozilla.com/pentaho/content/pentaho-cdf-dd/Render?solution=metrics2&path=mozillians&file=mozillians.wcdf Mozillians dashboard] will track the size of that group and will also allow you to easily export the contact information for group members. You can export these contacts to ensure all your contributors are signed up.<br />
<br />
=Define Contribution Opportunities=<br />
<br />
Q: Can you point someone interested in contributing to your project to a list of available contribution opportunities?<br />
<br />
A: The opportunities will be seasonal, mostly happening between September and March, with a much stronger need in the Fall. <br />
We would love contributors to help hosting workshops, play the role of evangelists during campus events, hold tech talks at universities, act as a mentor for capstone projects, GSoC (Mozilla based GSoC projects), and attend career fairs with us. Ideally, we would need contributors with a deep knowledge of Mozilla technologies who also understand our recruiting needs and could speak about our various teams and projects. <br />
<br />
Attend conferences + interview <br />
- <br />
<br />
Suggestion: Look at what your team's needs are and what gaps you have in staffing to come up with a list of contribution opportunities. Capture those on a wiki page, in bugs, as role descriptions in Jobvite or whatever makes sense for your community.<br />
<br />
=Map Contribution Paths=<br />
<br />
Q: Are there clearly understood steps someone can follow to go from knowing nothing about your project to successfully contributing?<br />
<br />
A: Here are the steps:<br />
<br />
1) Go to College Recruiting wiki page to find out the project descriptions;<br />
<br />
2) Sign up through the form<br />
<br />
3) Someone from college recruiting will reach out to you if you are qualified.<br />
<br />
4) Enroll into the contributor system<br />
<br />
5) Have monthly meeting on summaries and action plans<br />
<br />
Suggestion: In addition to just documenting these steps, look for a simple 5-minute task that someone can take to get started (for example, signing up for Bugzilla if they are interested in coding) and also figure out where in the process you can add a mentor to help people.<br />
<br />
=Establish Goals and Metrics=<br />
<br />
Q: Can you measure participation or contributors today? If so, what metrics can you track? What goal or metric would you like to achieve for Q1? Alternatively, what metrics would you like to get in place for Q1?<br />
<br />
A: Participation is only measured internally at this point, and we look at who in the organization supports our various events. <br />
<br />
A: College Recruiting has two main goals to involve the contributor community:<br />
<br />
1) Define great contributor mentor for Capstone project<br><br />
2) Engage contributors to represent Mozilla at career fairs or college events<br />
<br />
Suggestion: Write down what you think would be helpful to track even if it isn't possible to get that data today. We'll work on implementing dashboards when we know what data we want.</div>Jgouliehttps://wiki.mozilla.org/index.php?title=Contribute/Recruiting&diff=401996Contribute/Recruiting2012-02-28T21:08:00Z<p>Jgoulie: /* Identify Community */</p>
<hr />
<div>=Steward=<br />
<br />
Julie Deroche <br><br />
Please note that this plan is mainly for College Recruiting<br />
<br />
=Identify Community=<br />
<br />
Q: Can you identify all of the contributors on your team (both paid-staff and volunteer-staff)?<br />
<br />
A: At this point, we don't have contributors in College Recruiting, but we could use help from contributors with the Capstone Projects, career fairs and some other students-run events, such as school hackathons. <br />
<br />
Suggestion: Use the [http://www.mozillians.org mozillians.org contributor directory] to help. Communicate through your team's channels and encourage people to sign up and group themselves with a common team tag. If you assign a group tag to all contributors on your project, the [https://metrics.mozilla.com/pentaho/content/pentaho-cdf-dd/Render?solution=metrics2&path=mozillians&file=mozillians.wcdf Mozillians dashboard] will track the size of that group and will also allow you to easily export the contact information for group members. You can export these contacts to ensure all your contributors are signed up.<br />
<br />
=Define Contribution Opportunities=<br />
<br />
Q: Can you point someone interested in contributing to your project to a list of available contribution opportunities?<br />
<br />
A: The opportunities will be seasonal, mostly happening between September and March, with a much stronger need in the Fall. <br />
<br />
We would love contributors to help hosting workshops, hold tech talks at universities, act as a mentor for capstone projects, GSoC (Mozilla based GSoC projects), and attend career fairs with us. <br />
<br />
Attend conferences + interview <br />
- <br />
<br />
Suggestion: Look at what your team's needs are and what gaps you have in staffing to come up with a list of contribution opportunities. Capture those on a wiki page, in bugs, as role descriptions in Jobvite or whatever makes sense for your community.<br />
<br />
=Map Contribution Paths=<br />
<br />
Q: Are there clearly understood steps someone can follow to go from knowing nothing about your project to successfully contributing?<br />
<br />
A: Here are the steps:<br />
<br />
1) Go to College Recruiting wiki page to find out the project descriptions;<br />
<br />
2) Sign up through the form<br />
<br />
3) Someone from college recruiting will reach out to you if you are qualified.<br />
<br />
4) Enroll into the contributor system<br />
<br />
5) Have monthly meeting on summaries and action plans<br />
<br />
Suggestion: In addition to just documenting these steps, look for a simple 5-minute task that someone can take to get started (for example, signing up for Bugzilla if they are interested in coding) and also figure out where in the process you can add a mentor to help people.<br />
<br />
=Establish Goals and Metrics=<br />
<br />
Q: Can you measure participation or contributors today? If so, what metrics can you track? What goal or metric would you like to achieve for Q1? Alternatively, what metrics would you like to get in place for Q1?<br />
<br />
A: Participation is only measured internally at this point, and we look at who in the organization supports our various events. <br />
<br />
A: College Recruiting has two main goals to involve the contributor community:<br />
<br />
1) Define great contributor mentor for Capstone project<br><br />
2) Engage contributors to represent Mozilla at career fairs or college events<br />
<br />
Suggestion: Write down what you think would be helpful to track even if it isn't possible to get that data today. We'll work on implementing dashboards when we know what data we want.</div>Jgouliehttps://wiki.mozilla.org/index.php?title=Contribute/Recruiting&diff=401995Contribute/Recruiting2012-02-28T21:05:52Z<p>Jgoulie: /* Steward */</p>
<hr />
<div>=Steward=<br />
<br />
Julie Deroche <br><br />
Please note that this plan is mainly for College Recruiting<br />
<br />
=Identify Community=<br />
<br />
Q: Can you identify all of the contributors on your team (both paid-staff and volunteer-staff)?<br />
<br />
A: At this point, we don't have contributors in Recruiting, but we're looking at increasing our volunteer base for Capstone projects and also providing referrals for the Mozilla Project.<br />
People who could contribute and <br />
- interview process <br />
<br />
Suggestion: Use the [http://www.mozillians.org mozillians.org contributor directory] to help. Communicate through your team's channels and encourage people to sign up and group themselves with a common team tag. If you assign a group tag to all contributors on your project, the [https://metrics.mozilla.com/pentaho/content/pentaho-cdf-dd/Render?solution=metrics2&path=mozillians&file=mozillians.wcdf Mozillians dashboard] will track the size of that group and will also allow you to easily export the contact information for group members. You can export these contacts to ensure all your contributors are signed up.<br />
<br />
=Define Contribution Opportunities=<br />
<br />
Q: Can you point someone interested in contributing to your project to a list of available contribution opportunities?<br />
<br />
A: The opportunities will be seasonal, mostly happening between September and March, with a much stronger need in the Fall. <br />
<br />
We would love contributors to help hosting workshops, hold tech talks at universities, act as a mentor for capstone projects, GSoC (Mozilla based GSoC projects), and attend career fairs with us. <br />
<br />
Attend conferences + interview <br />
- <br />
<br />
Suggestion: Look at what your team's needs are and what gaps you have in staffing to come up with a list of contribution opportunities. Capture those on a wiki page, in bugs, as role descriptions in Jobvite or whatever makes sense for your community.<br />
<br />
=Map Contribution Paths=<br />
<br />
Q: Are there clearly understood steps someone can follow to go from knowing nothing about your project to successfully contributing?<br />
<br />
A: Here are the steps:<br />
<br />
1) Go to College Recruiting wiki page to find out the project descriptions;<br />
<br />
2) Sign up through the form<br />
<br />
3) Someone from college recruiting will reach out to you if you are qualified.<br />
<br />
4) Enroll into the contributor system<br />
<br />
5) Have monthly meeting on summaries and action plans<br />
<br />
Suggestion: In addition to just documenting these steps, look for a simple 5-minute task that someone can take to get started (for example, signing up for Bugzilla if they are interested in coding) and also figure out where in the process you can add a mentor to help people.<br />
<br />
=Establish Goals and Metrics=<br />
<br />
Q: Can you measure participation or contributors today? If so, what metrics can you track? What goal or metric would you like to achieve for Q1? Alternatively, what metrics would you like to get in place for Q1?<br />
<br />
A: Participation is only measured internally at this point, and we look at who in the organization supports our various events. <br />
<br />
A: College Recruiting has two main goals to involve the contributor community:<br />
<br />
1) Define great contributor mentor for Capstone project<br><br />
2) Engage contributors to represent Mozilla at career fairs or college events<br />
<br />
Suggestion: Write down what you think would be helpful to track even if it isn't possible to get that data today. We'll work on implementing dashboards when we know what data we want.</div>Jgouliehttps://wiki.mozilla.org/index.php?title=Contribute/Recruiting&diff=401994Contribute/Recruiting2012-02-28T21:05:25Z<p>Jgoulie: /* Steward */</p>
<hr />
<div>=Steward=<br />
<br />
Julie Deroche<br />
Please note that this plan is mainly for College Recruiting<br />
<br />
=Identify Community=<br />
<br />
Q: Can you identify all of the contributors on your team (both paid-staff and volunteer-staff)?<br />
<br />
A: At this point, we don't have contributors in Recruiting, but we're looking at increasing our volunteer base for Capstone projects and also providing referrals for the Mozilla Project.<br />
People who could contribute and <br />
- interview process <br />
<br />
Suggestion: Use the [http://www.mozillians.org mozillians.org contributor directory] to help. Communicate through your team's channels and encourage people to sign up and group themselves with a common team tag. If you assign a group tag to all contributors on your project, the [https://metrics.mozilla.com/pentaho/content/pentaho-cdf-dd/Render?solution=metrics2&path=mozillians&file=mozillians.wcdf Mozillians dashboard] will track the size of that group and will also allow you to easily export the contact information for group members. You can export these contacts to ensure all your contributors are signed up.<br />
<br />
=Define Contribution Opportunities=<br />
<br />
Q: Can you point someone interested in contributing to your project to a list of available contribution opportunities?<br />
<br />
A: The opportunities will be seasonal, mostly happening between September and March, with a much stronger need in the Fall. <br />
<br />
We would love contributors to help hosting workshops, hold tech talks at universities, act as a mentor for capstone projects, GSoC (Mozilla based GSoC projects), and attend career fairs with us. <br />
<br />
Attend conferences + interview <br />
- <br />
<br />
Suggestion: Look at what your team's needs are and what gaps you have in staffing to come up with a list of contribution opportunities. Capture those on a wiki page, in bugs, as role descriptions in Jobvite or whatever makes sense for your community.<br />
<br />
=Map Contribution Paths=<br />
<br />
Q: Are there clearly understood steps someone can follow to go from knowing nothing about your project to successfully contributing?<br />
<br />
A: Here are the steps:<br />
<br />
1) Go to College Recruiting wiki page to find out the project descriptions;<br />
<br />
2) Sign up through the form<br />
<br />
3) Someone from college recruiting will reach out to you if you are qualified.<br />
<br />
4) Enroll into the contributor system<br />
<br />
5) Have monthly meeting on summaries and action plans<br />
<br />
Suggestion: In addition to just documenting these steps, look for a simple 5-minute task that someone can take to get started (for example, signing up for Bugzilla if they are interested in coding) and also figure out where in the process you can add a mentor to help people.<br />
<br />
=Establish Goals and Metrics=<br />
<br />
Q: Can you measure participation or contributors today? If so, what metrics can you track? What goal or metric would you like to achieve for Q1? Alternatively, what metrics would you like to get in place for Q1?<br />
<br />
A: Participation is only measured internally at this point, and we look at who in the organization supports our various events. <br />
<br />
A: College Recruiting has two main goals to involve the contributor community:<br />
<br />
1) Define great contributor mentor for Capstone project<br><br />
2) Engage contributors to represent Mozilla at career fairs or college events<br />
<br />
Suggestion: Write down what you think would be helpful to track even if it isn't possible to get that data today. We'll work on implementing dashboards when we know what data we want.</div>Jgouliehttps://wiki.mozilla.org/index.php?title=Contribute/Recruiting&diff=392632Contribute/Recruiting2012-01-31T23:40:51Z<p>Jgoulie: /* Define Contribution Opportunities */</p>
<hr />
<div>=Steward=<br />
<br />
Julie Deroche<br />
<br />
=Identify Community=<br />
<br />
Q: Can you identify all of the contributors on your team (both paid-staff and volunteer-staff)?<br />
<br />
A: At this point, we don't have contributors in Recruiting, but we're looking at increasing our volunteer base for Capstone projects and also providing referrals for the Mozilla Project.<br />
People who could contribute and <br />
- interview process <br />
<br />
Suggestion: Use the [http://www.mozillians.org mozillians.org contributor directory] to help. Communicate through your team's channels and encourage people to sign up and group themselves with a common team tag. If you assign a group tag to all contributors on your project, the [https://metrics.mozilla.com/pentaho/content/pentaho-cdf-dd/Render?solution=metrics2&path=mozillians&file=mozillians.wcdf Mozillians dashboard] will track the size of that group and will also allow you to easily export the contact information for group members. You can export these contacts to ensure all your contributors are signed up.<br />
<br />
=Define Contribution Opportunities=<br />
<br />
Q: Can you point someone interested in contributing to your project to a list of available contribution opportunities?<br />
<br />
A: The opportunities will be seasonal, mostly happening between September and March, with a much stronger need in the Fall. <br />
<br />
We would love contributors to help hosting workshops, hold tech talks at universities, act as a mentor for capstone projects, GSoC (Mozilla based GSoC projects), and attend career fairs with us. <br />
<br />
Attend conferences + interview <br />
- <br />
<br />
Suggestion: Look at what your team's needs are and what gaps you have in staffing to come up with a list of contribution opportunities. Capture those on a wiki page, in bugs, as role descriptions in Jobvite or whatever makes sense for your community.<br />
<br />
=Map Contribution Paths=<br />
<br />
Q: Are there clearly understood steps someone can follow to go from knowing nothing about your project to successfully contributing?<br />
<br />
A: Here are the steps:<br />
<br />
1) Go to College Recruiting wiki page to find out the project descriptions;<br />
<br />
2) Sign up through the form<br />
<br />
3) Someone from college recruiting will reach out to you if you are qualified.<br />
<br />
4) Enroll into the contributor system<br />
<br />
5) Have monthly meeting on summaries and action plans<br />
<br />
Suggestion: In addition to just documenting these steps, look for a simple 5-minute task that someone can take to get started (for example, signing up for Bugzilla if they are interested in coding) and also figure out where in the process you can add a mentor to help people.<br />
<br />
=Establish Goals and Metrics=<br />
<br />
Q: Can you measure participation or contributors today? If so, what metrics can you track? What goal or metric would you like to achieve for Q1? Alternatively, what metrics would you like to get in place for Q1?<br />
<br />
A: Participation is only measured internally at this point, and we look at who in the organization supports our various events. <br />
<br />
A: College Recruiting has two main goals to involve the contributor community:<br />
<br />
1) Define great contributor mentor for Capstone project<br><br />
2) Engage contributors to represent Mozilla at career fairs or college events<br />
<br />
Suggestion: Write down what you think would be helpful to track even if it isn't possible to get that data today. We'll work on implementing dashboards when we know what data we want.</div>Jgouliehttps://wiki.mozilla.org/index.php?title=Contribute/Recruiting&diff=392630Contribute/Recruiting2012-01-31T23:34:31Z<p>Jgoulie: /* Identify Community */</p>
<hr />
<div>=Steward=<br />
<br />
Julie Deroche<br />
<br />
=Identify Community=<br />
<br />
Q: Can you identify all of the contributors on your team (both paid-staff and volunteer-staff)?<br />
<br />
A: At this point, we don't have contributors in Recruiting, but we're looking at increasing our volunteer base for Capstone projects and also providing referrals for the Mozilla Project.<br />
People who could contribute and <br />
- interview process <br />
<br />
Suggestion: Use the [http://www.mozillians.org mozillians.org contributor directory] to help. Communicate through your team's channels and encourage people to sign up and group themselves with a common team tag. If you assign a group tag to all contributors on your project, the [https://metrics.mozilla.com/pentaho/content/pentaho-cdf-dd/Render?solution=metrics2&path=mozillians&file=mozillians.wcdf Mozillians dashboard] will track the size of that group and will also allow you to easily export the contact information for group members. You can export these contacts to ensure all your contributors are signed up.<br />
<br />
=Define Contribution Opportunities=<br />
<br />
Q: Can you point someone interested in contributing to your project to a list of available contribution opportunities?<br />
<br />
A: We would love contributors to help hosting workshops, hold tech talks at universities, act as a mentor for capstone projects, GSoC (Mozilla based GSoC projects), and attend career fairs with us. <br />
<br />
Suggestion: Look at what your team's needs are and what gaps you have in staffing to come up with a list of contribution opportunities. Capture those on a wiki page, in bugs, as role descriptions in Jobvite or whatever makes sense for your community.<br />
<br />
=Map Contribution Paths=<br />
<br />
Q: Are there clearly understood steps someone can follow to go from knowing nothing about your project to successfully contributing?<br />
<br />
A: Here are the steps:<br />
<br />
1) Go to College Recruiting wiki page to find out the project descriptions;<br />
<br />
2) Sign up through the form<br />
<br />
3) Someone from college recruiting will reach out to you if you are qualified.<br />
<br />
4) Enroll into the contributor system<br />
<br />
5) Have monthly meeting on summaries and action plans<br />
<br />
Suggestion: In addition to just documenting these steps, look for a simple 5-minute task that someone can take to get started (for example, signing up for Bugzilla if they are interested in coding) and also figure out where in the process you can add a mentor to help people.<br />
<br />
=Establish Goals and Metrics=<br />
<br />
Q: Can you measure participation or contributors today? If so, what metrics can you track? What goal or metric would you like to achieve for Q1? Alternatively, what metrics would you like to get in place for Q1?<br />
<br />
A: Participation is only measured internally at this point, and we look at who in the organization supports our various events. <br />
<br />
A: College Recruiting has two main goals to involve the contributor community:<br />
<br />
1) Define great contributor mentor for Capstone project<br><br />
2) Engage contributors to represent Mozilla at career fairs or college events<br />
<br />
Suggestion: Write down what you think would be helpful to track even if it isn't possible to get that data today. We'll work on implementing dashboards when we know what data we want.</div>Jgouliehttps://wiki.mozilla.org/index.php?title=Contribute/Recruiting&diff=392625Contribute/Recruiting2012-01-31T22:54:00Z<p>Jgoulie: /* Establish Goals and Metrics */</p>
<hr />
<div>=Steward=<br />
<br />
Julie Deroche<br />
<br />
=Identify Community=<br />
<br />
Q: Can you identify all of the contributors on your team (both paid-staff and volunteer-staff)?<br />
<br />
A: At this point, we don't have contributors in Recruiting, but we're looking at increasing our volunteer base for Capstone projects and also providing referrals for the Mozilla Project. <br />
<br />
Suggestion: Use the [http://www.mozillians.org mozillians.org contributor directory] to help. Communicate through your team's channels and encourage people to sign up and group themselves with a common team tag. If you assign a group tag to all contributors on your project, the [https://metrics.mozilla.com/pentaho/content/pentaho-cdf-dd/Render?solution=metrics2&path=mozillians&file=mozillians.wcdf Mozillians dashboard] will track the size of that group and will also allow you to easily export the contact information for group members. You can export these contacts to ensure all your contributors are signed up.<br />
<br />
=Define Contribution Opportunities=<br />
<br />
Q: Can you point someone interested in contributing to your project to a list of available contribution opportunities?<br />
<br />
A: We would love contributors to help hosting workshops, hold tech talks at universities, act as a mentor for capstone projects, GSoC (Mozilla based GSoC projects), and attend career fairs with us. <br />
<br />
Suggestion: Look at what your team's needs are and what gaps you have in staffing to come up with a list of contribution opportunities. Capture those on a wiki page, in bugs, as role descriptions in Jobvite or whatever makes sense for your community.<br />
<br />
=Map Contribution Paths=<br />
<br />
Q: Are there clearly understood steps someone can follow to go from knowing nothing about your project to successfully contributing?<br />
<br />
A: Here are the steps:<br />
<br />
1) Go to College Recruiting wiki page to find out the project descriptions;<br />
<br />
2) Sign up through the form<br />
<br />
3) Someone from college recruiting will reach out to you if you are qualified.<br />
<br />
4) Enroll into the contributor system<br />
<br />
5) Have monthly meeting on summaries and action plans<br />
<br />
Suggestion: In addition to just documenting these steps, look for a simple 5-minute task that someone can take to get started (for example, signing up for Bugzilla if they are interested in coding) and also figure out where in the process you can add a mentor to help people.<br />
<br />
=Establish Goals and Metrics=<br />
<br />
Q: Can you measure participation or contributors today? If so, what metrics can you track? What goal or metric would you like to achieve for Q1? Alternatively, what metrics would you like to get in place for Q1?<br />
<br />
A: Participation is only measured internally at this point, and we look at who in the organization supports our various events. <br />
<br />
A: College Recruiting has two main goals to involve the contributor community:<br />
<br />
1) Define great contributor mentor for Capstone project<br><br />
2) Engage contributors to represent Mozilla at career fairs or college events<br />
<br />
Suggestion: Write down what you think would be helpful to track even if it isn't possible to get that data today. We'll work on implementing dashboards when we know what data we want.</div>Jgouliehttps://wiki.mozilla.org/index.php?title=Contribute/Recruiting&diff=392613Contribute/Recruiting2012-01-31T22:38:00Z<p>Jgoulie: /* Define Contribution Opportunities */</p>
<hr />
<div>=Steward=<br />
<br />
Julie Deroche<br />
<br />
=Identify Community=<br />
<br />
Q: Can you identify all of the contributors on your team (both paid-staff and volunteer-staff)?<br />
<br />
A: At this point, we don't have contributors in Recruiting, but we're looking at increasing our volunteer base for Capstone projects and also providing referrals for the Mozilla Project. <br />
<br />
Suggestion: Use the [http://www.mozillians.org mozillians.org contributor directory] to help. Communicate through your team's channels and encourage people to sign up and group themselves with a common team tag. If you assign a group tag to all contributors on your project, the [https://metrics.mozilla.com/pentaho/content/pentaho-cdf-dd/Render?solution=metrics2&path=mozillians&file=mozillians.wcdf Mozillians dashboard] will track the size of that group and will also allow you to easily export the contact information for group members. You can export these contacts to ensure all your contributors are signed up.<br />
<br />
=Define Contribution Opportunities=<br />
<br />
Q: Can you point someone interested in contributing to your project to a list of available contribution opportunities?<br />
<br />
A: We would love contributors to help hosting workshops, hold tech talks at universities, act as a mentor for capstone projects, GSoC (Mozilla based GSoC projects), and attend career fairs with us. <br />
<br />
Suggestion: Look at what your team's needs are and what gaps you have in staffing to come up with a list of contribution opportunities. Capture those on a wiki page, in bugs, as role descriptions in Jobvite or whatever makes sense for your community.<br />
<br />
=Map Contribution Paths=<br />
<br />
Q: Are there clearly understood steps someone can follow to go from knowing nothing about your project to successfully contributing?<br />
<br />
A: Here are the steps:<br />
<br />
1) Go to College Recruiting wiki page to find out the project descriptions;<br />
<br />
2) Sign up through the form<br />
<br />
3) Someone from college recruiting will reach out to you if you are qualified.<br />
<br />
4) Enroll into the contributor system<br />
<br />
5) Have monthly meeting on summaries and action plans<br />
<br />
Suggestion: In addition to just documenting these steps, look for a simple 5-minute task that someone can take to get started (for example, signing up for Bugzilla if they are interested in coding) and also figure out where in the process you can add a mentor to help people.<br />
<br />
=Establish Goals and Metrics=<br />
<br />
Q: Can you measure participation or contributors today? If so, what metrics can you track? What goal or metric would you like to achieve for Q1? Alternatively, what metrics would you like to get in place for Q1?<br />
<br />
A: College Recruiting has two main goals to involve the contributor community:<br />
<br />
1) Define great contributor mentor for Capstone project<br />
2) Engage contributors to represent Mozilla at career fairs or college events<br />
<br />
Suggestion: Write down what you think would be helpful to track even if it isn't possible to get that data today. We'll work on implementing dashboards when we know what data we want.</div>Jgouliehttps://wiki.mozilla.org/index.php?title=Contribute/Recruiting&diff=392610Contribute/Recruiting2012-01-31T22:36:02Z<p>Jgoulie: /* Identify Community */</p>
<hr />
<div>=Steward=<br />
<br />
Julie Deroche<br />
<br />
=Identify Community=<br />
<br />
Q: Can you identify all of the contributors on your team (both paid-staff and volunteer-staff)?<br />
<br />
A: At this point, we don't have contributors in Recruiting, but we're looking at increasing our volunteer base for Capstone projects and also providing referrals for the Mozilla Project. <br />
<br />
Suggestion: Use the [http://www.mozillians.org mozillians.org contributor directory] to help. Communicate through your team's channels and encourage people to sign up and group themselves with a common team tag. If you assign a group tag to all contributors on your project, the [https://metrics.mozilla.com/pentaho/content/pentaho-cdf-dd/Render?solution=metrics2&path=mozillians&file=mozillians.wcdf Mozillians dashboard] will track the size of that group and will also allow you to easily export the contact information for group members. You can export these contacts to ensure all your contributors are signed up.<br />
<br />
=Define Contribution Opportunities=<br />
<br />
Q: Can you point someone interested in contributing to your project to a list of available contribution opportunities?<br />
<br />
A: Yes, we plan to create a section on College recruiting wiki page<br />
<br />
Suggestion: Look at what your team's needs are and what gaps you have in staffing to come up with a list of contribution opportunities. Capture those on a wiki page, in bugs, as role descriptions in Jobvite or whatever makes sense for your community.<br />
<br />
=Map Contribution Paths=<br />
<br />
Q: Are there clearly understood steps someone can follow to go from knowing nothing about your project to successfully contributing?<br />
<br />
A: Here are the steps:<br />
<br />
1) Go to College Recruiting wiki page to find out the project descriptions;<br />
<br />
2) Sign up through the form<br />
<br />
3) Someone from college recruiting will reach out to you if you are qualified.<br />
<br />
4) Enroll into the contributor system<br />
<br />
5) Have monthly meeting on summaries and action plans<br />
<br />
Suggestion: In addition to just documenting these steps, look for a simple 5-minute task that someone can take to get started (for example, signing up for Bugzilla if they are interested in coding) and also figure out where in the process you can add a mentor to help people.<br />
<br />
=Establish Goals and Metrics=<br />
<br />
Q: Can you measure participation or contributors today? If so, what metrics can you track? What goal or metric would you like to achieve for Q1? Alternatively, what metrics would you like to get in place for Q1?<br />
<br />
A: College Recruiting has two main goals to involve the contributor community:<br />
<br />
1) Define great contributor mentor for Capstone project<br />
2) Engage contributors to represent Mozilla at career fairs or college events<br />
<br />
Suggestion: Write down what you think would be helpful to track even if it isn't possible to get that data today. We'll work on implementing dashboards when we know what data we want.</div>Jgouliehttps://wiki.mozilla.org/index.php?title=Community_Workshops&diff=374314Community Workshops2011-11-30T00:49:34Z<p>Jgoulie: </p>
<hr />
<div>*<b>Overview & Goal</b>: Give the community access to parts of the Mozilla projects other than l10n, through a series of workshops that will give new volunteers the appropriate training and tools to contribute to Mozilla. <br />
<br />
*<b>Audience</b>: We will develop this initial pilot program with Mozilla Tunisia and hopefully roll it out to other interested communities. Mozilla Tunisia will be launching a university starting in Dec. 2011 so hopefully we could target those workshops to students as early as Q1 2012. <br />
<br />
*<b>Process</b>:<br />
**Identify technical leads within Mozilla Tunisia that would be interested in owning a specific workshop (Q4 2011)<br />
**Assess overall technical knowledge for each workshop lead and offer appropriate training if needed. We need to give them the technical expertise to then run their own community, based on interest and fit within the organization (Q4 2011)<br />
**Create an internal Engineering Committee to assist with the development of those workshops (Q4 2011)<br />
**Start developing workshops (Q4 2011 / Q1 2012)<br />
**Launch the first workshop in Q1 2012 ; followed by another 4-5 sessions<br />
**Bring guidance to the community and clear milestones to keep the community engaged afterward (2012)<br />
**Create clear processes on how to get involved and opportunities available for each team/workshop (2011-12)<br />
<br />
*<b>Potential ideas for the workshops</b>:<br />
**SUMO (Michelle Luna)<br />
**QA (Tony Chung, Marcia Knous, and Stephen Donner)<br />
**IT (puppet automation) (mrz)<br />
**Web Security (Michael Coates)<br />
**Labs (BrowserID, Popcorn Maker)<br />
**Jetpack & add-on development<br />
**Engineering (FFx and Platform)<br />
<br />
*<b>Tools and Support</b>:<br />
**Have a clear channel of distribution and one central location for community members to have easy access to resources<br />
**Build an Engineering Committee<br />
**Series of Tutorial videos (Rainer)<br />
**Provide clear documentation<br />
**Have some sort of toolkit ready to be installed; one VM per workshop with all the right tools and environment, and make it easily accessible. <br />
**Come up with a set of expectations and projects available for the community each quarter, leveled by priorities (provide more structure overall)</div>Jgouliehttps://wiki.mozilla.org/index.php?title=Community_Workshops&diff=374313Community Workshops2011-11-30T00:48:48Z<p>Jgoulie: </p>
<hr />
<div>*<b>Overview & Goal</b>: Give the community access to parts of the Mozilla projects other than l10n, through a series of workshops that will give new volunteers the appropriate training and tools to contribute to Mozilla. <br />
<br />
*<b>Audience</b>: We will develop this initial pilot program with Mozilla Tunisia and hopefully roll it out to other interested communities. Mozilla Tunisia will be launching a university starting in Dec. 2011 so hopefully we could target those workshops to students as early as Q1 2012. <br />
<br />
*<b>Process</b>:<br />
**Identify technical leads within Mozilla Tunisia that would be interested in owning a specific workshop (Q4 2011)<br />
**Assess overall technical knowledge for each workshop lead and offer appropriate training if needed. We need to give them the technical expertise to then run their own community, based on interest and fit within the organization (Q4 2011)<br />
**Create an internal Engineering Committee to assist with the development of those workshops (Q4 2011)<br />
**Start developing workshops (Q4 2011 / Q1 2012)<br />
**Launch the first workshop in Q1 2012 ; followed by another 4-5 sessions<br />
**Bring guidance to the community and clear milestones to keep the community engaged afterward (2012)<br />
**Create clear processes on how to get involved and opportunities available for each team/workshop (2011-12)<br />
<br />
*<b>Potential ideas for the workshops</b>:<br />
**SUMO (Michelle Luna)<br />
**QA (Tony Chung, Marcia Knous, and Stephen Donner)<br />
**IT ( puppet automation) (mrz)<br />
**Web Security (Michael Coates)<br />
**Labs (BrowserID, Popcorn Maker)<br />
**Jetpack & add-on development<br />
**Engineering (FFx and Platform)<br />
<br />
*<b>Tools and Support</b>:<br />
**Have a clear channel of distribution and one central location for community members to have easy access to resources<br />
**Build an Engineering Committee<br />
**Series of Tutorial videos (Rainer)<br />
**Provide clear documentation<br />
**Have some sort of toolkit ready to be installed; one VM per workshop with all the right tools and environment, and make it easily accessible. <br />
**Come up with a set of expectations and projects available for the community each quarter, leveled by priorities (provide more structure overall)</div>Jgouliehttps://wiki.mozilla.org/index.php?title=Community_Workshops&diff=374290Community Workshops2011-11-29T23:14:11Z<p>Jgoulie: </p>
<hr />
<div>*<b>Overview & Goal</b>: Give the community access to parts of the Mozilla projects other than l10n, through a series of workshops that will give new volunteers the appropriate training and tools to contribute to Mozilla. <br />
<br />
*<b>Audience</b>: We will develop this initial pilot program with Mozilla Tunisia and hopefully roll it out to other interested communities. Mozilla Tunisia will be launching a university starting in Dec. 2011 so hopefully we could target those workshops to students as early as Q1 2012. <br />
<br />
*<b>Process</b>:<br />
**Identify technical leads within Mozilla Tunisia that would be interested in owning a specific workshop (Q4 2011)<br />
**Assess overall technical knowledge for each workshop lead and offer appropriate training if needed. We need to give them the technical expertise to then run their own community, based on interest and fit within the organization (Q4 2011)<br />
**Create an internal Engineering Committee to assist with the development of those workshops (Q4 2011)<br />
**Start developing workshops (Q4 2011 / Q1 2012)<br />
**Launch the first workshop in Q1 2012 ; followed by another 4-5 sessions<br />
**Bring guidance to the community and clear milestones to keep the community engaged afterward (2012)<br />
**Create clear processes on how to get involved and opportunities available for each team/workshop (2011-12)<br />
<br />
*<b>Potential ideas for the workshops</b>:<br />
**SUMO (Michelle Luna)<br />
**QA (Tony Chung, Marcia Knous, and Stephen Donner)<br />
**Web Security (Michael Coates)<br />
**Labs (BrowserID, Popcorn Maker)<br />
**Jetpack & add-on development<br />
**Engineering (FFx and Platform)<br />
<br />
*<b>Tools and Support</b>:<br />
**Have a clear channel of distribution and one central location for community members to have easy access to resources<br />
**Build an Engineering Committee<br />
**Series of Tutorial videos (Rainer)<br />
**Provide clear documentation<br />
**Have some sort of toolkit ready to be installed; one VM per workshop with all the right tools and environment, and make it easily accessible. <br />
**Come up with a set of expectations and projects available for the community each quarter, leveled by priorities (provide more structure overall)</div>Jgouliehttps://wiki.mozilla.org/index.php?title=Community_Workshops&diff=374288Community Workshops2011-11-29T23:09:29Z<p>Jgoulie: </p>
<hr />
<div>*<b>Overview & Goal</b>: Give the community access to parts of the Mozilla projects other than l10n, through a series of workshops that will give new volunteers the appropriate training and tools to contribute to Mozilla. <br />
<br />
*<b>Audience</b>: We will develop this initial pilot program with Mozilla Tunisia and hopefully roll it out to other interested communities. Mozilla Tunisia will be launching a university starting in Dec. 2011 so hopefully we could target those workshops to students as early as Q1 2012. <br />
<br />
*<b>Process</b>:<br />
**Identify technical leads within Mozilla Tunisia that would be interested in owning a specific workshop (Q4 2011)<br />
**Assess overall technical knowledge for each workshop lead and offer appropriate training if needed. We need to give them the technical expertise to then run their own community, based on interest and fit within the organization (Q4 2011)<br />
**Create an internal Engineering Committee to assist with the development of those workshops (Q4 2011)<br />
**Start developing workshops (Q4 2011 / Q1 2012)<br />
**Launch the first workshop in Q1 2012 ; followed by another 4-5 sessions<br />
**Bring guidance to the community and clear milestones to keep the community engaged afterward (2012)<br />
**Create clear processes on how to get involved and opportunities available for each team/workshop (2011-12)<br />
<br />
*<b>Potential areas for the workshops</b>:<br />
**SUMO (Michelle Luna)<br />
**QA (Tony Chung, Marcia Knous, and Stephen Donner)<br />
**Web Security (Michael Coates)<br />
**Labs (BrowserID, Popcorn Maker, <br />
**Jetpack & add-on development<br />
**Engineering (FFx and Platform)<br />
<br />
*<b>Tools and Support</b>:<br />
**Have a clear channel of distribution and one central location for community members to have easy access to resources<br />
**Build an Engineering Committee<br />
**Series of Tutorial videos (Rainer)<br />
**Provide clear documentation<br />
**Have some sort of toolkit ready to be installed; one VM per workshop with all the right tools and environment, and make it easily accessible. <br />
**Come up with a set of expectations and projects available for the community each quarter, leveled by priorities (provide more structure overall)</div>Jgouliehttps://wiki.mozilla.org/index.php?title=Community_Workshops&diff=374285Community Workshops2011-11-29T23:02:17Z<p>Jgoulie: </p>
<hr />
<div>*<b>Overview & Goal</b>: Give the community access to parts of the Mozilla projects other than l10n, through a series of workshops that will give new volunteers the appropriate training and tools to contribute to Mozilla. <br />
<br />
*<b>Audience</b>: We will develop this initial pilot program with Mozilla Tunisia and hopefully roll it out to other interested communities. Mozilla Tunisia will be launching a university starting in Dec. 2011 so hopefully we could target those workshops to students as early as Q1 2012. <br />
<br />
*<b>Process</b>:<br />
**Identify technical leads within Mozilla Tunisia that would be interested in owning a specific workshop<br />
**Assess overall technical knowledge for each workshop lead and offer appropriate training if needed. We need to give them the technical expertise to then run their own community, based on interest and fit within the organization<br />
**Create an internal Engineering Committee to assist with the development of those workshops<br />
**Bring guidance to the community and clear milestones to keep the community engaged afterward<br />
**Create clear processes on how to get involved and opportunities available for each team/workshop<br />
<br />
*<b>Potential areas for the workshops</b>:<br />
**SUMO (Michelle Luna)<br />
**QA (Tony Chung, Marcia Knous, and Stephen Donner)<br />
**Web Security (Michael Coates)<br />
**Labs (BrowserID)<br />
**Jetpack & add-on development<br />
**Engineering (FFx and Platform)<br />
<br />
*<b>Tools and Support</b>:<br />
**Have a clear channel of distribution and one central location for community members to have easy access to resources<br />
**Build an Engineering Committee<br />
**Series of Tutorial videos (Rainer)<br />
**Provide clear documentation<br />
**Have some sort of toolkit ready to be installed; one VM per workshop with all the right tools and environment, and make it easily accessible. <br />
**Come up with a set of expectations and projects available for the community each quarter, leveled by priorities (provide more structure overall)</div>Jgouliehttps://wiki.mozilla.org/index.php?title=Community_Workshops&diff=374277Community Workshops2011-11-29T22:48:55Z<p>Jgoulie: </p>
<hr />
<div>*<b>Overview & Goal</b>: Give the community access to parts of the Mozilla projects other than l10n, through a series of workshops that will give new volunteers the appropriate training and tools to contribute to Mozilla. <br />
<br />
*<b>Audience</b>: We will develop this initial pilot program with Mozilla Tunisia and hopefully roll it out to other interested communities. Mozilla Tunisia will be launching a university starting in Dec. 2011 so hopefully we could target those workshops to students as early as Q1 2012. <br />
<br />
*<b>Process</b>:<br />
**Identify technical leads within Mozilla Tunisia that would be interested in owning a specific workshop<br />
**Assess overall technical knowledge for each workshop lead and offer appropriate training if needed. We need to give them the technical expertise to then run their own community, based on interest and fit within the organization<br />
**Create an internal Engineering Committee to assist with the development of those workshops<br />
**Bring guidance to the community and clear milestones to keep the community engaged afterward<br />
**Create clear processes on how to get involved and opportunities available for each team/workshop<br />
<br />
*<b>Potential areas for the workshops</b>:<br />
**SUMO (Michelle Luna)<br />
**QA (Tony Chung, Marcia Knous, and Stephen Donner)<br />
**Web Security (Michael Coates)<br />
**Jetpack & add-on development<br />
**Engineering (FFx and Platform)<br />
<br />
*<b>Tools and Support</b>:<br />
**Have a clear channel of distribution and one central location for community members to have easy access to resources<br />
**Build an Engineering Committee<br />
**Series of Tutorial videos (Rainer)<br />
**Provide clear documentation<br />
**Have some sort of toolkit ready to be installed; one VM per workshop with all the right tools and environment, and make it easily accessible. <br />
**Come up with a set of expectations and projects available for the community each quarter, leveled by priorities (provide more structure overall)</div>Jgouliehttps://wiki.mozilla.org/index.php?title=Community_Workshops&diff=374276Community Workshops2011-11-29T22:47:48Z<p>Jgoulie: </p>
<hr />
<div>*<b>Overview & Goal</b>: Give the community access to parts of the Mozilla projects other than l10n, through a series of workshops that will give new volunteers the appropriate training and tools to contribute to Mozilla. <br />
<br />
*<b>Audience</b>: We will develop this initial pilot program with Mozilla Tunisia and hopefully roll it out to other interested communities. Mozilla Tunisia will be launching a university starting in Dec. 2011 so hopefully we could target those workshops to students as early as Q1 2012. <br />
<br />
*<b>Process</b>:<br />
**Identify technical leads within Mozilla Tunisia that would be interested in owning a specific workshop<br />
**Assess overall technical knowledge for each workshop lead and offer appropriate training if needed. We need to give them the technical expertise to then run their own community based on interest and fit within the organization<br />
**Create an internal Engineering Committee to assist with the development of those workshops<br />
**Bring guidance to the community and clear milestones to keep the community engaged afterward<br />
**Create clear processes on how to get involved and opportunities available for each team/workshop<br />
<br />
*<b>Potential areas for the workshops</b>:<br />
**SUMO (Michelle Luna)<br />
**QA (Tony Chung, Marcia Knous, and Stephen Donner)<br />
**Web Security (Michael Coates)<br />
**Jetpack & add-on development<br />
**Engineering (FFx and Platform)<br />
<br />
*<b>Tools and Support</b>:<br />
**Have a clear channel of distribution and one central location for community members to have easy access to resources<br />
**Build an Engineering Committee<br />
**Series of Tutorial videos (Rainer)<br />
**Provide clear documentation<br />
**Have some sort of toolkit ready to be installed; one VM per workshop with all the right tools and environment, and make it easily accessible. <br />
**Come up with a set of expectations and projects available for the community each quarter, leveled by priorities (provide more structure overall)</div>Jgouliehttps://wiki.mozilla.org/index.php?title=Community_Workshops&diff=374275Community Workshops2011-11-29T22:47:07Z<p>Jgoulie: </p>
<hr />
<div>*<b>Overview & Goal</b>: Give the community access to parts of the Mozilla projects other than l10n, through a series of workshops that will give new volunteers the appropriate training and tools to contribute to Mozilla. <br />
<br />
*<b>Audience</b>: We will develop this initial pilot program with Mozilla Tunisia and hopefully roll it out to other interested communities. Mozilla Tunisia will be launching a university starting in Dec. 2011 so hopefully we could target those workshops to students as early as Q1 2012. <br />
<br />
*<b>Process</b>:<br />
**Identify technical leads within Mozilla Tunisia that would be interested in owning a specific workshop<br />
**Assess overall technical knowledge for each workshop lead and offer appropriate training if needed. We need to give them the technical expertise to then run their own community based on interest and fit within the organization<br />
**Create an internal Engineering Committee to assist with the development of those workshops<br />
**Bring guidance to the community and clear milestones to keep the community engaged afterward<br />
**Create clear processes on how to get involved and opportunities available for each team/workshop<br />
<br />
*<b>Potential areas for the workshops</b>:<br />
**SUMO (Michelle Luna)<br />
**QA (Tony Chung, Marcia Knous, and Stephen Donner)<br />
**Web Security (Michael Coates)<br />
**Jetpack & add-on development<br />
**Engineering (FFx and Platform)<br />
<br />
*<b>Tools and Support<b>:<br />
**Have a clear channel of distribution and one central location for community members to have easy access to resources<br />
**Build an Engineering Committee<br />
**Series of Tutorial videos (Rainer)<br />
**Provide clear documentation<br />
**Have some sort of toolkit ready to be installed; one VM per workshop with all the right tools and environment, and make it easily accessible. <br />
**Come up with a set of expectations and projects available for the community each quarter, leveled by priorities (provide more structure overall)</div>Jgouliehttps://wiki.mozilla.org/index.php?title=Community_Workshops&diff=374274Community Workshops2011-11-29T22:46:25Z<p>Jgoulie: </p>
<hr />
<div>*<b>Overview & Goal</b>: Give the community access to parts of the Mozilla projects other than l10n, through a series of workshops that will give new volunteers the appropriate training and tools to contribute to Mozilla. <br />
<br />
*<b>Audience</b>: We will develop this initial pilot program with Mozilla Tunisia and hopefully roll it out to other interested communities. Mozilla Tunisia will be launching a university starting in Dec. 2011 so hopefully we could target those workshops to students as early as Q1 2012. <br />
<br />
*Process:<br />
**Identify technical leads within Mozilla Tunisia that would be interested in owning a specific workshop<br />
**Assess overall technical knowledge for each workshop lead and offer appropriate training if needed. We need to give them the technical expertise to then run their own community based on interest and fit within the organization<br />
**Create an internal Engineering Committee to assist with the development of those workshops<br />
**Bring guidance to the community and clear milestones to keep the community engaged afterward<br />
**Create clear processes on how to get involved and opportunities available for each team/workshop<br />
<br />
*Potential areas for the workshops:<br />
**SUMO (Michelle Luna)<br />
**QA (Tony Chung, Marcia Knous, and Stephen Donner)<br />
**Web Security (Michael Coates)<br />
**Jetpack & add-on development<br />
**Engineering (FFx and Platform)<br />
<br />
*Tools and Support<br />
**Have a clear channel of distribution and one central location for community members to have easy access to resources<br />
**Build an Engineering Committee<br />
**Series of Tutorial videos (Rainer)<br />
**Provide clear documentation<br />
**Have some sort of toolkit ready to be installed; one VM per workshop with all the right tools and environment, and make it easily accessible. <br />
**Come up with a set of expectations and projects available for the community each quarter, leveled by priorities (provide more structure overall)</div>Jgouliehttps://wiki.mozilla.org/index.php?title=Community_Workshops&diff=374273Community Workshops2011-11-29T22:45:45Z<p>Jgoulie: </p>
<hr />
<div>*Overview & Goal: Give the community access to parts of the Mozilla projects other than l10n, through a series of workshops that will give new volunteers the appropriate training and tools to contribute to Mozilla. <br />
<br />
*Audience: We will develop this initial pilot program with Mozilla Tunisia and hopefully roll it out to other interested communities. Mozilla Tunisia will be launching a university starting in Dec. 2011 so hopefully we could target those workshops to students as early as Q1 2012. <br />
<br />
*Process:<br />
**Identify technical leads within Mozilla Tunisia that would be interested in owning a specific workshop<br />
**Assess overall technical knowledge for each workshop lead and offer appropriate training if needed. We need to give them the technical expertise to then run their own community based on interest and fit within the organization<br />
**Create an internal Engineering Committee to assist with the development of those workshops<br />
**Bring guidance to the community and clear milestones to keep the community engaged afterward<br />
**Create clear processes on how to get involved and opportunities available for each team/workshop<br />
<br />
*Potential areas for the workshops:<br />
**SUMO (Michelle Luna)<br />
**QA (Tony Chung, Marcia Knous, and Stephen Donner)<br />
**Web Security (Michael Coates)<br />
**Jetpack & add-on development<br />
**Engineering (FFx and Platform)<br />
<br />
*Tools and Support<br />
**Have a clear channel of distribution and one central location for community members to have easy access to resources<br />
**Build an Engineering Committee<br />
**Series of Tutorial videos (Rainer)<br />
**Provide clear documentation<br />
**Have some sort of toolkit ready to be installed; one VM per workshop with all the right tools and environment, and make it easily accessible. <br />
**Come up with a set of expectations and projects available for the community each quarter, leveled by priorities (provide more structure overall)</div>Jgouliehttps://wiki.mozilla.org/index.php?title=Community_Workshops&diff=374270Community Workshops2011-11-29T22:45:05Z<p>Jgoulie: </p>
<hr />
<div>*Overview & Goal: <br />
Give the community access to parts of the Mozilla projects other than l10n, through a series of workshops that will give new volunteers the appropriate training and tools to contribute to Mozilla. <br />
<br />
*Audience:<br />
We will develop this initial pilot program with Mozilla Tunisia and hopefully roll it out to other interested communities. Mozilla Tunisia will be launching a university starting in Dec. 2011 so hopefully we could target those workshops to students as early as Q1 2012. <br />
<br />
*Process:<br />
**Identify technical leads within Mozilla Tunisia that would be interested in owning a specific workshop<br />
**Assess overall technical knowledge for each workshop lead and offer appropriate training if needed. We need to give them the technical expertise to then run their own community based on interest and fit within the organization<br />
**Create an internal Engineering Committee to assist with the development of those workshops<br />
**Bring guidance to the community and clear milestones to keep the community engaged afterward<br />
**Create clear processes on how to get involved and opportunities available for each team/workshop<br />
<br />
*Potential areas for the workshops:<br />
**SUMO (Michelle Luna)<br />
**QA (Tony Chung, Marcia Knous, and Stephen Donner)<br />
**Web Security (Michael Coates)<br />
**Jetpack & add-on development<br />
**Engineering (FFx and Platform)<br />
<br />
*Tools and Support<br />
**Have a clear channel of distribution and one central location for community members to have easy access to resources<br />
**Build an Engineering Committee<br />
**Series of Tutorial videos (Rainer)<br />
**Provide clear documentation<br />
**Have some sort of toolkit ready to be installed; one VM per workshop with all the right tools and environment, and make it easily accessible. <br />
**Come up with a set of expectations and projects available for the community each quarter, leveled by priorities (provide more structure overall)</div>Jgouliehttps://wiki.mozilla.org/index.php?title=Community_Workshops&diff=374262Community Workshops2011-11-29T22:34:15Z<p>Jgoulie: </p>
<hr />
<div>*Overview & Goal: <br />
Give the community access to parts of the Mozilla projects other than l10n, through a series of workshops that will give new volunteers the appropriate training and tools to contribute to Mozilla. <br />
<br />
*Audience:<br />
We will develop this initial pilot program with Mozilla Tunisia and hopefully roll it out to other interested communities. Mozilla Tunisia will be launching a university starting in Dec. 2011 so hopefully we could target those workshops to students as early as Q1 2012. <br />
<br />
*Process:<br />
**Identify technical leads within Mozilla Tunisia that would be interested in owning a specific workshop<br />
**Assess overall technical knowledge for each workshop lead <br />
**Create an internal Engineering Committee to assist with the development of those workshops<br />
**Bring guidance to the community and clear milestones to keep the community engaged afterward<br />
**Create clear processes on how to get involved and opportunities available for each team/workshop<br />
<br />
*Potential areas for the workshops:<br />
**SUMO (Michelle Luna)<br />
**QA (Tony Chung, Marcia Knous, and Stephen Donner)<br />
**Web Security (Michael Coates)<br />
**Jetpack & add-on development<br />
**Engineering (FFx and Platform)</div>Jgouliehttps://wiki.mozilla.org/index.php?title=Community_Workshops&diff=374258Community Workshops2011-11-29T22:28:37Z<p>Jgoulie: </p>
<hr />
<div>* <b>Overview & Goal</b>: <br />
Give the community access to parts of the Mozilla projects other than l10n, through a series of workshops that will give new volunteers the appropriate training and tools to contribute to Mozilla. <br />
<br />
* <b>Audience</b>:<br />
We will develop this initial pilot program with Mozilla Tunisia and hopefully roll it out to other interested communities. Mozilla Tunisia will be launching a <br />
<br />
* <b>How to</b>:<br />
**Identify technical leads within Mozilla Tunisia that would be interested in owning a specific workshop<br />
**Assess overall technical knowledge of the workshops leads <br />
**Create an internal Engineering Committee to assist with the development of those workshops<br />
**Bring guidance to the community and clear milestones to keep the community engaged afterward<br />
**Create clear processes on how to get involved and opportunities available for each team/workshop</div>Jgouliehttps://wiki.mozilla.org/index.php?title=Community_Workshops&diff=374257Community Workshops2011-11-29T22:28:11Z<p>Jgoulie: </p>
<hr />
<div>* <b>Overview & Goal</b>: <br />
Give the community access to parts of the Mozilla projects other than l10n, through a series of workshops that will give new volunteers the appropriate training and tools to contribute to Mozilla. <br />
<br />
* <b>Audience</b>:<br />
We will develop this initial pilot program with Mozilla Tunisia and hopefully roll it out to other interested communities. Mozilla Tunisia will be launching a <br />
<br />
* <b>How to</b>:<br />
**Identify technical leads within Mozilla Tunisia that would be interested in owning a specific workshop<br />
**Assess overall technical knowledge of the workshops leads <br />
**Create an internal Engineering Committee to assist with the development of those workshops<br />
**Bring guidance to the community and clear milestones to keep the community engaged afterward<br />
**Create clear processes on how to get involved and opportunities available for each team/workshop</div>Jgouliehttps://wiki.mozilla.org/index.php?title=Community_Workshops&diff=374203Community Workshops2011-11-29T20:59:11Z<p>Jgoulie: </p>
<hr />
<div>* <b>Overview & Goal</b>: <br />
Give the community access to parts of the projects other than l10n, through a series of workshops that will give the appropriate training and tools for community members to get involved with SUMO, QA, Web Security. Jetpack & add-on development, and potentially engineering. <br />
* <b>Audience</b>:<br />
We will develop this initial pilot program with Mozilla Tunisia and hopefully roll it out to other interested communities<br />
* Tools and Training<br />
**<br />
<br />
<br />
*Potential teams that would be a good fit to launch this program:<br />
** SUMO (Michelle Luna)<br />
** QA (Tony and Marcia)<br />
** Web Security <br />
** Jetpack and add-on development<br />
** Engineering (FE vs. BE)<br />
• hacking FE UI (Paul Rouget)<br />
• backend ⇒ C++ <br />
<br />
MozCamp ⇒ sprio south America<br />
• choffman, mary, Guillermo,…<br />
<br />
*Distribution channels and support<br />
**Tutorials videos <br />
**<br />
<br />
*Thoughts.... <br />
**Identify leaders from the community for each workshop and embrace them to become technical leaders afterward<br />
**Establish clear milestones after each workshop<br />
**Keeping track of bugs available and bugs filed (how do we monitor progress for each)<br />
<br />
* Composition of the team<br />
- one Mozilla point of contact for each workshop to walk the community through the initial training and provide them with the right tools<br />
<br />
- one technical leader from the community<br />
- figure out how many new members can each team absorb at once (for example, mcoates mentioned 20-30 new contributors. What's a reasonable number?)<br />
- how can we successfully advertise the different opportunities within Mozilla (mutual effort between Workshop Owner and Community Technical Lead)?<br />
<br />
- Rewarding the community:<br />
* Self valorization within the community and Mozilla (badges?)<br />
*</div>Jgouliehttps://wiki.mozilla.org/index.php?title=Community_Workshops&diff=374199Community Workshops2011-11-29T20:43:46Z<p>Jgoulie: </p>
<hr />
<div>* Overview & Goal: Give the community access to parts of the projects other than l10n, through a series of workshops that will give the appropriate training and tools for community members to get involved with SUMO, QA, Web Security. Jetpack & add-on development, and potentially engineering. <br />
* Audience: We will develop this initial pilot program with Mozilla Tunisia and hopefully roll it out to other interested communities<br />
* Tools and Training<br />
<br />
<br />
*Potential teams that would be a good fit to launch this program:<br />
** SUMO (Michelle Luna)<br />
** QA (Tony and Marcia)<br />
** Web Security <br />
** Jetpack and add-on development<br />
** Engineering (FE vs. BE)<br />
• hacking FE UI (Paul Rouget)<br />
• backend ⇒ C++ <br />
<br />
MozCamp ⇒ sprio south America<br />
• choffman, mary, Guillermo,…<br />
<br />
*Distribution channels and support<br />
**Tutorials videos <br />
**<br />
<br />
*Thoughts.... <br />
**Identify leaders from the community for each workshop and embrace them to become technical leaders afterward<br />
**Establish clear milestones after each workshop<br />
**Keeping track of bugs available and bugs filed (how do we monitor progress for each)<br />
<br />
* Composition of the team<br />
- one Mozilla point of contact for each workshop to walk the community through the initial training and provide them with the right tools<br />
<br />
- one technical leader from the community<br />
- figure out how many new members can each team absorb at once (for example, mcoates mentioned 20-30 new contributors. What's a reasonable number?)<br />
- how can we successfully advertise the different opportunities within Mozilla (mutual effort between Workshop Owner and Community Technical Lead)?<br />
<br />
- Rewarding the community:<br />
* Self valorization within the community and Mozilla (badges?)<br />
*</div>Jgouliehttps://wiki.mozilla.org/index.php?title=Community_Workshops&diff=374197Community Workshops2011-11-29T20:39:55Z<p>Jgoulie: Created page with "* Overview & Goal: Give the community access to parts of the projects other than a11y (Accessibility). *Potential teams that would be a good fit to launch this program: ** SUMO..."</p>
<hr />
<div>* Overview & Goal: Give the community access to parts of the projects other than a11y (Accessibility). <br />
<br />
*Potential teams that would be a good fit to launch this program:<br />
** SUMO (Michelle Luna)<br />
** QA (Tony and Marcia)<br />
** Web Security <br />
** Jetpack and add-on development<br />
** Engineering (FE vs. BE)<br />
• hacking FE UI (Paul Rouget)<br />
• backend ⇒ C++ <br />
<br />
MozCamp ⇒ sprio south America<br />
• choffman, mary, Guillermo,…<br />
<br />
*Distribution channels and support<br />
**Tutorials videos <br />
**<br />
<br />
*Thoughts.... <br />
**Identify leaders from the community for each workshop and embrace them to become technical leaders afterward<br />
**Establish clear milestones after each workshop<br />
**Keeping track of bugs available and bugs filed (how do we monitor progress for each)<br />
<br />
* Composition of the team<br />
- one Mozilla point of contact for each workshop to walk the community through the initial training and provide them with the right tools<br />
<br />
- one technical leader from the community<br />
- figure out how many new members can each team absorb at once (for example, mcoates mentioned 20-30 new contributors. What's a reasonable number?)<br />
- how can we successfully advertise the different opportunities within Mozilla (mutual effort between Workshop Owner and Community Technical Lead)?<br />
<br />
- Rewarding the community:<br />
* Self valorization within the community and Mozilla (badges?)<br />
*</div>Jgouliehttps://wiki.mozilla.org/index.php?title=User:Jgoulie&diff=374192User:Jgoulie2011-11-29T20:21:50Z<p>Jgoulie: </p>
<hr />
<div>= Mozilla Community Workshops =<br />
[[Community Workshops|Overview of the Community Workshops]] <br />
<br />
=<b>MIT IAP, January 10-14, 2011</b>=<br />
<br />
==Overview==<br />
* Name of the class: IAP HTML5 Game Programming Course and Competition<br />
* Coursework Component: 5 sessions, 2 hours each (total instruction time 10 hours)<br />
*Schedule, everyday 11.30-1.30pm EST<br />
*Room is 32-141 (32 Vassar St, room #141 (first floor) (http://whereis.mit.edu/)<br />
*Onsite support:<br />
**mitcho (Michael Erlewine), mitcho@mit.edu<br />
**office: 32-D866, Mondays during IAP or by appointment<br />
*Online support:<br />
**[http://irc.mozilla.org/ IRC] #mitiap2011<br />
**Feel free to email anyone from the group of the lecturers in case you have any specific question related to the course<br />
**Julie Deroche: jgoulie(IRC) or julie@mozilla.com<br />
*Here's a list of some [http://en.wikipedia.org/wiki/IRC#Client_software IRC clients] depending on your OS.<br><br />
*<b>Emergency line for the Stata Center</b>: 617-253-7669 || Please call on Wednesday to make sure the center is open!<br><br><br />
<br />
==Layout of the week==<br />
===January 10, 2011===<br />
*Lecturer: Dave Herman<br />
*<b>Lecture notes</b>: http://www.ccs.neu.edu/home/dherman/mit-iap-2011/<br />
*Contact info:<br />
**Email: dherman@mozilla.com<br />
**IRC: dherman -- available on irc.mozilla.org at #jslang and #jsapi <br />
**Twitter: @littlecalculist<br />
*Topics covered: Foundations of JavaScript programming in the browser. Language syntax and concepts. Browser environment, events. (object and prototype, scope and global object, closures, events and call backs, numbers, XHR)<br />
*Resources:<br />
**https://developer.mozilla.org/en/JavaScript/Guide<br />
**https://developer.mozilla.org/En/XMLHttpRequest/Using_XMLHttpRequest //documentation on XHR, which Dave will be talking a bit during his lecture (Students may or may not need it for their games, but it's a good way to learn about using callbacks for event handling without having to learn all the complications of DOM events.)<br />
**http://www.squarefree.com/shell/shell.html //Students can use it to test out JS commands in any browser. But the more recommended way would be to use the built-in developer tools of their browser (FF4 console or Firebug, Chrome console, Safari console).<br />
<br />
===January 11, 2011===<br />
*Lecturer: Boris Zbarsky<br />
*Contact info<br />
**Email: bzbarsky@mit.edu<br />
**IRC: bz -- available on irc.mozilla.org at #developers<br />
*Topics covered: The Document Object Model (DOM), the canvas element, resource loading (graphics)<br><br />
*Resources:<br />
**Presentation: http://web.mit.edu/bzbarsky/www/IAP-2011-DOM-talk/intro.html<br />
**HTML5 (draft): http://www.whatwg.org/specs/web-apps/current-work/multipage/<br />
**XMLHttpRequest (close to final): http://www.w3.org/TR/XMLHttpRequest/<br />
**XMLHttpRequest extensions (draft): http://dev.w3.org/2006/webapi/XMLHttpRequest-2/<br />
**CORS (for cross-site XMLHttpRequest, draft): http://www.w3.org/TR/cors/<br />
**CSS 2.1 (close to final): http://www.w3.org/TR/CSS21/<br />
**Canvas (mix of close to final and draft): http://www.whatwg.org/specs/web-apps/current-work/multipage/the-canvas-element.html<br />
**DOM Core: http://www.w3.org/TR/DOM-Level-3-Core/core.html<br />
**DOM Events: http://www.w3.org/TR/DOM-Level-2-Events/events.html<br />
<br />
===January 12, 2011===<br />
*Lecturers: Benoit Jacob and Andor Salga<br />
*Lecture notes: http://people.mozilla.org/~bjacob/iap2011/slides<br />
*Contact info (Benoit)<br />
**Email: bjacob@mozilla.com<br />
**IRC: bjacob -- available on irc.mozilla.org at #developers #gfx #audio<br />
*Contact info (Andor)<br />
**Email: andor.salga@senecac.on.ca<br />
**IRC: nick:asalga -- available on irc.mozilla.org on #Seneca #Processing.js and #C3DL Also avaiable on irc.freenode.net on #WebGL<br />
**Twitter: @asalga<br />
**Wordpress: http://asalga.wordpress.com<br><br />
*Topics covered: Introduction to 3D graphics with OpenGL/WebGL. Basics of shader programming<br />
*Notes from the lecture: https://github.com/bjacob/webgl-lessons/tree/master/iap2011<br><br />
*Useful links<br />
**WebGL specification: https://cvs.khronos.org/svn/repos/registry/trunk/public/webgl/doc/spec/WebGL-spec.html<br />
**WebGL tutorials: http://www.learningWebGL.com<br />
**http://www.doesmybrowsersupportwebgl.com/<br />
**http://learningwebgl.com/lessons/<br />
*Further links<br />
**WebGL point cloud renderer: http://zenit.senecac.on.ca/wiki/index.php/XB_PointStream<br />
**Data visualizer library which uses WebGL: www.processingjs.org<br />
**WebGL library: www.c3dl.org<br><br><br />
<br />
===January 13, 2011===<br />
*Lecturer: Chris Heilmann<br />
*Topics covered: Multimedia on the web - audio and video<br />
*Notes from the lecture:http://www.wait-till-i.com/2011/01/16/lecturing-at-mit-about-html5-video-slides-and-lots-of-notes/<br />
<br />
===January 14, 2011===<br />
*Lecturer: Pascal Rettig from [http://cykod.com/ Cykod]<br />
*Topics covered: Offline web applications, local storage, debugging and optimizing JS performance. Also to be discussed: server side Javascript (node.js) and Web sockets.<br />
*Resources:<br />
**Offline storage - http://diveintohtml5.org/offline.html<br />
**Local storage - http://diveintohtml5.org/storage.html<br />
**JS Debugging /w Firebug - http://getfirebug.com/javascript<br />
**Node.js - http://nodejs.org/<br />
**Node Package Manager - http://npmjs.org/<br />
**Node Realtime Sockets Module - http://socket.io/<br />
*Notes from the lecture: http://www.slideshare.net/cykod/javascript-everywhere<br />
*Further notes from the class: http://www.slideshare.net/cykod/vector-graphics-on-the-web-svg-canvas-css3<br />
<br />
==Competition==<br />
===Summary===<br />
After the course work component, students will compete in a HTML5 game programming competition. Mozilla will host a discussion forum for students to communicate and collaborate and ask and answer questions amongst each other (irc.mozilla.org, #mitiap2010). The goal is for students to implement an interesting HTML5 game or visual demonstration. Whether its a create re-implementation of existing games (HTML5 pong?), or a full fledge 3D game, anything goes. <br><br />
===Prize===<br />
The winning team (up to 4 team members max) will come to Mountain View and spend a w/e in SF. During their time at Mozila, the team will present its demo/game and spend some time with Brendan Eich. We will also offer a 1K stipend to the winning team to make sure you enjoy your time in sunny California. One last piece of swag will be a signed copy of John Resig's latest book: [http://jsninja.com/ Secrets of the JavaScript Ninja] <br />
===Criteria for the competition===<br />
*Deadline is February 20, 2011<br />
*Teams composition: up to 4 students<br />
*Use of existing libraries allowed, but you may not copy existing games<br />
=== Games Gallery ===<br />
<br />
[[Dots - Team Blobby]] <br> [[HTML5 Demo - Team Tom]]<br> [[QRticullis - Team Viral Ecology]]</div>Jgouliehttps://wiki.mozilla.org/index.php?title=User:Jgoulie&diff=374191User:Jgoulie2011-11-29T20:17:48Z<p>Jgoulie: /* Mozilla Workshops */</p>
<hr />
<div>=<b>MIT IAP, January 10-14, 2011</b>=<br />
<br />
==Overview==<br />
* Name of the class: IAP HTML5 Game Programming Course and Competition<br />
* Coursework Component: 5 sessions, 2 hours each (total instruction time 10 hours)<br />
*Schedule, everyday 11.30-1.30pm EST<br />
*Room is 32-141 (32 Vassar St, room #141 (first floor) (http://whereis.mit.edu/)<br />
*Onsite support:<br />
**mitcho (Michael Erlewine), mitcho@mit.edu<br />
**office: 32-D866, Mondays during IAP or by appointment<br />
*Online support:<br />
**[http://irc.mozilla.org/ IRC] #mitiap2011<br />
**Feel free to email anyone from the group of the lecturers in case you have any specific question related to the course<br />
**Julie Deroche: jgoulie(IRC) or julie@mozilla.com<br />
*Here's a list of some [http://en.wikipedia.org/wiki/IRC#Client_software IRC clients] depending on your OS.<br><br />
*<b>Emergency line for the Stata Center</b>: 617-253-7669 || Please call on Wednesday to make sure the center is open!<br><br><br />
<br />
==Layout of the week==<br />
===January 10, 2011===<br />
*Lecturer: Dave Herman<br />
*<b>Lecture notes</b>: http://www.ccs.neu.edu/home/dherman/mit-iap-2011/<br />
*Contact info:<br />
**Email: dherman@mozilla.com<br />
**IRC: dherman -- available on irc.mozilla.org at #jslang and #jsapi <br />
**Twitter: @littlecalculist<br />
*Topics covered: Foundations of JavaScript programming in the browser. Language syntax and concepts. Browser environment, events. (object and prototype, scope and global object, closures, events and call backs, numbers, XHR)<br />
*Resources:<br />
**https://developer.mozilla.org/en/JavaScript/Guide<br />
**https://developer.mozilla.org/En/XMLHttpRequest/Using_XMLHttpRequest //documentation on XHR, which Dave will be talking a bit during his lecture (Students may or may not need it for their games, but it's a good way to learn about using callbacks for event handling without having to learn all the complications of DOM events.)<br />
**http://www.squarefree.com/shell/shell.html //Students can use it to test out JS commands in any browser. But the more recommended way would be to use the built-in developer tools of their browser (FF4 console or Firebug, Chrome console, Safari console).<br />
<br />
===January 11, 2011===<br />
*Lecturer: Boris Zbarsky<br />
*Contact info<br />
**Email: bzbarsky@mit.edu<br />
**IRC: bz -- available on irc.mozilla.org at #developers<br />
*Topics covered: The Document Object Model (DOM), the canvas element, resource loading (graphics)<br><br />
*Resources:<br />
**Presentation: http://web.mit.edu/bzbarsky/www/IAP-2011-DOM-talk/intro.html<br />
**HTML5 (draft): http://www.whatwg.org/specs/web-apps/current-work/multipage/<br />
**XMLHttpRequest (close to final): http://www.w3.org/TR/XMLHttpRequest/<br />
**XMLHttpRequest extensions (draft): http://dev.w3.org/2006/webapi/XMLHttpRequest-2/<br />
**CORS (for cross-site XMLHttpRequest, draft): http://www.w3.org/TR/cors/<br />
**CSS 2.1 (close to final): http://www.w3.org/TR/CSS21/<br />
**Canvas (mix of close to final and draft): http://www.whatwg.org/specs/web-apps/current-work/multipage/the-canvas-element.html<br />
**DOM Core: http://www.w3.org/TR/DOM-Level-3-Core/core.html<br />
**DOM Events: http://www.w3.org/TR/DOM-Level-2-Events/events.html<br />
<br />
===January 12, 2011===<br />
*Lecturers: Benoit Jacob and Andor Salga<br />
*Lecture notes: http://people.mozilla.org/~bjacob/iap2011/slides<br />
*Contact info (Benoit)<br />
**Email: bjacob@mozilla.com<br />
**IRC: bjacob -- available on irc.mozilla.org at #developers #gfx #audio<br />
*Contact info (Andor)<br />
**Email: andor.salga@senecac.on.ca<br />
**IRC: nick:asalga -- available on irc.mozilla.org on #Seneca #Processing.js and #C3DL Also avaiable on irc.freenode.net on #WebGL<br />
**Twitter: @asalga<br />
**Wordpress: http://asalga.wordpress.com<br><br />
*Topics covered: Introduction to 3D graphics with OpenGL/WebGL. Basics of shader programming<br />
*Notes from the lecture: https://github.com/bjacob/webgl-lessons/tree/master/iap2011<br><br />
*Useful links<br />
**WebGL specification: https://cvs.khronos.org/svn/repos/registry/trunk/public/webgl/doc/spec/WebGL-spec.html<br />
**WebGL tutorials: http://www.learningWebGL.com<br />
**http://www.doesmybrowsersupportwebgl.com/<br />
**http://learningwebgl.com/lessons/<br />
*Further links<br />
**WebGL point cloud renderer: http://zenit.senecac.on.ca/wiki/index.php/XB_PointStream<br />
**Data visualizer library which uses WebGL: www.processingjs.org<br />
**WebGL library: www.c3dl.org<br><br><br />
<br />
===January 13, 2011===<br />
*Lecturer: Chris Heilmann<br />
*Topics covered: Multimedia on the web - audio and video<br />
*Notes from the lecture:http://www.wait-till-i.com/2011/01/16/lecturing-at-mit-about-html5-video-slides-and-lots-of-notes/<br />
<br />
===January 14, 2011===<br />
*Lecturer: Pascal Rettig from [http://cykod.com/ Cykod]<br />
*Topics covered: Offline web applications, local storage, debugging and optimizing JS performance. Also to be discussed: server side Javascript (node.js) and Web sockets.<br />
*Resources:<br />
**Offline storage - http://diveintohtml5.org/offline.html<br />
**Local storage - http://diveintohtml5.org/storage.html<br />
**JS Debugging /w Firebug - http://getfirebug.com/javascript<br />
**Node.js - http://nodejs.org/<br />
**Node Package Manager - http://npmjs.org/<br />
**Node Realtime Sockets Module - http://socket.io/<br />
*Notes from the lecture: http://www.slideshare.net/cykod/javascript-everywhere<br />
*Further notes from the class: http://www.slideshare.net/cykod/vector-graphics-on-the-web-svg-canvas-css3<br />
<br />
==Competition==<br />
===Summary===<br />
After the course work component, students will compete in a HTML5 game programming competition. Mozilla will host a discussion forum for students to communicate and collaborate and ask and answer questions amongst each other (irc.mozilla.org, #mitiap2010). The goal is for students to implement an interesting HTML5 game or visual demonstration. Whether its a create re-implementation of existing games (HTML5 pong?), or a full fledge 3D game, anything goes. <br><br />
===Prize===<br />
The winning team (up to 4 team members max) will come to Mountain View and spend a w/e in SF. During their time at Mozila, the team will present its demo/game and spend some time with Brendan Eich. We will also offer a 1K stipend to the winning team to make sure you enjoy your time in sunny California. One last piece of swag will be a signed copy of John Resig's latest book: [http://jsninja.com/ Secrets of the JavaScript Ninja] <br />
===Criteria for the competition===<br />
*Deadline is February 20, 2011<br />
*Teams composition: up to 4 students<br />
*Use of existing libraries allowed, but you may not copy existing games<br />
=== Games Gallery ===<br />
<br />
[[Dots - Team Blobby]] <br> [[HTML5 Demo - Team Tom]]<br> [[QRticullis - Team Viral Ecology]]</div>Jgouliehttps://wiki.mozilla.org/index.php?title=User:Jgoulie&diff=374189User:Jgoulie2011-11-29T20:17:22Z<p>Jgoulie: </p>
<hr />
<div>=<b>Mozilla Workshops</b>=<br />
<br />
=<b>MIT IAP, January 10-14, 2011</b>=<br />
<br />
==Overview==<br />
* Name of the class: IAP HTML5 Game Programming Course and Competition<br />
* Coursework Component: 5 sessions, 2 hours each (total instruction time 10 hours)<br />
*Schedule, everyday 11.30-1.30pm EST<br />
*Room is 32-141 (32 Vassar St, room #141 (first floor) (http://whereis.mit.edu/)<br />
*Onsite support:<br />
**mitcho (Michael Erlewine), mitcho@mit.edu<br />
**office: 32-D866, Mondays during IAP or by appointment<br />
*Online support:<br />
**[http://irc.mozilla.org/ IRC] #mitiap2011<br />
**Feel free to email anyone from the group of the lecturers in case you have any specific question related to the course<br />
**Julie Deroche: jgoulie(IRC) or julie@mozilla.com<br />
*Here's a list of some [http://en.wikipedia.org/wiki/IRC#Client_software IRC clients] depending on your OS.<br><br />
*<b>Emergency line for the Stata Center</b>: 617-253-7669 || Please call on Wednesday to make sure the center is open!<br><br><br />
<br />
==Layout of the week==<br />
===January 10, 2011===<br />
*Lecturer: Dave Herman<br />
*<b>Lecture notes</b>: http://www.ccs.neu.edu/home/dherman/mit-iap-2011/<br />
*Contact info:<br />
**Email: dherman@mozilla.com<br />
**IRC: dherman -- available on irc.mozilla.org at #jslang and #jsapi <br />
**Twitter: @littlecalculist<br />
*Topics covered: Foundations of JavaScript programming in the browser. Language syntax and concepts. Browser environment, events. (object and prototype, scope and global object, closures, events and call backs, numbers, XHR)<br />
*Resources:<br />
**https://developer.mozilla.org/en/JavaScript/Guide<br />
**https://developer.mozilla.org/En/XMLHttpRequest/Using_XMLHttpRequest //documentation on XHR, which Dave will be talking a bit during his lecture (Students may or may not need it for their games, but it's a good way to learn about using callbacks for event handling without having to learn all the complications of DOM events.)<br />
**http://www.squarefree.com/shell/shell.html //Students can use it to test out JS commands in any browser. But the more recommended way would be to use the built-in developer tools of their browser (FF4 console or Firebug, Chrome console, Safari console).<br />
<br />
===January 11, 2011===<br />
*Lecturer: Boris Zbarsky<br />
*Contact info<br />
**Email: bzbarsky@mit.edu<br />
**IRC: bz -- available on irc.mozilla.org at #developers<br />
*Topics covered: The Document Object Model (DOM), the canvas element, resource loading (graphics)<br><br />
*Resources:<br />
**Presentation: http://web.mit.edu/bzbarsky/www/IAP-2011-DOM-talk/intro.html<br />
**HTML5 (draft): http://www.whatwg.org/specs/web-apps/current-work/multipage/<br />
**XMLHttpRequest (close to final): http://www.w3.org/TR/XMLHttpRequest/<br />
**XMLHttpRequest extensions (draft): http://dev.w3.org/2006/webapi/XMLHttpRequest-2/<br />
**CORS (for cross-site XMLHttpRequest, draft): http://www.w3.org/TR/cors/<br />
**CSS 2.1 (close to final): http://www.w3.org/TR/CSS21/<br />
**Canvas (mix of close to final and draft): http://www.whatwg.org/specs/web-apps/current-work/multipage/the-canvas-element.html<br />
**DOM Core: http://www.w3.org/TR/DOM-Level-3-Core/core.html<br />
**DOM Events: http://www.w3.org/TR/DOM-Level-2-Events/events.html<br />
<br />
===January 12, 2011===<br />
*Lecturers: Benoit Jacob and Andor Salga<br />
*Lecture notes: http://people.mozilla.org/~bjacob/iap2011/slides<br />
*Contact info (Benoit)<br />
**Email: bjacob@mozilla.com<br />
**IRC: bjacob -- available on irc.mozilla.org at #developers #gfx #audio<br />
*Contact info (Andor)<br />
**Email: andor.salga@senecac.on.ca<br />
**IRC: nick:asalga -- available on irc.mozilla.org on #Seneca #Processing.js and #C3DL Also avaiable on irc.freenode.net on #WebGL<br />
**Twitter: @asalga<br />
**Wordpress: http://asalga.wordpress.com<br><br />
*Topics covered: Introduction to 3D graphics with OpenGL/WebGL. Basics of shader programming<br />
*Notes from the lecture: https://github.com/bjacob/webgl-lessons/tree/master/iap2011<br><br />
*Useful links<br />
**WebGL specification: https://cvs.khronos.org/svn/repos/registry/trunk/public/webgl/doc/spec/WebGL-spec.html<br />
**WebGL tutorials: http://www.learningWebGL.com<br />
**http://www.doesmybrowsersupportwebgl.com/<br />
**http://learningwebgl.com/lessons/<br />
*Further links<br />
**WebGL point cloud renderer: http://zenit.senecac.on.ca/wiki/index.php/XB_PointStream<br />
**Data visualizer library which uses WebGL: www.processingjs.org<br />
**WebGL library: www.c3dl.org<br><br><br />
<br />
===January 13, 2011===<br />
*Lecturer: Chris Heilmann<br />
*Topics covered: Multimedia on the web - audio and video<br />
*Notes from the lecture:http://www.wait-till-i.com/2011/01/16/lecturing-at-mit-about-html5-video-slides-and-lots-of-notes/<br />
<br />
===January 14, 2011===<br />
*Lecturer: Pascal Rettig from [http://cykod.com/ Cykod]<br />
*Topics covered: Offline web applications, local storage, debugging and optimizing JS performance. Also to be discussed: server side Javascript (node.js) and Web sockets.<br />
*Resources:<br />
**Offline storage - http://diveintohtml5.org/offline.html<br />
**Local storage - http://diveintohtml5.org/storage.html<br />
**JS Debugging /w Firebug - http://getfirebug.com/javascript<br />
**Node.js - http://nodejs.org/<br />
**Node Package Manager - http://npmjs.org/<br />
**Node Realtime Sockets Module - http://socket.io/<br />
*Notes from the lecture: http://www.slideshare.net/cykod/javascript-everywhere<br />
*Further notes from the class: http://www.slideshare.net/cykod/vector-graphics-on-the-web-svg-canvas-css3<br />
<br />
==Competition==<br />
===Summary===<br />
After the course work component, students will compete in a HTML5 game programming competition. Mozilla will host a discussion forum for students to communicate and collaborate and ask and answer questions amongst each other (irc.mozilla.org, #mitiap2010). The goal is for students to implement an interesting HTML5 game or visual demonstration. Whether its a create re-implementation of existing games (HTML5 pong?), or a full fledge 3D game, anything goes. <br><br />
===Prize===<br />
The winning team (up to 4 team members max) will come to Mountain View and spend a w/e in SF. During their time at Mozila, the team will present its demo/game and spend some time with Brendan Eich. We will also offer a 1K stipend to the winning team to make sure you enjoy your time in sunny California. One last piece of swag will be a signed copy of John Resig's latest book: [http://jsninja.com/ Secrets of the JavaScript Ninja] <br />
===Criteria for the competition===<br />
*Deadline is February 20, 2011<br />
*Teams composition: up to 4 students<br />
*Use of existing libraries allowed, but you may not copy existing games<br />
=== Games Gallery ===<br />
<br />
[[Dots - Team Blobby]] <br> [[HTML5 Demo - Team Tom]]<br> [[QRticullis - Team Viral Ecology]]</div>Jgouliehttps://wiki.mozilla.org/index.php?title=User:Jgoulie&diff=374188User:Jgoulie2011-11-29T20:16:33Z<p>Jgoulie: </p>
<hr />
<div>=<b>Mozilla Workshops for Mozilla Tunisia</b>=<br />
==Overview of the Program==<br />
<br />
=<b>MIT IAP, January 10-14, 2011</b>=<br />
<br />
==Overview==<br />
* Name of the class: IAP HTML5 Game Programming Course and Competition<br />
* Coursework Component: 5 sessions, 2 hours each (total instruction time 10 hours)<br />
*Schedule, everyday 11.30-1.30pm EST<br />
*Room is 32-141 (32 Vassar St, room #141 (first floor) (http://whereis.mit.edu/)<br />
*Onsite support:<br />
**mitcho (Michael Erlewine), mitcho@mit.edu<br />
**office: 32-D866, Mondays during IAP or by appointment<br />
*Online support:<br />
**[http://irc.mozilla.org/ IRC] #mitiap2011<br />
**Feel free to email anyone from the group of the lecturers in case you have any specific question related to the course<br />
**Julie Deroche: jgoulie(IRC) or julie@mozilla.com<br />
*Here's a list of some [http://en.wikipedia.org/wiki/IRC#Client_software IRC clients] depending on your OS.<br><br />
*<b>Emergency line for the Stata Center</b>: 617-253-7669 || Please call on Wednesday to make sure the center is open!<br><br><br />
<br />
==Layout of the week==<br />
===January 10, 2011===<br />
*Lecturer: Dave Herman<br />
*<b>Lecture notes</b>: http://www.ccs.neu.edu/home/dherman/mit-iap-2011/<br />
*Contact info:<br />
**Email: dherman@mozilla.com<br />
**IRC: dherman -- available on irc.mozilla.org at #jslang and #jsapi <br />
**Twitter: @littlecalculist<br />
*Topics covered: Foundations of JavaScript programming in the browser. Language syntax and concepts. Browser environment, events. (object and prototype, scope and global object, closures, events and call backs, numbers, XHR)<br />
*Resources:<br />
**https://developer.mozilla.org/en/JavaScript/Guide<br />
**https://developer.mozilla.org/En/XMLHttpRequest/Using_XMLHttpRequest //documentation on XHR, which Dave will be talking a bit during his lecture (Students may or may not need it for their games, but it's a good way to learn about using callbacks for event handling without having to learn all the complications of DOM events.)<br />
**http://www.squarefree.com/shell/shell.html //Students can use it to test out JS commands in any browser. But the more recommended way would be to use the built-in developer tools of their browser (FF4 console or Firebug, Chrome console, Safari console).<br />
<br />
===January 11, 2011===<br />
*Lecturer: Boris Zbarsky<br />
*Contact info<br />
**Email: bzbarsky@mit.edu<br />
**IRC: bz -- available on irc.mozilla.org at #developers<br />
*Topics covered: The Document Object Model (DOM), the canvas element, resource loading (graphics)<br><br />
*Resources:<br />
**Presentation: http://web.mit.edu/bzbarsky/www/IAP-2011-DOM-talk/intro.html<br />
**HTML5 (draft): http://www.whatwg.org/specs/web-apps/current-work/multipage/<br />
**XMLHttpRequest (close to final): http://www.w3.org/TR/XMLHttpRequest/<br />
**XMLHttpRequest extensions (draft): http://dev.w3.org/2006/webapi/XMLHttpRequest-2/<br />
**CORS (for cross-site XMLHttpRequest, draft): http://www.w3.org/TR/cors/<br />
**CSS 2.1 (close to final): http://www.w3.org/TR/CSS21/<br />
**Canvas (mix of close to final and draft): http://www.whatwg.org/specs/web-apps/current-work/multipage/the-canvas-element.html<br />
**DOM Core: http://www.w3.org/TR/DOM-Level-3-Core/core.html<br />
**DOM Events: http://www.w3.org/TR/DOM-Level-2-Events/events.html<br />
<br />
===January 12, 2011===<br />
*Lecturers: Benoit Jacob and Andor Salga<br />
*Lecture notes: http://people.mozilla.org/~bjacob/iap2011/slides<br />
*Contact info (Benoit)<br />
**Email: bjacob@mozilla.com<br />
**IRC: bjacob -- available on irc.mozilla.org at #developers #gfx #audio<br />
*Contact info (Andor)<br />
**Email: andor.salga@senecac.on.ca<br />
**IRC: nick:asalga -- available on irc.mozilla.org on #Seneca #Processing.js and #C3DL Also avaiable on irc.freenode.net on #WebGL<br />
**Twitter: @asalga<br />
**Wordpress: http://asalga.wordpress.com<br><br />
*Topics covered: Introduction to 3D graphics with OpenGL/WebGL. Basics of shader programming<br />
*Notes from the lecture: https://github.com/bjacob/webgl-lessons/tree/master/iap2011<br><br />
*Useful links<br />
**WebGL specification: https://cvs.khronos.org/svn/repos/registry/trunk/public/webgl/doc/spec/WebGL-spec.html<br />
**WebGL tutorials: http://www.learningWebGL.com<br />
**http://www.doesmybrowsersupportwebgl.com/<br />
**http://learningwebgl.com/lessons/<br />
*Further links<br />
**WebGL point cloud renderer: http://zenit.senecac.on.ca/wiki/index.php/XB_PointStream<br />
**Data visualizer library which uses WebGL: www.processingjs.org<br />
**WebGL library: www.c3dl.org<br><br><br />
<br />
===January 13, 2011===<br />
*Lecturer: Chris Heilmann<br />
*Topics covered: Multimedia on the web - audio and video<br />
*Notes from the lecture:http://www.wait-till-i.com/2011/01/16/lecturing-at-mit-about-html5-video-slides-and-lots-of-notes/<br />
<br />
===January 14, 2011===<br />
*Lecturer: Pascal Rettig from [http://cykod.com/ Cykod]<br />
*Topics covered: Offline web applications, local storage, debugging and optimizing JS performance. Also to be discussed: server side Javascript (node.js) and Web sockets.<br />
*Resources:<br />
**Offline storage - http://diveintohtml5.org/offline.html<br />
**Local storage - http://diveintohtml5.org/storage.html<br />
**JS Debugging /w Firebug - http://getfirebug.com/javascript<br />
**Node.js - http://nodejs.org/<br />
**Node Package Manager - http://npmjs.org/<br />
**Node Realtime Sockets Module - http://socket.io/<br />
*Notes from the lecture: http://www.slideshare.net/cykod/javascript-everywhere<br />
*Further notes from the class: http://www.slideshare.net/cykod/vector-graphics-on-the-web-svg-canvas-css3<br />
<br />
==Competition==<br />
===Summary===<br />
After the course work component, students will compete in a HTML5 game programming competition. Mozilla will host a discussion forum for students to communicate and collaborate and ask and answer questions amongst each other (irc.mozilla.org, #mitiap2010). The goal is for students to implement an interesting HTML5 game or visual demonstration. Whether its a create re-implementation of existing games (HTML5 pong?), or a full fledge 3D game, anything goes. <br><br />
===Prize===<br />
The winning team (up to 4 team members max) will come to Mountain View and spend a w/e in SF. During their time at Mozila, the team will present its demo/game and spend some time with Brendan Eich. We will also offer a 1K stipend to the winning team to make sure you enjoy your time in sunny California. One last piece of swag will be a signed copy of John Resig's latest book: [http://jsninja.com/ Secrets of the JavaScript Ninja] <br />
===Criteria for the competition===<br />
*Deadline is February 20, 2011<br />
*Teams composition: up to 4 students<br />
*Use of existing libraries allowed, but you may not copy existing games<br />
=== Games Gallery ===<br />
<br />
[[Dots - Team Blobby]] <br> [[HTML5 Demo - Team Tom]]<br> [[QRticullis - Team Viral Ecology]]</div>Jgouliehttps://wiki.mozilla.org/index.php?title=User:Jgoulie&diff=374187User:Jgoulie2011-11-29T20:15:18Z<p>Jgoulie: </p>
<hr />
<div>=<b>Mozilla Workshops for Mozilla Tunisia</b><br />
[[Overview of the Program|Overview of the Mozilla Tunisia Workshops]]<br />
<br />
=<b>MIT IAP, January 10-14, 2011</b>=<br />
<br />
==Overview==<br />
* Name of the class: IAP HTML5 Game Programming Course and Competition<br />
* Coursework Component: 5 sessions, 2 hours each (total instruction time 10 hours)<br />
*Schedule, everyday 11.30-1.30pm EST<br />
*Room is 32-141 (32 Vassar St, room #141 (first floor) (http://whereis.mit.edu/)<br />
*Onsite support:<br />
**mitcho (Michael Erlewine), mitcho@mit.edu<br />
**office: 32-D866, Mondays during IAP or by appointment<br />
*Online support:<br />
**[http://irc.mozilla.org/ IRC] #mitiap2011<br />
**Feel free to email anyone from the group of the lecturers in case you have any specific question related to the course<br />
**Julie Deroche: jgoulie(IRC) or julie@mozilla.com<br />
*Here's a list of some [http://en.wikipedia.org/wiki/IRC#Client_software IRC clients] depending on your OS.<br><br />
*<b>Emergency line for the Stata Center</b>: 617-253-7669 || Please call on Wednesday to make sure the center is open!<br><br><br />
<br />
==Layout of the week==<br />
===January 10, 2011===<br />
*Lecturer: Dave Herman<br />
*<b>Lecture notes</b>: http://www.ccs.neu.edu/home/dherman/mit-iap-2011/<br />
*Contact info:<br />
**Email: dherman@mozilla.com<br />
**IRC: dherman -- available on irc.mozilla.org at #jslang and #jsapi <br />
**Twitter: @littlecalculist<br />
*Topics covered: Foundations of JavaScript programming in the browser. Language syntax and concepts. Browser environment, events. (object and prototype, scope and global object, closures, events and call backs, numbers, XHR)<br />
*Resources:<br />
**https://developer.mozilla.org/en/JavaScript/Guide<br />
**https://developer.mozilla.org/En/XMLHttpRequest/Using_XMLHttpRequest //documentation on XHR, which Dave will be talking a bit during his lecture (Students may or may not need it for their games, but it's a good way to learn about using callbacks for event handling without having to learn all the complications of DOM events.)<br />
**http://www.squarefree.com/shell/shell.html //Students can use it to test out JS commands in any browser. But the more recommended way would be to use the built-in developer tools of their browser (FF4 console or Firebug, Chrome console, Safari console).<br />
<br />
===January 11, 2011===<br />
*Lecturer: Boris Zbarsky<br />
*Contact info<br />
**Email: bzbarsky@mit.edu<br />
**IRC: bz -- available on irc.mozilla.org at #developers<br />
*Topics covered: The Document Object Model (DOM), the canvas element, resource loading (graphics)<br><br />
*Resources:<br />
**Presentation: http://web.mit.edu/bzbarsky/www/IAP-2011-DOM-talk/intro.html<br />
**HTML5 (draft): http://www.whatwg.org/specs/web-apps/current-work/multipage/<br />
**XMLHttpRequest (close to final): http://www.w3.org/TR/XMLHttpRequest/<br />
**XMLHttpRequest extensions (draft): http://dev.w3.org/2006/webapi/XMLHttpRequest-2/<br />
**CORS (for cross-site XMLHttpRequest, draft): http://www.w3.org/TR/cors/<br />
**CSS 2.1 (close to final): http://www.w3.org/TR/CSS21/<br />
**Canvas (mix of close to final and draft): http://www.whatwg.org/specs/web-apps/current-work/multipage/the-canvas-element.html<br />
**DOM Core: http://www.w3.org/TR/DOM-Level-3-Core/core.html<br />
**DOM Events: http://www.w3.org/TR/DOM-Level-2-Events/events.html<br />
<br />
===January 12, 2011===<br />
*Lecturers: Benoit Jacob and Andor Salga<br />
*Lecture notes: http://people.mozilla.org/~bjacob/iap2011/slides<br />
*Contact info (Benoit)<br />
**Email: bjacob@mozilla.com<br />
**IRC: bjacob -- available on irc.mozilla.org at #developers #gfx #audio<br />
*Contact info (Andor)<br />
**Email: andor.salga@senecac.on.ca<br />
**IRC: nick:asalga -- available on irc.mozilla.org on #Seneca #Processing.js and #C3DL Also avaiable on irc.freenode.net on #WebGL<br />
**Twitter: @asalga<br />
**Wordpress: http://asalga.wordpress.com<br><br />
*Topics covered: Introduction to 3D graphics with OpenGL/WebGL. Basics of shader programming<br />
*Notes from the lecture: https://github.com/bjacob/webgl-lessons/tree/master/iap2011<br><br />
*Useful links<br />
**WebGL specification: https://cvs.khronos.org/svn/repos/registry/trunk/public/webgl/doc/spec/WebGL-spec.html<br />
**WebGL tutorials: http://www.learningWebGL.com<br />
**http://www.doesmybrowsersupportwebgl.com/<br />
**http://learningwebgl.com/lessons/<br />
*Further links<br />
**WebGL point cloud renderer: http://zenit.senecac.on.ca/wiki/index.php/XB_PointStream<br />
**Data visualizer library which uses WebGL: www.processingjs.org<br />
**WebGL library: www.c3dl.org<br><br><br />
<br />
===January 13, 2011===<br />
*Lecturer: Chris Heilmann<br />
*Topics covered: Multimedia on the web - audio and video<br />
*Notes from the lecture:http://www.wait-till-i.com/2011/01/16/lecturing-at-mit-about-html5-video-slides-and-lots-of-notes/<br />
<br />
===January 14, 2011===<br />
*Lecturer: Pascal Rettig from [http://cykod.com/ Cykod]<br />
*Topics covered: Offline web applications, local storage, debugging and optimizing JS performance. Also to be discussed: server side Javascript (node.js) and Web sockets.<br />
*Resources:<br />
**Offline storage - http://diveintohtml5.org/offline.html<br />
**Local storage - http://diveintohtml5.org/storage.html<br />
**JS Debugging /w Firebug - http://getfirebug.com/javascript<br />
**Node.js - http://nodejs.org/<br />
**Node Package Manager - http://npmjs.org/<br />
**Node Realtime Sockets Module - http://socket.io/<br />
*Notes from the lecture: http://www.slideshare.net/cykod/javascript-everywhere<br />
*Further notes from the class: http://www.slideshare.net/cykod/vector-graphics-on-the-web-svg-canvas-css3<br />
<br />
==Competition==<br />
===Summary===<br />
After the course work component, students will compete in a HTML5 game programming competition. Mozilla will host a discussion forum for students to communicate and collaborate and ask and answer questions amongst each other (irc.mozilla.org, #mitiap2010). The goal is for students to implement an interesting HTML5 game or visual demonstration. Whether its a create re-implementation of existing games (HTML5 pong?), or a full fledge 3D game, anything goes. <br><br />
===Prize===<br />
The winning team (up to 4 team members max) will come to Mountain View and spend a w/e in SF. During their time at Mozila, the team will present its demo/game and spend some time with Brendan Eich. We will also offer a 1K stipend to the winning team to make sure you enjoy your time in sunny California. One last piece of swag will be a signed copy of John Resig's latest book: [http://jsninja.com/ Secrets of the JavaScript Ninja] <br />
===Criteria for the competition===<br />
*Deadline is February 20, 2011<br />
*Teams composition: up to 4 students<br />
*Use of existing libraries allowed, but you may not copy existing games<br />
=== Games Gallery ===<br />
<br />
[[Dots - Team Blobby]] <br> [[HTML5 Demo - Team Tom]]<br> [[QRticullis - Team Viral Ecology]]</div>Jgouliehttps://wiki.mozilla.org/index.php?title=User:Jgoulie&diff=374185User:Jgoulie2011-11-29T20:12:33Z<p>Jgoulie: </p>
<hr />
<div>=<b>Mozilla Workshops | Pilot Program</b>=<br />
* [[Overview|Overview of the Mozilla Tunisia Workshops]]<br />
=<b>MIT IAP, January 10-14, 2011</b>=<br />
<br />
==Overview==<br />
* Name of the class: IAP HTML5 Game Programming Course and Competition<br />
* Coursework Component: 5 sessions, 2 hours each (total instruction time 10 hours)<br />
*Schedule, everyday 11.30-1.30pm EST<br />
*Room is 32-141 (32 Vassar St, room #141 (first floor) (http://whereis.mit.edu/)<br />
*Onsite support:<br />
**mitcho (Michael Erlewine), mitcho@mit.edu<br />
**office: 32-D866, Mondays during IAP or by appointment<br />
*Online support:<br />
**[http://irc.mozilla.org/ IRC] #mitiap2011<br />
**Feel free to email anyone from the group of the lecturers in case you have any specific question related to the course<br />
**Julie Deroche: jgoulie(IRC) or julie@mozilla.com<br />
*Here's a list of some [http://en.wikipedia.org/wiki/IRC#Client_software IRC clients] depending on your OS.<br><br />
*<b>Emergency line for the Stata Center</b>: 617-253-7669 || Please call on Wednesday to make sure the center is open!<br><br><br />
<br />
==Layout of the week==<br />
===January 10, 2011===<br />
*Lecturer: Dave Herman<br />
*<b>Lecture notes</b>: http://www.ccs.neu.edu/home/dherman/mit-iap-2011/<br />
*Contact info:<br />
**Email: dherman@mozilla.com<br />
**IRC: dherman -- available on irc.mozilla.org at #jslang and #jsapi <br />
**Twitter: @littlecalculist<br />
*Topics covered: Foundations of JavaScript programming in the browser. Language syntax and concepts. Browser environment, events. (object and prototype, scope and global object, closures, events and call backs, numbers, XHR)<br />
*Resources:<br />
**https://developer.mozilla.org/en/JavaScript/Guide<br />
**https://developer.mozilla.org/En/XMLHttpRequest/Using_XMLHttpRequest //documentation on XHR, which Dave will be talking a bit during his lecture (Students may or may not need it for their games, but it's a good way to learn about using callbacks for event handling without having to learn all the complications of DOM events.)<br />
**http://www.squarefree.com/shell/shell.html //Students can use it to test out JS commands in any browser. But the more recommended way would be to use the built-in developer tools of their browser (FF4 console or Firebug, Chrome console, Safari console).<br />
<br />
===January 11, 2011===<br />
*Lecturer: Boris Zbarsky<br />
*Contact info<br />
**Email: bzbarsky@mit.edu<br />
**IRC: bz -- available on irc.mozilla.org at #developers<br />
*Topics covered: The Document Object Model (DOM), the canvas element, resource loading (graphics)<br><br />
*Resources:<br />
**Presentation: http://web.mit.edu/bzbarsky/www/IAP-2011-DOM-talk/intro.html<br />
**HTML5 (draft): http://www.whatwg.org/specs/web-apps/current-work/multipage/<br />
**XMLHttpRequest (close to final): http://www.w3.org/TR/XMLHttpRequest/<br />
**XMLHttpRequest extensions (draft): http://dev.w3.org/2006/webapi/XMLHttpRequest-2/<br />
**CORS (for cross-site XMLHttpRequest, draft): http://www.w3.org/TR/cors/<br />
**CSS 2.1 (close to final): http://www.w3.org/TR/CSS21/<br />
**Canvas (mix of close to final and draft): http://www.whatwg.org/specs/web-apps/current-work/multipage/the-canvas-element.html<br />
**DOM Core: http://www.w3.org/TR/DOM-Level-3-Core/core.html<br />
**DOM Events: http://www.w3.org/TR/DOM-Level-2-Events/events.html<br />
<br />
===January 12, 2011===<br />
*Lecturers: Benoit Jacob and Andor Salga<br />
*Lecture notes: http://people.mozilla.org/~bjacob/iap2011/slides<br />
*Contact info (Benoit)<br />
**Email: bjacob@mozilla.com<br />
**IRC: bjacob -- available on irc.mozilla.org at #developers #gfx #audio<br />
*Contact info (Andor)<br />
**Email: andor.salga@senecac.on.ca<br />
**IRC: nick:asalga -- available on irc.mozilla.org on #Seneca #Processing.js and #C3DL Also avaiable on irc.freenode.net on #WebGL<br />
**Twitter: @asalga<br />
**Wordpress: http://asalga.wordpress.com<br><br />
*Topics covered: Introduction to 3D graphics with OpenGL/WebGL. Basics of shader programming<br />
*Notes from the lecture: https://github.com/bjacob/webgl-lessons/tree/master/iap2011<br><br />
*Useful links<br />
**WebGL specification: https://cvs.khronos.org/svn/repos/registry/trunk/public/webgl/doc/spec/WebGL-spec.html<br />
**WebGL tutorials: http://www.learningWebGL.com<br />
**http://www.doesmybrowsersupportwebgl.com/<br />
**http://learningwebgl.com/lessons/<br />
*Further links<br />
**WebGL point cloud renderer: http://zenit.senecac.on.ca/wiki/index.php/XB_PointStream<br />
**Data visualizer library which uses WebGL: www.processingjs.org<br />
**WebGL library: www.c3dl.org<br><br><br />
<br />
===January 13, 2011===<br />
*Lecturer: Chris Heilmann<br />
*Topics covered: Multimedia on the web - audio and video<br />
*Notes from the lecture:http://www.wait-till-i.com/2011/01/16/lecturing-at-mit-about-html5-video-slides-and-lots-of-notes/<br />
<br />
===January 14, 2011===<br />
*Lecturer: Pascal Rettig from [http://cykod.com/ Cykod]<br />
*Topics covered: Offline web applications, local storage, debugging and optimizing JS performance. Also to be discussed: server side Javascript (node.js) and Web sockets.<br />
*Resources:<br />
**Offline storage - http://diveintohtml5.org/offline.html<br />
**Local storage - http://diveintohtml5.org/storage.html<br />
**JS Debugging /w Firebug - http://getfirebug.com/javascript<br />
**Node.js - http://nodejs.org/<br />
**Node Package Manager - http://npmjs.org/<br />
**Node Realtime Sockets Module - http://socket.io/<br />
*Notes from the lecture: http://www.slideshare.net/cykod/javascript-everywhere<br />
*Further notes from the class: http://www.slideshare.net/cykod/vector-graphics-on-the-web-svg-canvas-css3<br />
<br />
==Competition==<br />
===Summary===<br />
After the course work component, students will compete in a HTML5 game programming competition. Mozilla will host a discussion forum for students to communicate and collaborate and ask and answer questions amongst each other (irc.mozilla.org, #mitiap2010). The goal is for students to implement an interesting HTML5 game or visual demonstration. Whether its a create re-implementation of existing games (HTML5 pong?), or a full fledge 3D game, anything goes. <br><br />
===Prize===<br />
The winning team (up to 4 team members max) will come to Mountain View and spend a w/e in SF. During their time at Mozila, the team will present its demo/game and spend some time with Brendan Eich. We will also offer a 1K stipend to the winning team to make sure you enjoy your time in sunny California. One last piece of swag will be a signed copy of John Resig's latest book: [http://jsninja.com/ Secrets of the JavaScript Ninja] <br />
===Criteria for the competition===<br />
*Deadline is February 20, 2011<br />
*Teams composition: up to 4 students<br />
*Use of existing libraries allowed, but you may not copy existing games<br />
=== Games Gallery ===<br />
<br />
[[Dots - Team Blobby]] <br> [[HTML5 Demo - Team Tom]]<br> [[QRticullis - Team Viral Ecology]]</div>Jgouliehttps://wiki.mozilla.org/index.php?title=User:Jgoulie&diff=374179User:Jgoulie2011-11-29T20:03:53Z<p>Jgoulie: </p>
<hr />
<div>=<b>Mozilla Workshops | Pilot Program</b>=<br />
<br />
=<b>MIT IAP, January 10-14, 2011</b>=<br />
<br />
==Overview==<br />
* Name of the class: IAP HTML5 Game Programming Course and Competition<br />
* Coursework Component: 5 sessions, 2 hours each (total instruction time 10 hours)<br />
*Schedule, everyday 11.30-1.30pm EST<br />
*Room is 32-141 (32 Vassar St, room #141 (first floor) (http://whereis.mit.edu/)<br />
*Onsite support:<br />
**mitcho (Michael Erlewine), mitcho@mit.edu<br />
**office: 32-D866, Mondays during IAP or by appointment<br />
*Online support:<br />
**[http://irc.mozilla.org/ IRC] #mitiap2011<br />
**Feel free to email anyone from the group of the lecturers in case you have any specific question related to the course<br />
**Julie Deroche: jgoulie(IRC) or julie@mozilla.com<br />
*Here's a list of some [http://en.wikipedia.org/wiki/IRC#Client_software IRC clients] depending on your OS.<br><br />
*<b>Emergency line for the Stata Center</b>: 617-253-7669 || Please call on Wednesday to make sure the center is open!<br><br><br />
<br />
==Layout of the week==<br />
===January 10, 2011===<br />
*Lecturer: Dave Herman<br />
*<b>Lecture notes</b>: http://www.ccs.neu.edu/home/dherman/mit-iap-2011/<br />
*Contact info:<br />
**Email: dherman@mozilla.com<br />
**IRC: dherman -- available on irc.mozilla.org at #jslang and #jsapi <br />
**Twitter: @littlecalculist<br />
*Topics covered: Foundations of JavaScript programming in the browser. Language syntax and concepts. Browser environment, events. (object and prototype, scope and global object, closures, events and call backs, numbers, XHR)<br />
*Resources:<br />
**https://developer.mozilla.org/en/JavaScript/Guide<br />
**https://developer.mozilla.org/En/XMLHttpRequest/Using_XMLHttpRequest //documentation on XHR, which Dave will be talking a bit during his lecture (Students may or may not need it for their games, but it's a good way to learn about using callbacks for event handling without having to learn all the complications of DOM events.)<br />
**http://www.squarefree.com/shell/shell.html //Students can use it to test out JS commands in any browser. But the more recommended way would be to use the built-in developer tools of their browser (FF4 console or Firebug, Chrome console, Safari console).<br />
<br />
===January 11, 2011===<br />
*Lecturer: Boris Zbarsky<br />
*Contact info<br />
**Email: bzbarsky@mit.edu<br />
**IRC: bz -- available on irc.mozilla.org at #developers<br />
*Topics covered: The Document Object Model (DOM), the canvas element, resource loading (graphics)<br><br />
*Resources:<br />
**Presentation: http://web.mit.edu/bzbarsky/www/IAP-2011-DOM-talk/intro.html<br />
**HTML5 (draft): http://www.whatwg.org/specs/web-apps/current-work/multipage/<br />
**XMLHttpRequest (close to final): http://www.w3.org/TR/XMLHttpRequest/<br />
**XMLHttpRequest extensions (draft): http://dev.w3.org/2006/webapi/XMLHttpRequest-2/<br />
**CORS (for cross-site XMLHttpRequest, draft): http://www.w3.org/TR/cors/<br />
**CSS 2.1 (close to final): http://www.w3.org/TR/CSS21/<br />
**Canvas (mix of close to final and draft): http://www.whatwg.org/specs/web-apps/current-work/multipage/the-canvas-element.html<br />
**DOM Core: http://www.w3.org/TR/DOM-Level-3-Core/core.html<br />
**DOM Events: http://www.w3.org/TR/DOM-Level-2-Events/events.html<br />
<br />
===January 12, 2011===<br />
*Lecturers: Benoit Jacob and Andor Salga<br />
*Lecture notes: http://people.mozilla.org/~bjacob/iap2011/slides<br />
*Contact info (Benoit)<br />
**Email: bjacob@mozilla.com<br />
**IRC: bjacob -- available on irc.mozilla.org at #developers #gfx #audio<br />
*Contact info (Andor)<br />
**Email: andor.salga@senecac.on.ca<br />
**IRC: nick:asalga -- available on irc.mozilla.org on #Seneca #Processing.js and #C3DL Also avaiable on irc.freenode.net on #WebGL<br />
**Twitter: @asalga<br />
**Wordpress: http://asalga.wordpress.com<br><br />
*Topics covered: Introduction to 3D graphics with OpenGL/WebGL. Basics of shader programming<br />
*Notes from the lecture: https://github.com/bjacob/webgl-lessons/tree/master/iap2011<br><br />
*Useful links<br />
**WebGL specification: https://cvs.khronos.org/svn/repos/registry/trunk/public/webgl/doc/spec/WebGL-spec.html<br />
**WebGL tutorials: http://www.learningWebGL.com<br />
**http://www.doesmybrowsersupportwebgl.com/<br />
**http://learningwebgl.com/lessons/<br />
*Further links<br />
**WebGL point cloud renderer: http://zenit.senecac.on.ca/wiki/index.php/XB_PointStream<br />
**Data visualizer library which uses WebGL: www.processingjs.org<br />
**WebGL library: www.c3dl.org<br><br><br />
<br />
===January 13, 2011===<br />
*Lecturer: Chris Heilmann<br />
*Topics covered: Multimedia on the web - audio and video<br />
*Notes from the lecture:http://www.wait-till-i.com/2011/01/16/lecturing-at-mit-about-html5-video-slides-and-lots-of-notes/<br />
<br />
===January 14, 2011===<br />
*Lecturer: Pascal Rettig from [http://cykod.com/ Cykod]<br />
*Topics covered: Offline web applications, local storage, debugging and optimizing JS performance. Also to be discussed: server side Javascript (node.js) and Web sockets.<br />
*Resources:<br />
**Offline storage - http://diveintohtml5.org/offline.html<br />
**Local storage - http://diveintohtml5.org/storage.html<br />
**JS Debugging /w Firebug - http://getfirebug.com/javascript<br />
**Node.js - http://nodejs.org/<br />
**Node Package Manager - http://npmjs.org/<br />
**Node Realtime Sockets Module - http://socket.io/<br />
*Notes from the lecture: http://www.slideshare.net/cykod/javascript-everywhere<br />
*Further notes from the class: http://www.slideshare.net/cykod/vector-graphics-on-the-web-svg-canvas-css3<br />
<br />
==Competition==<br />
===Summary===<br />
After the course work component, students will compete in a HTML5 game programming competition. Mozilla will host a discussion forum for students to communicate and collaborate and ask and answer questions amongst each other (irc.mozilla.org, #mitiap2010). The goal is for students to implement an interesting HTML5 game or visual demonstration. Whether its a create re-implementation of existing games (HTML5 pong?), or a full fledge 3D game, anything goes. <br><br />
===Prize===<br />
The winning team (up to 4 team members max) will come to Mountain View and spend a w/e in SF. During their time at Mozila, the team will present its demo/game and spend some time with Brendan Eich. We will also offer a 1K stipend to the winning team to make sure you enjoy your time in sunny California. One last piece of swag will be a signed copy of John Resig's latest book: [http://jsninja.com/ Secrets of the JavaScript Ninja] <br />
===Criteria for the competition===<br />
*Deadline is February 20, 2011<br />
*Teams composition: up to 4 students<br />
*Use of existing libraries allowed, but you may not copy existing games<br />
=== Games Gallery ===<br />
<br />
[[Dots - Team Blobby]] <br> [[HTML5 Demo - Team Tom]]<br> [[QRticullis - Team Viral Ecology]]</div>Jgouliehttps://wiki.mozilla.org/index.php?title=IonMonkey&diff=365956IonMonkey2011-11-07T19:19:13Z<p>Jgoulie: </p>
<hr />
<div>IonMonkey is the next generation JavaScript JIT compiler for SpiderMonkey. It is a whole-method JIT with the ability to perform type specialization. It has two goals: a cleanly engineered design that makes future optimization work possible, and excellent performance.<br />
<br />
=Planning=<br />
<br />
See [[Platform/Features/IonMonkey]] for IonMonkey's planning page.<br />
<br />
=Design=<br />
<br />
See [[IonMonkey/Overview]] for an overview of the IonMonkey architecture and its files.<br />
<br />
=Development=<br />
<br />
*Source code: [http://hg.mozilla.org/projects/ionmonkey http://hg.mozilla.org/projects/ionmonkey]<br />
*TBPL: [http://tbpl.mozilla.org/?tree=Ionmonkey http://tbpl.mozilla.org/?tree=Ionmonkey]<br />
<br />
To get started, see the [https://developer.mozilla.org/En/SpiderMonkey/Build_Documentation Build Documentation for SpiderMonkey]. Use the '-h' shell option to see all of IonMonkey's options.<br />
<br />
Currently, IonMonkey is disabled by default. Use '--ion' to enable it.<br />
<br />
=Debugging=<br />
<br />
A few tools exist to help debug IonMonkey.<br />
*Debug spew, controlled by the environment variable <tt>IONFLAGS</tt>. Set it to <tt>help</tt> to see available options.<br />
*Instruction spew, via setting the environment variable <tt>JMFLAGS</tt> to <tt>insns</tt>.<br />
*[http://java.net/projects/c1visualizer/ c1visualizer] IonMonkey writes a spew file to <tt>/tmp/ion.cfg</tt>, which can be imported into the c1visualizer. It can display a clickable control-flow graph, MIR, LIR, and liveness intervals for LSRA.<br />
*[https://github.com/sstangl/iongraph iongraph] by Sean Stangl, using IonMonkey's JSON spew.</div>Jgouliehttps://wiki.mozilla.org/index.php?title=Websites/Careers&diff=364975Websites/Careers2011-11-04T19:46:16Z<p>Jgoulie: /* Where we are now */</p>
<hr />
<div>'''{{bug|604247}} - Tracking bug'''<br />
<br />
= Elevator Pitch =<br />
Let's make our careers site rock.<br />
<br />
= Description =<br />
<br />
== Where we are now ==<br />
<br />
http://www.mozilla.org/en-US/careers <br><br />
https://college.mozilla.com <br><br />
http://linoderedis.server.serverboy.net/wp/<br />
<br />
== What we want to improve ==<br />
* need to serve 4 channels: career, volunteer, foundation and college<br />
* Better integration with Jobvite feeds so user can stay on Mozilla.org site longer.<br />
* college is a seperate site, in wordpress, but we’ll want to tie in to it<br />
* want the visitor to be able to slice by location, experience and level<br />
* improvements to the application process. e.g. can we add fields that will enable us to screen applicants earlier?<br />
* Want to add team videos. Can shoot them over time and add as ready.<br />
* On the careers landing page, we should consider featuring / linking to the following:<br />
* MozSpaces and Offices (Map?)<br />
* Featured WFH setups<br />
* YouTube Channel with employees & what they do<br />
* Salary info (e.g that we offer competitive pay)<br />
<br />
= Overview =<br />
<br />
* Code name: <br />
* Prod URL: <br />
* Stage URL: <br />
* Code Repo: https://github.com/mozilla/bedrock/tree/master/apps/careers<br />
* L10N Repo: <br />
* Code: <br />
* Product Owner: [https://phonebook.mozilla.org/#search/breckard breckard]<br />
* Dev Team: <br />
* IRC Channel: #{websitename} on irc.mozilla.com<br />
* Team Email: <br />
<br />
= Meetings =<br />
<br />
* [[Websites/Careers/meetings/10-19-2010|10-19-2011 -- Re-starting the project]]<br />
<br />
<br />
== Kickoff Meeting ==<br />
* [[Websites/Careers/meetings/kickoff|(Re)Kick-off Meeting]]<br />
<br />
== Weekly Meetings ==<br />
== Retrospectives ==<br />
<br />
= Designs =<br />
<br />
== Mockups ==<br />
* [https://mofo.mozillalabs.com/en-US/careers html mockup]<br />
(this seems to have disappeared, but ckoehler is looking for it.)<br />
* [https://www.dropbox.com/gallery/10327105/2/Mockups/Careers?h=9c8c33#/ design comps]<br />
<br />
== Wireframes ==<br />
== User Stories ==<br />
<br />
= Bugs =<br />
Bugs should be filed with normal visibility; Security bugs should be filed with private visibility.<br />
<br />
* {{bug|604247}} - Tracking bug<br />
<br />
= End of Life =</div>Jgouliehttps://wiki.mozilla.org/index.php?title=Websites/Careers&diff=364974Websites/Careers2011-11-04T19:45:14Z<p>Jgoulie: /* Where we are now */</p>
<hr />
<div>'''{{bug|604247}} - Tracking bug'''<br />
<br />
= Elevator Pitch =<br />
Let's make our careers site rock.<br />
<br />
= Description =<br />
<br />
== Where we are now ==<br />
<br />
http://www.mozilla.org/en-US/careers<br />
http://linoderedis.server.serverboy.net/wp/<br />
<br />
== What we want to improve ==<br />
* need to serve 4 channels: career, volunteer, foundation and college<br />
* Better integration with Jobvite feeds so user can stay on Mozilla.org site longer.<br />
* college is a seperate site, in wordpress, but we’ll want to tie in to it<br />
* want the visitor to be able to slice by location, experience and level<br />
* improvements to the application process. e.g. can we add fields that will enable us to screen applicants earlier?<br />
* Want to add team videos. Can shoot them over time and add as ready.<br />
* On the careers landing page, we should consider featuring / linking to the following:<br />
* MozSpaces and Offices (Map?)<br />
* Featured WFH setups<br />
* YouTube Channel with employees & what they do<br />
* Salary info (e.g that we offer competitive pay)<br />
<br />
= Overview =<br />
<br />
* Code name: <br />
* Prod URL: <br />
* Stage URL: <br />
* Code Repo: https://github.com/mozilla/bedrock/tree/master/apps/careers<br />
* L10N Repo: <br />
* Code: <br />
* Product Owner: [https://phonebook.mozilla.org/#search/breckard breckard]<br />
* Dev Team: <br />
* IRC Channel: #{websitename} on irc.mozilla.com<br />
* Team Email: <br />
<br />
= Meetings =<br />
<br />
* [[Websites/Careers/meetings/10-19-2010|10-19-2011 -- Re-starting the project]]<br />
<br />
<br />
== Kickoff Meeting ==<br />
* [[Websites/Careers/meetings/kickoff|(Re)Kick-off Meeting]]<br />
<br />
== Weekly Meetings ==<br />
== Retrospectives ==<br />
<br />
= Designs =<br />
<br />
== Mockups ==<br />
* [https://mofo.mozillalabs.com/en-US/careers html mockup]<br />
(this seems to have disappeared, but ckoehler is looking for it.)<br />
* [https://www.dropbox.com/gallery/10327105/2/Mockups/Careers?h=9c8c33#/ design comps]<br />
<br />
== Wireframes ==<br />
== User Stories ==<br />
<br />
= Bugs =<br />
Bugs should be filed with normal visibility; Security bugs should be filed with private visibility.<br />
<br />
* {{bug|604247}} - Tracking bug<br />
<br />
= End of Life =</div>Jgouliehttps://wiki.mozilla.org/index.php?title=WeeklyUpdates/2011-08-22&diff=341705WeeklyUpdates/2011-08-222011-08-22T00:28:44Z<p>Jgoulie: /* Introducing New Hires */</p>
<hr />
<div><br />
<small>[[WeeklyUpdates/{{#time:Y-m-d|{{SUBPAGENAME}} -1 week}}|« previous week]] | [[WeeklyUpdates|index]] | [[WeeklyUpdates/{{#time:Y-m-d|{{SUBPAGENAME}} +1 week}}|next week »]]</small><br />
<br />
{{conf|8600}}<br />
<br />
__TOC__<br />
<br />
== Friends of the Tree [[Image:Tree.gif|Friends of the Tree]] ==<br />
<br />
== Upcoming Events ==<br />
<br />
=== This Week ===<br />
<br />
=== Monday, {{#time:d F|{{SUBPAGENAME}}}} ===<br />
<br />
=== Tuesday, {{#time:d F|{{SUBPAGENAME}} +1 day}} ===<br />
<br />
=== Wednesday, {{#time:d F|{{SUBPAGENAME}} +2 days}} ===<br />
<br />
=== Thursday, {{#time:d F|{{SUBPAGENAME}} +3 days}} ===<br />
* Mozilla Hosts [https://wiki.mozilla.org/WebAppSec#August_25.2C_2011_-_OWASP_Bay_Area_Chapter_Meeting OWASP Bay Area Chapter] Meeting at 6pm (10 Forward & Air mozilla)<br />
** Approx 75 security experts attending<br />
** Talks on Enabling Browser Security in Web Applications & BlackHat SEO Spam<br />
<br />
=== Friday, {{#time:d F|{{SUBPAGENAME}} +4 days}} ===<br />
<br />
=== Next Week ===<br />
<br />
== Product Status Updates ==<br />
<br />
=== Firefox Future (7, 8, 9) ===<br />
<br />
=== Firefox Current (3.6, 4.0, 5.0, 6.0) ===<br />
<br />
=== Mobile Firefox ===<br />
<br />
=== Thunderbird ===<br />
<br />
=== Older Branch Work ===<br />
<br />
=== Drumbeat ===<br />
<br />
== Speakers ==<br />
<br />
The limit is 3 minutes per speaker. It's like a lightning talk, but don't feel that you have to have slides in order to make a presentation.<br />
<br />
{| class="fullwidth-table"<br />
|-<br />
! Title<br />
! Presenter<br />
! Topic<br />
! Media<br />
! More Details<br />
|-<br />
| Your Title Here<br />
| Your Name Here<br />
| What are you going to talk about?<br />
| Links to slides or images you want displayed on screen<br />
| Link to where audience can find out more information<br />
|-<br />
|}<br />
<br />
== Status Updates By Team ==<br />
<br />
=== Firefox ===<br />
<br />
=== Platform ===<br />
<br />
=== Messaging ===<br />
<br />
=== Mobile ===<br />
<br />
=== IT ===<br />
<br />
=== Release Engineering ===<br />
<br />
=== QA ===<br />
<br />
==== Test Execution ====<br />
<br />
==== WebQA ====<br />
<br />
==== QA Community ====<br />
<br />
==== Automation Services ====<br />
<br />
=== Automation & Tools ===<br />
<br />
=== Security ===<br />
<br />
=== Engagement ===<br />
<br />
==== PR ====<br />
<br />
==== Events ====<br />
<br />
==== Creative Team ====<br />
<br />
==== Community Marketing ====<br />
<br />
=== Support ===<br />
<br />
=== Metrics ===<br />
<br />
=== Evangelism ===<br />
<br />
=== Labs ===<br />
<br />
=== Developer Tools ===<br />
<br />
=== Add-ons ===<br />
<br />
=== Webdev ===<br />
<br />
=== L10n ===<br />
<br />
=== People Team ===<br />
<br />
== Introducing New Hires ==<br />
<br />
Vivien Jin (College Recruiting - University Programs Manager)<br />
<br />
== Introducing New Interns ==<br />
<br />
Doug Sherk - Platform<br />
<br />
== Foundation Updates ==<br />
<br />
== Roundtable ==</div>Jgouliehttps://wiki.mozilla.org/index.php?title=WeeklyUpdates/2011-08-01&diff=335129WeeklyUpdates/2011-08-012011-08-01T17:47:11Z<p>Jgoulie: /* Speakers */</p>
<hr />
<div><small>[[WeeklyUpdates/2011-07-25|« previous week]] | [[WeeklyUpdates|index]] | [[WeeklyUpdates/2011-08-08|next week »]]</small><br />
<br />
= Video for today's meeting =<br />
<br />
<video controls="controls"><source src="http://videos.mozilla.org/serv/air_mozilla/monday_meetings/status-2011-08-01.ogg" type="video/ogg; codecs=&quot;theora, vorbis&quot;" /></video> <br />
<br />
= Friends of the Tree [[Image:Tree.gif|Friends of the Tree]] =<br />
It's a bit overdue, but a bunch of Mozillians truly deserve a warm thank you for their help with WSOH: (the list is quite long): IT (Tim, mrz, Derek, Guillermo), Havi, Pascal, Julie C, Todd, Potch, CHeilmann, Anant, Philipp, Bret, Kimber, Jill A., Didem, Felipe, Spencer, Margaret, Frank, Gilbert, Saptarshi, Chris Jung, Rainer and Spencer!<br />
<br />
= Upcoming Events =<br />
'''This Week'''<br />
<br />
'''Monday, 1 August'''<br />
<br />
'''Tuesday, 2 August'''<br />
<br />
'''Wednesday, 3 August'''<br />
<br />
'''Thursday, 4 August'''<br />
<br />
'''Friday, 5 August''' <br />
<br />
'''Next Week'''<br />
<br />
= Product Status Updates =<br />
<br />
== Firefox Future (6, 7, 8) ==<br />
* Planning to create the last beta build / "RC" for this cycle on this Wednesday, 2011-08-03<br />
** '''If you find any issues that would prevent us from releasing please email [mailto:release-drivers@mozilla.org release drivers]'''<br />
<br />
* '''Reminder: ''' The next mozilla-central &rarr; mozilla-aurora source migration date is 2011-08-16, ''~2 weeks away''<br />
<br />
== Firefox Current (3.5, 3.6, 4.0, 5.0) ==<br />
<br />
== Mobile Firefox ==<br />
<br />
== Thunderbird ==<br />
<br />
* Thunderbird 6.0 Beta 2 will be released tomorrow.<br />
** The Aero Glass theme has been changed to try and make it easier to read.<br />
** Bug 658534 (can't collapse+expand folders) has been fixed.<br />
<br />
== Older Branch Work ==<br />
<br />
== Drumbeat ==<br />
<br />
= Speakers =<br />
<br />
The limit is 3 minutes per speaker. It's like a lightning talk, but don't feel that you have to have slides in order to make a presentation.<br />
<br />
{| class="fullwidth-table"<br />
|-<br />
! Title<br />
! Presenter<br />
! Topic<br />
! Media<br />
|-<br />
| Firefox Brand Toolkit<br />
| John Slater<br />
| Quick overview of what this is and why we're doing it + we need input<br />
| http://www.intothefuzz.com/2011/08/01/firefox-brand-toolkit-first-draft/<br />
|-<br />
| Announcing Upcoming Metrics Brown Bags<br />
| Gilbert FitzGerald<br />
| Two upcoming brown bags from the Metrics Team: Analytics (8/3/11) and Data Engineering<br />
| <br />
|-<br />
| WSOH<br />
| Julie Deroche<br />
| Quick update + video of the event<br />
| http://www.youtube.com/watch?v=YuQ3byMEuI8<br />
|-<br />
|}<br />
<br />
= Status Updates By Team =<br />
<br />
== Firefox ==<br />
<br />
== Platform ==<br />
<br />
== Messaging ==<br />
<br />
== Mobile ==<br />
<br />
== IT ==<br />
<br />
== Release Engineering ==<br />
<br />
== QA ==<br />
<br />
;Test Execution<br />
* Fx6 Beta 4: To be signed off this morning before ~9am.<br />
** Preparing for a crowd-sourced web compatibility testrun on top sites functionality (to be done by uTest).<br />
<br />
;WebQA<br />
* SUMO: http://moxie.jamessocol.com/bugstats/sumo/2011-07-26<br />
* AMO [https://bugzilla.mozilla.org/buglist.cgi?list_id=918506&resolution=FIXED&classification=Server%20Software&query_format=advanced&target_milestone=6.1.7&product=addons.mozilla.org 6.1.7]<br />
<br />
;QA Community<br />
<br />
;Automation Services<br />
<br />
== Automation & Tools ==<br />
<br />
== Security ==<br />
<br />
== Engagement ==<br />
<br />
'''PR''' <br />
<br><br />
*[http://www.eweek.com/c/a/Mobile-and-Wireless/Mozilla-Building-Mobile-Operating-System-to-Rival-Googles-Chrome-OS-877280/ Mozilla building mobile Operating System to rival Google's Chrome OS]<br />
*[http://www.linuxinsider.com/rsstory/72950.html Mozilla's Head Is in the Cloud With New Mobile OS Idea]<br />
*[http://www.engadget.com/2011/07/26/mozilla-planning-a-chrome-os-like-operating-system-for-phones-an/ Mozilla planning a Chrome OS-like operating system for phones and tablets]<br />
*[http://www.pcworld.com/article/236564/mozillas_boot_to_gecko_a_mobile_os_that_could_succeed.html Mozilla's Boot to Gecko: A mobile OS that could succeed]<br />
*[http://techcrunch.com/2011/07/25/boot-to-gecko-mozillas-open-source-mobile-answer-to-chromeos/ Boot to Gecko: Mozilla's open-source, mobile answer to Chrome OS]<br />
*[http://www.zdnet.com/blog/microsoft/mozillas-boot-to-gecko-a-windows-phone-os-competitor-or-something-else/10180v Mozilla's Boot to Gecko: A Windows Phone OS competitor or something else?]<br />
<br />
*[http://www.h-online.com/open/features/Mozilla-s-next-Firefox-moment-1288362.html Mozilla's next Firefox moment?]<br />
<br />
*[http://www.usatoday.com/tech/news/2011-07-26-mozilla-chrome-internet-explorer-privacy_n.htm Do Not Track' challenges tech industry]<br />
<br />
'''Events''' <br />
<br />
'''Creative Team''' <br />
<br />
'''Community Marketing'''<br />
<br />
== Support ==<br />
<br />
== Metrics ==<br />
<br />
== Evangelism ==<br />
<br />
== Labs ==<br />
<br />
== Developer Tools ==<br />
<br />
== Add-ons ==<br />
<br />
== Webdev ==<br />
<br />
== L10n ==<br />
<br />
= Introducing New Hires =<br />
<br />
<br />
= Introducing a New Intern =<br />
Michael Kurze, Metrics (welcome back!)<br />
<br />
= Foundation Updates =<br />
<br />
= Roundtable =</div>Jgouliehttps://wiki.mozilla.org/index.php?title=WeeklyUpdates/2011-08-01&diff=335120WeeklyUpdates/2011-08-012011-08-01T17:41:00Z<p>Jgoulie: /* Speakers */</p>
<hr />
<div><small>[[WeeklyUpdates/2011-07-25|« previous week]] | [[WeeklyUpdates|index]] | [[WeeklyUpdates/2011-08-08|next week »]]</small><br />
<br />
= Video for today's meeting =<br />
<br />
<video controls="controls"><source src="http://videos.mozilla.org/serv/air_mozilla/monday_meetings/status-2011-08-01.ogg" type="video/ogg; codecs=&quot;theora, vorbis&quot;" /></video> <br />
<br />
= Friends of the Tree [[Image:Tree.gif|Friends of the Tree]] =<br />
It's a bit overdue, but a bunch of Mozillians truly deserve a warm thank you for their help with WSOH: (the list is quite long): IT (Tim, mrz, Derek, Guillermo), Havi, Pascal, Julie C, Todd, Potch, CHeilmann, Anant, Philipp, Bret, Kimber, Jill A., Didem, Felipe, Spencer, Margaret, Frank, Gilbert, Saptarshi, Chris Jung, Rainer and Spencer!<br />
<br />
= Upcoming Events =<br />
'''This Week'''<br />
<br />
'''Monday, 1 August'''<br />
<br />
'''Tuesday, 2 August'''<br />
<br />
'''Wednesday, 3 August'''<br />
<br />
'''Thursday, 4 August'''<br />
<br />
'''Friday, 5 August''' <br />
<br />
'''Next Week'''<br />
<br />
= Product Status Updates =<br />
<br />
== Firefox Future (6, 7, 8) ==<br />
<br />
== Firefox Current (3.5, 3.6, 4.0, 5.0) ==<br />
<br />
== Mobile Firefox ==<br />
<br />
== Thunderbird ==<br />
<br />
== Older Branch Work ==<br />
<br />
== Drumbeat ==<br />
<br />
= Speakers =<br />
<br />
The limit is 3 minutes per speaker. It's like a lightning talk, but don't feel that you have to have slides in order to make a presentation.<br />
<br />
{| class="fullwidth-table"<br />
|-<br />
! Title<br />
! Presenter<br />
! Topic<br />
! Media<br />
! More Details<br />
|-<br />
| Firefox Brand Toolkit<br />
| John Slater<br />
| Quick overview of what this is and why we're doing it + we need input<br />
| http://www.intothefuzz.com/2011/08/01/firefox-brand-toolkit-first-draft/<br />
|-<br />
| Announcing Upcoming Metrics Brown Bags<br />
| Gilbert FitzGerald<br />
| Two upcoming brown bags from the Metrics Team: Analytics (8/3/11) and Data Engineering<br />
| <br />
| <br />
|-<br />
| WSOH<br />
| Julie Deroche<br />
| Quick update + video of the event<br />
| <br />
|-<br />
|}<br />
<br />
= Status Updates By Team =<br />
<br />
== Firefox ==<br />
<br />
== Platform ==<br />
<br />
== Messaging ==<br />
<br />
== Mobile ==<br />
<br />
== IT ==<br />
<br />
== Release Engineering ==<br />
<br />
== QA ==<br />
<br />
;Test Execution<br />
* Fx6 Beta 4: To be signed off this morning before ~9am.<br />
** Preparing for a crowd-sourced web compatibility testrun on top sites functionality (to be done by uTest).<br />
<br />
;WebQA<br />
* SUMO: http://moxie.jamessocol.com/bugstats/sumo/2011-07-26<br />
* AMO [https://bugzilla.mozilla.org/buglist.cgi?list_id=918506&resolution=FIXED&classification=Server%20Software&query_format=advanced&target_milestone=6.1.7&product=addons.mozilla.org 6.1.7]<br />
<br />
;QA Community<br />
<br />
;Automation Services<br />
<br />
== Automation & Tools ==<br />
<br />
== Security ==<br />
<br />
== Engagement ==<br />
<br />
'''PR''' <br />
<br><br />
*[http://www.eweek.com/c/a/Mobile-and-Wireless/Mozilla-Building-Mobile-Operating-System-to-Rival-Googles-Chrome-OS-877280/ Mozilla building mobile Operating System to rival Google's Chrome OS]<br />
*[http://www.linuxinsider.com/rsstory/72950.html Mozilla's Head Is in the Cloud With New Mobile OS Idea]<br />
*[http://www.engadget.com/2011/07/26/mozilla-planning-a-chrome-os-like-operating-system-for-phones-an/ Mozilla planning a Chrome OS-like operating system for phones and tablets]<br />
*[http://www.pcworld.com/article/236564/mozillas_boot_to_gecko_a_mobile_os_that_could_succeed.html Mozilla's Boot to Gecko: A mobile OS that could succeed]<br />
*[http://techcrunch.com/2011/07/25/boot-to-gecko-mozillas-open-source-mobile-answer-to-chromeos/ Boot to Gecko: Mozilla's open-source, mobile answer to Chrome OS]<br />
*[http://www.zdnet.com/blog/microsoft/mozillas-boot-to-gecko-a-windows-phone-os-competitor-or-something-else/10180v Mozilla's Boot to Gecko: A Windows Phone OS competitor or something else?]<br />
<br />
*[http://www.h-online.com/open/features/Mozilla-s-next-Firefox-moment-1288362.html Mozilla's next Firefox moment?]<br />
<br />
*[http://www.usatoday.com/tech/news/2011-07-26-mozilla-chrome-internet-explorer-privacy_n.htm Do Not Track' challenges tech industry]<br />
<br />
'''Events''' <br />
<br />
'''Creative Team''' <br />
<br />
'''Community Marketing'''<br />
<br />
== Support ==<br />
<br />
== Metrics ==<br />
<br />
== Evangelism ==<br />
<br />
== Labs ==<br />
<br />
== Developer Tools ==<br />
<br />
== Add-ons ==<br />
<br />
== Webdev ==<br />
<br />
== L10n ==<br />
<br />
= Introducing New Hires =<br />
<br />
<br />
= Introducing a New Intern =<br />
Michael Kurze, Metrics (welcome back!)<br />
<br />
= Foundation Updates =<br />
<br />
= Roundtable =</div>Jgouliehttps://wiki.mozilla.org/index.php?title=WeeklyUpdates/2011-08-01&diff=335117WeeklyUpdates/2011-08-012011-08-01T17:39:12Z<p>Jgoulie: /* Friends of the Tree Friends of the Tree */</p>
<hr />
<div><small>[[WeeklyUpdates/2011-07-25|« previous week]] | [[WeeklyUpdates|index]] | [[WeeklyUpdates/2011-08-08|next week »]]</small><br />
<br />
= Video for today's meeting =<br />
<br />
<video controls="controls"><source src="http://videos.mozilla.org/serv/air_mozilla/monday_meetings/status-2011-08-01.ogg" type="video/ogg; codecs=&quot;theora, vorbis&quot;" /></video> <br />
<br />
= Friends of the Tree [[Image:Tree.gif|Friends of the Tree]] =<br />
It's a bit overdue, but a bunch of Mozillians truly deserve a warm thank you for their help with WSOH: (the list is quite long): IT (Tim, mrz, Derek, Guillermo), Havi, Pascal, Julie C, Todd, Potch, CHeilmann, Anant, Philipp, Bret, Kimber, Jill A., Didem, Felipe, Spencer, Margaret, Frank, Gilbert, Saptarshi, Chris Jung, Rainer and Spencer!<br />
<br />
= Upcoming Events =<br />
'''This Week'''<br />
<br />
'''Monday, 1 August'''<br />
<br />
'''Tuesday, 2 August'''<br />
<br />
'''Wednesday, 3 August'''<br />
<br />
'''Thursday, 4 August'''<br />
<br />
'''Friday, 5 August''' <br />
<br />
'''Next Week'''<br />
<br />
= Product Status Updates =<br />
<br />
== Firefox Future (6, 7, 8) ==<br />
<br />
== Firefox Current (3.5, 3.6, 4.0, 5.0) ==<br />
<br />
== Mobile Firefox ==<br />
<br />
== Thunderbird ==<br />
<br />
== Older Branch Work ==<br />
<br />
== Drumbeat ==<br />
<br />
= Speakers =<br />
<br />
The limit is 3 minutes per speaker. It's like a lightning talk, but don't feel that you have to have slides in order to make a presentation.<br />
<br />
{| class="fullwidth-table"<br />
|-<br />
! Title<br />
! Presenter<br />
! Topic<br />
! Media<br />
! More Details<br />
|-<br />
| Firefox Brand Toolkit<br />
| John Slater<br />
| Quick overview of what this is and why we're doing it + we need input<br />
| http://www.intothefuzz.com/2011/08/01/firefox-brand-toolkit-first-draft/<br />
|-<br />
| Announcing Upcoming Metrics Brown Bags<br />
| Gilbert FitzGerald<br />
| Two upcoming brown bags from the Metrics Team: Analytics (8/3/11) and Data Engineering<br />
| <br />
| <br />
|-<br />
|}<br />
<br />
= Status Updates By Team =<br />
<br />
== Firefox ==<br />
<br />
== Platform ==<br />
<br />
== Messaging ==<br />
<br />
== Mobile ==<br />
<br />
== IT ==<br />
<br />
== Release Engineering ==<br />
<br />
== QA ==<br />
<br />
;Test Execution<br />
* Fx6 Beta 4: To be signed off this morning before ~9am.<br />
** Preparing for a crowd-sourced web compatibility testrun on top sites functionality (to be done by uTest).<br />
<br />
;WebQA<br />
* SUMO: http://moxie.jamessocol.com/bugstats/sumo/2011-07-26<br />
* AMO [https://bugzilla.mozilla.org/buglist.cgi?list_id=918506&resolution=FIXED&classification=Server%20Software&query_format=advanced&target_milestone=6.1.7&product=addons.mozilla.org 6.1.7]<br />
<br />
;QA Community<br />
<br />
;Automation Services<br />
<br />
== Automation & Tools ==<br />
<br />
== Security ==<br />
<br />
== Engagement ==<br />
<br />
'''PR''' <br />
<br><br />
*[http://www.eweek.com/c/a/Mobile-and-Wireless/Mozilla-Building-Mobile-Operating-System-to-Rival-Googles-Chrome-OS-877280/ Mozilla building mobile Operating System to rival Google's Chrome OS]<br />
*[http://www.linuxinsider.com/rsstory/72950.html Mozilla's Head Is in the Cloud With New Mobile OS Idea]<br />
*[http://www.engadget.com/2011/07/26/mozilla-planning-a-chrome-os-like-operating-system-for-phones-an/ Mozilla planning a Chrome OS-like operating system for phones and tablets]<br />
*[http://www.pcworld.com/article/236564/mozillas_boot_to_gecko_a_mobile_os_that_could_succeed.html Mozilla's Boot to Gecko: A mobile OS that could succeed]<br />
*[http://techcrunch.com/2011/07/25/boot-to-gecko-mozillas-open-source-mobile-answer-to-chromeos/ Boot to Gecko: Mozilla's open-source, mobile answer to Chrome OS]<br />
*[http://www.zdnet.com/blog/microsoft/mozillas-boot-to-gecko-a-windows-phone-os-competitor-or-something-else/10180v Mozilla's Boot to Gecko: A Windows Phone OS competitor or something else?]<br />
<br />
*[http://www.h-online.com/open/features/Mozilla-s-next-Firefox-moment-1288362.html Mozilla's next Firefox moment?]<br />
<br />
*[http://www.usatoday.com/tech/news/2011-07-26-mozilla-chrome-internet-explorer-privacy_n.htm Do Not Track' challenges tech industry]<br />
<br />
'''Events''' <br />
<br />
'''Creative Team''' <br />
<br />
'''Community Marketing'''<br />
<br />
== Support ==<br />
<br />
== Metrics ==<br />
<br />
== Evangelism ==<br />
<br />
== Labs ==<br />
<br />
== Developer Tools ==<br />
<br />
== Add-ons ==<br />
<br />
== Webdev ==<br />
<br />
== L10n ==<br />
<br />
= Introducing New Hires =<br />
<br />
<br />
= Introducing a New Intern =<br />
Michael Kurze, Metrics (welcome back!)<br />
<br />
= Foundation Updates =<br />
<br />
= Roundtable =</div>Jgouliehttps://wiki.mozilla.org/index.php?title=WeeklyUpdates/2011-06-27&diff=322991WeeklyUpdates/2011-06-272011-06-27T18:00:52Z<p>Jgoulie: /* Speakers */</p>
<hr />
<div><small>[[WeeklyUpdates/2011-06-20|« previous week]] | [[WeeklyUpdates|index]] | [[WeeklyUpdates/2011-07-4|next week »]]</small><br />
<br />
= Video for today's meeting =<br />
<br />
<video controls="controls"><source src="http://videos.mozilla.org/serv/air_mozilla/monday_meetings/status-2011-06-27.ogg" type="video/ogg; codecs=&quot;theora, vorbis&quot;" /></video> <br />
<br />
= Friends of the Tree [[Image:Tree.gif|Friends of the Tree]] =<br />
* Two [https://developer.mozilla.org/en-US/demos/devderby Dev Derby] contributors who have stood out for their enthusiasm, creativity, and dedication.<br />
** Stu Nicholls, who in less than two weeks has already submitted [https://developer.mozilla.org/en-US/demos/profile/Stu%20Nicholls four awesome demos] that are sure to push the web forward and be useful to web developers everywhere.<br />
** Anthony Calzadilla, who submitted the awesome [https://developer.mozilla.org/en-US/demos/detail/rofox-css3-animation-by-anthony-calzadilla Rofox] demo which quickly amassed hundreds of views and helped generate [https://twitter.com/#!/search/rofox lots of interest] in Firefox 5.<br />
<br />
= Upcoming Events =<br />
'''This Week'''<br />
<br />
'''Monday, 27 June'''<br />
<br />
'''Tuesday, 28 June'''<br />
<br />
'''Wednesday, 29 June'''<br />
<br>Community Marketing Call: 10 a.m. PDT/17:00 UTC/19:00 CET. In-progress agenda and dial-in info [http://etherpad.mozilla.com:9000/call-agenda-june-29 here].<br> <br />
<br />
'''Thursday, 30 June'''<br />
<br />
*'''[BrownBag]''' Understand your users and good ideas will follow - What is User Research & how we can help you. ''(Noon @TenForward)'' <br />
<br />
<br />
'''Friday, 1 July''' <br />
<br />
'''Next Week'''<br />
<br />
= Product Status Updates =<br />
<br />
== Firefox Future (5, 6, 7) ==<br />
* Firefox 5 released last week, and now being served as an update for all 4.0 users<br />
** 30MM users already<br />
* Next week, the next trains start rolling. That means:<br />
** Beta will pick up Firefox 6<br />
** Aurora will pick up Firefox 7<br />
** Nightly will start being Firefox 8<br />
<br />
== Firefox Current (3.5, 3.6, 4.0) ==<br />
<br />
== Mobile Firefox ==<br />
* Firefox 5 is out, getting good reviews/uptake<br />
* Ready for Aurora to beta merge<br />
<br />
== Thunderbird ==<br />
* Thunderbird 5.0 out tomorrow!<br />
** Please update your add-ons.<br />
* Thunderbird 6.0 moves to Beta and Thunderbird 7.0 moves to Earlybird next week.<br />
<br />
== Older Branch Work ==<br />
<br />
== Drumbeat ==<br />
* '''Universal Subtitles''' adopted by Khan Academy. GigaOm story: "[http://gigaom.com/video/khan-academy-universal-subtitles/ Khan Academy goes global with crowdsourced subtitles]" <br />
* New online home for '''School of Webcraft'''. Old Drupal site replaced by Django-based app. [http://learninglearning.wordpress.com/2011/06/23/school-of-webcraft-update-23062011/ Blog post] on the transition and next steps.<br />
* New '''Mozilla Popcorn''' code tutorials. Neat way to demo code. Check it out [http://popcornjs.org/documentation here].<br />
<br />
= Speakers =<br />
<br />
The limit is 3 minutes per speaker. It's like a lightning talk, but don't feel that you have to have slides in order to make a presentation.<br />
<br />
{| class="fullwidth-table"<br />
|-<br />
! Title<br />
! Presenter<br />
! Topic<br />
! Media<br />
! More Details<br />
|-<br />
| Head of College Recruiting<br />
| Julie Deroche<br />
| WSOH<br />
| http://htmlpad.org/wsoh/#<br />
| http://wsoh.eventbrite.com<br />
|-<br />
| <br />
|Patrick, Jinghua and Gilbert<br />
|Market insights, User Research, Metrics, and how we can help you. <br />
|[https://intranet.mozilla.org/images/0/02/Research_insights_metrics.png]<br />
|<br />
|-<br />
| Tour Guide<br />
| David Boswell<br />
| Community infographic and numbers<br />
| [https://wiki.mozilla.org/images/4/47/Infographic_5.jpg Infographic]<br />
| Please add to the [http://etherpad.mozilla.com:9000/active-community-numbers Community Numbers Etherpad]<br />
|-<br />
| Director, Web Development<br />
| Mike Morgan (morgamic)<br />
| From Portland with Love - highlights/notes from the webdev offsite<br />
| [http://www.flickr.com/photos/morgamic/sets/72157627036526878/ photos]<br />
| [http://opensourcebridge.org/about/ about OS Bridge]<br />
|-<br />
| <br />
| John O'Duinn (joduinn)<br />
| Firefox 3.5 EOL<br />
| <br />
| <br />
|}<br />
<br />
= Status Updates By Team =<br />
<br />
== Firefox ==<br />
<br />
== Platform ==<br />
<br />
== Messaging ==<br />
<br />
== Mobile ==<br />
<br />
== IT ==<br />
<br />
== Release Engineering ==<br />
<br />
== QA ==<br />
;Desktop Firefox<br />
* Fx5, tested and released, including major and minor updates to Fx5<br />
** 3.6, 4.0 -> 5.0<br />
<br />
;Browser Technologies<br />
* Shipped Firefox 5 for Mobile<br />
* Mobile Testday last friday. [http://etherpad.mozilla.com:9000/testday-20110624 Bugs found]<br />
* Test signoff of Python Sync server testing. Bugs found: {{Bug|667060}},{{Bug|667074}}<br />
* Test pilot 1.2pre8 in testing<br />
<br />
;WebQA<br />
*Really successful WebQA work week last week: https://wiki.mozilla.org/QA/Execution/Web_Testing/WorkWeek/2011/06<br />
*[https://bugzilla.mozilla.org/buglist.cgi?list_id=579234&resolution=FIXED&classification=Server%20Software&query_format=advanced&target_milestone=6.1.1&product=addons.mozilla.org AMO 6.1.1]<br />
*SUMO:<br />
**http://moxie.jamessocol.com/bugstats/sumo/2011-06-21<br />
*AMO Builder 6/21/2011<br />
*MDN [https://bugzilla.mozilla.org/buglist.cgi?list_id=579229&resolution=FIXED&classification=Other&query_format=advanced&target_milestone=0.9.6&product=Mozilla%20Developer%20Network 0.9.6.1] 6/22/11<br />
;QA Community<br />
<br />
;Test Automation<br />
* Investigation and fix for broken Mozmill 1.5.3b3 beta release; Released [http://groups.google.com/group/mozmill-dev/browse_thread/thread/36c2f77a6638ec3c Mozmill 1.5.4b4]<br />
<br />
== Automation & Tools ==<br />
<br />
== Security ==<br />
<br />
== Engagement ==<br />
<br />
'''Communications'''<br />
<br />
*[http://news.cnet.com/8301-30685_3-20074033-264/mozilla-drafts-firefox-vision-statement/ Mozilla drafts Firefox vision statement] <br />
<br />
*[http://www.eweek.com/c/a/Desktops-and-Notebooks/Firefox-5-Browser-Launches-Boasting-Tweaks-Security-Privacy-383151/ Desktops and Notebooks: Firefox 5 Browser Launches, Boasting Tweaks, Security, Privacy] <br />
*[http://www.informationweek.com/news/personal-tech/desktop-apps/231000190 Firefox 5.0: 5 Reasons To Upgrade] <br />
*[http://www.zdnet.co.uk/news/workspace-it/2011/06/22/firefox-5-focuses-on-security-and-privacy-40093191/ Firefox 5 focuses on security and privacy] <br />
*[http://www.washingtonpost.com/blogs/faster-forward/post/firefox-5-offers-small-improvements-do-not-track/2011/06/22/AGDf5lfH_blog.html Firefox 5 offers small improvements, Do Not Track] <br />
*[http://www.huffingtonpost.com/2011/06/21/firefox-5-beta-features_n_881521.html Firefox 5 Beta Released For Desktop And Android: See The New Features]<br />
*[http://www.pcworld.com/businesscenter/article/230805/five_good_reasons_to_download_firefox_5.html Five Good Reasons to Download Firefox 5] <br />
<br />
'''Contributor Engagement'''<br />
* Videos updates from the last weeks:<br />
**[http://www.youtube.com/watch?v=29vqOrk2aTI Week of June 13]<br />
**[http://www.youtube.com/watch?v=qZCLGef8U78 Week of June 6]<br />
* [https://wiki.mozilla.org/Community Community definitions updated].<br />
<br />
<br />
'''Events''' <br />
<br />
'''Creative Team''' <br />
<br />
'''Community Marketing'''<br />
<br />
== Support ==<br />
<br />
== Metrics ==<br />
<br />
== Evangelism ==<br />
<br />
== Labs ==<br />
<br />
== Developer Tools ==<br />
<br />
== Add-ons ==<br />
<br />
== Webdev ==<br />
<br />
== L10n ==<br />
<br />
= Introducing New Hires =<br />
* Priya Patel - Recruiting - Lead for Mobile and Engineering<br />
* Jason Haas - Contributor Engagement - Student Reps<br />
* Robert Nyman - Developer Engagement<br />
<br />
= Foundation Updates =<br />
<br />
= Roundtable =</div>Jgoulie