MozillaWiki - User contributions [en]

Marketplace/Reviewers/Apps/Meetings

2014-08-07T15:24:48Z

Fharper: /* Details */

= Details =
Time: Every Thursday at 10:00 AM Pacific 
Vidyo: AppReview - https://v.mozilla.com/flex.html?roomdirect.html&key=GUu6xymhnjZc 
Backchannel: #app-reviewers 

Next meeting: https://appreview.etherpad.mozilla.org/2014-08-07

= Tips =
DO: add whatever bullet points and notes you think are valuable to someone following the day-to-day operations of the app review program. The person whose name is in parentheses for each section will drive that part of the discussion (Lisa has a habit of braindumping topics beforehand...drivers, feel free to edit as necessary).

DON'T: try to discuss every bullet point in the meeting notes. All of us should be quite capable of reading, so section owners are encouraged to reference topics for discussion by line number, and skip over other bullet points that are included for reference.

DO: test your Vidyo configuration at least 15 minutes before the meeting.

DON'T: let background processes on your computer steal all your bandwidth. Pause syncing apps such as Dropbox, Google Drive, Crashplan, etc. If your connection still seems slow, try disabling your video (cleverly referred to as facemuting).

DO: mute your audio if you're not speaking to reduce background noise.

DON'T: fret if others on the call have trouble hearing you. Just type questions and comments in the etherpad chat, we're happy to accommodate and can follow up on irc if necessary.

= Archive =

* 2014-07-31: https://appreview.etherpad.mozilla.org/2014-07-31
* 2014-07-24: https://appreview.etherpad.mozilla.org/2014-07-24
* 2014-07-17: https://appreview.etherpad.mozilla.org/2014-07-17
* 2014-07-10: https://appreview.etherpad.mozilla.org/2014-07-10
* 2014-07-03: https://appreview.etherpad.mozilla.org/2014-07-03
* 2014-06-26: https://appreview.etherpad.mozilla.org/2014-06-26
* 2014-06-12: https://appreview.etherpad.mozilla.org/2014-06-12
* 2014-06-05: https://appreview.etherpad.mozilla.org/2014-06-05
* 2014-05-29: https://appreview.etherpad.mozilla.org/2014-05-29
* 2014-05-22: https://appreview.etherpad.mozilla.org/2014-05-22
* 2014-05-15: https://appreview.etherpad.mozilla.org/2014-05-15
* 2014-04-24: https://appreview.etherpad.mozilla.org/75
* 2013-04-10: https://appreview.etherpad.mozilla.org/68

Marketplace/Reviewers/Apps/Meetings

2014-08-07T15:22:48Z

Fharper: /* Archive */

= Details =
Time: Every Thursday at 10:00 AM Pacific 
Vidyo: AppReview - https://v.mozilla.com/flex.html?roomdirect.html&key=GUu6xymhnjZc 
Backchannel: #app-reviewers 

Next meeting: https://appreview.etherpad.mozilla.org/2014-07-24

= Tips =
DO: add whatever bullet points and notes you think are valuable to someone following the day-to-day operations of the app review program. The person whose name is in parentheses for each section will drive that part of the discussion (Lisa has a habit of braindumping topics beforehand...drivers, feel free to edit as necessary).

DON'T: try to discuss every bullet point in the meeting notes. All of us should be quite capable of reading, so section owners are encouraged to reference topics for discussion by line number, and skip over other bullet points that are included for reference.

DO: test your Vidyo configuration at least 15 minutes before the meeting.

DON'T: let background processes on your computer steal all your bandwidth. Pause syncing apps such as Dropbox, Google Drive, Crashplan, etc. If your connection still seems slow, try disabling your video (cleverly referred to as facemuting).

DO: mute your audio if you're not speaking to reduce background noise.

DON'T: fret if others on the call have trouble hearing you. Just type questions and comments in the etherpad chat, we're happy to accommodate and can follow up on irc if necessary.

= Archive =

* 2014-07-31: https://appreview.etherpad.mozilla.org/2014-07-31
* 2014-07-24: https://appreview.etherpad.mozilla.org/2014-07-24
* 2014-07-17: https://appreview.etherpad.mozilla.org/2014-07-17
* 2014-07-10: https://appreview.etherpad.mozilla.org/2014-07-10
* 2014-07-03: https://appreview.etherpad.mozilla.org/2014-07-03
* 2014-06-26: https://appreview.etherpad.mozilla.org/2014-06-26
* 2014-06-12: https://appreview.etherpad.mozilla.org/2014-06-12
* 2014-06-05: https://appreview.etherpad.mozilla.org/2014-06-05
* 2014-05-29: https://appreview.etherpad.mozilla.org/2014-05-29
* 2014-05-22: https://appreview.etherpad.mozilla.org/2014-05-22
* 2014-05-15: https://appreview.etherpad.mozilla.org/2014-05-15
* 2014-04-24: https://appreview.etherpad.mozilla.org/75
* 2013-04-10: https://appreview.etherpad.mozilla.org/68

MozCamps 2014

2014-05-30T20:05:53Z

Fharper: /* Developer Outreach */

{{admon/note|MozCamps are invite-only events| If you have questions or feedback, please check out the FAQ [[MozCamps_2014/FAQ|the MozCamp 2014 FAQ]] then ping us on [http://irc.mozilla.org/ IRC] #mozcamp2014. }}

2014 MozCamp Beta: June 20 - 22, Bangalore, India. Info on 2014 MozCamps in Asia, EMEA and LatAm coming soon. 

[[Category:Events]]
[[Category:MozCamps]]

= Overview =
[[image:Grow mozilla wordmark.jpg]]

MozCamps are a critical part of our Grow Mozilla program, aiming to mentor and train core contributors to help us bring our products to market and bolster our efforts to recruit new contributors in region. In 2014, we will shift the focus of MozCamp to be a "train the trainer" event, in order to teach current Community members how to recruit and onboard new contributors.

We are currently planning MozCamps for 2014. Watch the page for updates and information on how to get involved.

= Planning =

2014 MozCamps are being planned by a cross-organizational core team consisting of Reps and MoFo/MoCo paid staff.

Please see [[MozCamps_2014/Planning | the MozCamp 2014 Planning wiki page]] for more information on MozCamp 2014 planning.

= Communications =

* Bi-weekly updates at [https://wiki.mozilla.org/WeeklyUpdates the Project Meeting]
* IRC #mozcamp2014 (office hours below):
** Monday - Friday, 9 AM PDT - 5 PM PDT
* Email:
** GENERAL DISCUSSIONS: [https://lists.mozilla.org/listinfo/events Community Events Forum]

= MozCamp Beta - India =

== Specifics ==

===Location and Dates===
June 20 - June 22, 2014 in Bangalore, India 
JW Marriott 
24/1, Vittal Mallya Rd, Ashok Nagar, Bangalore, Karnataka 560001, India

===Agenda & Content Overview===

MozCamp Beta is testing out both general sessions, participated in by all, and breakout CA tracks (contribution areas) that focus on building community and recruiting new contributors into specific pathways. The diagram below shows the structure of this content. Because MozCamp Beta is being held in India in anticipation of the launch of Mozilla's $25 smartphone, there's a special focus of this content on Firefox OS and engagement with the new phone. Firefox OS specific content is being developed specifically for the Indian region and this Beta event. Most content however will be tested in India for future MozCamps, and iterated upon based on what we learn at the Beta and in subsequent results metrics and feedback.

See the below image for an overview of the agenda for MozCamp Beta - India.

 

[[File:Agenda.png|framed|center|MozCamp Beta - India Agenda ]]

 

== Getting There ==

[[MozCamps 2014/Logistics|Please find information on travel logistics and other helpful in-country information for MozCamp Beta - India here.]]

===Travel Info===

===Travel Tips===

== FAQ ==

[[MozCamps 2014/FAQ|See MozCamp 2014 FAQs here.]]

If you have any to add, please ping lmn in IRC #mozsummit.

== General Sessions ==

===Appmaker Hackathon/Demo===

===Moz Strategy===

===Firefox OS===

===Storytelling===
The goal of this session is to collaborate on crafting personally meaningful and engaging stories about Mozilla, to enable each participant to confidently describe Mozilla and it's mission to anybody (regardless of familiarity with the web!). We'll build a story in a game activity throughout the course of the weekend, answering:

1. Mozilla is...

2. Here's how I first got involved....

3. If this is interesting to you, here's how you can get involved too....

===Community Building for All===

== Contribution Areas ==
A "CA Track" (in the agenda image above) refers to "Contribution Area" track. 

At MozCamp Beta - India, we are testing four of the ~10 CA (tied to our community pathways). Each runs twice: once Saturday, and once Sunday. So each attendee gets to participate in two different CA tracks. The goal of each track is to focus on building community and recruiting new participants, with a focus (for all but User Centered Design) on Firefox OS. 

===Engagement===
'''(all attendees will to to this track, plus one other of their choosing)''' 
'''Goal:''' Recruiting community for $25 phone launch and thinking through the Mobilizers program for India's smartphone distribution model 
'''Owners:''' Jessica Osorio and William Quiviger

===SUMO===
'''Goal:''' Develop localized support docs and forum responses to support phone launch 
'''Owner:''' Ralph Daub

===User Centered Design===
(User Research + UX Design) 
'''Goal:''' Build a local user centered design community to collect on-the-ground observational data, localize surveys, and identify top-potential contributors to receive special training and badges to support new product development through developing cultural insights and need finding 
'''Owner:''' Bill Selman

===Developer Outreach===
(Developer Relations / MDN) 
'''Goal:''' Teach community members on how to approach, and to talk to developers about Firefox OS so that the developers wants to contribute to Mozilla and create apps for this platform. It's also about helping them being virtual evangelists, and helping the developer relation to share the awesomeness of Firefox OS. 
'''Owner:''' Frédéric Harper

File:9245001391 8897527f95 o.jpg

2014-05-30T19:09:56Z

Fharper: Fharper uploaded a new version of "File:9245001391 8897527f95 o.jpg": Creative Commons https://flic.kr/p/f5X3PH

Creative Commons https://flic.kr/p/f5X3PH

File:9245001391 8897527f95 o.jpg

2014-05-30T19:09:28Z

Fharper: Fharper uploaded a new version of "File:9245001391 8897527f95 o.jpg": Reverted to version as of 19:00, 30 May 2014

Creative Commons https://flic.kr/p/f5X3PH

File:9245001391 8897527f95 o.jpg

2014-05-30T19:04:57Z

Fharper: Fharper uploaded a new version of "File:9245001391 8897527f95 o.jpg": 350px width - smaller

Creative Commons https://flic.kr/p/f5X3PH

File:9245001391 8897527f95 o.jpg

2014-05-30T19:00:30Z

Fharper: Creative Commons https://flic.kr/p/f5X3PH

Creative Commons https://flic.kr/p/f5X3PH

WeeklyUpdates/2014-03-24

2014-03-24T18:04:54Z

Fharper: /* Thursday, {{#time:d F|{{SUBPAGENAME}} +3 days}} */

{{WeeklyUpdateNav}}
{{conf|8600}}

__TOC__

= All-hands Status Meeting Agenda =

Items in this section will be shared during the live all-hand status meeting.

== Friends of Mozilla [[Image:Tree.gif|Friends of Mozilla]] ==
* KaiRo would like to nominate [https://mozillians.org/en-US/u/xtc4uall/ XtC4UaLL] for helping with undoing changes on MozillaWiki over the weekend by people who think editing a public wiki and "defacing" pages there constitutes "1337 hacking". (See {{bug|986832}} for more background.)

== Upcoming Events ==

=== This Week ===

=== Monday, {{#time:d F|{{SUBPAGENAME}}}} ===
Developer Relatoins published the first edition of "DevPulse" today. This provides highlights about what is happening among web & app developers worldwide, and is intended to foster greater points of collaboration among various groups at Mozilla to support them. You can read past and current issues on the DevRelations wiki: https://wiki.mozilla.org/Engagement/Developer_Engagement/DevPulse and send feedback to diane@mozilla.com

=== Tuesday, {{#time:d F|{{SUBPAGENAME}} +1 day}} ===

=== Wednesday, {{#time:d F|{{SUBPAGENAME}} +2 days}} ===

* '''[http://indiewebcamp.com/events/2014-03-26-homebrew-website-club Homebrew Website Club Meeting]''', 18:30-19:30 simultaneously at Mozilla [[SF]] and [[MozPDX]]. Description: <blockquote>Are you building your own website? Indie reader? Personal publishing web app? Or some other digital magic-cloud proxy?If so (or you want to!), come on by and join a gathering of people with like-minded interests. Bring your friends that want to start a personal web site. Exchange information, swap ideas, talk shop, help work on a project...</blockquote> Any questions? See [http://indiewebcamp.com/events/2014-03-26-homebrew-website-club the wiki page]] or irc://irc.freenode.net/indiewebcamp.

=== Thursday, {{#time:d F|{{SUBPAGENAME}} +3 days}} ===
* [http://pixlcrew.com/pixlfest/ Pixlfest], Oklahoma City, OK, US
** Luke Crouch speaking, Developer Relations sponsoring
* [http://www.praguejs.cz/ PragueJS], Prague, Czech Republic
** Frédéric Harper speaking on Firefox OS

=== Friday, {{#time:d F|{{SUBPAGENAME}} +4 days}} ===

=== Saturday, {{#time:d F|{{SUBPAGENAME}} +5 days}} ===

=== Sunday, {{#time:d F|{{SUBPAGENAME}} +6 days}} ===

=== Next Week ===

== Project Status Updates (voice updates) ==

=== Firefox Desktop ===
''Speaker Location:''

=== Firefox Mobile ===
''Speaker Location:''

=== Firefox OS ===
''Speaker Location:''

=== [https://webmaker.org/ Webmaker] ===
''Speaker Location: nonverbal''

* Webmaker [https://blog.mozilla.org/blog/2014/03/21/congratulations-to-mozillas-thimble-code-editor-for-being-recognized-as-gamechanger-for-education/ won a prize] for our Thimble tool from Common Sense Media!

* We're hosting monthly "Geekouts" on the HOMAGO.com (stands for Hanging Out, Messing Around, Geeking Out) for community members to connect on specific topics
** This Thursday, March 27th at 12:00pm EDT, Karen Smith from Hive Toronto is [https://beta.homago.com/webmaking/geekout/119/mozilla-webmaker-ask-me-anything/212 hosting a discussion] about how you can teach the web without laptops and in an engaging and participatory way.

=== [https://openbadges.org/ Open Badges] ===
''Speaker Location: nonverbal''

* Mozilla BadgeKit is now available in private beta! Know how to build your own front end website to run it, or want to integrate it into your MoFo project? Fill out [https://docs.google.com/forms/d/1-e_auhjSAjnkzOB_SOYgYvEmki65P-cdXjAiU214O-I/viewform this form.]

=== [https://mozillascience.org/ Mozilla Science Lab] ===
''Speaker Location: nonverbal''

* The first Science Lab prototype is live! [http://mozillascience.org/code-as-a-research-object-updates-prototypes-next-steps/ Read the blog post.]

=== Policy & Advocacy ===
''Speaker location: nonverbal''

* The Web We Want campaign has just announced its 2014 Small Grants Program to find events or actions that will get people involved in debating, celebrating, and imagining the Web they Want.
** People can apply for any amount between $1,000 and $5,000.
** Applications due by April 7th. Here’s an action idea: host a ‘quilting bee’ in schools, libraries, youth clubs, etc., where you teach people digital skills by showing them how to make their own part of the Web We Want interactive quilt using Mozilla’s Webmaker tools and curriculum.
** Apply for a grant at https://webwewant.org/2014-grants/

=== Open News ===
''Speaker location: nonverbal''
* Catch the Open News team at [https://source.opennews.org/en-US/articles/event-roundup-mar-17/ these events] over the next few weeks:

=== Mozilla Reps ===
''Speaker Location:''

=== Grow Mozilla ===
''Speaker Location:''

=== Identity ===
''Speaker Location:''

=== Services ===
''Speaker Location:''

=== Firefox Marketplace ===
''Speaker Location:''

=== IT ===
''Speaker Location:''

=== Web Compatibility ===
''Speaker Location: nonverbal''

*Karl and Hallvord from the webcompat team took a trip to Beijing to discuss compatibility in China. Karl wrote about [http://www.otsukare.info/2014/03/24/webcompat-china some very interesting insights gained into the Chinese web and browser markets].

== Speakers ==

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. If you plan on showing a video, you need to contact the Air Mozilla team before the day of the meeting or you will be deferred to the next week.

{| class="fullwidth-table"
|-
! Presenter
! Title
! Topic
! Location
! Share?
! Media
! More Details
|-
| Who Are You?
| What Do You Do?
| What are you going to talk about?
| Where are you presenting from? (Moz Space, your house, space)
| Will you be sharing your screen? (yes/no, other info)
| Links to slides or images you want displayed on screen
| Link to where audience can find out more information
|-
|Robyn Chau
|Events Project Manager
|Game Developers Conference
|SF
|No
|https://wiki.mozilla.org/Games/GDC
|https://wiki.mozilla.org/Games/GDC
|-
|}

= Roundtable =

Do you have a question about a Mozilla Project or initiative? Let us know by Friday- we'll do our best to get you an answer.

Please note that we may not always be able to get to every item on this list, but we will try!

{| class="fullwidth-table"
|-
! Who are you?
! Area of question
! Question
|-
| ''What's your name? What do you work on?''
| ''Is your question about policy, a product, a Foundation initiative, etc.''
| ''What would you like to know?''

|-
|}

= Welcome! =

Let's say hello to some new Mozillians! If you are not able to join the meeting live, you can add a link to a short video introducing yourself.

== Introducing New Volunteers ==
{| class="fullwidth-table"
|-
! New Volunteer(s)
! Introduced by
! Speaker location
! New Volunteer location
! Will be working on
|-
| ''Who is the new volunteer(s)?''
| ''Who will be introducing that person?''
| ''Where is the introducer?''
| ''Where is the new person based?''
| ''What will the new person be doing?''
|-

|-
|}

== Introducing New Hires ==
{| class="fullwidth-table"
|-
! New Hire
! Introduced by
! Speaker location
! New Hire location
! Will be working on
|-
| ''Who is the new hire?''
| ''Who will be introducing that person?''
| ''Where is the introducer?''
| ''Where will the new person be working from?''
| ''What will the new person be working on?''
|-

|-
| Maisha Cannon
| Mat Cadwell
| San Francisco
| Mountain View
| Recruiting
|-
| Arcadio Lainez
| Eric Petitt
| Mountain View
| San Francisco
| Engagement
|-
|-
| Lars Hansen
| Naveed Ihsanullah
| Toronto
| Norway
| JavaScript
|-
| Junior Hsu
| Marco Chen
| Taipei (Recording)
| Taipei
| Software Engineer
|}

== Introducing New Interns ==
{| class="fullwidth-table"
|-
! New Intern
! Introduced by
! Speaker location
! New Hire location
! Will be working on
|-
| ''Who is the new intern?''
| ''Who will be introducing that person?''
| ''Where is the introducer?''
| ''Where will the new person be working from?''
| ''What will the new person be working on?''
|-

|-
|}

= <meta> =

Notes and non-voice status updates that aren't part of the live meeting go here.

== Status Updates By Team (*non-voice* updates) ==

=== Firefox ===

=== Platform ===

=== Services ===

=== Messaging ===

=== Mobile ===

=== IT ===

=== Release Engineering ===

=== QA ===

==== Test Execution ====

==== WebQA ====

==== QA Community ====

=== Automation & Tools ===

=== Security ===

=== Engagement ===

==== PR ====

==== Events ====

==== Social Support ====

Engagement/Engagement-Offsite-2014-January

2013-12-06T21:38:06Z

Fharper: /* Travel Details */

=All Engagement Offsite, January 2014=

==Location & Dates==

* Bay Area - place TBD
* Dates: 01/13-17 (Monday and Friday being travel days)

==Agenda==
*Here's a link to the [https://etherpad.mozilla.org/Engagement-Offsite-2014] Etherpad for adding session proposals and agenda topics for the working days

==Travel Info==
Your name in the following table is considered an RSVP.
*Please add a number next to your first and last names, arrival and departure dates and any dietary restrictions.
We will use this document to make hotel reservation for the offsite (check in on Monday - check out on Friday).
* For airline tickets and any additional hotel days, please book through Egencia.

==Travel Details==
{| class="fullwidth-table"
! Full Name || Arrival and Departure Dates || Dietary restrictions
|-
| 1. William Reynolds || 01/13-17 || Carbs. Lots of carbs. As many as you can give me.
|-
| 2. Luciana Viana || 01/13-17 || None
|-
| 3. Grace Jimenez || 01/13-17 || None
|-
| 4. Pete Scanlon || 01/13-17 || Vegetarian
|-
| 5. Jean Collings || 01/13-17 || None
|-
| 6. Kristin Baird || 01/14-16 || None
|-
| 7. Ibai Garcia || 01/13-17 || None
|-
| 8. Jessilyn Davis || 01/13-17 || Vegetarian
|-
| 9. Karolina Shaw || 01/11-16 (11-13 in SF) || No grains (rice, pasta, wheat, oats)
|-
|10. Roland Tanglao || 01/13-17 || None
|-
|11. John Bernard || 01/13-16 || None
|-
|12. Kadir Topal || 01/13-17 || Vegetarian
|-
|13. Chris Heilmann || 01/11-18 || Paleo
|-
|14. Jesse Montano || 01/14-17 || None
|-
|15. Katherine Naszradi || 01/13-17 || None
|-
|16. Mike Manning || 01/13-17 || None
|-
|17. Carmen Collins || 01/13-16 || Gluten Free
|-
|18. Michael Kelly || 01/13-17 || I like hot chocolate!
|-
|19. Ali Spivak || 01/13-17 (local) || Gluten Free
|-
|20. Dan Horner || 01/13-17 || Paleo
|-
|21. Laura Forrest || 01/13-17 || Paleo
|-
|22. Shannon Prior || 01/13-17 || Gluten Free
|-
|23. Matej Novak || 01/12–18 || None
|-
|24. Chelsea Novak || 01/12–18 || Severe Peanut Allergy
|-
|25. Michelle Luna || 01/13-17 || None
|-
|26. Havi Hoffman || 01/14-17 || None
|-
|27. Frédéric Harper || 01/11-18 || No mushrooms
|-
|28. Giorgos Logiotatidis || 01/12-18 || None
|-
|29. Alex Gibson || 01/12-18 || None
|-
|30. Gen Kanai || 01/13-17 || None
|-
|31. Jessica Osorio || 01/13-17 || None
|-
|32. Lee Tom || 01/13-15 || None
|-
|33. Angelina Fabbro || 01/13-17 || Lactose intolerant
|-}
|34. Sakina Groth || 01/13-17 || Vegetarian
|-}
|35. Michael Ellis || 01/13-17 || None
|-}
|36. Marcia Zikan || 01/13-17 || None
|-}
|37. Josh Mize || 01/13-17 || No mammals
|-}
|38. Benjamin Sternthal || 01/13-17 || None
|-}
|39. Chris More || 01/13-17 || None
|-}
|40. Jennifer Bertsch || 01/13-17 || None
|-}
|41. Mike Alexis || 01/13-17 || No red meat; no eggs
|-}
|42. Florian Scholz || 01/12-24 (17-24 in SF) || None
|-}
|43. John Slater || 01/14-17 || None
|-}
|44. Chris Mills || 01/13-22 (17-22 in SF), arriving 2pm on the 13th || None
|-}
|45. Hermina Condei || 01/13-17 || None
|-}
|46. Michael Verdi || 01/12-18 || Vegan
|-}
|47. Brian King || 01/12-19 || None
|-}
|48. Holly Habstritt Gaal || 01/13-17 || None
|-}
|49. Madalina Ana || 01/13-18 || None
|-}
|50. Barry Munsterteiger || 01/13-17 || None
|-}
|51. Robert Nyman || 01/13-18 || None
|-}
|52. Sean Martell || 01/12-17 || High bacon tolerance
|-}
|53. Dia Bondi || 01/13-16 || None
|-}
|54. Michael Hung || 01/12-17 || None
|-}
|55. Jane Hsu || 01/12-18 || None
|-}
|56. Jack Guo || 01/13 - 18|| None
|-}
|57. Mark Coggins || 01/13 - 17 (local) || None
|-}
|58. Ty Flanagan || 01/12-17 || No onions, peppers, garlic. (sigh, I know)
|-}
|59. Tetsuya Kosaka || 01/13-17 || None
|-}
|60. Jennifer Balaco || 01/13-17 || None
|-}
|61. Noritada Shimizu || 01/14-17 || None
|-}
|62. Eric Petitt || 01/13-17 || None
|-}
|63. Tristan Nitot || 01/13/17 || None
|-}
|64. Jason Weathersby || 01/13-18 || None
|-}
|65. Jon Petto || 01/13-17 || Vegetarian
|-}
|66. Niran Amir || 01/13-17 || Vegetarian
|-}
|67. Robyn Chau || 01/13-17 || Vegetarian
|-}
|68. Rainer Cvillink || 01/13-17 || None
|-}
|69. Justin O'Kelly || 01/15-17 || None
|-}
|70. Natalia Martinez-Winter || 01/13-18 || None
|-}
|71. Guillermo Movia || 01/13-18 || None
|-}
|72. Winston Bowden || 01/13-18 || None
|-}
|73. Jean-Yves Perrier || 01/13-24 (17-24 in SF) || None
|-}
|74. Craig Cook || 01/13-17 (local) || None
|-}
|75. Michaela Thayer || 01/12-17 || Vegetarian
|-}
|76. Liza Fox || 01/12-16 || None
|-}
|77. Patrick McClard || 01/13-17 || None
|-}
|78. Mary Colvig || 01/13-17 (local) || Nothing I can hug
|-}
|79. Luke Crouch || 01/13-17 || None
|-}
|80. Rosana Ardila || 01/13-17 || None
|-}
|81. Cheng Wang || 01/13-17 || None
|-}
|82. Rachel McGuigan || 1/13-17 || No soy, dairy
|-}
|83. Spencer Hui || 01/13-17 || None
|-}
|84. Tyler Downer || 01/13-17 || None
|-}
|85. Christie Koehler || TBD-01/18 || Vegan, no mushrooms, no eggplant
|-}
|86. Matt Grimes || 01/13-17 || Lean proteins and scotch
|-}
|87. Justin Crawford || 01/13-17 || Likewise
|-
|88. Janet Swisher || 01/13-22 (have accom. for 01/17-22) || None
|-)
|89. Greg Jost || 01/13-17 || None
|-)
|90. Vik Iya || 01/13-17 || None
|-)
|91. Shezmeen Prasad || 01/13-17 || None
|-)
|92. Gareth Cull || 01/13-17 || None
|-)
|93. Matt Ternoway || 01/12-17 || None
|-)
|94. Stacy Martin || 01/13-17 || None
|-)
|95. Ralph Daub || 01/12-17 || None

Engagement/Engagement-Offsite-2014-January

2013-12-06T21:37:06Z

Fharper: /* Travel Details */

=All Engagement Offsite, January 2014=

==Location & Dates==

* Bay Area - place TBD
* Dates: 01/13-17 (Monday and Friday being travel days)

==Agenda==
*Here's a link to the [https://etherpad.mozilla.org/Engagement-Offsite-2014] Etherpad for adding session proposals and agenda topics for the working days

==Travel Info==
Your name in the following table is considered an RSVP.
*Please add a number next to your first and last names, arrival and departure dates and any dietary restrictions.
We will use this document to make hotel reservation for the offsite (check in on Monday - check out on Friday).
* For airline tickets and any additional hotel days, please book through Egencia.

==Travel Details==
{| class="fullwidth-table"
! Full Name || Arrival and Departure Dates || Dietary restrictions
|-
| 1. William Reynolds || 01/13-17 || Carbs. Lots of carbs. As many as you can give me.
|-
| 2. Luciana Viana || 01/13-17 || None
|-
| 3. Grace Jimenez || 01/13-17 || None
|-
| 4. Pete Scanlon || 01/13-17 || Vegetarian
|-
| 5. Jean Collings || 01/13-17 || None
|-
| 6. Kristin Baird || 01/14-16 || None
|-
| 7. Ibai Garcia || 01/13-17 || None
|-
| 8. Jessilyn Davis || 01/13-17 || Vegetarian
|-
| 9. Karolina Shaw || 01/11-16 (11-13 in SF) || No grains (rice, pasta, wheat, oats)
|-
|10. Roland Tanglao || 01/13-17 || None
|-
|11. John Bernard || 01/13-16 || None
|-
|12. Kadir Topal || 01/13-17 || Vegetarian
|-
|13. Chris Heilmann || 01/11-18 || Paleo
|-
|14. Jesse Montano || 01/14-17 || None
|-
|15. Katherine Naszradi || 01/13-17 || None
|-
|16. Mike Manning || 01/13-17 || None
|-
|17. Carmen Collins || 01/13-16 || Gluten Free
|-
|18. Michael Kelly || 01/13-17 || I like hot chocolate!
|-
|19. Ali Spivak || 01/13-17 (local) || Gluten Free
|-
|20. Dan Horner || 01/13-17 || Paleo
|-
|21. Laura Forrest || 01/13-17 || Paleo
|-
|22. Shannon Prior || 01/13-17 || Gluten Free
|-
|23. Matej Novak || 01/12–18 || None
|-
|24. Chelsea Novak || 01/12–18 || Severe Peanut Allergy
|-
|25. Michelle Luna || 01/13-17 || None
|-
|26. Havi Hoffman || 01/14-17 || None
|-
|27. Frédéric Harper || 01/11-18 || Mushrooms
|-
|28. Giorgos Logiotatidis || 01/12-18 || None
|-
|29. Alex Gibson || 01/12-18 || None
|-
|30. Gen Kanai || 01/13-17 || None
|-
|31. Jessica Osorio || 01/13-17 || None
|-
|32. Lee Tom || 01/13-15 || None
|-
|33. Angelina Fabbro || 01/13-17 || Lactose intolerant
|-}
|34. Sakina Groth || 01/13-17 || Vegetarian
|-}
|35. Michael Ellis || 01/13-17 || None
|-}
|36. Marcia Zikan || 01/13-17 || None
|-}
|37. Josh Mize || 01/13-17 || No mammals
|-}
|38. Benjamin Sternthal || 01/13-17 || None
|-}
|39. Chris More || 01/13-17 || None
|-}
|40. Jennifer Bertsch || 01/13-17 || None
|-}
|41. Mike Alexis || 01/13-17 || No red meat; no eggs
|-}
|42. Florian Scholz || 01/12-24 (17-24 in SF) || None
|-}
|43. John Slater || 01/14-17 || None
|-}
|44. Chris Mills || 01/13-22 (17-22 in SF), arriving 2pm on the 13th || None
|-}
|45. Hermina Condei || 01/13-17 || None
|-}
|46. Michael Verdi || 01/12-18 || Vegan
|-}
|47. Brian King || 01/12-19 || None
|-}
|48. Holly Habstritt Gaal || 01/13-17 || None
|-}
|49. Madalina Ana || 01/13-18 || None
|-}
|50. Barry Munsterteiger || 01/13-17 || None
|-}
|51. Robert Nyman || 01/13-18 || None
|-}
|52. Sean Martell || 01/12-17 || High bacon tolerance
|-}
|53. Dia Bondi || 01/13-16 || None
|-}
|54. Michael Hung || 01/12-17 || None
|-}
|55. Jane Hsu || 01/12-18 || None
|-}
|56. Jack Guo || 01/13 - 18|| None
|-}
|57. Mark Coggins || 01/13 - 17 (local) || None
|-}
|58. Ty Flanagan || 01/12-17 || No onions, peppers, garlic. (sigh, I know)
|-}
|59. Tetsuya Kosaka || 01/13-17 || None
|-}
|60. Jennifer Balaco || 01/13-17 || None
|-}
|61. Noritada Shimizu || 01/14-17 || None
|-}
|62. Eric Petitt || 01/13-17 || None
|-}
|63. Tristan Nitot || 01/13/17 || None
|-}
|64. Jason Weathersby || 01/13-18 || None
|-}
|65. Jon Petto || 01/13-17 || Vegetarian
|-}
|66. Niran Amir || 01/13-17 || Vegetarian
|-}
|67. Robyn Chau || 01/13-17 || Vegetarian
|-}
|68. Rainer Cvillink || 01/13-17 || None
|-}
|69. Justin O'Kelly || 01/15-17 || None
|-}
|70. Natalia Martinez-Winter || 01/13-18 || None
|-}
|71. Guillermo Movia || 01/13-18 || None
|-}
|72. Winston Bowden || 01/13-18 || None
|-}
|73. Jean-Yves Perrier || 01/13-24 (17-24 in SF) || None
|-}
|74. Craig Cook || 01/13-17 (local) || None
|-}
|75. Michaela Thayer || 01/12-17 || Vegetarian
|-}
|76. Liza Fox || 01/12-16 || None
|-}
|77. Patrick McClard || 01/13-17 || None
|-}
|78. Mary Colvig || 01/13-17 (local) || Nothing I can hug
|-}
|79. Luke Crouch || 01/13-17 || None
|-}
|80. Rosana Ardila || 01/13-17 || None
|-}
|81. Cheng Wang || 01/13-17 || None
|-}
|82. Rachel McGuigan || 1/13-17 || No soy, dairy
|-}
|83. Spencer Hui || 01/13-17 || None
|-}
|84. Tyler Downer || 01/13-17 || None
|-}
|85. Christie Koehler || TBD-01/18 || Vegan, no mushrooms, no eggplant
|-}
|86. Matt Grimes || 01/13-17 || Lean proteins and scotch
|-}
|87. Justin Crawford || 01/13-17 || Likewise
|-
|88. Janet Swisher || 01/13-22 (have accom. for 01/17-22) || None
|-)
|89. Greg Jost || 01/13-17 || None
|-)
|90. Vik Iya || 01/13-17 || None
|-)
|91. Shezmeen Prasad || 01/13-17 || None
|-)
|92. Gareth Cull || 01/13-17 || None
|-)
|93. Matt Ternoway || 01/12-17 || None
|-)
|94. Stacy Martin || 01/13-17 || None
|-)
|95. Ralph Daub || 01/12-17 || None

Engagement/Engagement-Offsite-2014-January

2013-11-19T01:04:17Z

Fharper: /* Travel Details */

Engagement/Developer Engagement/Meetings/2013-08-13

2013-08-13T16:05:59Z

Fharper: /* Agenda */

* Tuesday, August 13, 2013 @ 9:00am Pacific Time (16:00 UTC through November 6)

= Agenda =
Add your agenda items here before hand. Add links to more information or background whenever possible.

* Intros
* News & Updates: Product, Demo, Resources
** MDN Stability Issues
** MDN Redesign
* Upcoming developer events (Mark)
** [https://developer.mozilla.org/en-US/events https://developer.mozilla.org/en-US/events]
* Roundtable
** Do we have free evening at the offsite, when?
** Devtools & Hacks - planning posts

= Actions =
* ACTION: sole to write a post on web audio and the audiomonkey patch polyfill
* ACTION: chrismills to help with demo for WebRTC
* ACTION: Ali Spivak to work with teams to figure out metrics around awareness and linking.

= Notes =
* MDN Stability Issues
** https://groups.google.com/d/msg/mozilla.dev.mdn/jCaPu1x6wTY/QwS4SsGfU6wJ
** https://groups.google.com/d/msg/mozilla.mdn.drivers/YUI_bskDoUA/hx_sIjMrXR8J

= IRC Log =

Engagement/Developer Engagement/Meetings/2013-08-13

2013-08-13T16:02:47Z

Fharper: /* Agenda */

* Tuesday, August 13, 2013 @ 9:00am Pacific Time (16:00 UTC through November 6)

= Agenda =
Add your agenda items here before hand. Add links to more information or background whenever possible.

* Intros
* News & Updates: Product, Demo, Resources
** MDN Stability Issues
** MDN Redesign
* Upcoming developer events (Mark)
** [https://developer.mozilla.org/en-US/events https://developer.mozilla.org/en-US/events]
* Do we expect to have something every evening at the offsite?

= Actions =
* ACTION: sole to write a post on web audio and the audiomonkey patch polyfill
* ACTION: chrismills to help with demo for WebRTC
* ACTION: Ali Spivak to work with teams to figure out metrics around awareness and linking.

= Notes =

= IRC Log =

Engagement/Developer Engagement/Technical Evangelism/Loan Program

2013-08-01T18:33:12Z

Fharper: /* Possible problems */

== Loan program ==

The goal of the loan program is to give access to a Firefox OS device to more developers. We got many requests in the Phones for Apps program, and unfortunately, we cannot give a device to all developers. Having a real device can be a good motivation for some developers to develop on the platform. We also have a good simulator, but there is nothing as good as testing your application with a real device. By loaning devices to developers, it will give us the opportunity to get more quality application, and saving on cost (shipping vs buying new devices).

As an example, with the Phones for Apps we got 10 000 applications, and we may have given 200 phones. If each developer creates one application, we are ''potentially'' missing 9800 applications (we know that some developers don't need a real device to publish their application). If we dedicate only 20 phones for the program, with an estimate use time of 4 weeks per phone (2 weeks for the developers, 1 week shipping in/out & 1 week of administrative/delay), in one year, we'll have a potential of 260 more applications (52 weeks / 4 weeks * 20 devices), that mean an average of 13 applications per phones.

== Rules of the program ==
* Every developer can participate.
* You already built or ported an application for Firefox OS.
* You need to ship back the device two weeks after you received it.
* You need to publish your application to the marketplace one month after you received the device.

== Process ==
We might need/want to empower our ReMo to help us with the program to scale.
* Developers who want to have a device to test their application, will apply for the program.
* We will ship the devices to people who applied.
** Depending upon the number of devices allowed in the program, and number of participants, we may want to check with participants first if they still need a device (if we have delay)
* We will enter the date the phone has been delivered
* We will contact developers two weeks after the date they received it

== Possible problems ==
* We cannot guarantee that developers will really build application (like with the Phones for Apps program)
* We cannot guarantee that the developers will ship back the phones (see next step point on this)
* ReMo may not wants to give their postal address for shipping return (do we deal with local offices?)

== Application form ==
* First name
* Last name
* Company
* Address
* City
* State
* Postal Code / Zip Code
* Country
* Phone number
* Email
* Link to the actual application or code (to prove that the application exist - low hanging fruit)
* Acceptance of the terms & conditions
** You actually have an application ready to test on a real device.
** You will return the device after two weeks in your possession.
** You will publish a Firefox OS application in the marketplace one month after you received the device.
** If you don't return the device or wants to keep it, your credit card will be charged.

== Next steps ==
* Finding a way to guarantee the return of the devices
* Validate the big picture of the program with the rest of the team
* Create the Google form (or any other form) for application for the program
* Promote the program in our network (maybe a Hacks blog post)
* Contact (if it's possible) people who applied for Phones for Apps program who didn't get a phone

Engagement/Developer Engagement/Technical Evangelism/Loan Program

2013-07-30T18:36:36Z

Fharper:

== Loan program ==

The goal of the loan program is to give access to a Firefox OS device to more developers. We got many requests in the Phones for Apps program, and unfortunately, we cannot give a device to all developers. Having a real device can be a good motivation for some developers to develop on the platform. We also have a good simulator, but there is nothing as good as testing your application with a real device. By loaning devices to developers, it will give us the opportunity to get more quality application, and saving on cost (shipping vs buying new devices).

As an example, with the Phones for Apps we got 10 000 applications, and we may have given 200 phones. If each developer creates one application, we are ''potentially'' missing 9800 applications (we know that some developers don't need a real device to publish their application). If we dedicate only 20 phones for the program, with an estimate use time of 4 weeks per phone (2 weeks for the developers, 1 week shipping in/out & 1 week of administrative/delay), in one year, we'll have a potential of 260 more applications (52 weeks / 4 weeks * 20 devices), that mean an average of 13 applications per phones.

== Rules of the program ==
* Every developer can participate.
* You already built or ported an application for Firefox OS.
* You need to ship back the device two weeks after you received it.
* You need to publish your application to the marketplace one month after you received the device.

== Process ==
We might need/want to empower our ReMo to help us with the program to scale.
* Developers who want to have a device to test their application, will apply for the program.
* We will ship the devices to people who applied.
** Depending upon the number of devices allowed in the program, and number of participants, we may want to check with participants first if they still need a device (if we have delay)
* We will enter the date the phone has been delivered
* We will contact developers two weeks after the date they received it

== Possible problems ==
* We cannot guarantee that developers will really build application (like with the Phones for Apps program)
* We cannot guarantee that the developers will ship back the phones (see next step point on this)

== Application form ==
* First name
* Last name
* Company
* Address
* City
* State
* Postal Code / Zip Code
* Country
* Phone number
* Email
* Link to the actual application or code (to prove that the application exist - low hanging fruit)
* Acceptance of the terms & conditions
** You actually have an application ready to test on a real device.
** You will return the device after two weeks in your possession.
** You will publish a Firefox OS application in the marketplace one month after you received the device.
** If you don't return the device or wants to keep it, your credit card will be charged.

== Next steps ==
* Finding a way to guarantee the return of the devices
* Validate the big picture of the program with the rest of the team
* Create the Google form (or any other form) for application for the program
* Promote the program in our network (maybe a Hacks blog post)
* Contact (if it's possible) people who applied for Phones for Apps program who didn't get a phone

Engagement/Developer Engagement/Technical Evangelism/Loan Program

2013-07-30T18:34:24Z

Fharper:

== Loan program ==

The goal of the loan program is to give access to a Firefox OS device to more developers. We got many requests in the Phones for Apps program, and unfortunately, we cannot give a device to all developers. Having a real device can be a good motivation for some developers to develop on the platform. We also have a good simulator, but there is nothing as good as testing your application with a real device. By loaning devices to developers, it will give us the opportunity to get more quality application, and saving on cost (shipping vs buying new devices).

As an example, with the Phones for Apps we got 10 000 applications, and we may have given 200 phones. If each developer creates one application, we are ''potentially'' missing 9800 applications (we know that some developers don't need a real device to publish their application). If we dedicate only 20 phones for the program, with an estimate use time of 4 weeks per phone (2 weeks for the developers, 1 week shipping in/out & 1 week of administrative/delay), in one year, we'll have a potential of 260 more applications (52 weeks / 4 weeks * 20 devices), that mean an average of 13 applications per phones.

== Rules of the program ==
* Every developer can participate.
* You already built or ported an application for Firefox OS.
* You need to ship back the device two weeks after you received it.
* You need to publish your application to the marketplace one month after you received the device.

== Process ==
* Developers who want to have a device to test their application, will apply for the program.
* We will ship the devices to people who applied.
** Depending upon the number of devices allowed in the program, and number of participants, we may want to check with participants first if they still need a device (if we have delay)
* We will enter the date the phone has been delivered
* We will contact developers two weeks after the date they received it

== Possible problems ==
* We cannot guarantee that developers will really build application (like with the Phones for Apps program)
* We cannot guarantee that the developers will ship back the phones (see next step point on this)

== Application form ==
* First name
* Last name
* Company
* Address
* City
* State
* Postal Code / Zip Code
* Country
* Phone number
* Email
* Link to the actual application or code (to prove that the application exist - low hanging fruit)
* Acceptance of the terms & conditions
** You actually have an application ready to test on a real device.
** You will return the device after two weeks in your possession.
** You will publish a Firefox OS application in the marketplace one month after you received the device.
** If you don't return the device or wants to keep it, your credit card will be charged.

== Next steps ==
* Finding a way to guarantee the return of the devices
* Validate the big picture of the program with the rest of the team
* Create the Google form (or any other form) for application for the program
* Promote the program in our network (maybe a Hacks blog post)
* Contact (if it's possible) people who applied for Phones for Apps program who didn't get a phone

Engagement/Developer Engagement/Technical Evangelism/Loan Program

2013-07-30T18:20:31Z

Fharper: /* Loan program */

== Loan program ==

The goal of the loan program is to give access to a Firefox OS device to more developers. We got many requests in the Phones for Apps program, and unfortunately, we cannot give a device to all developers. Having a real device can be a good motivation for some developers to develop on the platform. We also have a good simulator, but there is nothing as good as testing your application with a real device. By loaning devices to developers, it will give us the opportunity to get more quality application, and saving on cost (shipping vs buying new devices).

As an example, with the Phones for Apps we got 10 000 applications, and we may have given 200 phones. If each developer creates one application, we are ''potentially'' missing 9800 applications (we know that some developers don't need a real device to publish their application). If we dedicate only 20 phones for the program, with an estimate use time of 4 weeks per phone (2 weeks for the developers, 1 week shipping in/out & 1 week of administrative/delay), in one year, we'll have a potential of 260 more applications (52 weeks / 4 weeks * 20 devices), that mean an average of 13 applications per phones.

== Rules of the program ==
* Every developer can participate.
* You already built or ported an application for Firefox OS.
* You need to ship back the device two weeks after you received it.
* You need to publish your application to the marketplace one month after you received the device.
* ? You need a credit card to register (we will bill you the price of the phone if you want to keep it, or if you don't return it)

== Process ==
* Developers who want to have a device to test their application, will apply for the program.
* We will ship the devices to people who applied.
** Depending upon the number of devices allowed in the program, and number of participants, we may want to check with participants first if they still need a device (if we have delay)
* We will enter the date the phone has been delivered
* We will contact developers two weeks after the date they received it
** ? We will charge the credit card of the developer if he want to keep the phone, or if the developer doesn't return it.

== Application form ==
* First name
* Last name
* Company
* Address
* City
* State
* Postal Code / Zip Code
* Country
* Phone number
* Email
* Link to the actual application or code (to prove that the application exist - low hanging fruit)
* Acceptance of the terms & conditions
** You actually have an application ready to test on a real device.
** You will return the device after two weeks in your possession.
** You will publish a Firefox OS application in the marketplace one month after you received the device.
** If you don't return the device or wants to keep it, your credit card will be charged.

== Next steps ==
* Validate the big picture of the program with the rest of the team
* Create the Google form (or any other form) for application for the program
* Promote the program in our network (maybe a Hacks blog post)
* Contact (if it's possible) people who applied for Phones for Apps program who didn't get a phone

Engagement/Developer Engagement/Technical Evangelism/Loan Program

2013-07-30T18:15:59Z

Fharper: /* Application form */

== Loan program ==

The goal of the loan program is to give access to a Firefox OS device to more developers. We got many requests in the Phones for Apps program, and unfortunately, we cannot give a device to all developers. Having a real device can be a good motivation for some developers to develop on the platform. We also have a good simulator, but there is nothing as good as testing your application with a real device. By loaning devices to developers, it will give us the opportunity to get more quality application, and saving on cost (shipping vs buying new devices).

== Rules of the program ==
* Every developer can participate.
* You already built or ported an application for Firefox OS.
* You need to ship back the device two weeks after you received it.
* You need to publish your application to the marketplace one month after you received the device.
* ? You need a credit card to register (we will bill you the price of the phone if you want to keep it, or if you don't return it)

== Process ==
* Developers who want to have a device to test their application, will apply for the program.
* We will ship the devices to people who applied.
** Depending upon the number of devices allowed in the program, and number of participants, we may want to check with participants first if they still need a device (if we have delay)
* We will enter the date the phone has been delivered
* We will contact developers two weeks after the date they received it
** ? We will charge the credit card of the developer if he want to keep the phone, or if the developer doesn't return it.

== Application form ==
* First name
* Last name
* Company
* Address
* City
* State
* Postal Code / Zip Code
* Country
* Phone number
* Email
* Link to the actual application or code (to prove that the application exist - low hanging fruit)
* Acceptance of the terms & conditions
** You actually have an application ready to test on a real device.
** You will return the device after two weeks in your possession.
** You will publish a Firefox OS application in the marketplace one month after you received the device.
** If you don't return the device or wants to keep it, your credit card will be charged.

== Next steps ==
* Validate the big picture of the program with the rest of the team
* Create the Google form (or any other form) for application for the program
* Promote the program in our network (maybe a Hacks blog post)
* Contact (if it's possible) people who applied for Phones for Apps program who didn't get a phone

Engagement/Developer Engagement/Technical Evangelism/Loan Program

2013-07-30T18:15:43Z

Fharper: /* Next steps */

== Loan program ==

The goal of the loan program is to give access to a Firefox OS device to more developers. We got many requests in the Phones for Apps program, and unfortunately, we cannot give a device to all developers. Having a real device can be a good motivation for some developers to develop on the platform. We also have a good simulator, but there is nothing as good as testing your application with a real device. By loaning devices to developers, it will give us the opportunity to get more quality application, and saving on cost (shipping vs buying new devices).

== Rules of the program ==
* Every developer can participate.
* You already built or ported an application for Firefox OS.
* You need to ship back the device two weeks after you received it.
* You need to publish your application to the marketplace one month after you received the device.
* ? You need a credit card to register (we will bill you the price of the phone if you want to keep it, or if you don't return it)

== Process ==
* Developers who want to have a device to test their application, will apply for the program.
* We will ship the devices to people who applied.
** Depending upon the number of devices allowed in the program, and number of participants, we may want to check with participants first if they still need a device (if we have delay)
* We will enter the date the phone has been delivered
* We will contact developers two weeks after the date they received it
** ? We will charge the credit card of the developer if he want to keep the phone, or if the developer doesn't return it.

== Application form ==
* First name

* Last name
* Company
* Address
* City
* State
* Postal Code / Zip Code
* Country
* Phone number
* Email
* Link to the actual application or code (to prove that the application exist * low hanging fruit)
* Acceptance of the terms & conditions
** You actually have an application ready to test on a real device.
** You will return the device after two weeks in your possession.
** You will publish a Firefox OS application in the marketplace one month after you received the device.
** If you don't return the device or wants to keep it, your credit card will be charged.

== Next steps ==
* Validate the big picture of the program with the rest of the team
* Create the Google form (or any other form) for application for the program
* Promote the program in our network (maybe a Hacks blog post)
* Contact (if it's possible) people who applied for Phones for Apps program who didn't get a phone

Engagement/Developer Engagement/Technical Evangelism/Loan Program

2013-07-30T18:14:53Z

Fharper: /* Process */

== Loan program ==

The goal of the loan program is to give access to a Firefox OS device to more developers. We got many requests in the Phones for Apps program, and unfortunately, we cannot give a device to all developers. Having a real device can be a good motivation for some developers to develop on the platform. We also have a good simulator, but there is nothing as good as testing your application with a real device. By loaning devices to developers, it will give us the opportunity to get more quality application, and saving on cost (shipping vs buying new devices).

== Rules of the program ==
* Every developer can participate.
* You already built or ported an application for Firefox OS.
* You need to ship back the device two weeks after you received it.
* You need to publish your application to the marketplace one month after you received the device.
* ? You need a credit card to register (we will bill you the price of the phone if you want to keep it, or if you don't return it)

== Process ==
* Developers who want to have a device to test their application, will apply for the program.
* We will ship the devices to people who applied.
** Depending upon the number of devices allowed in the program, and number of participants, we may want to check with participants first if they still need a device (if we have delay)
* We will enter the date the phone has been delivered
* We will contact developers two weeks after the date they received it
** ? We will charge the credit card of the developer if he want to keep the phone, or if the developer doesn't return it.

== Application form ==
* First name

* Last name
* Company
* Address
* City
* State
* Postal Code / Zip Code
* Country
* Phone number
* Email
* Link to the actual application or code (to prove that the application exist * low hanging fruit)
* Acceptance of the terms & conditions
** You actually have an application ready to test on a real device.
** You will return the device after two weeks in your possession.
** You will publish a Firefox OS application in the marketplace one month after you received the device.
** If you don't return the device or wants to keep it, your credit card will be charged.

== Next steps ==
* Validate the big picture of the program with the rest of the team
* Create the Google form (or any other form) for application for the program
* We will promote the program in our network (maybe a Hacks blog post)
* We will contact (if it's possible) people who applied for Phones for Apps program who didn't get a phone

Engagement/Developer Engagement/Technical Evangelism/Loan Program

2013-07-30T18:13:59Z

Fharper: /* Application form */

== Loan program ==

The goal of the loan program is to give access to a Firefox OS device to more developers. We got many requests in the Phones for Apps program, and unfortunately, we cannot give a device to all developers. Having a real device can be a good motivation for some developers to develop on the platform. We also have a good simulator, but there is nothing as good as testing your application with a real device. By loaning devices to developers, it will give us the opportunity to get more quality application, and saving on cost (shipping vs buying new devices).

== Rules of the program ==
* Every developer can participate.
* You already built or ported an application for Firefox OS.
* You need to ship back the device two weeks after you received it.
* You need to publish your application to the marketplace one month after you received the device.
* ? You need a credit card to register (we will bill you the price of the phone if you want to keep it, or if you don't return it)

== Process ==
* Developers who want to have a device to test their application, will apply for the program.
* We will ship the devices to people who applied.
** Depending upon the number of devices allowed in the program, and number of participants, we may want to check with participants first if they still need a device (if we have delay)
* We will enter the date the phone has been delivered
* We will contact developers two weeks after the date they received it
** ? We will charge the credit card of the developer if he want to keep the phone, or if he doesn't return it.

== Application form ==
* First name

* Last name
* Company
* Address
* City
* State
* Postal Code / Zip Code
* Country
* Phone number
* Email
* Link to the actual application or code (to prove that the application exist * low hanging fruit)
* Acceptance of the terms & conditions
** You actually have an application ready to test on a real device.
** You will return the device after two weeks in your possession.
** You will publish a Firefox OS application in the marketplace one month after you received the device.
** If you don't return the device or wants to keep it, your credit card will be charged.

== Next steps ==
* Validate the big picture of the program with the rest of the team
* Create the Google form (or any other form) for application for the program
* We will promote the program in our network (maybe a Hacks blog post)
* We will contact (if it's possible) people who applied for Phones for Apps program who didn't get a phone

Engagement/Developer Engagement/Technical Evangelism/Loan Program

2013-07-30T18:13:21Z

Fharper: /* Rules of the program */

== Loan program ==

The goal of the loan program is to give access to a Firefox OS device to more developers. We got many requests in the Phones for Apps program, and unfortunately, we cannot give a device to all developers. Having a real device can be a good motivation for some developers to develop on the platform. We also have a good simulator, but there is nothing as good as testing your application with a real device. By loaning devices to developers, it will give us the opportunity to get more quality application, and saving on cost (shipping vs buying new devices).

== Rules of the program ==
* Every developer can participate.
* You already built or ported an application for Firefox OS.
* You need to ship back the device two weeks after you received it.
* You need to publish your application to the marketplace one month after you received the device.
* ? You need a credit card to register (we will bill you the price of the phone if you want to keep it, or if you don't return it)

== Process ==
* Developers who want to have a device to test their application, will apply for the program.
* We will ship the devices to people who applied.
** Depending upon the number of devices allowed in the program, and number of participants, we may want to check with participants first if they still need a device (if we have delay)
* We will enter the date the phone has been delivered
* We will contact developers two weeks after the date they received it
** ? We will charge the credit card of the developer if he want to keep the phone, or if he doesn't return it.

== Application form ==
* First name

* Last name
* Company
* Address
* City
* State
* Postal Code / Zip Code
* Country
* Phone number
* Email
* Link to the actual application or code (to prove that the application exist * low hanging fruit)
* Acceptance of the terms & conditions
** You actually have an application ready to test on a real device.
** You will return the device after two weeks in your possession.
** If you don't return the device or wants to keep it, your credit card will be charged.

== Next steps ==
* Validate the big picture of the program with the rest of the team
* Create the Google form (or any other form) for application for the program
* We will promote the program in our network (maybe a Hacks blog post)
* We will contact (if it's possible) people who applied for Phones for Apps program who didn't get a phone

Engagement/Developer Engagement/Technical Evangelism/Loan Program

2013-07-30T18:12:40Z

Fharper: /* Loan program */

== Loan program ==

The goal of the loan program is to give access to a Firefox OS device to more developers. We got many requests in the Phones for Apps program, and unfortunately, we cannot give a device to all developers. Having a real device can be a good motivation for some developers to develop on the platform. We also have a good simulator, but there is nothing as good as testing your application with a real device. By loaning devices to developers, it will give us the opportunity to get more quality application, and saving on cost (shipping vs buying new devices).

== Rules of the program ==
* Every developer can participate.
* You already built or ported an application for Firefox OS.
* You need to ship back the device two weeks after you received it.
* You need to publish your application to the marketplace.
* ? You need a credit card to register (we will bill you the price of the phone if you want to keep it, or if you don't return it)

== Process ==
* Developers who want to have a device to test their application, will apply for the program.
* We will ship the devices to people who applied.
** Depending upon the number of devices allowed in the program, and number of participants, we may want to check with participants first if they still need a device (if we have delay)
* We will enter the date the phone has been delivered
* We will contact developers two weeks after the date they received it
** ? We will charge the credit card of the developer if he want to keep the phone, or if he doesn't return it.

== Application form ==
* First name

* Last name
* Company
* Address
* City
* State
* Postal Code / Zip Code
* Country
* Phone number
* Email
* Link to the actual application or code (to prove that the application exist * low hanging fruit)
* Acceptance of the terms & conditions
** You actually have an application ready to test on a real device.
** You will return the device after two weeks in your possession.
** If you don't return the device or wants to keep it, your credit card will be charged.

== Next steps ==
* Validate the big picture of the program with the rest of the team
* Create the Google form (or any other form) for application for the program
* We will promote the program in our network (maybe a Hacks blog post)
* We will contact (if it's possible) people who applied for Phones for Apps program who didn't get a phone

Engagement/Developer Engagement/Technical Evangelism/Loan Program

2013-07-30T18:12:04Z

Fharper: /* Loan program */

== Loan program ==

The goal of the loan program is to give access to a Firefox OS device to more developers. We got many requests in the Phones for Apps program, and unfortunately, we cannot give a device to all developers. Having a real device can be a good motivation for some developers to develop on the platform. We also have a good simulator, but there is nothing as good as testing your application with a real device. By loaning devices to developers, it will give us the opportunity to get more quality application, but saving on cost (shipping vs buying new devices).

== Rules of the program ==
* Every developer can participate.
* You already built or ported an application for Firefox OS.
* You need to ship back the device two weeks after you received it.
* You need to publish your application to the marketplace.
* ? You need a credit card to register (we will bill you the price of the phone if you want to keep it, or if you don't return it)

== Process ==
* Developers who want to have a device to test their application, will apply for the program.
* We will ship the devices to people who applied.
** Depending upon the number of devices allowed in the program, and number of participants, we may want to check with participants first if they still need a device (if we have delay)
* We will enter the date the phone has been delivered
* We will contact developers two weeks after the date they received it
** ? We will charge the credit card of the developer if he want to keep the phone, or if he doesn't return it.

== Application form ==
* First name

* Last name
* Company
* Address
* City
* State
* Postal Code / Zip Code
* Country
* Phone number
* Email
* Link to the actual application or code (to prove that the application exist * low hanging fruit)
* Acceptance of the terms & conditions
** You actually have an application ready to test on a real device.
** You will return the device after two weeks in your possession.
** If you don't return the device or wants to keep it, your credit card will be charged.

== Next steps ==
* Validate the big picture of the program with the rest of the team
* Create the Google form (or any other form) for application for the program
* We will promote the program in our network (maybe a Hacks blog post)
* We will contact (if it's possible) people who applied for Phones for Apps program who didn't get a phone

Engagement/Developer Engagement/Technical Evangelism/Loan Program

2013-07-30T18:05:45Z

Fharper:

== Loan program ==

The goal of the loan program is to give access to a Firefox OS device to more developers. We got many requests in the Phones for Apps program, and unfortunately, we cannot give a device to all developers. Having a real device can be a real motivation for some developers to develop on the platform. We also have a good simulator, but there is nothing as good as testing your application with a real device. By loaning devices to developers, it will give us the opportunity to get more quality application, but saving on cost (shipping vs buying new devices).

== Rules of the program ==
* Every developer can participate.
* You already built or ported an application for Firefox OS.
* You need to ship back the device two weeks after you received it.
* You need to publish your application to the marketplace.
* ? You need a credit card to register (we will bill you the price of the phone if you want to keep it, or if you don't return it)

== Process ==
* Developers who want to have a device to test their application, will apply for the program.
* We will ship the devices to people who applied.
** Depending upon the number of devices allowed in the program, and number of participants, we may want to check with participants first if they still need a device (if we have delay)
* We will enter the date the phone has been delivered
* We will contact developers two weeks after the date they received it
** ? We will charge the credit card of the developer if he want to keep the phone, or if he doesn't return it.

== Application form ==
* First name

* Last name
* Company
* Address
* City
* State
* Postal Code / Zip Code
* Country
* Phone number
* Email
* Link to the actual application or code (to prove that the application exist * low hanging fruit)
* Acceptance of the terms & conditions
** You actually have an application ready to test on a real device.
** You will return the device after two weeks in your possession.
** If you don't return the device or wants to keep it, your credit card will be charged.

== Next steps ==
* Validate the big picture of the program with the rest of the team
* Create the Google form (or any other form) for application for the program
* We will promote the program in our network (maybe a Hacks blog post)
* We will contact (if it's possible) people who applied for Phones for Apps program who didn't get a phone

Engagement/Developer Engagement/Technical Evangelism

2013-07-30T18:03:57Z

Fharper:

<section begin=summary />{{TeamSummary
|teamtitle=Technical Evangelism
|teampagelocation=Engagement/Developer_Engagement/Technical_Evangelism
|teamlead=Mark Coggins
|mailinglist= n/a
|description=Mozilla's Technology Evangelism group engages with developers and the broader web community to:
*Share the Mozilla mission of openness, innovation and opportunity on the web
*Encourage adoption of open web standards and open standards-based technology created by Mozilla and others in support of our mission
*Provide developer enablement resources
*Collect and champion developer feedback on Mozilla initiatives and technology
*Understand competing initiatives and technology from for-profit players
}}<section end=summary />

== Communication Channels ==
{| class="fullwidth-table"
|-
| style="background:#EFEFEF;" | '''Name'''
| style="background:#EFEFEF;" | '''Description'''
| style="background:#EFEFEF;" | '''Location'''
| style="background:#EFEFEF;" | '''Notes'''
|-
|Hacks Blog
|Information about open web technology of interest to developers.
|[https://hacks.mozilla.org/ hacks.mozilla.org]
|[[Engagement/Developer Engagement/Hacks blog|Editorial guidelines and calendar]]
|-
|Hacks YouTube Video Channel
|Videos of talks, demonstrations and how-tos.
|[http://www.youtube.com/user/mozhacks/ Mozhacks on YouTube]
|
|-
|Hacks on Twitter
|Tweets about open web technology.
|[https://twitter.com/mozhacks/ @mozhacks]
|
|}

== Team: Role & Focus ==
{| class="fullwidth-table"
|-
| style="background:#EFEFEF;" | '''Name'''
| style="background:#EFEFEF;" | '''Role'''
| style="background:#EFEFEF;" | '''Q2 Focus'''
|-
|[https://phonebook.mozilla.org/search.php?format=html&query=mcoggins@mozilla.com Mark Coggins]
|Team lead.
|Plan and lead execution of the Firefox OS developer engagement initiative.
|-
|[https://phonebook.mozilla.org/search.php?format=html&query=cheilmann@mozilla.com Christian Heilmann]
|Principal Developer Evangelist. Making the world love HTML5 and the open web as much as I do. Helping Mozilla folk to speak to developers.
|Determine curriculum requirements and host Firefox OS Workshops, train and recruit speaker reps on Firefox OS and lead myth-busting efforts around HTML5.
|-
|[https://phonebook.mozilla.org/search.php?format=html&query=hhoffman@mozilla.com Havi Hoffman]
|Content wrangler. Creating developer content, planning developer events and moving information across time and space.
|Create content, learning materials and program for worldwide Firefox OS Workshops. Tweet from @mozlabs and manage the Apps & Hacks Newsletter.
|-
|[[User:Ckoehler | Christie Koehler]]
|Program Manager & Evangelist.
|Plan and administer the developer phone program for Firefox OS.
|-
|[https://phonebook.mozilla.org/search.php?format=html&query=rnyman@mozilla.com Robert Nyman]
|Technical Evangelist. Editor of Mozilla Hacks.
|Increase readership of Hacks Blog, develop and deliver curriculum at Firefox OS Workshops.
|-
|[https://phonebook.mozilla.org/search.php?format=html&query=jweathersby@mozilla.com Jason Weathersby]
|Firefox OS Evangelist.
|Recruit developers--and their apps--to the Firefox OS platform.
|-
|[https://phonebook.mozilla.org/search.php?format=html&query=fharper@mozilla.com Frédéric Harper]
|Firefox OS Evangelist. Work his magic to help Firefox OS developers to be successful.
|Recruit developers--and their apps--to the Firefox OS platform.
|}

== Q2 Goals ==
* Enable acceptance of 400 Firefox OS apps in the Marketplace from independent developers (aka "long tail developers"), 100 of which were created by developers with whom we have a direct relationship
* Successful launch of the Developer Phone program, including:
** Functioning GP store for phone purchases
** Working OTA updates
** On-hand inventory of devices for use at developer events run by Tech Evan or Reps
** Distribution of phones to employees, Reps, and other priority groups
* Average of 180,000 unique visitors per month for Hacks blog

== Key Initiatives ==
* [[ReMo/SIGs/Evangelism_Reps|Evangelism Reps Program]]
* [[ReMo/SIGs/Evangelism_Reps/Conference_participation|Conference Participation]]
* [[Engagement/Developer_Engagement/FirefoxOS-porting-training|Firefox OS App Migration Workshops]]
* [[Engagement/Developer_Engagement/FirefoxOSAppsv2/JanuaryEvent|Firefox OS App Days]]
* [[Engagement/Developer_Engagement/Hardware|Firefox OS Developer Phone Program]]
* [[Engagement/Developer_Engagement/FirefoxOSAppsv2|Overall Firefox OS Developer Engagement Plan]]
* [[/Loan_Program|Loan Program]]

Engagement/Developer Engagement/Technical Evangelism/Loan Program

2013-07-30T18:01:40Z

Fharper: Created page with "== Loan program == The goal of the loan program is to give access to a Firefox OS device to more developers. We got many requests in the Phones for Apps program, and unfortun..."

== Loan program ==

The goal of the loan program is to give access to a Firefox OS device to more developers. We got many requests in the Phones for Apps program, and unfortunately, we cannot give a device to all developers. Having a real device can be a real motivation for some developers to develop on the platform. We also have a good simulator, but there is nothing as good as testing your application with a real device. By loaning devices to developers, it will give us the opportunity to get more quality application, but saving on cost (shipping vs buying new devices).

== Rules of the program ==
* Every developers can participate.
* You already built or ported an application for Firefox OS.
* You need to ship back the device two weeks after you received it.
* You need to publish your application to the marketplace.
* ? You need a credit card to register (we will bill you the price of the phone if you want to keep it or if you don't return it)

== Process ==
* Developers who want to have a device to test their application, will apply to the program.
* We will ship the devices to people who applied.
** Depending on the number of devices allowed to the program, and number of participants, we may want to check with participants first if they still need a device (if we have delay)
* We will enter the date the phone has been delivered
* We will contact developers two weeks after the date they received it
** ? We will charge the credit card of the developer of he want to keep the phone or if he don't return it

== Application form ==
* First name

* Last name
* Company
* Address
* City
* State
* Postal Code / Zip Code
* Country
* Phone number
* Email
* Link to the actual application or code (to prove that the application exist * low hanging fruit)
* Acceptance of the terms & conditions
** You actually have an application ready to test on a real device
** You will return the device after two weeks in your possession
** If you don't return the device or wants to keep it, your credit card will be charge

== Next steps ==
* Validate the big picture of the program with the rest of the team
* Create the Google form (or any other form) for application to the program
* We will promote the program in our network (maybe a Hacks blog post)
* We will contact (if it's possible) people who applied for Phones for Apps program who didn't get a phone

Engagement/Developer Engagement/Technical Evangelism

2013-07-30T15:06:23Z

Fharper: /* Team: Role & Focus */