MozillaWiki - User contributions [en]

Matrix/Userstyles

2020-02-27T22:13:09Z

Sheppy: /* Matrix Userstyles */ add photon screenshot

'''Work in Progress'''

== Matrix Userstyles ==

This page contains a list of userstyles for [https://riot.im/ Riot Web] created by mozillians.

{| class="wikitable"
|-
! Userstyle Name !! Description !! Screenshot !! Link
|-
| Riot Compact Sidebar || A userstyle that let you see more rooms and users in the sidebars || || [https://gist.github.com/dannycolin/71cd8c657e205e0a232529ff9e581804 GitHub]
|-
| Riot Photon || A Riot Web theme based on [https://design.firefox.com/photon/ Mozilla's Photon Design System] ||
[[File:Photon-screenshot.png|thumb]]
|| [https://github.com/Photonize/riot-photon GitHub]
|}

File:Photon-screenshot.png

2020-02-27T22:10:39Z

Sheppy: Screenshot of the photon theme for Matrix

Screenshot of the photon theme for Matrix

Matrix/Userstyles

2020-02-27T22:08:21Z

Sheppy: /* Matrix Userstyles */ Add screenshot column

'''Work in Progress'''

== Matrix Userstyles ==

This page contains a list of userstyles for [https://riot.im/ Riot Web] created by mozillians.

{| class="wikitable"
|-
! Userstyle Name !! Description !! Screenshot !! Link
|-
| Riot Compact Sidebar || A userstyle that let you see more rooms and users in the sidebars || || [https://gist.github.com/dannycolin/71cd8c657e205e0a232529ff9e581804 GitHub]
|-
| Riot Photon || A Riot Web theme based on [https://design.firefox.com/photon/ Mozilla's Photon Design System] ||
[[File:Https://raw.githubusercontent.com/Photonize/riot-photon/master/screenshot.png|160px|thumb]]
|| [https://github.com/Photonize/riot-photon GitHub]
|}

Engagement/MDN Durable Team

2020-02-07T16:08:26Z

Sheppy: /* Team Members */ update sheppy area

== Overview ==
{{admon/note|[https://tree.taiga.io/project/viya-mdn-durable-team/taskboard/2017-q1-sprint-1-1?kanban-status=649183 Q1 Sprint 1] starts on January 25!}}
We are the [https://developer.mozilla.org/en-US/'''MDN'''] (Mozilla Developer Network) durable team. See the main '''[[MDN]]''' wiki page for MDN's mission, vision, and KPI.

The MDN Durable Team is now part of the Developer Outreach group in Emerging Technologies (ET), and is no longer part of Marketing/Engagement. The content team moved to ET in July 2017, and the dev team moved in March 2018.

==Team Members==
{| class="wikitable"
! Role !! Name !! Area
|-
|colspan="3"| '''Managers and planners'''
|-
| [[Engagement/MDN_Durable_Team/Agile_glossary#Product Owner|Product manager]] || Kadir Topal ||
|-
| Writers' Team Manager, Content Lead || Chris Mills ||
|-
| Agile coach
| Janet Swisher
|
|-
|colspan="3"| '''[[Engagement/MDN_Durable_Team/Agile_glossary#Maker|Makers]]'''
|-
|rowspan="5" style="vertical-align:top;"| Content
|-
| William Bamberg
| Web, Interactive Examples
|-
| Florian Scholz
| Web, Browser Compatibility Data
|-
| Eric ("Sheppy") Shepherd
| WebAPIs, WebXR, Media (incl. WebRTC), SEO
|-
| Rachel Andrew
| CSS
|-
|rowspan="5" style="vertical-align:top;"| Web development
| Peter Bengtsson
| Back-end
|-
| Ryan Johnson
| Back-end
|-
| Schalk Neethling
| Front-end
|-
| Dan Callahan
| Full stack
|-
| Nick Brandt
| UX design
|}

==Accountability==
===Objectives and Key Results===
What are [https://en.wikipedia.org/wiki/OKR Objectives and Key Results]?
====2017 Objectives and Q3 Key Results====
[https://docs.google.com/a/mozilla.com/spreadsheets/d/1tPEf3VVkLtaQK_3sXx_Sb3nK7ep4ZVlaXIL9v1gM4ZM/edit?usp=sharing|Complete Developer Outreach Q3 OKRs] (mozilla.com logins only)
{| class="wikitable"
! Developer Outreach 2017 Objective
! MDN Q3 Key Results
|-
| style="vertical-align:top;" rowspan=6|Increase number of MDN sessions 40% y/y
| style="vertical-align:top;" |Serve 39 million sessions on MDN (an increase of 11.2m sessions y/y)
|-
| Evaluate the impact of SEO recommendations on CTR
* Perform 2 less-complex development tasks for SEO gains
* 8 experiments from SEO recommendations executed
|-
| Complete static examples (excl. APIs)
* Complete examples for all of JS
* Complete 60 CSS output examples
* Complete HTML examples
* Plan API examples
|-
| Launch A/B test of final live sample code editor
|-
| Content updates for Firefox 56/57 release support
* Firefox 56 release support
* Firefox 57 release support
* CSS box alignment
* <input type=””> ref updates
* Flash to HTML5 transition
|-
| 100% of production traffic on AWS to provide stable technical foundation for MDN
* Serve maintenance mode from AWS with production traffic
* Serve dev R/W site from AWS
|-
| style="vertical-align:top;" rowspan=2 |80% of MDN visitors to understand that MDN is powered by Mozilla (Baseline: 52%)
| Complete redesign for home page, all article pages, and all landing pages
* home page updated
* article pages updated
* landing pages updated
|-
| Run brand perception survey on MDN
|-
| style="vertical-align:top;" rowspan=2|At least 1 editor offers integrated access to MDN compat data by end of 2017
| style="vertical-align:top;" | Complete migration of 100% of compat data
* JS compat data complete
* CSS compat data complete
* HTML compat data complete
* API compat data complete
|-
| [https://docs.google.com/document/d/1qse7VhMVWN2WnIcP56nwhoHpP3V1xnAQTWEIfWUwWVo/edit Sign up one editor vendor for inclusion of compat data by end of 2017]
|-
| style="vertical-align:top;" rowspan=2|Launch experiments with 2 new types of community/contribution programs that help Mozilla promote web standards usage to developers
|-
| style="vertical-align:top;" | Deliver strategy and plan to establish and build a thriving core MDN Community that goes beyond casual editorial improvement of our documentation.
* Investigate refocusing MDN Community strategy on attracting and retaining core contributors on MDN
* Define and implement an onboarding process for institutional contributors
|-
|}

* [[Engagement/MDN_Durable_Team/Accountability/2017#Q2_Key_Results|2017 Q2 Key Results]]
* [[Engagement/MDN_Durable_Team/Accountability/2017#Q1_Key_Results|2017 Q1 Key Results]]
* [[Engagement/MDN_Durable_Team/Accountability/2016|2016 Quarterly Targets]]

== Sprint Schedule ==
{| class="wikitable"
! Task Board !! Start !! End !! Demo/Outcomes
|-
| colspan="4" | 2017 Q2
|-
| [https://tree.taiga.io/project/viya-mdn-durable-team/taskboard/q2-sprint-1?kanban-status=649183 Sprint 1]
| April 3 || April 18
|
|-
| [https://tree.taiga.io/project/viya-mdn-durable-team/taskboard/2017-q2-sprint-2 Sprint 2]
| April 24 || May 9
|
|-
| Sprint 3
| May 15 || May 30
|
|-
| Sprint 4
| June 5 || June 20
|
|-
| colspan="4" | 2017 Q1
|-
| [https://tree.taiga.io/project/viya-mdn-durable-team/taskboard/2017-q1-sprint-1?kanban-status=649183 Sprint 0]
| January 9 || January 24
| No demo; the MDN team started early, so work before Sprint 1's official start is "Sprint 0".
|-
|[https://tree.taiga.io/project/viya-mdn-durable-team/taskboard/2017-q1-sprint-1-1?kanban-status=649183 Sprint 1]
| January 25 || February 7
| [https://groups.google.com/forum/#!topic/mozilla.mdn/4Slmxts-bIU demo summary]
|-
| [https://tree.taiga.io/project/viya-mdn-durable-team/taskboard/2017-q1-sprint-2 Sprint 2]
| February 13 || February 28
| [https://docs.google.com/presentation/d/1_z7jkfqz2gkgWhdCZgTB-m5bXD8kpOpO2iUuxEOoZMM/edit#slide=id.p4 demo slides]; [https://groups.google.com/d/msg/mozilla.mdn/kH74h-YlhPw/h4mVIrP1AQAJ demo summary]
|-
| [https://tree.taiga.io/project/viya-mdn-durable-team/taskboard/q1-sprint-3-2 Sprint 3]
| March 6 || March 21
| [https://groups.google.com/forum/#!topic/mozilla.mdn/lEFGcwIKMVQ demo summary]; [https://docs.google.com/presentation/d/1Zl3TCCWhke8PEGulZZkjr0kNQ6Ksx7KvLJZ1VhVW8H8/edit?usp=sharing slides about User Testing]
|-
| colspan="4" | 2016 Q4
|-
| [https://tree.taiga.io/project/viya-mdn-durable-team/taskboard/q4-sprint-1-1 Sprint 1]
| 10 October || 25 October
| [https://docs.google.com/presentation/d/1NneuyvcnIklv9xFkK9M10dmz3zm6nDWp4sahhRrdwiU/edit?usp=sharing Demo]
|-
| [https://tree.taiga.io/project/viya-mdn-durable-team/taskboard/q4-sprint-2-1 Sprint 2]
| 31 Oct || 15 Nov
| [https://docs.google.com/presentation/d/15_v5OSMiOXMUANtTw6_XUQ8sZ-cZxdz91cviH1w3Ck4/edit#slide=id.p4 Demo]
|-
| [https://tree.taiga.io/project/viya-mdn-durable-team/taskboard/working-sprint-backlog Sprint 3]
| November 21 || December 2
| No demo due to All-Hands
|-
| [https://tree.taiga.io/project/viya-mdn-durable-team/taskboard/next-sprint-working-backlog Sprint 4]
| December 12 || December 30
| No demo, due to lots of PTO
|-
| colspan="4" | 2016 Q3
|-
| [https://tree.taiga.io/project/viya-mdn-durable-team/taskboard/sprint-3-1557 Sprint 1]
| 27 June || 12 July
| [https://docs.google.com/presentation/d/1mycek61a_icdxc0jsksfX9hnB5ovUQ35VqyohPzX6yE/edit?usp=sharing Demo]
|-
| [https://tree.taiga.io/project/viya-mdn-durable-team/taskboard/q3-sprint-2-1 Sprint 2]
| 18 July || 2 August
|
|-
| [https://tree.taiga.io/project/viya-mdn-durable-team/taskboard/q3-sprint-3-1 Sprint 3]
| 8 August || 23 August
| [https://docs.google.com/presentation/d/1ooNMa3hkpR9qFX2806aN8ZehCBgTtGxa1ddI2PrmzEU/edit?usp=sharing Demo]
|-
| [https://tree.taiga.io/project/viya-mdn-durable-team/taskboard/q3-sprint-4-1 Sprint 4]
| 29 August || 13 September
| [https://docs.google.com/presentation/d/1R-lluQZP67AAYBL_bfiz8SYNuE-ZPlF9sJJsQhoUZFE/edit?usp=sharing Demo]
|-
| [https://tree.taiga.io/project/viya-mdn-durable-team/taskboard/q3-sprint-5-draft Sprint 5]
| 19 September || 4 October
| [https://docs.google.com/presentation/d/1YJ171Ei9e4PS8g50yj12pfZ6q1N8XiI2saHeTT_rPbk/edit?usp=sharing Demo]
|-
| colspan="4"| 2016 Q2
|-
| [https://mozilla.kanbanery.com/projects/68288/board/?key=775e5e65ceb38d40d0dc1a4e481901387d08abdf Sprint 1]
| 25 April || 10 May
| [https://drive.google.com/open?id=1DEBELSYe8nQezlGa13A_qDwmvWiuckjaeAt_YecVZCU Demo]
|-
| [https://tree.taiga.io/project/viya-mdn-durable-team/taskboard/sprint-2-2059 Sprint 2]
| 16 May || 31 May
| [https://docs.google.com/presentation/d/1gbf6EsNVuPb1EJhynEYqNTAsL3QPwZGzEGaxY46AR_M/edit?usp=sharing Demo]
|-
| Sprint 3
| colspan="2" | Mini-sprint weeks of 6-10 and 20-24 June
|}

== Relevant Links ==
* [https://docs.google.com/spreadsheets/d/1K8RDKNO-oeimbRNBEWJEnKIPeJUEkPNXrMgmUmmgmMY/edit?usp=sharing Per-sprint user stories]
* [[Engagement/MDN_Durable_Team/Processes|MDN Durable team processes]]
* [[Engagement/MDN_Durable_Team/Agile_glossary|Agile glossary]]
* [https://tree.taiga.io/project/viya-mdn-durable-team/backlog MDN backlog] in Taiga
* [[Engagement/MDN_Durable_Team/Mentoring|How the MDN team handles mentoring]]
* [https://docs.google.com/spreadsheets/d/1TTMsjNUKWg5H7EZh6U7DWhC_ZYzb6jwn4---JDnJyGI/edit?usp=sharing 2016 MDN Roadmap]: [[Engagement/MDN_Durable_Team/Agile_glossary#Epic|Epics]] by theme and timeframe
* [https://docs.google.com/a/mozilla.com/spreadsheets/d/1a36G1Qt2d8a9yptgm8ZnAtG6bTJtXho8KoNAQIxSV10/edit?usp=sharing 2016 Initial product backlog]
* [[Engagement/MDN_Durable_Team/Periodic_maintenance_checklist|MDN Periodic maintenance checklist]]

* [https://docs.google.com/a/mozilla.com/presentation/d/1VOIKQ7p9VtPGPCwUUxv6Dt5HYJMoHIFXe3I_XpJzrG8/edit?usp=sharing MDN Agile Playbook]
* [https://docs.google.com/a/mozilla.com/document/d/1blL_Jvu3FhPMTE7PkrqvVLiUqAYDvnmCTTIK5s2b-Yg/edit?usp=sharing MDN's Definition of Done]
* [https://docs.google.com/a/mozilla.com/spreadsheets/d/1fV2_wiA_wwVwK8k69lr1wU-LkkOuOmGOxvFWcgacy0Y/edit?usp=sharing Project Issues / Risks / Requests Log]
* [https://drive.google.com/a/mozilla.com/folderview?id=0B0Nv3O9ZjM0ZNzlabk5La1RFZlU&usp=sharing Meeting Notes]

==Meetings==
'''Sprint Meetings:'''

{| class="wikitable"
|-
! Meeting !! Time and Days !! Attendees !! Notes
|-
| Sprint Planning, Full Team Review || Every third Thursday, 8:30am PT<br>Planning meetings with sub-teams take place earlier in the same week. || Core Team required|| Stakeholders may listen in.<br> This meeting lasts as long as it takes.
|-
| Daily Stand-Up <br>(15 minutes only) || 8:30am Pacific daily <br>
* Content & Community: Monday & Wednesday, first week & second week of Sprint, Monday third week of Sprint<br>
* Development: Tuesday & Thursday, first week & second week of Sprint, Tuesday third week of Sprint
| Relevant core team required || Anyone is welcome to listen, but only core team members speak. All questions from non-core team members should be taken offline with Kadir or Vik.
|-
| Mid-sprint check-in || every third Tuesday, 8:30 PT || Core team required || High-level check of how the sprint is going, adjustments that need to be made immediately, and progress toward completing the committed user stories for the sprint.
|-
| Sprint Demo Meeting || every third Monday, 9:00am PT || Everyone welcome || The team will show the work completed in the sprint. It's a place to ask questions and give feedback.
|-
| Sprint Retrospective Meeting || every third Wednesday, starting on May 11 || Core Team only || No one else is invited to this meeting.
|}

* Unless otherwise specified, all team meetings will be in Vik's Vidyo room.

'''Non-Sprint MDN Meetings:'''

(All times Pacific)
* MDN Weekly Dev Planning: Mondays, 10:00AM
* MDN Content Coordination meeting: Tuesdays, 9.00AM
* MDN Weekly Doc Request Triage: Tuesdays, 9:30AM
* MDN Opportunity Review: Wednesdays, 9:00AM
* MDN Weekly Bug Swat: Fridays, 8:00AM

See full [https://calendar.google.com/calendar/embed?src=mozilla.com_2d35383434313235392d323530@resource.calendar.google.com&ctz=GMT&pli=1 calendar] for dates and participation info.

== Communication Channels ==

* Email: mdn-team@mozilla.com
* IRC: #mdn and #mdndev are our main channels (public conversations) / #team-awesome for private conversations.
* Discussion forum: [https://discourse.mozilla-community.org/c/mdn MDN category on Discourse]

Engagement/MDN Durable Team

2020-02-07T16:07:27Z

Sheppy: /* Team Members */ Fix table breakage

== Overview ==
{{admon/note|[https://tree.taiga.io/project/viya-mdn-durable-team/taskboard/2017-q1-sprint-1-1?kanban-status=649183 Q1 Sprint 1] starts on January 25!}}
We are the [https://developer.mozilla.org/en-US/'''MDN'''] (Mozilla Developer Network) durable team. See the main '''[[MDN]]''' wiki page for MDN's mission, vision, and KPI.

The MDN Durable Team is now part of the Developer Outreach group in Emerging Technologies (ET), and is no longer part of Marketing/Engagement. The content team moved to ET in July 2017, and the dev team moved in March 2018.

==Team Members==
{| class="wikitable"
! Role !! Name !! Area
|-
|colspan="3"| '''Managers and planners'''
|-
| [[Engagement/MDN_Durable_Team/Agile_glossary#Product Owner|Product manager]] || Kadir Topal ||
|-
| Writers' Team Manager, Content Lead || Chris Mills ||
|-
| Agile coach
| Janet Swisher
|
|-
|colspan="3"| '''[[Engagement/MDN_Durable_Team/Agile_glossary#Maker|Makers]]'''
|-
|rowspan="5" style="vertical-align:top;"| Content
|-
| William Bamberg
| Web, Interactive Examples
|-
| Florian Scholz
| Web, Browser Compatibility Data
|-
| Eric ("Sheppy") Shepherd
| WebAPIs, Media, SEO
|-
| Rachel Andrew
| CSS
|-
|rowspan="5" style="vertical-align:top;"| Web development
| Peter Bengtsson
| Back-end
|-
| Ryan Johnson
| Back-end
|-
| Schalk Neethling
| Front-end
|-
| Dan Callahan
| Full stack
|-
| Nick Brandt
| UX design
|}

==Accountability==
===Objectives and Key Results===
What are [https://en.wikipedia.org/wiki/OKR Objectives and Key Results]?
====2017 Objectives and Q3 Key Results====
[https://docs.google.com/a/mozilla.com/spreadsheets/d/1tPEf3VVkLtaQK_3sXx_Sb3nK7ep4ZVlaXIL9v1gM4ZM/edit?usp=sharing|Complete Developer Outreach Q3 OKRs] (mozilla.com logins only)
{| class="wikitable"
! Developer Outreach 2017 Objective
! MDN Q3 Key Results
|-
| style="vertical-align:top;" rowspan=6|Increase number of MDN sessions 40% y/y
| style="vertical-align:top;" |Serve 39 million sessions on MDN (an increase of 11.2m sessions y/y)
|-
| Evaluate the impact of SEO recommendations on CTR
* Perform 2 less-complex development tasks for SEO gains
* 8 experiments from SEO recommendations executed
|-
| Complete static examples (excl. APIs)
* Complete examples for all of JS
* Complete 60 CSS output examples
* Complete HTML examples
* Plan API examples
|-
| Launch A/B test of final live sample code editor
|-
| Content updates for Firefox 56/57 release support
* Firefox 56 release support
* Firefox 57 release support
* CSS box alignment
* <input type=””> ref updates
* Flash to HTML5 transition
|-
| 100% of production traffic on AWS to provide stable technical foundation for MDN
* Serve maintenance mode from AWS with production traffic
* Serve dev R/W site from AWS
|-
| style="vertical-align:top;" rowspan=2 |80% of MDN visitors to understand that MDN is powered by Mozilla (Baseline: 52%)
| Complete redesign for home page, all article pages, and all landing pages
* home page updated
* article pages updated
* landing pages updated
|-
| Run brand perception survey on MDN
|-
| style="vertical-align:top;" rowspan=2|At least 1 editor offers integrated access to MDN compat data by end of 2017
| style="vertical-align:top;" | Complete migration of 100% of compat data
* JS compat data complete
* CSS compat data complete
* HTML compat data complete
* API compat data complete
|-
| [https://docs.google.com/document/d/1qse7VhMVWN2WnIcP56nwhoHpP3V1xnAQTWEIfWUwWVo/edit Sign up one editor vendor for inclusion of compat data by end of 2017]
|-
| style="vertical-align:top;" rowspan=2|Launch experiments with 2 new types of community/contribution programs that help Mozilla promote web standards usage to developers
|-
| style="vertical-align:top;" | Deliver strategy and plan to establish and build a thriving core MDN Community that goes beyond casual editorial improvement of our documentation.
* Investigate refocusing MDN Community strategy on attracting and retaining core contributors on MDN
* Define and implement an onboarding process for institutional contributors
|-
|}

* [[Engagement/MDN_Durable_Team/Accountability/2017#Q2_Key_Results|2017 Q2 Key Results]]
* [[Engagement/MDN_Durable_Team/Accountability/2017#Q1_Key_Results|2017 Q1 Key Results]]
* [[Engagement/MDN_Durable_Team/Accountability/2016|2016 Quarterly Targets]]

== Sprint Schedule ==
{| class="wikitable"
! Task Board !! Start !! End !! Demo/Outcomes
|-
| colspan="4" | 2017 Q2
|-
| [https://tree.taiga.io/project/viya-mdn-durable-team/taskboard/q2-sprint-1?kanban-status=649183 Sprint 1]
| April 3 || April 18
|
|-
| [https://tree.taiga.io/project/viya-mdn-durable-team/taskboard/2017-q2-sprint-2 Sprint 2]
| April 24 || May 9
|
|-
| Sprint 3
| May 15 || May 30
|
|-
| Sprint 4
| June 5 || June 20
|
|-
| colspan="4" | 2017 Q1
|-
| [https://tree.taiga.io/project/viya-mdn-durable-team/taskboard/2017-q1-sprint-1?kanban-status=649183 Sprint 0]
| January 9 || January 24
| No demo; the MDN team started early, so work before Sprint 1's official start is "Sprint 0".
|-
|[https://tree.taiga.io/project/viya-mdn-durable-team/taskboard/2017-q1-sprint-1-1?kanban-status=649183 Sprint 1]
| January 25 || February 7
| [https://groups.google.com/forum/#!topic/mozilla.mdn/4Slmxts-bIU demo summary]
|-
| [https://tree.taiga.io/project/viya-mdn-durable-team/taskboard/2017-q1-sprint-2 Sprint 2]
| February 13 || February 28
| [https://docs.google.com/presentation/d/1_z7jkfqz2gkgWhdCZgTB-m5bXD8kpOpO2iUuxEOoZMM/edit#slide=id.p4 demo slides]; [https://groups.google.com/d/msg/mozilla.mdn/kH74h-YlhPw/h4mVIrP1AQAJ demo summary]
|-
| [https://tree.taiga.io/project/viya-mdn-durable-team/taskboard/q1-sprint-3-2 Sprint 3]
| March 6 || March 21
| [https://groups.google.com/forum/#!topic/mozilla.mdn/lEFGcwIKMVQ demo summary]; [https://docs.google.com/presentation/d/1Zl3TCCWhke8PEGulZZkjr0kNQ6Ksx7KvLJZ1VhVW8H8/edit?usp=sharing slides about User Testing]
|-
| colspan="4" | 2016 Q4
|-
| [https://tree.taiga.io/project/viya-mdn-durable-team/taskboard/q4-sprint-1-1 Sprint 1]
| 10 October || 25 October
| [https://docs.google.com/presentation/d/1NneuyvcnIklv9xFkK9M10dmz3zm6nDWp4sahhRrdwiU/edit?usp=sharing Demo]
|-
| [https://tree.taiga.io/project/viya-mdn-durable-team/taskboard/q4-sprint-2-1 Sprint 2]
| 31 Oct || 15 Nov
| [https://docs.google.com/presentation/d/15_v5OSMiOXMUANtTw6_XUQ8sZ-cZxdz91cviH1w3Ck4/edit#slide=id.p4 Demo]
|-
| [https://tree.taiga.io/project/viya-mdn-durable-team/taskboard/working-sprint-backlog Sprint 3]
| November 21 || December 2
| No demo due to All-Hands
|-
| [https://tree.taiga.io/project/viya-mdn-durable-team/taskboard/next-sprint-working-backlog Sprint 4]
| December 12 || December 30
| No demo, due to lots of PTO
|-
| colspan="4" | 2016 Q3
|-
| [https://tree.taiga.io/project/viya-mdn-durable-team/taskboard/sprint-3-1557 Sprint 1]
| 27 June || 12 July
| [https://docs.google.com/presentation/d/1mycek61a_icdxc0jsksfX9hnB5ovUQ35VqyohPzX6yE/edit?usp=sharing Demo]
|-
| [https://tree.taiga.io/project/viya-mdn-durable-team/taskboard/q3-sprint-2-1 Sprint 2]
| 18 July || 2 August
|
|-
| [https://tree.taiga.io/project/viya-mdn-durable-team/taskboard/q3-sprint-3-1 Sprint 3]
| 8 August || 23 August
| [https://docs.google.com/presentation/d/1ooNMa3hkpR9qFX2806aN8ZehCBgTtGxa1ddI2PrmzEU/edit?usp=sharing Demo]
|-
| [https://tree.taiga.io/project/viya-mdn-durable-team/taskboard/q3-sprint-4-1 Sprint 4]
| 29 August || 13 September
| [https://docs.google.com/presentation/d/1R-lluQZP67AAYBL_bfiz8SYNuE-ZPlF9sJJsQhoUZFE/edit?usp=sharing Demo]
|-
| [https://tree.taiga.io/project/viya-mdn-durable-team/taskboard/q3-sprint-5-draft Sprint 5]
| 19 September || 4 October
| [https://docs.google.com/presentation/d/1YJ171Ei9e4PS8g50yj12pfZ6q1N8XiI2saHeTT_rPbk/edit?usp=sharing Demo]
|-
| colspan="4"| 2016 Q2
|-
| [https://mozilla.kanbanery.com/projects/68288/board/?key=775e5e65ceb38d40d0dc1a4e481901387d08abdf Sprint 1]
| 25 April || 10 May
| [https://drive.google.com/open?id=1DEBELSYe8nQezlGa13A_qDwmvWiuckjaeAt_YecVZCU Demo]
|-
| [https://tree.taiga.io/project/viya-mdn-durable-team/taskboard/sprint-2-2059 Sprint 2]
| 16 May || 31 May
| [https://docs.google.com/presentation/d/1gbf6EsNVuPb1EJhynEYqNTAsL3QPwZGzEGaxY46AR_M/edit?usp=sharing Demo]
|-
| Sprint 3
| colspan="2" | Mini-sprint weeks of 6-10 and 20-24 June
|}

== Relevant Links ==
* [https://docs.google.com/spreadsheets/d/1K8RDKNO-oeimbRNBEWJEnKIPeJUEkPNXrMgmUmmgmMY/edit?usp=sharing Per-sprint user stories]
* [[Engagement/MDN_Durable_Team/Processes|MDN Durable team processes]]
* [[Engagement/MDN_Durable_Team/Agile_glossary|Agile glossary]]
* [https://tree.taiga.io/project/viya-mdn-durable-team/backlog MDN backlog] in Taiga
* [[Engagement/MDN_Durable_Team/Mentoring|How the MDN team handles mentoring]]
* [https://docs.google.com/spreadsheets/d/1TTMsjNUKWg5H7EZh6U7DWhC_ZYzb6jwn4---JDnJyGI/edit?usp=sharing 2016 MDN Roadmap]: [[Engagement/MDN_Durable_Team/Agile_glossary#Epic|Epics]] by theme and timeframe
* [https://docs.google.com/a/mozilla.com/spreadsheets/d/1a36G1Qt2d8a9yptgm8ZnAtG6bTJtXho8KoNAQIxSV10/edit?usp=sharing 2016 Initial product backlog]
* [[Engagement/MDN_Durable_Team/Periodic_maintenance_checklist|MDN Periodic maintenance checklist]]

* [https://docs.google.com/a/mozilla.com/presentation/d/1VOIKQ7p9VtPGPCwUUxv6Dt5HYJMoHIFXe3I_XpJzrG8/edit?usp=sharing MDN Agile Playbook]
* [https://docs.google.com/a/mozilla.com/document/d/1blL_Jvu3FhPMTE7PkrqvVLiUqAYDvnmCTTIK5s2b-Yg/edit?usp=sharing MDN's Definition of Done]
* [https://docs.google.com/a/mozilla.com/spreadsheets/d/1fV2_wiA_wwVwK8k69lr1wU-LkkOuOmGOxvFWcgacy0Y/edit?usp=sharing Project Issues / Risks / Requests Log]
* [https://drive.google.com/a/mozilla.com/folderview?id=0B0Nv3O9ZjM0ZNzlabk5La1RFZlU&usp=sharing Meeting Notes]

==Meetings==
'''Sprint Meetings:'''

{| class="wikitable"
|-
! Meeting !! Time and Days !! Attendees !! Notes
|-
| Sprint Planning, Full Team Review || Every third Thursday, 8:30am PT<br>Planning meetings with sub-teams take place earlier in the same week. || Core Team required|| Stakeholders may listen in.<br> This meeting lasts as long as it takes.
|-
| Daily Stand-Up <br>(15 minutes only) || 8:30am Pacific daily <br>
* Content & Community: Monday & Wednesday, first week & second week of Sprint, Monday third week of Sprint<br>
* Development: Tuesday & Thursday, first week & second week of Sprint, Tuesday third week of Sprint
| Relevant core team required || Anyone is welcome to listen, but only core team members speak. All questions from non-core team members should be taken offline with Kadir or Vik.
|-
| Mid-sprint check-in || every third Tuesday, 8:30 PT || Core team required || High-level check of how the sprint is going, adjustments that need to be made immediately, and progress toward completing the committed user stories for the sprint.
|-
| Sprint Demo Meeting || every third Monday, 9:00am PT || Everyone welcome || The team will show the work completed in the sprint. It's a place to ask questions and give feedback.
|-
| Sprint Retrospective Meeting || every third Wednesday, starting on May 11 || Core Team only || No one else is invited to this meeting.
|}

* Unless otherwise specified, all team meetings will be in Vik's Vidyo room.

'''Non-Sprint MDN Meetings:'''

(All times Pacific)
* MDN Weekly Dev Planning: Mondays, 10:00AM
* MDN Content Coordination meeting: Tuesdays, 9.00AM
* MDN Weekly Doc Request Triage: Tuesdays, 9:30AM
* MDN Opportunity Review: Wednesdays, 9:00AM
* MDN Weekly Bug Swat: Fridays, 8:00AM

See full [https://calendar.google.com/calendar/embed?src=mozilla.com_2d35383434313235392d323530@resource.calendar.google.com&ctz=GMT&pli=1 calendar] for dates and participation info.

== Communication Channels ==

* Email: mdn-team@mozilla.com
* IRC: #mdn and #mdndev are our main channels (public conversations) / #team-awesome for private conversations.
* Discussion forum: [https://discourse.mozilla-community.org/c/mdn MDN category on Discourse]

Engagement/MDN Durable Team

2020-02-07T16:03:08Z

Sheppy: /* Team Members */ Removed Irene and Estelle :(

== Overview ==
{{admon/note|[https://tree.taiga.io/project/viya-mdn-durable-team/taskboard/2017-q1-sprint-1-1?kanban-status=649183 Q1 Sprint 1] starts on January 25!}}
We are the [https://developer.mozilla.org/en-US/'''MDN'''] (Mozilla Developer Network) durable team. See the main '''[[MDN]]''' wiki page for MDN's mission, vision, and KPI.

The MDN Durable Team is now part of the Developer Outreach group in Emerging Technologies (ET), and is no longer part of Marketing/Engagement. The content team moved to ET in July 2017, and the dev team moved in March 2018.

==Team Members==
{| class="wikitable"
! Role !! Name !! Area
|-
| [[Engagement/MDN_Durable_Team/Agile_glossary#Product Owner|Product manager]] || Kadir Topal ||
|-
| Writers' Team Manager, Content Lead || Chris Mills ||
|-
| Agile coach
| Janet Swisher
|-
|colspan="3"| [[Engagement/MDN_Durable_Team/Agile_glossary#Maker|Makers]]
|-
|rowspan="8" style="vertical-align:top;"| Content
|-
| William Bamberg
| Web, Interactive Examples
|-
| Florian Scholz
| Web, Browser Compatibility Data
|-
| Eric ("Sheppy") Shepherd
| WebAPIs, Media, SEO
|-
| Rachel Andrew
| CSS
|-
|rowspan="5" style="vertical-align:top;"| Web development
| Peter Bengtsson
| Back-end
|-
| Ryan Johnson
| Back-end
|-
| Schalk Neethling
| Front-end
|-
| Dan Callahan
| Full stack
|-
| Nick Brandt
| UX design
|}

==Accountability==
===Objectives and Key Results===
What are [https://en.wikipedia.org/wiki/OKR Objectives and Key Results]?
====2017 Objectives and Q3 Key Results====
[https://docs.google.com/a/mozilla.com/spreadsheets/d/1tPEf3VVkLtaQK_3sXx_Sb3nK7ep4ZVlaXIL9v1gM4ZM/edit?usp=sharing|Complete Developer Outreach Q3 OKRs] (mozilla.com logins only)
{| class="wikitable"
! Developer Outreach 2017 Objective
! MDN Q3 Key Results
|-
| style="vertical-align:top;" rowspan=6|Increase number of MDN sessions 40% y/y
| style="vertical-align:top;" |Serve 39 million sessions on MDN (an increase of 11.2m sessions y/y)
|-
| Evaluate the impact of SEO recommendations on CTR
* Perform 2 less-complex development tasks for SEO gains
* 8 experiments from SEO recommendations executed
|-
| Complete static examples (excl. APIs)
* Complete examples for all of JS
* Complete 60 CSS output examples
* Complete HTML examples
* Plan API examples
|-
| Launch A/B test of final live sample code editor
|-
| Content updates for Firefox 56/57 release support
* Firefox 56 release support
* Firefox 57 release support
* CSS box alignment
* <input type=””> ref updates
* Flash to HTML5 transition
|-
| 100% of production traffic on AWS to provide stable technical foundation for MDN
* Serve maintenance mode from AWS with production traffic
* Serve dev R/W site from AWS
|-
| style="vertical-align:top;" rowspan=2 |80% of MDN visitors to understand that MDN is powered by Mozilla (Baseline: 52%)
| Complete redesign for home page, all article pages, and all landing pages
* home page updated
* article pages updated
* landing pages updated
|-
| Run brand perception survey on MDN
|-
| style="vertical-align:top;" rowspan=2|At least 1 editor offers integrated access to MDN compat data by end of 2017
| style="vertical-align:top;" | Complete migration of 100% of compat data
* JS compat data complete
* CSS compat data complete
* HTML compat data complete
* API compat data complete
|-
| [https://docs.google.com/document/d/1qse7VhMVWN2WnIcP56nwhoHpP3V1xnAQTWEIfWUwWVo/edit Sign up one editor vendor for inclusion of compat data by end of 2017]
|-
| style="vertical-align:top;" rowspan=2|Launch experiments with 2 new types of community/contribution programs that help Mozilla promote web standards usage to developers
|-
| style="vertical-align:top;" | Deliver strategy and plan to establish and build a thriving core MDN Community that goes beyond casual editorial improvement of our documentation.
* Investigate refocusing MDN Community strategy on attracting and retaining core contributors on MDN
* Define and implement an onboarding process for institutional contributors
|-
|}

* [[Engagement/MDN_Durable_Team/Accountability/2017#Q2_Key_Results|2017 Q2 Key Results]]
* [[Engagement/MDN_Durable_Team/Accountability/2017#Q1_Key_Results|2017 Q1 Key Results]]
* [[Engagement/MDN_Durable_Team/Accountability/2016|2016 Quarterly Targets]]

== Sprint Schedule ==
{| class="wikitable"
! Task Board !! Start !! End !! Demo/Outcomes
|-
| colspan="4" | 2017 Q2
|-
| [https://tree.taiga.io/project/viya-mdn-durable-team/taskboard/q2-sprint-1?kanban-status=649183 Sprint 1]
| April 3 || April 18
|
|-
| [https://tree.taiga.io/project/viya-mdn-durable-team/taskboard/2017-q2-sprint-2 Sprint 2]
| April 24 || May 9
|
|-
| Sprint 3
| May 15 || May 30
|
|-
| Sprint 4
| June 5 || June 20
|
|-
| colspan="4" | 2017 Q1
|-
| [https://tree.taiga.io/project/viya-mdn-durable-team/taskboard/2017-q1-sprint-1?kanban-status=649183 Sprint 0]
| January 9 || January 24
| No demo; the MDN team started early, so work before Sprint 1's official start is "Sprint 0".
|-
|[https://tree.taiga.io/project/viya-mdn-durable-team/taskboard/2017-q1-sprint-1-1?kanban-status=649183 Sprint 1]
| January 25 || February 7
| [https://groups.google.com/forum/#!topic/mozilla.mdn/4Slmxts-bIU demo summary]
|-
| [https://tree.taiga.io/project/viya-mdn-durable-team/taskboard/2017-q1-sprint-2 Sprint 2]
| February 13 || February 28
| [https://docs.google.com/presentation/d/1_z7jkfqz2gkgWhdCZgTB-m5bXD8kpOpO2iUuxEOoZMM/edit#slide=id.p4 demo slides]; [https://groups.google.com/d/msg/mozilla.mdn/kH74h-YlhPw/h4mVIrP1AQAJ demo summary]
|-
| [https://tree.taiga.io/project/viya-mdn-durable-team/taskboard/q1-sprint-3-2 Sprint 3]
| March 6 || March 21
| [https://groups.google.com/forum/#!topic/mozilla.mdn/lEFGcwIKMVQ demo summary]; [https://docs.google.com/presentation/d/1Zl3TCCWhke8PEGulZZkjr0kNQ6Ksx7KvLJZ1VhVW8H8/edit?usp=sharing slides about User Testing]
|-
| colspan="4" | 2016 Q4
|-
| [https://tree.taiga.io/project/viya-mdn-durable-team/taskboard/q4-sprint-1-1 Sprint 1]
| 10 October || 25 October
| [https://docs.google.com/presentation/d/1NneuyvcnIklv9xFkK9M10dmz3zm6nDWp4sahhRrdwiU/edit?usp=sharing Demo]
|-
| [https://tree.taiga.io/project/viya-mdn-durable-team/taskboard/q4-sprint-2-1 Sprint 2]
| 31 Oct || 15 Nov
| [https://docs.google.com/presentation/d/15_v5OSMiOXMUANtTw6_XUQ8sZ-cZxdz91cviH1w3Ck4/edit#slide=id.p4 Demo]
|-
| [https://tree.taiga.io/project/viya-mdn-durable-team/taskboard/working-sprint-backlog Sprint 3]
| November 21 || December 2
| No demo due to All-Hands
|-
| [https://tree.taiga.io/project/viya-mdn-durable-team/taskboard/next-sprint-working-backlog Sprint 4]
| December 12 || December 30
| No demo, due to lots of PTO
|-
| colspan="4" | 2016 Q3
|-
| [https://tree.taiga.io/project/viya-mdn-durable-team/taskboard/sprint-3-1557 Sprint 1]
| 27 June || 12 July
| [https://docs.google.com/presentation/d/1mycek61a_icdxc0jsksfX9hnB5ovUQ35VqyohPzX6yE/edit?usp=sharing Demo]
|-
| [https://tree.taiga.io/project/viya-mdn-durable-team/taskboard/q3-sprint-2-1 Sprint 2]
| 18 July || 2 August
|
|-
| [https://tree.taiga.io/project/viya-mdn-durable-team/taskboard/q3-sprint-3-1 Sprint 3]
| 8 August || 23 August
| [https://docs.google.com/presentation/d/1ooNMa3hkpR9qFX2806aN8ZehCBgTtGxa1ddI2PrmzEU/edit?usp=sharing Demo]
|-
| [https://tree.taiga.io/project/viya-mdn-durable-team/taskboard/q3-sprint-4-1 Sprint 4]
| 29 August || 13 September
| [https://docs.google.com/presentation/d/1R-lluQZP67AAYBL_bfiz8SYNuE-ZPlF9sJJsQhoUZFE/edit?usp=sharing Demo]
|-
| [https://tree.taiga.io/project/viya-mdn-durable-team/taskboard/q3-sprint-5-draft Sprint 5]
| 19 September || 4 October
| [https://docs.google.com/presentation/d/1YJ171Ei9e4PS8g50yj12pfZ6q1N8XiI2saHeTT_rPbk/edit?usp=sharing Demo]
|-
| colspan="4"| 2016 Q2
|-
| [https://mozilla.kanbanery.com/projects/68288/board/?key=775e5e65ceb38d40d0dc1a4e481901387d08abdf Sprint 1]
| 25 April || 10 May
| [https://drive.google.com/open?id=1DEBELSYe8nQezlGa13A_qDwmvWiuckjaeAt_YecVZCU Demo]
|-
| [https://tree.taiga.io/project/viya-mdn-durable-team/taskboard/sprint-2-2059 Sprint 2]
| 16 May || 31 May
| [https://docs.google.com/presentation/d/1gbf6EsNVuPb1EJhynEYqNTAsL3QPwZGzEGaxY46AR_M/edit?usp=sharing Demo]
|-
| Sprint 3
| colspan="2" | Mini-sprint weeks of 6-10 and 20-24 June
|}

== Relevant Links ==
* [https://docs.google.com/spreadsheets/d/1K8RDKNO-oeimbRNBEWJEnKIPeJUEkPNXrMgmUmmgmMY/edit?usp=sharing Per-sprint user stories]
* [[Engagement/MDN_Durable_Team/Processes|MDN Durable team processes]]
* [[Engagement/MDN_Durable_Team/Agile_glossary|Agile glossary]]
* [https://tree.taiga.io/project/viya-mdn-durable-team/backlog MDN backlog] in Taiga
* [[Engagement/MDN_Durable_Team/Mentoring|How the MDN team handles mentoring]]
* [https://docs.google.com/spreadsheets/d/1TTMsjNUKWg5H7EZh6U7DWhC_ZYzb6jwn4---JDnJyGI/edit?usp=sharing 2016 MDN Roadmap]: [[Engagement/MDN_Durable_Team/Agile_glossary#Epic|Epics]] by theme and timeframe
* [https://docs.google.com/a/mozilla.com/spreadsheets/d/1a36G1Qt2d8a9yptgm8ZnAtG6bTJtXho8KoNAQIxSV10/edit?usp=sharing 2016 Initial product backlog]
* [[Engagement/MDN_Durable_Team/Periodic_maintenance_checklist|MDN Periodic maintenance checklist]]

* [https://docs.google.com/a/mozilla.com/presentation/d/1VOIKQ7p9VtPGPCwUUxv6Dt5HYJMoHIFXe3I_XpJzrG8/edit?usp=sharing MDN Agile Playbook]
* [https://docs.google.com/a/mozilla.com/document/d/1blL_Jvu3FhPMTE7PkrqvVLiUqAYDvnmCTTIK5s2b-Yg/edit?usp=sharing MDN's Definition of Done]
* [https://docs.google.com/a/mozilla.com/spreadsheets/d/1fV2_wiA_wwVwK8k69lr1wU-LkkOuOmGOxvFWcgacy0Y/edit?usp=sharing Project Issues / Risks / Requests Log]
* [https://drive.google.com/a/mozilla.com/folderview?id=0B0Nv3O9ZjM0ZNzlabk5La1RFZlU&usp=sharing Meeting Notes]

==Meetings==
'''Sprint Meetings:'''

{| class="wikitable"
|-
! Meeting !! Time and Days !! Attendees !! Notes
|-
| Sprint Planning, Full Team Review || Every third Thursday, 8:30am PT<br>Planning meetings with sub-teams take place earlier in the same week. || Core Team required|| Stakeholders may listen in.<br> This meeting lasts as long as it takes.
|-
| Daily Stand-Up <br>(15 minutes only) || 8:30am Pacific daily <br>
* Content & Community: Monday & Wednesday, first week & second week of Sprint, Monday third week of Sprint<br>
* Development: Tuesday & Thursday, first week & second week of Sprint, Tuesday third week of Sprint
| Relevant core team required || Anyone is welcome to listen, but only core team members speak. All questions from non-core team members should be taken offline with Kadir or Vik.
|-
| Mid-sprint check-in || every third Tuesday, 8:30 PT || Core team required || High-level check of how the sprint is going, adjustments that need to be made immediately, and progress toward completing the committed user stories for the sprint.
|-
| Sprint Demo Meeting || every third Monday, 9:00am PT || Everyone welcome || The team will show the work completed in the sprint. It's a place to ask questions and give feedback.
|-
| Sprint Retrospective Meeting || every third Wednesday, starting on May 11 || Core Team only || No one else is invited to this meeting.
|}

* Unless otherwise specified, all team meetings will be in Vik's Vidyo room.

'''Non-Sprint MDN Meetings:'''

(All times Pacific)
* MDN Weekly Dev Planning: Mondays, 10:00AM
* MDN Content Coordination meeting: Tuesdays, 9.00AM
* MDN Weekly Doc Request Triage: Tuesdays, 9:30AM
* MDN Opportunity Review: Wednesdays, 9:00AM
* MDN Weekly Bug Swat: Fridays, 8:00AM

See full [https://calendar.google.com/calendar/embed?src=mozilla.com_2d35383434313235392d323530@resource.calendar.google.com&ctz=GMT&pli=1 calendar] for dates and participation info.

== Communication Channels ==

* Email: mdn-team@mozilla.com
* IRC: #mdn and #mdndev are our main channels (public conversations) / #team-awesome for private conversations.
* Discussion forum: [https://discourse.mozilla-community.org/c/mdn MDN category on Discourse]

Bugzilla:WebServices:Errors

2018-08-09T22:20:29Z

Sheppy: Swapped 108 and 10; these were backward per https://github.com/bugzilla/bugzilla/blob/5.0/Bugzilla/WebService/Constants.pm

This page attempts to be a comprehensive list of the errors that may be returned by the Bugzilla XML-RPC API and the BzAPI HTTP API proxy.

====50 (Param Required)====

A login or password parameter was not provided.

====51 (Invalid Object)====

A value was specified that does not exist in the database.

====52 (Invalid XML-RPC Value)====

The XML-RPC input itself is invalid e.g. you specified something like <int>a string</int>, or you tried to pass a string into a parameter that only accepts ints.

====53 (Invalid Parameter)====

You attempted to pass an undefined value to an internal function in Bugzilla.

====100 (Invalid Bug Alias)====

You specified an alias and either: (a) the Bugzilla you're querying doesn't support aliases or (b) there is no bug with that alias.

====101 (Invalid Bug ID)====

The bug_id you specified doesn't exist in the database.

====102 (Access Denied)====

You do not have access to the bug_id you specified.

====103 (Invalid Alias)====

You asked for a bug to be created with an alias, and the alias you specified is invalid for some reason.

====104 (Invalid Field)====

One of the drop-down fields has an invalid value, or a value entered in a text field is too long. (This code is retired; see code 51.)

====105 (Invalid Component)====

You didn't specify a component.

====106 (Invalid Product)====

Either you didn't specify a product, this product doesn't exist, or you don't have permission to enter bugs in this product.

====107 (Invalid Summary)====

You didn't specify a summary for the bug

====108 (Invalid Field Name)====

You specified a field that doesn't exist or isn't a drop-down field.

====109 (Bug Edit Denied)====

You did not have the necessary rights to edit the bug.

====110 (Comment Is Private)====

You specified the id of a private comment in the comment_ids argument, and you are not in the "insider group" that can see private comments.

====111 (Invalid Comment ID)====

You specified an id in the comment_ids argument that is invalid--either you specified something that wasn't a number, or there is no comment with that id.

====112 (Invalid Bug URL)====

One of the URLs you provided did not look like a valid bug URL.

====113 (Can't Make Private Comments)====

You tried to add a private comment, but don't have the necessary rights.

====300 (Invalid Username or Password)====

The username does not exist, or the password is wrong.

====301 (Account Disabled)====

The account has been disabled. A reason may be specified with the error.

====302 (Auth: Invalid Email)====

An external verification source, such as LDAP, returned an invalid email address.

====-303 extern_id_conflict====

====304 (Authorization Required)====

You are logged in, but you are not authorized to see one of the users you wanted to get information about by user id.

====500 (Illegal Email Address)====

This Bugzilla does not allow you to create accounts with the format of email address you specified. Account creation may be entirely disabled.

====501 (Account Already Exists)====

An account with that email address already exists in Bugzilla.

====502 (Password Too Short)====

The password specified is too short. (Usually, this means the password is under three characters.)

====503 (Password Too Long)====

The password specified is too long. (Usually, this means the password is over ten characters.

====504 (Invalid User)====

Either the QA Contact, Assignee, or CC lists have some invalid user in them. The error message will have more details.

====505 (User Access By Id or User-Matching Denied)====

Logged-out users cannot use the "ids" or "match" arguments to this function.

WeeklyUpdates/2016-11-14

2016-11-14T19:06:33Z

Sheppy: FoT

{{WeeklyUpdateNav}}
* Every Monday @ 11:00am Pacific Time (19:00 UTC)
* https://air.mozilla.org/channels/project-meeting/ to watch and listen
* join irc.mozilla.org #airmozilla for backchannel discussion
* Presenters only: Vidyo room "Brownbags". Do '''not''' use this room if you're not planning to speak.
{{conf|8600}}
** If you plan on presenting, please join the Vidyo BrownBags 20 minutes prior to the start of the meeting and announce to the A/V Technicians that you will be speaking so that they can confirm your Audio and Video.

__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]] ==
* Thanks to Potch for hosting this meeting :-P
* Thanks to DevTools contributor Tim Nguyen for covering news of the upcoming release
* Thanks to Gjis for getting an updated list of reviewers for Firefox components in Bugzilla
* Thanks to Michal Wajszczuk aka MichalTHEDUDE for writing automated tests for Treeherder!
* Thanks to the MDN dev team for working hard to make MDN amazing, with Persona removal, moving macros to Github (coming soon!) and more!

Peter Bengtsson for lots of hard work on his own time to Move Air Mozilla off Persona onto Auth0.

Thanks to all of our New Zealand employees for staying safe!

Potch for his awesome hosting and for reminding us to be thankful!

== Upcoming Events ==

=== This Week ===

=== Monday, {{#time:d F|{{SUBPAGENAME}}}} ===
*November Privacy Lab, [https://www.eventbrite.com/e/privacy-lab-privacy-around-the-world-tickets-28895968620 Privacy Around the World], 6-8pm PT, Santa Clara University and [https://air.mozilla.org/privacy-lab-privacy-around-the-world-2016-11-14/ Air Mozilla].

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

=== Wednesday, {{#time:d F|{{SUBPAGENAME}} +2 days}} ===
* '''[https://wiki.mozilla.org/Speaker_Series#Wednesday.2C_November_16:_Failure:_The_Hard_Part_about_Innovation.2C_with_Ashley_Good.2C_Fail_Forward Failure: The Hard Part About Innovation]''' with [https://www.linkedin.com/in/ashleygood Ashley Good] of [https://failforward.org/ Fail Forward] and [https://mozillians.org/en-US/u/geroter/ George Roter] (host)
** '''Wednesday, November 16 @ 10AM PT / 1PM ET / 5PM UTC, Mozilla SF + [https://air.mozilla.org/failure-the-hard-part-about-innovation-2016-11-16/ AirMozilla]'''
** [https://wiki.mozilla.org/Speaker_Series#Wednesday.2C_November_16:_Failure:_The_Hard_Part_about_Innovation.2C_with_Ashley_Good.2C_Fail_Forward Details] at [https://wiki.mozilla.org/Speaker_Series Speaker Series wiki]
*[https://cyberlaw.stanford.edu/events/government-hacking-vulnerabilities-equities-process Government Hacking: Vulnerabilities Equities Process], 4-6pm PT at Stanford.

* '''[https://indiewebcamp.com/events/2016-11-16-homebrew-website-club Homebrew Website Club Meetup]''' (now most Wednesdays)<br/><strong>Be a part of the open web with your own website.</strong>
** '''London ENGLAND'''
** 18:30-20:00 meetup, demos, & hack night <blockquote><p>Create or update your personal web site!<br/>Share what you've gotten working, ask the experts questions.</p><p>Join a community with like-minded interests. <br/>Bring friends that want a personal site!</p></blockquote> Any questions? See '''[https://indiewebcamp.com/events/2016-11-16-homebrew-website-club the wiki page for details]''' <br/>or join IRC: http://indieweb.org/irc/today?beta#bottom

=== Thursday, {{#time:d F|{{SUBPAGENAME}} +3 days}} ===

=== Friday, {{#time:d F|{{SUBPAGENAME}} +4 days}} ===
*[http://www.msummit.com.br Mobile Summit] is happening the 18th and 19th in Porto Alegre Brazil
**Several Mozillians including members of our local Brazil community will attend this 600 person event focused on supporting community to create projects related with IoT and mobility.
* Calling all staff and volunteers: feeling Foxy? Bring your love and knowledge Firefox by joining the Social Support Sprint from 8:00 AM PST - 10:00 AM PST. During these two hours, we’ll hang out in Vidyo while answering as many questions as possible. It’s a fun way to get to know one another around the world while helping our loyal Firefox users. Want to join or learn more about Social Support? Contact Sierra, sreed@mozilla.com.
* [[Webdev/Beer_And_Tell/2016/November|Webdev Beer and Tell]]: 11:00 AM Pacific in the Webdev Vidyo (Open to the public)
** Stream on Air Mozilla: https://air.mozilla.org/webdev-beer-and-tell-november-2016/
** Monthly get-together for anyone in Mozilla to share their web-development-related side projects!
*SUMO Support Day in the Forums and in Social, join all day in the forums to answer questions about the new Firefox Release. [https://public.etherpad-mozilla.org/p/social-sumo-day-2016-11-18]

=== Saturday, {{#time:d F|{{SUBPAGENAME}} +5 days}} ===
*[http://novemb.rs/ Rust Code Sprint] is happening this weekend on the 19th and 20th
**novemb.rs is a Rust code sprint that is happening in a distributed fashion, organized by our contributors. The organisation and event will run from the Mozilla Berlin office. The goal is to start new projects, work on your current ones or get involved in new ones. The event is open to anyone and happens at several locations. Cologne Meetup is organized by our TechSpeaker Jan-Erik.

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

=== Next Week ===

== Speakers ==

The limit is '''3 minutes per topic'''. 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. The meeting is streamed in a 4:3 format in order to allow for split screen. If your slides are 16:9 "widescreen" format, please indicate in the "Sharing" column below.

{| class="fullwidth-table wikitable"
|-
! [https://mozillians.org/u/USERNAME Presenter]
! Title
! Topic
! Location
! Sharing
! 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, 4:3 or 16:9)
| Links to slides or images you want displayed on screen
| Link to where audience can find out more information
|-
| Jean Gong
| Connected Devices EPM
| Project SensorWeb Overview
| MTV
| no
| [https://docs.google.com/presentation/d/1359mOSfVeqCn5M5TwAQ6infxOxzHuhjb-0jxDKmUYFo/edit?usp=sharing Slides]
| [[Connected Devices/Projects/SensorWeb]]
|-
| Mike Hoye
|
| Engineering Onboarding update.
| MoTo
| no
|
|
|-
| Francisco Picolini
| Community Events Coordinator
| FOSDEM 2017 - Call for Papers
| Home
| no
| [https://docs.google.com/a/mozilla.com/presentation/d/1hGbBBI1SMl9Xoj6Nl_3zudNMKqYK_8gGdHjauA6XZRk/edit?usp=sharing Slides]
| [https://discourse.mozilla-community.org/t/fosdem-2017-call-for-papers-talks/11670 Discourse Topic]
|-
| Richard Milewski
| Air Mozilla Producer
| AirMo Change
| MTV Commons
|
|
|
|-
| Asa Dotzler
| Firefox
| Firefox Updates
|
|
|
|
|}

= 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.

{| class="fullwidth-table wikitable"
|-
! ''Who is being introduced?''
! ''Who are you? (the introducer)''
! ''Where are you doing the introduction?''
! ''Where are they from?''
! ''How will they be part of Mozilla?''
|-

|-
| Blair MacIntyre
| Sean White
| Mountain View
| Atlanta, GA
| Emerging Technologies with a focus on Augmented Reality
|
|-
| Connor Ameres and Andre Duarte
| Sam Penrose
| San Francisco
| University of San Francisco
| Data Analysis Practicums
|}

= Fireside Chat =
A chance to hear from leadership at Mozilla, and have a short Q&A about a specific topic.

===This Week===

'''Name''', "Title"

===Topics===

You can submit questions in advance on the Moderator page (link), or ask them live on Air Mozilla using a Mozilla Space mic or in #airmozilla on IRC.

[[Category:Weekly Updates]]
[[Category:Meeting Notes]]

MDN/Archives/Meetings/Community/2016/09-21

2016-09-21T17:45:52Z

Sheppy: /* Miscellaneous */ glossary and meeting start

=Agenda/Notes=

The MDN community meeting takes place in the [irc://irc.mozilla.org/mdn #mdn] channel on irc.mozilla.org at:
* 10 AM PDT (18:00 UTC). [http://arewemeetingyet.com/Los%20Angeles/2016-09-21/10:00/b/MDN%20Community%20meeting See the meeting time in your time zone.]

==Introductions==
Since lots of people lurk in #mdn, if you're actively attending the meeting please speak up and introduce yourself.

* Attending: jswisher, sheppy, klez, dvincent

==Help wanted==
Please share documentation bugs that need work, or other things where you need short-term help.
* We need to finish documentation updates for Firefox 50! Take a look here for a list of remaining issues:
** [https://tree.taiga.io/project/viya-mdn-durable-team/task/281 Layout: CSS/HTML/SVG/etc]
** [https://tree.taiga.io/project/viya-mdn-durable-team/task/191 DOM and general APIs]
** [https://tree.taiga.io/project/viya-mdn-durable-team/task/192 Media: WebRTC, Web Audio, etc]
* As always, you can find bugs you can help out with on our [http://www.joshmatthews.net/bugsahoy/?mdn=1 Bugs Ahoy] page.

==Blockers==
Is there anything keeping you from making progress?
* We have tons of items marked for tech review but not really anyone working to clear those. We need to find a way to make this happen.

==What are you working on?==
Please share recent accomplishments, and goals you have for the next few weeks.
* (sheppy) Nearly done with documentation updates for File and Directory Entry API.

==Actions==
===Previous===

===New/Continuing===
* (klez) Provide a prioritized list of glossary entries in need of technical review

== Miscellaneous ==
Anything else we need to discuss synchronously?
* Who will moderate the next meeting?
* (klez) Redundant (?) Glossary links in the Learning Area
** Some pages use a term linked to the glossary entry but then also define the term inline. This is unnecessary.
** If the page is about or directly related to the term, remove the glossary link and just define the term inline.
** If the definition is tangential to the page's content, remove the definition and use the glossary link.
* (klez) A modest proposal about starting meetings
** When the agenda is posted and the meeting is announced on dev-mdc, ask that people add themselves to the agenda's list of attendees.
** When the meeting starts, post in IRC the agenda link and the names of those users, so that their IRC client can notify them. For example: "Hi user1, user2, user3! The meeting is starting! Here's the agenda: <link>."

MDN/Archives/Meetings/Community/2016/09-21

2016-09-21T17:18:48Z

Sheppy: /* Blockers */ dup

MDN/Archives/Meetings/Community/2016/09-21

2016-09-21T17:17:41Z

Sheppy: /* Blockers */ tech reviews

=Agenda/Notes=

The MDN community meeting takes place in the [irc://irc.mozilla.org/mdn #mdn] channel on irc.mozilla.org at:
* 10 AM PDT (18:00 UTC). [http://arewemeetingyet.com/Los%20Angeles/2016-09-21/10:00/b/MDN%20Community%20meeting See the meeting time in your time zone.]

==Introductions==
Since lots of people lurk in #mdn, if you're actively attending the meeting please speak up and introduce yourself.

* Attending: jswisher, sheppy, klez, dvincent

==Help wanted==
Please share documentation bugs that need work, or other things where you need short-term help.
* We need to finish documentation updates for Firefox 50! Take a look here for a list of remaining issues:
** [https://tree.taiga.io/project/viya-mdn-durable-team/task/281 Layout: CSS/HTML/SVG/etc]
** [https://tree.taiga.io/project/viya-mdn-durable-team/task/191 DOM and general APIs]
** [https://tree.taiga.io/project/viya-mdn-durable-team/task/192 Media: WebRTC, Web Audio, etc]
* As always, you can find bugs you can help out with on our [http://www.joshmatthews.net/bugsahoy/?mdn=1 Bugs Ahoy] page.

==Blockers==
Is there anything keeping you from making progress?
* We have tons of items marked for tech review but not really anyone working to clear those. We need to find a way to make this happen.
** klez has volunteered to make a list of prioritized pages for review which dvincent can use to generate some tweets, perhaps.

==What are you working on?==
Please share recent accomplishments, and goals you have for the next few weeks.
* (sheppy) Nearly done with documentation updates for File and Directory Entry API.

==Actions==
===Previous===

===New/Continuing===

== Miscellaneous ==
Anything else we need to discuss synchronously?
* Who will moderate the next meeting?
* (klez) Redundant (?) Glossary links in the Learning Area
* (klez) A modest proposal about starting meetings

MDN/Archives/Meetings/Community/2016/09-21

2016-09-21T17:16:45Z

Sheppy: /* Blockers */ tech reviews

MDN/Archives/Meetings/Community/2016/09-21

2016-09-21T17:09:28Z

Sheppy: /* Introductions */ attending

MDN/Archives/Meetings/Community/2016/09-21

2016-09-21T17:07:22Z

Sheppy: /* Introductions */ attending

MDN/Archives/Meetings/Community/2016/09-21

2016-09-21T16:01:44Z

Sheppy: /* What are you working on? */ sheppy's status

MDN/Archives/Meetings/Community/2016/09-21

2016-09-21T16:00:15Z

Sheppy: /* Help wanted */ Add Firefox 50 tasks

MDN/Archives/Meetings/Community//2016/08-24

2016-08-24T17:16:10Z

Sheppy: /* What are you working on? */ JS learning area

=Agenda/Notes=

The MDN community meeting takes place in the [irc://irc.mozilla.org/mdn #mdn] channel on irc.mozilla.org at:
* 10 AM PDT (18:00 UTC). [http://arewemeetingyet.com/Los%20Angeles/2016-08-24/10:00/b/MDN%20Community%20meeting See the meeting time in your time zone.]

==Introductions==
Since lots of people lurk in #mdn, if you're actively attending the meeting please speak up and introduce yourself.

* Attending:

==Help wanted==
Please share documentation bugs that need work, or other things where you need short-term help.
* As always, you can find bugs you can help out with on our [http://www.joshmatthews.net/bugsahoy/?mdn=1 Bugs Ahoy] page.
* (sheppy) I've finished completely redoing the documentation for [https://developer.mozilla.org/en-US/docs/Web/API/KeyboardEvent/key KeyboardEvent.key] values and would appreciate any reviews and error corrections if any are needed.

==Blockers==
Is there anything keeping you from making progress?

==What are you working on?==
Please share recent accomplishments, and goals you have for the next few weeks.

* All Firefox 49 documentation appears to be complete!
* (sebo) Waiting for feedback on https://bugzil.la/1278516 and https://bugzil.la/1282679.
* (sebo) Updating -webkit prefixed items for Firefox 49 and earlier (mostly done, was a big task; people missed to set ddn and to refer to them in the meta-bugs)
* (klez) Looking through the Learning Area to find words to link to the Glossary
* (sheppy) Now working on Firefox 50 WebRTC and media doc updates.
* (chrismills) Introduction to [https://developer.mozilla.org/en-US/docs/Learn/JavaScript JavaScript Learning Area content] is coming along really well.

==Actions==
===Previous===

===New/Continuing===

== Miscellaneous ==
Anything else we need to discuss synchronously?

MDN/Archives/Meetings/Community//2016/08-24

2016-08-24T17:04:35Z

Sheppy: add sheppy stuff

MDN/Archives/Meetings/Community//2016/07-27

2016-07-27T17:06:08Z

Sheppy: /* Help wanted */ MDN newcomers input request

=Agenda/Notes=

The MDN community meeting takes place in the [irc://irc.mozilla.org/mdn #mdn] channel on irc.mozilla.org at:
* 10 AM PDT (17:00 UTC). [http://arewemeetingyet.com/Los%20Angeles/2016-07-27/10:00/b/MDN%20Community%20meeting See the meeting time in your time zone.]

==Introductions==
Since lots of people lurk in #mdn, if you're actively attending the meeting please speak up and introduce yourself.

* Attending: sheppy

==Help wanted==
Please share documentation bugs that need work, or other things where you need short-term help.
* As always, you can find bugs you can help out with on our [http://www.joshmatthews.net/bugsahoy/?mdn=1 Bugs Ahoy] page.
* Tasks that the MDN staff team is working on are listed on the current [https://tree.taiga.io/project/viya-mdn-durable-team/taskboard/q3-sprint-2-1 Taiga task board].
* If you're new to MDN, please don't hesitate to share the pain points you encounter. What's hard to do? What's confusing? What do we need to improve in our documentation about how to write documentation?
* -webkit prefixed properties and values need to be updated for Firefox 49

==Blockers==
Is there anything keeping you from making progress?

==What are you working on?==
Please share recent accomplishments, and goals you have for the next few weeks.

* (wbamberg) Has been furiously documenting WebExtensions, since they'll be a big deal for Firefox 48. He's now on PTO, so chrismills and sheppy and others will try to finish it up.
* (sheppy) Finished the reference pages for the core of RTCPeerConnection and for RTCDataChannel.
* (sheppy) Finishing up Firefox 49 reference updates, then moving on to help with WebExtensions docs for Firefox 49.
* (sheppy) Also working gradually on a first draft of a standardized API overview page per past discussions.
* (teoli, fscholz) Working on building out our new and vastly improved HTTP documentation!

==Actions==
===Previous===

===New/Continuing===

== Miscellaneous ==
Anything else we need to discuss synchronously?
* Who will moderate the next meeting?

MDN/Archives/Meetings/Community//2016/07-27

2016-07-27T17:04:44Z

Sheppy: /* What are you working on? */ WebExtensions

=Agenda/Notes=

The MDN community meeting takes place in the [irc://irc.mozilla.org/mdn #mdn] channel on irc.mozilla.org at:
* 10 AM PDT (17:00 UTC). [http://arewemeetingyet.com/Los%20Angeles/2016-07-27/10:00/b/MDN%20Community%20meeting See the meeting time in your time zone.]

==Introductions==
Since lots of people lurk in #mdn, if you're actively attending the meeting please speak up and introduce yourself.

* Attending: sheppy

==Help wanted==
Please share documentation bugs that need work, or other things where you need short-term help.
* As always, you can find bugs you can help out with on our [http://www.joshmatthews.net/bugsahoy/?mdn=1 Bugs Ahoy] page.
* Tasks that the MDN staff team is working on are listed on the current [https://tree.taiga.io/project/viya-mdn-durable-team/taskboard/q3-sprint-2-1 Taiga task board].

* -webkit prefixed properties and values need to be updated for Firefox 49

==Blockers==
Is there anything keeping you from making progress?

==What are you working on?==
Please share recent accomplishments, and goals you have for the next few weeks.

* (wbamberg) Has been furiously documenting WebExtensions, since they'll be a big deal for Firefox 48. He's now on PTO, so chrismills and sheppy and others will try to finish it up.
* (sheppy) Finished the reference pages for the core of RTCPeerConnection and for RTCDataChannel.
* (sheppy) Finishing up Firefox 49 reference updates, then moving on to help with WebExtensions docs for Firefox 49.
* (sheppy) Also working gradually on a first draft of a standardized API overview page per past discussions.
* (teoli, fscholz) Working on building out our new and vastly improved HTTP documentation!

==Actions==
===Previous===

===New/Continuing===

== Miscellaneous ==
Anything else we need to discuss synchronously?
* Who will moderate the next meeting?

MDN/Archives/Meetings/Community//2016/07-27

2016-07-27T17:03:25Z

Sheppy: /* What are you working on? */ HTTP

=Agenda/Notes=

The MDN community meeting takes place in the [irc://irc.mozilla.org/mdn #mdn] channel on irc.mozilla.org at:
* 10 AM PDT (17:00 UTC). [http://arewemeetingyet.com/Los%20Angeles/2016-07-27/10:00/b/MDN%20Community%20meeting See the meeting time in your time zone.]

==Introductions==
Since lots of people lurk in #mdn, if you're actively attending the meeting please speak up and introduce yourself.

* Attending: sheppy

==Help wanted==
Please share documentation bugs that need work, or other things where you need short-term help.
* As always, you can find bugs you can help out with on our [http://www.joshmatthews.net/bugsahoy/?mdn=1 Bugs Ahoy] page.
* Tasks that the MDN staff team is working on are listed on the current [https://tree.taiga.io/project/viya-mdn-durable-team/taskboard/q3-sprint-2-1 Taiga task board].

* -webkit prefixed properties and values need to be updated for Firefox 49

==Blockers==
Is there anything keeping you from making progress?

==What are you working on?==
Please share recent accomplishments, and goals you have for the next few weeks.

* (sheppy) Finished the reference pages for the core of RTCPeerConnection and for RTCDataChannel.
* (sheppy) Finishing up Firefox 49 reference updates, then moving on to help with WebExtensions docs for Firefox 49.
* (sheppy) Also working gradually on a first draft of a standardized API overview page per past discussions.
* (teoli, fscholz) Working on building out our new and vastly improved HTTP documentation!

==Actions==
===Previous===

===New/Continuing===

== Miscellaneous ==
Anything else we need to discuss synchronously?
* Who will moderate the next meeting?

MDN/Archives/Meetings/Community//2016/07-27

2016-07-27T16:57:29Z

Sheppy: sheppy's stuff

Engagement/MDN Durable Team/Processes

2016-07-08T19:25:24Z

Sheppy: Finished tweaks and updates

=MDN Durable Team Processes=

This page documents the processes used by the [[Engagement/MDN_Durable_Team|MDN Durable Team]] to help stakeholders, including volunteer contributors, to understand them. Many terms used here are linked to their definition in the team's [[Engagement/MDN_Durable_Team/Agile_glossary|agile glossary]].

==Proposing Work==
Anyone may propose [[Engagement/MDN_Durable_Team/Agile_glossary#User_Story|User Stories]] or [[Engagement/MDN_Durable_Team/Agile_glossary#Epic|Epics]] which describe work that may be done by the team.

* Team members can create User Stories in the [[Engagement/MDN_Durable_Team/Agile_glossary#Backlog|Backlog]] in [https://tree.taiga.io/project/viya-mdn-durable-team/backlog Taiga], and [https://tree.taiga.io/project/viya-mdn-durable-team/wiki/writing-an-epic Epics as Taiga issues].
* Other stakeholders can contact the [[Engagement/MDN_Durable_Team/Agile_glossary#Product_Owner|Product Owner]] ([https://mozillians.org/en-US/u/Topal/ Kadir Topal]) to propose User Stories and Epics.

'''Tools'''

* [https://tree.taiga.io/project/viya-mdn-durable-team/backlog Taiga backlog]
* [https://tree.taiga.io/project/viya-mdn-durable-team/issues?page=1&types=404887 List of Epics]

===Connecting Epics and User Stories===
An Epic is a task or project which is too large in scope to be completed in a single sprint (currently 12 business days), so it must be broken down into multiple User Stories. Taiga does not explicitly support Epics, so the MDN team represents them as a type of "issue". Epic issues are linked to their user stories, and the user stories are tagged with the issue ID of their epic (for example, "epic 211"). For the mechanics of doing this in Taiga, see [https://tree.taiga.io/project/viya-mdn-durable-team/wiki/connecting-epics-and-user-stories Connecting Epics and User Stories] in the Taiga wiki.

==Prioritizing Work==
The product owner and other team members collaborate to prioritize proposed User Stories and Epics, and place them in the [https://docs.google.com/spreadsheets/d/1TTMsjNUKWg5H7EZh6U7DWhC_ZYzb6jwn4---JDnJyGI/edit?usp=sharing MDN Roadmap], based on when (if ever) they are expected to be worked on. Prioritization is done once per quarter. Priorities are driven by several factors, including:

* Mozilla software development timelines and releases
* Web standardization milestones
* Marketing initiatives
* IT infrastructure requirements and deadlines

Entries in the roadmap are linked to items in the Taiga backlog, which is the canonical repository of User Stories and Epics.

'''Tools'''

* [https://tree.taiga.io/project/viya-mdn-durable-team/backlog Taiga backlog]
* [https://docs.google.com/spreadsheets/d/1TTMsjNUKWg5H7EZh6U7DWhC_ZYzb6jwn4---JDnJyGI/edit?usp=sharing MDN Roadmap]

===Triaging Requests===
In addition to Epics and User Stories driven by organizational priorities as described above, requests for work to be done by the MDN durable team also arrive in the form of [https://bugzilla.mozilla.org/ Bugzilla] "bugs", in several forms:

* [https://mzl.la/DocRequests Requests for documentation changes] (product="Developer Documentation")
* [https://mzl.la/DDN Mozilla product issues with the "dev-doc-needed" keyword set]
* [https://mzl.la/MDNBugs Requests for changes to the MDN platform] (product="Mozilla Developer Network")

The process for triaging the first two types of requests is [https://developer.mozilla.org/en-US/docs/MDN/Contribute/Processes/Documentation_bugs documented on MDN].

Bugs with "dev-doc-needed" are grouped based on the Firefox version in which the relevant code will be released. A User Story is created to address these "dev-doc-needed bugs" (often shortened to "DDN bugs" or even "DDNs") for each Firefox version, and is scheduled in a Sprint in order to be ready for the release date of Firefox Developer Edition with that version.

The third category of requests is triaged in a weekly "Bug Swat" meeting. See [https://public.etherpad-mozilla.org/p/mdn-bug-triage MDN Bug Triage Guidelines] for details. See the [[MDN/Meetings]] page for details about triage meetings, and the [https://calendar.google.com/calendar/embed?src=mozilla.com_2d35383434313235392d323530@resource.calendar.google.com&ctz=GMT&pli=1 Public MDN Events calendar] for their schedule.

The outcome of triaging MDN platform issues is usually either "right now" or "someday". Emergency work ("right now") may be started immediately, and tracked as "other" tasks not contributing to a user story. Bugs in current work may be added as new tasks to existing user stories. Other work will be deferred, either as user stories in future sprints or deferred indefinitely. Leaving a bug open is rarely a commitment to fix the bug.

'''Tools'''
* [https://docs.google.com/spreadsheets/d/1YVuD7bQBUMw7hAPafCxR7QmpD3ZmUQ2vaon7d6v2tww/edit?pli=1#gid=1969422041 DocTracker spreadsheet]
* [http://mzl.la/1ACJg7w MDN|MDN platform bugs triage query]

==Planning Sprints==
Selection of User Stories to be worked on during a [[Engagement/MDN_Durable_Team/Agile_glossary#Sprint|Sprint]] happens in the week before the start of a new Sprint. Durable team members in the content and development areas work separately to select and flesh out the User Stories in each area, and place them in the [[Engagement/MDN_Durable_Team/Agile_glossary#Task_Board|Task Board]] for that sprint. The groups also review the [[Engagement/MDN_Durable_Team/Agile_glossary#Task_|Tasks]] for each User Story, to ensure that they can be done in one Sprint, and are complete enough to ensure that the [[Engagement/MDN_Durable_Team/Agile_glossary#Acceptance_Criteria|Acceptance Criteria]] will be met. The whole team convenes for a [[Engagement/MDN_Durable_Team/Agile_glossary#Sprint_Planning_Meeting|Sprint Planning Meeting]] (usually on Thursday), to review and refine all the selected stories for the sprint. The team's committed User Stories will be shared with the broader Marketing team.

'''Tools'''

* [https://tree.taiga.io/project/viya-mdn-durable-team/backlog Taiga backlog]
* [https://docs.google.com/spreadsheets/d/1TTMsjNUKWg5H7EZh6U7DWhC_ZYzb6jwn4---JDnJyGI/edit?usp=sharing MDN Roadmap]
* Task board for the Sprint; each one has a unique URL within Taiga.[[#taskboard|*]]
* [https://tree.taiga.io/project/viya-mdn-durable-team/kanban Kanban board] in Taiga

===User Story Lifecycle===
In addition to the Backlog, the MDN team uses the [https://tree.taiga.io/project/viya-mdn-durable-team/kanban Kanban board in Taiga] to track the status of User Stories in the planning process. The team represents the lifecycle of user stories with the following columns:

; Draft
: The user story is proposed, but incomplete.
; New
: The author has added Acceptance Criteria and Tasks; it is ready for review by the team.
; Ready
: The team accepts the user story as complete; it is ready to be prioritized and pushed into a sprint by the Product Owner.
; In Progress
: The user story has been committed for a Sprint, and at least one task is the In Progress task state.
; Ready for Test
: All tasks have been completed; it is ready for review of the Acceptance Criteria and [[Engagement/MDN_Durable_Team/Agile_glossary#Definition_of_Done|Definition of Done]].
; Done
: The Acceptance Criteria and Definition of Done have been met.
; Archived
: User stories that have been abandoned in Ready or In Progress with a comment explaining why they were abandoned (?? and those that were Done in a previous quarter ??).
* User stories that are abandoned in the Draft or New states are deleted from Taiga.

==Managing Work==
The ideal progression of a Sprint is that team members claim tasks, work on each of them until they are all done, and as a result, all the Acceptance Criteria of all the User Stories selected for the sprint are satisfied. Of course, life in the real world never runs perfectly, and the processes of a Sprint are designed to accommodate the bumps, blockages, and shifts that naturally happen. User Stories may sometimes move back to earlier stages if something unexpected happens, for example.

'''Tools'''
* Task board for the Sprint; each one has a unique URL within Taiga.[[#taskboard|*]]

===Task Workflow===
Tasks in a Task Board can be in one of the following states, typically in order (left to right in the columns of the board):

; New
: Planned, not being worked on at the moment
; In Progress
: Currently being worked on
; Ready for Test
: Completed, needs test or review
; Closed
: Completed and tested or reviewed
; Needs Info
: ?? Purpose is not clear

The following practices govern the handling of tasks:

* Each task that is not New should have an assigned owner.
* Each team member should minimize the number of tasks they have in In Progress at any given time, preferably to one task (but not zero unless on PTO).
* If a progress on a task is blocked by a dependency external to the team, set it as "Blocked", with an explanation; mention the blocker in the next Standup meeting.
* If a team member suspends work on a task without being blocked, move it back to the New state; make sure that comments on the task reflect the state of work completed so far, so that it can be picked up by someone else if needed.
* When a task moves into the Ready for Test state, find a specific other person to test or review the work; if needed, ask for a volunteer during the next Standup meeting. ''Asking "anyone" to do it means no one will do it.''
* When a work product requires review by someone outside the team, create a separate task for managing the review, to avoid having completion of the main task be blocked by external factors.
* Use the "Unassigned tasks" swimlane for tasks that are not part of a User Story, but are necessary during the sprint and take up significant time of a team member.

===Tracking progress===
During the 12 work days of a Sprint, team members meet in a daily [[Engagement/MDN_Durable_Team/Agile_glossary#Standup|Standup]] meeting. For the MDN team, the discussion is driven by the order of tasks on the Task Board in the In Progress or Ready for Test columns (vs. "around the room" order).

In addition, the MDN team holds a [[Engagement/MDN_Durable_Team/Agile_glossary#Mid-sprint_check-in|Mid-sprint check-in]] on the second Tuesday of the sprint.

==Sharing Outcomes==
The Marketing-wide [[Engagement/MDN_Durable_Team/Agile_glossary#Sprint_Review|Sprint Review]] is typically held on the Wednesday of the third week of a Sprint cycle. In preparation, the MDN team holds a demo planning meeting on the third Monday, to review the accomplishments expected by the end of the Sprint, and agree on what the team will present in the Sprint Review. Team members add demo items or accomplishments into a template shared by the Scrum Master, which then becomes the demo packet that the team presents.

While the Product Owner leads the demo for the MDN team, teams members are welcome and encouraged to participate in the demo (while staying within the team's allotted 10 minutes).

'''Tools'''
* Google Slides

==Improving Processes==
At the conclusion of a Sprint, the team holds a [[Engagement/MDN_Durable_Team/Agile_glossary#Retrospective|Retrospective]] to reflect on the team's processes and habits, in order to find ways to improve or strengthen them. This meeting is limited to core team members, to facilitate frank discussion.

Marketing Durable Teams hold their Retrospectives on the third Wednesday of the sprint cycle, in most cases following the Sprint Review meeting. The MDN team holds theirs on that Wednesday, but ''prior'' to the Sprint Review, to accommodate the schedules of team members in Europe.

If the team decides to change processes that are documented in this article, then this article will be updated to reflect the change.

'''Tools'''
* Google Docs
* This wiki page

==Communicating About Processes With Community And Other Stakeholders==
The plans, activities, and outcomes of the MDN team's processes are of interest to a variety of stakeholders, most especially members of MDN's volunteer community.

The following practices will ensure that information is available to stakeholders as they need it, and is delivered to them at appropriate times.

* The MDN Taiga project is set as a "public project".
* The MDN roadmap and other related planning and outcome documents are publicly visible, by being linked from the [[Engagement/MDN_Durable_Team|MDN Durable Team's wiki page]], and set with access "anyone with the link can view".
* The User Stories planned for each Sprint are announced on the [mailto://mdn@lists.mozilla.org MDN stakeholder mailing list], once they have been decided upon. Volunteers are encouraged to share their plans for MDN-related work as part of the thread.
* The work accomplished during a Sprint is shared on the [mailto://mdn@lists.mozilla.org MDN stakeholder mailing list], along with a link to the MDN team's "demo package" (note that the Marketing-wide Sprint Demo meeting is not public, because some durable teams may share confidential information).
* MDN Durable Team meetings (except Retrospectives) are public, and are marked in the [https://www.google.com/calendar/embed?src=mozilla.com_2d35383434313235392d323530%40resource.calendar.google.com Public MDN Events calendar], along with video conference connection information for video meetings.
* Team members are encouraged to seek help from volunteers for day-to-day tasks and reviews of work, by posting on the [mailto://dev-mdc@lists.mozilla.org dev-mdc mailing list] for content-related work, or the [mailto://dev-mdn@lists.mozilla.org dev-mdn mailing list] for web development work, and by discussing their work in [[MDN/Meetings/Community|MDN Community Meetings]].

<div id="taskboard" style="font-size: smaller">* To find the task board for a specific Sprint, view the [https://tree.taiga.io/project/viya-mdn-durable-team/backlog backlog], and look in the right sidebar for the name and dates of the Sprint you want; click the '''Sprint Taskboard''' button under the section for that Sprint. Or, on the MDN Durable Team's wiki page, look for the Taskboard link corresponding to the Sprint you want, in the [[Engagement/MDN_Durable_Team#Sprint_Schedule|Sprint Schedule]] table.</div>

Engagement/MDN Durable Team/Processes

2016-07-08T18:46:33Z

Sheppy: A couple of tweaks, nothing major - just starting to look things over

=MDN Durable Team Processes=

This page documents the processes used by the [[Engagement/MDN_Durable_Team|MDN Durable Team]] to help stakeholders, including volunteer contributors, to understand them. Many terms used here are linked to their definition in the team's [[Engagement/MDN_Durable_Team/Agile_glossary|agile glossary]].

==Proposing Work==
Anyone may propose [[Engagement/MDN_Durable_Team/Agile_glossary#User_Story|User Stories]] or [[Engagement/MDN_Durable_Team/Agile_glossary#Epic|Epics]] which describe work that may be done by the team.

* Team members can create User Stories in the [[Engagement/MDN_Durable_Team/Agile_glossary#Backlog|Backlog]] in [https://tree.taiga.io/project/viya-mdn-durable-team/backlog Taiga], and [https://tree.taiga.io/project/viya-mdn-durable-team/wiki/writing-an-epic Epics as issues].
* Other stakeholders can contact the [[Engagement/MDN_Durable_Team/Agile_glossary#Product_Owner|Product Owner]] ([https://mozillians.org/en-US/u/Topal/ Kadir Topal]) to propose User Stories and Epics.

'''Tools'''

* [https://tree.taiga.io/project/viya-mdn-durable-team/backlog Taiga backlog]
* [https://tree.taiga.io/project/viya-mdn-durable-team/issues?page=1&types=404887 List of Epics]

===Connecting Epics and User Stories===
Since an Epic is larger in scope than can be completed in a single Sprint, it must be decomposed into multiple User Stories. Taiga does not explicitly support Epics, so the MDN team represents them as a type of "issue". Epic issues are linked to their user stories, and the user stories are tagged with the issue ID of their epic (for example, "epic 211"). For the mechanics of doing this in Taiga, see [https://tree.taiga.io/project/viya-mdn-durable-team/wiki/connecting-epics-and-user-stories Connecting Epics and User Stories] in the Taiga wiki.

==Prioritizing Work==
The product owner and other team members collaborate to prioritize proposed User Stories and Epics, and place them in the [https://docs.google.com/spreadsheets/d/1TTMsjNUKWg5H7EZh6U7DWhC_ZYzb6jwn4---JDnJyGI/edit?usp=sharing MDN Roadmap], based on when (if ever) they are expected to be worked on. Prioritization is done once per quarter. Priorities are driven by several factors, including:

* Marketing initiatives
* Mozilla software development timelines and releases
* Web standardization milestones
* IT infrastructure requirements and deadlines

Entries in the roadmap are linked to items in the backlog in Taiga, which is the canonical repository of User Stories and Epics.

'''Tools'''

* [https://tree.taiga.io/project/viya-mdn-durable-team/backlog Taiga backlog]
* [https://docs.google.com/spreadsheets/d/1TTMsjNUKWg5H7EZh6U7DWhC_ZYzb6jwn4---JDnJyGI/edit?usp=sharing MDN Roadmap]

===Triaging Requests===
In addition to Epics and User Stories driven by corporate priorities, requests for work to be done by the MDN durable team also arrive in the form of Bugzilla "bugs", in several forms:

* Requests for documentation changes (product="Developer Documentation")
* Mozilla product issues with the "dev-doc-needed" flag set
* Requests for changes to the MDN platform (product="Mozilla Developer Network")

The process for triaging the first two types of requests is [https://developer.mozilla.org/en-US/docs/MDN/Contribute/Processes/Documentation_bugs documented on MDN].

Bugs with "dev-doc-needed" are grouped based on the Firefox version in which the relevant code will be released. A User Story is created to address the "dev-doc-needed" bugs for each Firefox version, and is scheduled in a Sprint in order to be ready for the release date of Firefox Developer Edition with that version.

The third category of requests are triaged in a weekly "Bug Swat" meeting. See [https://public.etherpad-mozilla.org/p/mdn-bug-triage MDN Bug Triage Guidelines] for details. See the [[MDN/Meetings]] page for details about triage meetings, and the [https://calendar.google.com/calendar/embed?src=mozilla.com_2d35383434313235392d323530@resource.calendar.google.com&ctz=GMT&pli=1 Public MDN Events calendar] for their schedule.

The outcome of triaging MDN platform issues is usually either "right now" or "someday". Emergency work ("right now") may be started immediately, and tracked as "other" tasks not contributing to a user story. Bugs in current work may be added as new tasks to existing user stories. Other work will be deferred, either as user stories in future sprints or deferred indefinitely. Leaving a bug open is rarely a commitment to fix the bug.

'''Tools'''
* [https://docs.google.com/spreadsheets/d/1YVuD7bQBUMw7hAPafCxR7QmpD3ZmUQ2vaon7d6v2tww/edit?pli=1#gid=1969422041 DocTracker spreadsheet]
* [http://mzl.la/1ACJg7w MDN|Bugzilla triage query]

==Planning Sprints==
Selection of User Stories to be worked on during a [[Engagement/MDN_Durable_Team/Agile_glossary#Sprint|Sprint]] happens in the week before the start of a new Sprint. Team members in the content and development areas work separately to select and flesh out the User Stories in each area, and place them in the [[Engagement/MDN_Durable_Team/Agile_glossary#Task_Board|Task Board]] for that sprint. The groups also review the [[Engagement/MDN_Durable_Team/Agile_glossary#Task_|Tasks]] for each User Story, to ensure that they can be done in one Sprint, and are complete enough to ensure that the [[Engagement/MDN_Durable_Team/Agile_glossary#Acceptance_Criteria|Acceptance Criteria]] will be met. The whole team convenes for a [[Engagement/MDN_Durable_Team/Agile_glossary#Sprint_Planning_Meeting|Sprint Planning Meeting]] (usually on Thursday), to review and refine all the selected stories for the sprint. The team's committed User Stories will be shared with the broader Marketing team.

'''Tools'''

* [https://tree.taiga.io/project/viya-mdn-durable-team/backlog Taiga backlog]
* [https://docs.google.com/spreadsheets/d/1TTMsjNUKWg5H7EZh6U7DWhC_ZYzb6jwn4---JDnJyGI/edit?usp=sharing MDN Roadmap]
* Task board for the Sprint; each one has a unique URL within Taiga.[[#taskboard|*]]
* [https://tree.taiga.io/project/viya-mdn-durable-team/kanban Kanban board] in Taiga

===User Story Lifecycle===
In addition to the Backlog, the MDN team uses the [https://tree.taiga.io/project/viya-mdn-durable-team/kanban Kanban board in Taiga] to track the status of User Stories in the planning process. The team represents the lifecycle of user stories with the following columns:

; Draft
: The user story is proposed, but incomplete.
; New
: The author has added Acceptance Criteria and Tasks; it is ready for review by the team.
; Ready
: The team accepts the user story as complete; it is ready to be prioritized and pushed into a sprint by the Product Owner.
; In Progress
: The user story has been committed for a Sprint, and at least one task is the In Progress task state.
; Ready for Test
: All tasks have been completed; it is ready for review of the Acceptance Criteria and [[Engagement/MDN_Durable_Team/Agile_glossary#Definition_of_Done|Definition of Done]].
; Done
: The Acceptance Criteria and Definition of Done have been met.
; Archived
: User stories that have been abandoned in Ready or In Progress with a comment explaining why they were abandoned (?? and those that were Done in a previous quarter ??).
* User stories that are abandoned in the Draft or New states are deleted from Taiga.

==Managing Work==
The ideal progression of a Sprint is that team members claim tasks, work on each of them until they are all done, and as a result, all the Acceptance Criteria of all the User Stories selected for the sprint are satisfied. Of course, life in the real world never runs perfectly, and the processes of a Sprint are designed accommodate the bumps, blockages, and shifts that naturally happen.

'''Tools'''
* Task board for the Sprint; each one has a unique URL within Taiga.[[#taskboard|*]]

===Task Workflow===
Tasks in a Task Board can be in one of the following states, typically in order (left to right in the columns of the board):

; New
: Planned, not being worked on at the moment
; In Progress
: Currently being worked on
; Ready for Test
: Completed, needs test or review
; Closed
: Completed and tested or reviewed
; Needs Info
: ?? Purpose is not clear

The following practices govern the handling of tasks:

* Each task that is not New should have an assigned owner.
* Each team member should minimize the number of tasks they have in In Progress at any given time, preferably to one task (but not zero unless on PTO).
* If a progress on a task is blocked by a dependency external to the team, set it as "Blocked", with an explanation; mention the blocker in the next Standup meeting.
* If a team member suspends work on a task without being blocked, move it back to the New state; make sure that comments on the task reflect the state of work completed so far, so that it can be picked up by someone else if needed.
* When a task moves into the Ready for Test state, find a specific other person to test or review the work; if needed, ask for a volunteer during the next Standup meeting. Asking "anyone" to do it means no one will do it.
* When a work product requires review by someone outside the team, create a separate task for managing the review, to avoid having completion of the main task be blocked by external factors.
* Use the "Unassigned tasks" swimlane for tasks that are not part of a User Story, but are necessary during the sprint and take up significant time of a team member.

===Tracking progress===
During the 12 work days of a Sprint, team members meet in a daily [[Engagement/MDN_Durable_Team/Agile_glossary#Standup|Standup]] meeting. For the MDN team, the discussion is driven by the order of tasks on the Task Board in the In Progress or Ready for Test columns (vs. "around the room" order).

In addition, the MDN team holds a [[Engagement/MDN_Durable_Team/Agile_glossary#Mid-sprint_check-in|Mid-sprint check-in]] on the second Tuesday of the sprint.

==Sharing Outcomes==
The Marketing-wide [[Engagement/MDN_Durable_Team/Agile_glossary#Sprint_Review|Sprint Review]] is typically held on the Wednesday of the third week of a Sprint cycle. In preparation, the MDN team holds a demo planning meeting on the third Monday, to review the accomplishments expected by the end of the Sprint, and agree on what the team will present in the Sprint Review. Team members add demo items or accomplishments into a template shared by the Scrum Master, which then becomes the demo packet that the team presents.

While the Product Owner leads the demo for the MDN team, teams members are welcome and encouraged to participate in the demo (while staying within the team's allotted 10 minutes).

'''Tools'''
* Google Slides

==Improving Processes==
At the conclusion of a Sprint, the team holds a [[Engagement/MDN_Durable_Team/Agile_glossary#Retrospective|Retrospective]] to reflect on the team's processes and habits, in order to find ways to improve or strengthen them. This meeting is restricted to core team members, to facilitate frank discussion.

Marketing Durable Teams hold their Retrospectives on the third Wednesday of the sprint cycle, in most cases following the Sprint Review meeting. The MDN team holds theirs on that Wednesday, but ''prior'' to the Sprint Review, to accommodate the schedules of team members in Europe.

If the team decides to change processes that are documented in this article, then this article will be updated to reflect the change.

'''Tools'''
* Google Docs
* This wiki page

==Communicating about these processes with community and other stakeholders==
The plans, activities, and outcomes of the MDN team's processes are of interest to a variety of stakeholders, most especially members of MDN's volunteer community.

The following practices will ensure that information is available to stakeholders as they need it, and is delivered to them at appropriate times.

* The MDN Taiga project is set as a "public project".
* The MDN roadmap and other related planning and outcome documents are publicly visible, by being linked from the [[Engagement/MDN_Durable_Team|MDN Durable Team's wiki page]], and set with access "anyone with the link can view".
* The User Stories planned for each Sprint are announced on the [mailto://mdn@lists.mozilla.org MDN] stakeholder mailing list, once they have been decided. Volunteers are encouraged to share their plans for MDN-related work as part of the thread.
* The work accomplished during a Sprint is shared on the [mailto://mdn@lists.mozilla.org MDN] stakeholder mailing list, along with a link to the MDN team's "demo package". (Note that the Marketing-wide Sprint Demo meeting is not public, because some durable teams may share confidential information.)
* MDN Durable Team meetings (except Retrospectives) are public, and are marked in the [https://www.google.com/calendar/embed?src=mozilla.com_2d35383434313235392d323530%40resource.calendar.google.com Public MDN Events calendar], along with video conference connection information for video meetings.
* Team members are encouraged to seek help from volunteers for day-to-day tasks and reviews of work, by posting on the [mailto://dev-mdc@lists.mozilla.org dev-mdc] mailing list for content-related work, or the [mailto://dev-mdn@lists.mozilla.org dev-mdn] mailing list for web development work, and by discussing their work in [[MDN/Meetings/Community|MDN Community Meetings]].

<div id="taskboard" style="font-size: smaller">* To find the task board for a specific Sprint, view the [https://tree.taiga.io/project/viya-mdn-durable-team/backlog backlog], and look in the right sidebar for the name and dates of the Sprint you want; click the '''Sprint Taskboard''' button under the section for that Sprint. Or, on the MDN Durable Team's wiki page, look for the Taskboard link corresponding to the Sprint you want, in the [[Engagement/MDN_Durable_Team#Sprint_Schedule|Sprint Schedule]] table.</div>

MDN/Archives/Meetings/Community/2016/06-29

2016-06-29T17:04:02Z

Sheppy: /* Introductions */ attending

=Agenda/Notes=

The MDN community meeting takes place in the [irc://irc.mozilla.org/mdn #mdn] channel on irc.mozilla.org at 10 AM PDT (18:00 UTC). [http://arewemeetingyet.com/Los%20Angeles/2014-11-19/10:00/b/MDN%20Community%20meeting See the meeting time in your time zone.]

==Introductions==
Since lots of people lurk in #mdn, if you're actively attending the meeting please speak up and introduce yourself.

* Attending: sheppy, jswisher

==Help wanted==
Please share documentation bugs that need work, or other things where you need short-term help.
* As always, you can find bugs you can help out with on our [http://www.joshmatthews.net/bugsahoy/?mdn=1 Bugs Ahoy] page.
* If you have ideas for things that should be tweeted out by @MozDevNet, please suggest it using our [https://docs.google.com/a/mozilla.com/forms/d/1cwNp_iA0cjNY8C9g-ff9rpf3fVg6OF_pKSFjxse0WPc/viewform handy form]!

===Learning area (chris)===

I am still writing lots of material for the MDN learning area, but would still love some help reviewing or writing material. You can see what kind of work is up for grabs at our [https://trello.com/b/LDggrYSV/learning-area-glossary Learning Area Trello Board]. Get in touch with me if you want to help (chrismills on IRC.)

==Blockers==
Is there anything keeping you from making progress?

==What are you working on?==
Please share recent accomplishments, and goals you have for the next few weeks.

* Sheppy
** [https://developer.mozilla.org/en-US/docs/Web/API/RTCDataChannel RTCDataChannel] reference is essentially finished; I plan to clean up the main page later today, then send it to the dev team for review.
** [https://developer.mozilla.org/en-US/docs/Web/API/RTCPeerConnection RTCPeerConnection] reference main page needs to be tidied up then sent for review as well.
** Finished documenting [https://developer.mozilla.org/en-US/docs/Web/API/HTMLLabelElement HTMLLabelElement] interface today, including its members.
* Janet
** Documenting the MDN team's new agile processes. First email to dev-mdc about it coming shortly.

==Actions==
===Previous===

===New/Continuing===
* Spam project work is ongoing, with features being added to make it easier to handle it when it happens, and with a dashboard being built to track statistics around spam.

== Miscellaneous ==
Anything else we need to discuss synchronously?
* Who will moderate the next meeting?

MDN/Archives/Meetings/Community/2016/06-29

2016-06-29T17:00:23Z

Sheppy: /* New/Continuing */ spam status

=Agenda/Notes=

The MDN community meeting takes place in the [irc://irc.mozilla.org/mdn #mdn] channel on irc.mozilla.org at 10 AM PDT (18:00 UTC). [http://arewemeetingyet.com/Los%20Angeles/2014-11-19/10:00/b/MDN%20Community%20meeting See the meeting time in your time zone.]

==Introductions==
Since lots of people lurk in #mdn, if you're actively attending the meeting please speak up and introduce yourself.

* Attending: sheppy

==Help wanted==
Please share documentation bugs that need work, or other things where you need short-term help.
* As always, you can find bugs you can help out with on our [http://www.joshmatthews.net/bugsahoy/?mdn=1 Bugs Ahoy] page.
* If you have ideas for things that should be tweeted out by @MozDevNet, please suggest it using our [https://docs.google.com/a/mozilla.com/forms/d/1cwNp_iA0cjNY8C9g-ff9rpf3fVg6OF_pKSFjxse0WPc/viewform handy form]!

===Learning area (chris)===

I am still writing lots of material for the MDN learning area, but would still love some help reviewing or writing material. You can see what kind of work is up for grabs at our [https://trello.com/b/LDggrYSV/learning-area-glossary Learning Area Trello Board]. Get in touch with me if you want to help (chrismills on IRC.)

==Blockers==
Is there anything keeping you from making progress?

==What are you working on?==
Please share recent accomplishments, and goals you have for the next few weeks.

* Sheppy
** [https://developer.mozilla.org/en-US/docs/Web/API/RTCDataChannel RTCDataChannel] reference is essentially finished; I plan to clean up the main page later today, then send it to the dev team for review.
** [https://developer.mozilla.org/en-US/docs/Web/API/RTCPeerConnection RTCPeerConnection] reference main page needs to be tidied up then sent for review as well.
** Finished documenting [https://developer.mozilla.org/en-US/docs/Web/API/HTMLLabelElement HTMLLabelElement] interface today, including its members.

==Actions==
===Previous===

===New/Continuing===
* Spam project work is ongoing, with features being added to make it easier to handle it when it happens, and with a dashboard being built to track statistics around spam.

== Miscellaneous ==
Anything else we need to discuss synchronously?
* Who will moderate the next meeting?

MDN/Archives/Meetings/Community/2016/06-29

2016-06-29T16:53:47Z

Sheppy: add sheppy status

=Agenda/Notes=

The MDN community meeting takes place in the [irc://irc.mozilla.org/mdn #mdn] channel on irc.mozilla.org at 10 AM PDT (18:00 UTC). [http://arewemeetingyet.com/Los%20Angeles/2014-11-19/10:00/b/MDN%20Community%20meeting See the meeting time in your time zone.]

==Introductions==
Since lots of people lurk in #mdn, if you're actively attending the meeting please speak up and introduce yourself.

* Attending: sheppy

==Help wanted==
Please share documentation bugs that need work, or other things where you need short-term help.
* As always, you can find bugs you can help out with on our [http://www.joshmatthews.net/bugsahoy/?mdn=1 Bugs Ahoy] page.
* If you have ideas for things that should be tweeted out by @MozDevNet, please suggest it using our [https://docs.google.com/a/mozilla.com/forms/d/1cwNp_iA0cjNY8C9g-ff9rpf3fVg6OF_pKSFjxse0WPc/viewform handy form]!

===Learning area (chris)===

I am still writing lots of material for the MDN learning area, but would still love some help reviewing or writing material. You can see what kind of work is up for grabs at our [https://trello.com/b/LDggrYSV/learning-area-glossary Learning Area Trello Board]. Get in touch with me if you want to help (chrismills on IRC.)

==Blockers==
Is there anything keeping you from making progress?

==What are you working on?==
Please share recent accomplishments, and goals you have for the next few weeks.

* Sheppy
** [https://developer.mozilla.org/en-US/docs/Web/API/RTCDataChannel RTCDataChannel] reference is essentially finished; I plan to clean up the main page later today, then send it to the dev team for review.
** [https://developer.mozilla.org/en-US/docs/Web/API/RTCPeerConnection RTCPeerConnection] reference main page needs to be tidied up then sent for review as well.
** Finished documenting [https://developer.mozilla.org/en-US/docs/Web/API/HTMLLabelElement HTMLLabelElement] interface today, including its members.

==Actions==
===Previous===

===New/Continuing===

== Miscellaneous ==
Anything else we need to discuss synchronously?
* Who will moderate the next meeting?

MDN/Archives/Meetings/Community/2016/06-29

2016-06-29T16:47:13Z

Sheppy: template for the page

IRC

2016-06-24T15:32:34Z

Sheppy: /* Project Channels */ Removed #camino; fixed some eerrors

How to use '''IRC''' to get connected with others in the Mozilla project is shown on this page.

Also frequently used IRC channels with descriptions of their general purpose are listed. And some instructions for the non-technical folks on how they can join an IRC chat are given.

<div style="float:right; margin-left:2.5em">__TOC__</div>
==Getting Started ==
IRC stands for "Internet Relay Chat". It's a protocol for real-time chat sessions. (Read more [http://en.wikipedia.org/wiki/Irc about IRC on Wikipedia].) It was invented before the World Wide Web, so it was adopted by early open source contributors and Web developers, and it has been used by those communities ever since. Like email, no single company controls IRC. IRC servers are offered by many individuals and organizations. Users log in to a particular server to chat with other users on that server, using a client program designed for IRC; just as there are many programs for reading email, there are many different IRC client programs. Chat discussions take place in "channels," which have names starting with a '#' symbol.

Mozilla runs an IRC server to host channels for discussion of topics related to the Mozilla project.

===Pick an IRC client===

There are several ways to participate in IRC and here are a some common options.

* [http://mibbit.com/ Mibbit]: web-based chat client.

* [https://kiwiirc.com/ Kiwi IRC] Open Source web-based chat client that works on mobile too.

* [https://addons.mozilla.org/en-US/firefox/addon/chatzilla/ Chatzilla] is an add-on for Firefox; it comes built-in with SeaMonkey. You can also install it [http://chatzilla.rdmsoft.com/xulrunner/ standalone].

* [http://konversation.kde.org/ Konversation] is a client for Linux, you can probably get it as a package from your distribution. Its look and feel is similar to that of ChatZilla while being built on [http://www.kde.org/ KDE].

* [http://colloquy.info/ Colloquy] is a Mac client with a nice looking interface. It also has a mobile client for iPad/iPhone/iTouch.

* [http://limechat.net/mac/ Limechat] is a cross-platform IRC client by Satoshi Nakagawa. Warning: main site is in Japanese, this is not just for Mac, there are [http://hp.vector.co.jp/authors/VA022249/files/lime218.exe Windows] and [http://limechat.net/iphone/ iOS] versions as well. A number of people have happily switched from Colloquy to Limechat.

* [http://www.mozilla.org/en-US/thunderbird/ Thunderbird] is a communication client made by Mozilla. As of version 15, it has IRC support.

* [http://www.instantbird.com Instantbird] is a cross-platform multi-protocol instant messaging client based on Mozilla technologies (and libpurple from Pidgin) with an emphasis on simplicity and extensibility.

* [http://www.yaaic.org/ Yaaic] is a free (as in freedom), multiserver, Android IRC client, now fully conformant with the UI style of the Iced Cream Sandwich (and later).

* [http://www.andchat.net/ AndChat] is a free (as in beer), multiserver, IRC app for the Android platform.

* [https://hexchat.github.io/ HexChat] is a great chat program for both Linux and Windows.

* [https://www.irccloud.com/ IRCCloud] is a great IRC app that is compatible with Android phones, iPhone, iPad, and iPod touch. This app is optimized for iPhone 5. Requires iOS 5.1.1 or later. It has both a free and a paid option.

See also [https://en.wikipedia.org/wiki/Comparison_of_IRC_clients Comparison of IRC clients] at Wikipedia.

===Connect to the Mozilla IRC server===

====Mibbit====
* [http://chat.mibbit.com/?server=irc.mozilla.org Click here to connect]
* enter a nickname for yourself, then click GO (no channel needed at first, but you can put one in if you know where you're going)
* look for a "Mozilla" tab right under the Mibbit logo and click on it (it doesn't come to the front automatically for some reason)
[[File:mibbit_connection.png|400px]]

====Colloquy====
Set up a connection as per the screenshot and hit 'connect':

[[File:create_connection_colloquy.png|400px]]

For those of you who have turned pictures off, the settings are:
Nickname: Your_IRC_nickname
Server Protocol: IRC
Chat Server: irc.mozilla.org
Proxy: None
Chat Server Port: 6697
Chat Server Port for users of [https://bugzilla.mozilla.org/show_bug.cgi?id=716814 mobile carriers that block IRC (e.g. Verizon)] : 8443
SSL Connection: Checked
Username: Your_IRC_nickname
Server Password: [blank]
Real Name: Lukas Blakk

====Chatzilla ====
Use the <tt>/networks</tt> command to display the list of predefined IRC networks. Click on <tt>moznet</tt> in the list.

[[File:chatzilla_networks.png|400px]]

====Andchat ====
[[File:Andchat-mozilla-irc-setup.png|240px|right]]
* Name : Mozilla
* Address : <b>irc.mozilla.org</b>
* Port
** The normal port value is <b>6697</b>
** [https://bugzilla.mozilla.org/show_bug.cgi?id=716814 Some mobile carriers (like Verizon)] block all common IRC ports. If this affects you, use port <b>8443</b> instead
* SSL : <b>checked</b>
* Nick 1 : Your_IRC_nickname
NOTE : In 2012, Verizon blocked all access to irc.mozilla.org over cellular connections. Any connection attempts now get a 504 Gateway Timeout

=== Nicknames ===
====Choosing a nickname====
Nicknames on IRC can become a major part of your identity if you spend a significant amount of time talking with people in IRC. Sometimes you may even find that people in real life call you by your IRC handle. If you're having trouble coming up with a catchy nickname or if you're concerned about getting stuck with something that seems funny now but will be tiresome to you in a few weeks, a good way to create a nickname is to take the first letter of your first and most or all of your last name to make a nick that people will recognize as you.

Often in IRC people look for others by using tab complete so if someone's name is John they might type a 'j' and then tab several times to see who's in the channel whose name starts with a 'j'.

Using just your first name can also be a good option, if it's unique. But:
# Beware that IRC "seems" case-sensitive but actually isn't: e.g. <tt>/whois mossop</tt> (all lowercase) will return info on Mossop (with initial capital) if he's online, and <tt>/nick mossop</tt> will either be refused (if Mossop is online) or make NickServ tell you that this nick is registered and that you should IDENTIFY with its password if it's yours (if he isn't). ([[#Register your nickname|See below]] about this NickServ stuff.)
# If you are new to IRC and you use a female name you will most likely at some point get private messages from people that are unwelcome. This is hopefully less frequent on the Mozilla network but this behaviour does exist anywhere that also allows anonymity so take this into consideration in choosing your nickname and make sure you are prepared to fend off jerks.

====Set your nickname====
Now that you're connected to the IRC server, you can set/register your nickname with Nickserv. If you’re going to be hanging around a lot (and we hope that you will!), you will want to register your nickname. That way, other people can’t pose as you on the channel and you can join password-protected channels. First, set your preferred nickname by either doing:

/nick NICKNAME

(where NICKNAME is the desired nickname); or if you are using a client you may have already set your nickname and/or can change it through the application's interface. Note that if someone has already registered your preferred nick, you’ll need to use a different one.

====Register your nickname====
Once you have settled on a nickname here’s how to register:

/msg nickserv register [YOUR PASSWORD] [YOUR EMAIL]

You do not need to include the square brackets. Email address is mandatory.

Congratulations! Your nickname is now registered.

Next time you log on, you will need to identify yourself to nickserv as follows (<u>after</u> you get the nickname):

/msg nickserv identify [YOUR PASSWORD]

Once you have identified yourself, you will be able to join password-protected irc channels and also, if needed, disconnect anyone using the nickname without the password. See <tt>/msg NickServ help</tt> for details.

=== Interesting umodes ===
Using the /umode command with one of the following parameters will cause the specified effect.
* +B - Marks a user as a bot for /whois reporting purposes.
* +x - Cloaking - Hide part of a user's hostname (on by default).
* +c - Blocks private messages from everyone except for people that are in at least 1 channel with you.
* +R - Blocks private messages from unregistered users.
* +d - Deaf - Stop receiving channel messages & notices. Useful if you want to silence all the channels you're in, but still be available for /msg.
* +I - Hides the list of channels you're in from other users when they /whois you.

=== Joining Channels ===

IRC channels are like 'rooms' where people talk or hang out. Their names begin with a # (octothorpe, hash, pound sign etc.). Do not confuse them with social media 'hashtags' :-)

For most irc.mozilla.org channels you can join them with the following command:

/join #channel_name

This will open a tab, window or section in your IRC client that allows you to participate in discussions on that channel.

For a password protected channel you need to include the password:

/join #channel_name [CHANNEL PASSWORD]

If doing this command does not open a new tab or otherwise allow you to enter the channel for discussion, please check the steps above about registering your nick and make sure you have identified yourself to Nickserv.

===Start a private message===
You can start a private chat with another person who is also on irc.mozilla.org by doing

/msg [other person's nickname] [initiating message, like 'hi']

This creates a new tab or channel that is just between you and that person. You must have a message to create the new tab/room otherwise the /msg command will complain that there are not enough arguments.

If you want to know if the person you're trying to chat with is in the room you can either enter the first letter of their nick and then hit tab to tab-complete all the nicks in the channel that start with this letter until you see the one you are looking for or you can use
/names
This will give you a list of all the people in the room you are currently in. To start a private chat, you must be in the room with someone. If you're not sure what room someone is in you can go to the main irc.mozilla.org tab/room and do

/whois [other person's nickname]

which will tell you (hopefully) their real name as well as list the channels they are currently in with that nick.

===Create your own channel===
To start a channel for multiple people to hang out and chat in, create a unique channel like this:
/j #my_channel_name

Now you can tell all your friends, teammates, community members where to find the backchannel you've created!

===Registering a channel===
If the channel you've created is going to be permanent, you'll want to register it with chanserv. Does 'chanserv' sound familiar? That's right - it works very much like 'nickserv' :)

# eg: /msg chanserv register #moz-in-my-town "a channel for people who work on mozilla and live in my town"
/msg chanserv REGISTER [channel name] [password (optional)] [description]

===Managing a channel===

===Channel Modes===
For a list of all channel modes supported by our IRC network, please visit [http://wiki.inspircd.org/2.0/Channel_Modes]. A list of particularly unique & interesting channel modes follows.

* +u - Auditorium mode - Hides everyone in a channel except yourself (potentially useful for #moco or #townhall).
* +e - Ban exception - Same syntax as +b, but allows you to exclude someone from a ban.
* +B - Block ALL CAPS MESSAGES.
* +c - Block color messages.
* +S - Strip color from messages.
* +g - Message filtering using simple string matches. Example: '''/mode #channel +g *candy*'''. Now, no one in #channel can use the word candy. Use multiple /mode commands to add more words. To see the list of banned words, omit the + symbol, e.g.: '''/mode #channel g'''.
* +d - Silence join/part messages until the person speaks. Useful for channels with people who, e.g., IRC from their laptop and flood channels with join/quit messages every time they close their laptop.
* +f - Flood protection - Example: '''/mode #channel +f 7:3''' - If a user types 7 or more line within 3 seconds, they will be kicked. You can also do '''/mode #channel +f *7:3''' to make them kickbanned instead of just kicked.
* +j - Join Flood Protection - Example: '''/mode #channel +j 20:5''' - If 20 or more clients join #channel within 5 seconds, the channel will be locked for 60 seconds, preventing anyone from joining.
* +C - Stops users from using /ctcp on a channel
* +Q - Prevents users from using /kick on a channel
* +N - Prevents users from changing their nick while in a channel with +N set. Can also be used as an extban to prevent a specific user from changing their nick, e.g.: '''/mode #channel +b N:lerxst!*@*''' would prevent lerxst from changing his nick to anything else.
* +T - Prevents users from using /notice on a channel. Also works as an extban (see +N for syntax)
* +b m - Mute - Extban for preventing a user from speaking in channel. e.g.: '''/mode #channel +b m:lerxst!*@*''' prevents lerxst from speaking #channel.
* +l x - Limit - Prevents users from joining a channel if the number of clients exceeds x. Example: '''/mode #channel +l 5''' prevents users from joining #channel if there are already 5 users present.
* +L - Redirect - If a channel's limit is exceeded (via +l), this forces users to join the specified channel. Example: '''/mode #channel +L #channel-overflow'''. If you want to redirect everyone attempting to join a channel, set +l to 0.
* +z - SSL only - Users can only join a channel if they're connected via SSL

===Join some channels right now!===
Being new to IRC can be intimidating. Mozilla's IRC channels are very friendly and welcoming but some of them are geared to teams trying to get things done where others are more relaxed and open to new folks giving IRC or other Mozilla tools a try.
#mozillians - meet other Mozilla project folks all over the world
#newbies - kind of self-explanatory, right?
#introduction - a place to get started and be welcoming to new contributors
#sf,#toronto - remote office's water-cooler hotspot for socializing and planning lunch

==Need General Help with IRC?==
If you're able to connect to IRC and join channels, try asking for help in [irc://irc.mozilla.org/introduction #introduction], [irc://irc.mozilla.org/mozillians #mozillians], [irc://irc.mozilla.org/newbies #newbies], [irc://irc.mozilla.org/seneca #seneca] or [irc://irc.mozilla.org/coding #coding]. The folks who hang out in those channels will be happy to help.

You can also get help from IRC by doing:
/help
This will give you a list of all the IRC commands and then you can do /help [command] to get info on that particular command.
<pre>
Example:
/help msg

IRC returns:
MSG [-<server tag>] [-channel | -nick] <targets> <message>
Sends a message to a nick or a channel.
Usually this is used for sending private messages to other persons.
Examples:

/MSG friend Hi, what's up?
</pre>
You can also visit [http://irchelp.org irchelp.org] to learn about how IRC works, or find a client you can use to connect to the chat server.

/!\ '''If you're using ChatZilla,''' note that <tt>/help</tt> is a ChatZilla command which gets you a ChatZilla answer. In ChatZilla, <tt>/commands</tt> returns the list of all known commands (including the aliases you defined yourself), and <tt>/help ''command''</tt> (without the slash before ''command'') gives you help on ''/command''. These are usually enough, but you <u>can</u> get help '''from the server''' when using ChatZilla, by using <tt>/quote help</tt> or (on the Mozilla network) <tt>/helpop</tt>

==How to ask questions on IRC==

* Join a question-friendly channel like [irc://irc.mozilla.org/introduction #introduction], [irc://irc.mozilla.org/mozillians #mozillians], [irc://irc.mozilla.org/newbies #newbies], [irc://irc.mozilla.org/seneca #seneca] or [irc://irc.mozilla.org/coding #coding].
* Ask away! You don't have to ask permission to ask first. It is better to just blurt out your question, even though you don't know if anyone is paying attention.
* Leave your IRC client open if nobody answers right away. Most of the folks on IRC do not spend all day watching their IRC client. They just leave it open while they're doing other things. It might be an hour before the right person notices your question. When answering someone's question, especially if there's a delay, the nick of the questioner should be used in the answer so that you'll see a highlighted line with their response. (eg: "lsblakk: the answer is 42")
* Be prepared to ask in several places. Very often the first response to a question is, "I don't know, but you should ask that question in #extdev" or #developers or #devtools or #jsapi or any of a hundred other special-purpose channels. Over time, you'll get a better sense of which questions to ask where, but to start with, it's always OK to ask in #introduction.
* Remember to be courteous. Don't repeat your question every time someone new enters the room. Don't individually ask everybody in the room if they know the answer. Don't type <code>helllooooooooo</code>. And if someone is rude to you, please do the rest of us a favor and respond politely anyway.

==Commonly Used Mozilla IRC Channels==

There are many different [https://wiki.mozilla.org/IRC irc channels] for various topics. If you have ChatZilla, you can just click the provided links below to join that particular channel. For other clients, connect to server irc.mozilla.org and type /join channelname, replacing channelname with the name of the channel (including the leading "#"). All channels use English unless otherwise specified.

===Development and Planning===

These channels are frequently used for discussions regarding development and planning of Firefox and Thunderbird.

====Project Channels====
* [irc://irc.mozilla.org/firefox #firefox] - Firefox project discussion and end-user help. ''Another official #firefox channel is maintained on the [irc://irc.freenode.net/firefox Freenode] network)
* [irc://irc.mozilla.org/accessibility #accessibility] - Discussion about accessibility in Mozilla applications - developers and end users welcome
* [irc://irc.mozilla.org/addons #addons] - End user support for add-ons, extensions, and themes
* [irc://irc.mozilla.org/amo-editors #amo-editors] - Support for add-on reviews and the addons.mozilla.org website
* [irc://irc.mozilla.org/balrog #balrog] - Balrog (Application Update Service) project discussion.
* [irc://irc.mozilla.org/bugzilla #bugzilla] - Bugzilla project discussion
* [irc://irc.mozilla.org/calendar #calendar] - Calendar project and Lightning. ''This addon is for Thunderbird and SeaMonkey while the freestanding Sunbird isn't actively developed.''
* [irc://irc.mozilla.org/chatzilla #chatzilla] - Discussion about ChatZilla, the IRC client extension
* [irc://irc.mozilla.org/firefoxstudents #firefoxstudents] - [[StudentAmbassadors|Student Ambassadors]] main channel
* [irc://irc.mozilla.org/instantbird #instantbird] - Instantbird project discussion
* [irc://irc.mozilla.org/extdev #extdev] - Discussion about extension development
* [irc://irc.mozilla.org/js #js] - Discussion about JavaScript programming
* [irc://irc.mozilla.org/l10n #l10n] - Discussion about localization (l10n) of Mozilla applications
* [irc://irc.mozilla.org/mdn #mdn] - Discussion about developer documentation
* [irc://irc.mozilla.org/mdndev #mdndev] - Discussion about development of the documentation web site (Kuma platform)
* [irc://irc.mozilla.org/mozillazine #mozillazine] - Community for Users, Web Authors, and Testers; go here if you need help
* [irc://irc.mozilla.org/mozdev #mozdev] - Discussion of and support for free project hosting at mozdev.org
* [irc://irc.mozilla.org/mozwebqa #mozwebqa] - Home of Mozilla's web-testing efforts
* [irc://irc.mozilla.org/nightingale #nightingale] - Nightingale project discussion
* [irc://irc.mozilla.org/qa #qa] - Mozilla QA Community of users and testers dedicated to improving the quality of Firefox and other Mozilla applications
* [irc://irc.mozilla.org/remo #remo] - [[ReMo|Mozilla Reps]] main channel
* [irc://irc.mozilla.org/remo-dev #remo-dev] - Discussion about webdev and planning of next Mozilla Reps web properties
* [irc://irc.mozilla.org/rust #rust] - General discussion about the Rust programming language
* [irc://irc.mozilla.org/rust-gamedev #rust-gamedev] - Computer graphics and game development with Rust
* [irc://irc.mozilla.org/rust-internals #rust-internals] - Rust compiler and library development
* [irc://irc.mozilla.org/rust-osdev #rust-osdev] - Operating system development with Rust
* [irc://irc.mozilla.org/seamonkey #seamonkey] - Community project to revive the bundled application suite
* [irc://irc.mozilla.org/servo #servo] - Development of a research web browser in Rust
* [irc://irc.mozilla.org/songbird #songbird] - Songbird project discussion
* [irc://irc.mozilla.org/sumo #sumo] - [[Support|Mozilla Support]] main channel
* [irc://irc.mozilla.org/sync #sync] - Discussion of [[CloudServices/Sync|Firefox Sync]], including self-hosting
* [irc://irc.mozilla.org/testpilot #testpilot] - Discussion about the [[Test Pilot]] project prototyping new features in Firefox.
* [irc://irc.mozilla.org/themedev #themedev] - Discussion about theme development
* [irc://irc.mozilla.org/thunderbird #thunderbird] - Thunderbird project discussion and end-user help
* [irc://irc.mozilla.org/tb-support-crew #tb-support-crew] - for Thunderbird support meta discussion NOT for Thunderbird support;
** ''informal'' companion IRC channel to the [[Thunderbird/tb-support-crew|tb-support-crew mailing list]]
* [irc://irc.mozilla.org/tb-qa #tb-qa] - QA Community of users and testers dedicated to improving the quality of Thunderbird
* [irc://irc.mozilla.org/transvision #transvision] - Transvision (l10n QA tool in PHP) project discussion
* [irc://irc.mozilla.org/webtools #webtools] - Bonsai, LXR, Tinderbox, and Mozbot project discussion
* [irc://irc.mozilla.org/webcompat #webcompat] - Home of Mozilla's [https://wiki.mozilla.org/Compatibility Web compatibility effort]
* [irc://irc.mozilla.org/womoz #womoz] - Women & Mozilla Discussion channel
* [irc://irc.mozilla.org/xul #xul] - Discussion about the XUL interface specification language

====General Discussion====

* [irc://irc.mozilla.org/contributors #contributors] - A offtopic channel for all contributors to chat in and discuss their projects with each other (although this channel still exists, discussion has moved to [irc://irc.mozilla.org/mozillians #mozillians])
* [irc://irc.mozilla.org/developers #developers] - general Firefox and Gecko development discussion
* [irc://irc.mozilla.org/planning #planning] - discussion of upcoming Firefox and Gecko branch and trunk releases

====Specific Areas====

* [irc://irc.mozilla.org/airmozilla #airmozilla] - discussion around https://air.mozilla.org/
* [irc://irc.mozilla.org/ateam #ateam] - Automation & Tools development discussion
* [irc://irc.mozilla.org/audio #audio] - development discussion for audio specifically
* [irc://irc.mozilla.org/webmaker #badges] - discussion and support channel for the Mozilla Open Badges project
* [irc://irc.mozilla.org/bluetooth #bluetooth] - development discussion for bluetooth specifically
* [irc://irc.mozilla.org/build #build] - The build system - make/autoconf etc
* [irc://irc.mozilla.org/content #content] - development discussion for DOM code
* [irc://irc.mozilla.org/devtools #devtools] - development discussion for Firefox Devtools
* [irc://irc.mozilla.org/e10s #e10s] - development discussion for Electrolysis
* [irc://irc.mozilla.org/fistbump #fistbump] - visual design for both products and marketing; copywriting
* [irc://irc.mozilla.org/fx-team #fx-team] - Firefox front-end development discussion and team channel
* [irc://irc.mozilla.org/fxa #fxa] - Firefox Accounts development and support channel
* [irc://irc.mozilla.org/fxos #fxos] - Firefox OS development
* [irc://irc.mozilla.org/gfx #gfx] - development discussion for graphics, widget and OS-specific code
* [irc://irc.mozilla.org/identity #identity] - Persona and BrowserID protocol discussion
* [irc://irc.mozilla.org/jsapi #jsapi] - development discussion for the JavaScript engine
* [irc://irc.mozilla.org/jsctypes #jsctypes] - discussion and support for js-ctypes development
* [irc://irc.mozilla.org/labs #labs] - discussion of development of Mozilla Labs projects
* [irc://irc.mozilla.org/layout #layout] - development discussion for layout code
* [irc://irc.mozilla.org/macdev #macdev] - OSX developers
* [irc://irc.mozilla.org/maildev #maildev] - Thunderbird development channel
* [irc://irc.mozilla.org/media #media] - development discussion for audio/video and related topics like WebRTC
* [irc://irc.mozilla.org/memshrink #memshrink] - development discussion about memory consumption
* [irc://irc.mozilla.org/mobile #mobile] - Fennec development discussion
* [irc://irc.mozilla.org/necko #necko] - development discussion for the networking code
* [irc://irc.mozilla.org/newslettercode #newslettercode] - community newsletter channel
* [irc://irc.mozilla.org/power #power] - development discussion about power consumption
* [irc://irc.mozilla.org/push #push] - Push server and DOM API development channel
* [irc://irc.mozilla.org/releng #releng] - Build & Release channel - for issues with Mozilla Build infrastructure
* [irc://irc.mozilla.org/seamonkey #seamonkey] - SeaMonkey development channel
* [irc://irc.mozilla.org/services-dev #services-dev] - Cloud Services discussion channel
* [irc://irc.mozilla.org/telemetry #telemetry] - Telemetry development channel
* [irc://irc.mozilla.org/ur #ur] - discussion of user experience research for all Mozilla projects
* [irc://irc.mozilla.org/ux #ux] - discussion of visual and interactive user experience design for all Mozilla projects
* [irc://irc.mozilla.org/videol10n #videol10n] - making/translating subtitles for Mozilla related videos
* [irc://irc.mozilla.org/webdev #webdev] - the web development group's channel
* [irc://irc.mozilla.org/webmaker #webmaker] - discussion and support channel for Mozilla Webmaker
* [irc://irc.mozilla.org/wiki #wiki] - discussion and support channel for MozillaWiki
* [irc://irc.mozilla.org/windev #windev] - development discussion for Windows platforms
* [irc://irc.mozilla.org/www #www] - discussion of the development of www.mozilla.org

====Specific Locations====
* [irc://irc.mozilla.org/atlanta #atlanta] - general chat for people in the Atlanta, GA area
* [irc://irc.mozilla.org/australia #australia] - general chat for the Australian Mozilla community
* [irc://irc.mozilla.org/bangladesh #bangladesh] - general chat for the Mozilla Bangladesh community
* [irc://irc.mozilla.org/berlin #berlin] - general chat for the Berlin Mozilla community
* [irc://irc.mozilla.org/canada #canada] - general chat for the Canadian Mozilla community
* [irc://irc.mozilla.org/chicago #chicago] - general chat for the Mozilla Chicago community
* [irc://irc.mozilla.org/india #india] - general chat for the Mozilla India community
* [irc://irc.mozilla.org/kerala #kerala] - general chat for the Mozilla Kerala community
* [irc://irc.mozilla.org/london #london] - general chat for people connected to or interested in the London MozSpace
* [irc://irc.mozilla.org/michigan #michigan] - general chat for the Mozillian Michigan community
* [irc://irc.mozilla.org/montreal #montreal] - general chat for people in Montreal, including community. Bilingual channel. (French-English)
* [irc://irc.mozilla.org/mozilla-cm #mozilla-cm] - general chat for the Mozilla Cameroon community
* [irc://irc.mozilla.org/mozilla.ch #mozilla.ch] - general chat for people in Switzerland
* [irc://irc.mozilla.org/mozpdx #mozpdx] - general chat for the Mozilla Portland community
* [irc://irc.mozilla.org/munich #munich] - general chat for the Mozilla Munich Area community
* [irc://irc.mozilla.org/mv #mv] - general chat for people in the Mountain View office
* [irc://irc.mozilla.org/rochester #rochester] - general chat for people in the Rochester, NY area
* [irc://irc.mozilla.org/sf #SF] - general chat for people in the San Francisco office
* [irc://irc.mozilla.org/seattle #seattle] - general chat for people in the greater Seattle area
* [irc://irc.mozilla.org/socal #socal] - general chat for people in the greater Southern California area
* [irc://irc.mozilla.org/spain #spain] - general chat for people in Spain
* [irc://irc.mozilla.org/tokyo #tokyo] - general chat for people in the Tokyo office and area
* [irc://irc.mozilla.org/toronto #toronto] - general chat for people in the Toronto office
* [irc://irc.mozilla.org/triangle #triangle] - general chat for people in the Raleigh/Durham, NC area
* [irc://irc.mozilla.org/tulsa #tulsa] - general chat for people in the Tulsa area
* [irc://irc.mozilla.org/uk #uk] - general chat for the Mozilla UK community
* [irc://irc.mozilla.org/vancouver #vancouver] - general chat for people in the Vancouver office

====Channels in Other Languages====

=====Arabic=====

* [irc://irc.mozilla.org/arabicmozilla #arabicmozilla]
* [irc://irc.mozilla.org/mozilla-algeria #mozilla-algeria]
* [irc://irc.mozilla.org/mozilla-eg #mozilla-eg]
* [irc://irc.mozilla.org/mozillatunisia #mozillatunisia]

=====Azerbaijani=====

* [irc://irc.mozilla.org/mozillaz #mozillaz]

=====Bangladesh=====

* [irc://irc.mozilla.org/#bangladesh #bangladesh]

=====Brazilian Portuguese=====

* [irc://irc.mozilla.org/developers-br #developers-br]
* [irc://irc.mozilla.org/firefox-br #firefox-br]
* [irc://irc.mozilla.org/mozilla-br #mozilla-br]
* [irc://irc.mozilla.org/openwebapps-br #openwebapps-br]
* [irc://irc.mozilla.org/sumo-br #sumo-br]
* [irc://irc.mozilla.org/webmaker-br #webmaker-br]

=====Bulgarian=====
* [irc://irc.mozilla.org/mozilla-bg #mozilla-bg]

=====Catalan=====
* [irc://irc.mozilla.org/mozilla-cat #mozilla-cat]

=====Chinese=====

* [irc://irc.mozilla.org/china #china]
* [irc://irc.mozilla.org/mozilla-taiwan #mozilla-taiwan]
* [irc://irc.mozilla.org/taipei-platform #taipei-platform]

=====Croatian=====

* [irc://irc.mozilla.org/croatia #croatia]

=====Czech=====

* currently none, see [[L10n:Teams:cs|this page]] to know how to reach us

=====Danish=====

* [irc://irc.mozilla.org/mozilla.dk #mozilla.dk]

=====Dutch=====

* [irc://irc.mozilla.org/mozilla.nl #mozilla.nl]
* [irc://irc.mozilla.org/xhtml.nl #xhtml.nl]

=====Esperanto=====

* [irc://irc.mozilla.org/Mozilla-eo #Mozilla-eo]

=====Finnish=====

* [irc://irc.mozilla.org/mozilla.fi #mozilla.fi]

=====French=====

* [irc://irc.mozilla.org/mozfr #mozfr] Channel for community monthly meetings and generally for community members work
* [irc://irc.mozilla.org/frenchmoz #frenchmoz] Main channel for Francophone community chat
* [irc://irc.mozilla.org/L10n-fr #L10n-fr] Main channel for French localization
* [irc://irc.mozilla.org/devfr #devfr] Main channel for developers (both webdev and platform)
* [irc://irc.mozilla.org/politiques #politiques] Channel for Netpolicy discussions
* [irc://irc.mozilla.org/support-fr #support-fr] Technical support
* [irc://irc.mozilla.org/xulfr #xulfr] Historically XUL technology channel
* [irc://irc.mozilla.org/rust-fr #rust-fr] Rust language channel

=====German=====
* [irc://irc.mozilla.org/de #de]
* [irc://irc.mozilla.org/chatzilla.de #chatzilla.de]
* [irc://irc.mozilla.org/firefox.de #firefox.de]
* [irc://irc.mozilla.org/firefoxOS.de #firefoxOS.de]
* [irc://irc.mozilla.org/mozilla.de #mozilla.de]
* [irc://irc.mozilla.org/thunderbird.de #thunderbird.de]

=====Greek=====
* [irc://irc.mozilla.org/athens #athens]

=====Hebrew=====
* [irc://irc.mozilla.org/mozilla.il #mozilla.il]

=====Indonesia=====
* [irc://irc.mozilla.org/idmoz #idmoz]

=====Italian=====
* [irc://irc.mozilla.org/developers-it #developers-it]

=====Japanese=====

* [irc://irc.mozilla.org/firefox-jp #firefox-jp (iso-2022-jp)]
* [irc://irc.mozilla.org/japan #japan (UTF-8)]

=====Korean=====
* [irc://irc.mozilla.org/mozillakr #mozillakr]

=====Lithuanian=====
* [irc://irc.mozilla.org/mozilla-lt #mozilla-lt]

=====Marathi=====
* [irc://irc.mozilla.org/marathi #marathi]

=====Myanmar=====
* [irc://irc.mozilla.org/mozillamm #mozillamm]

=====Norwegian=====

* [irc://irc.mozilla.org/mozilla.no #mozilla.no]

=====Persian=====

* [irc://irc.mozilla.org/iranmozilla #iranmozilla]

=====Polish=====

* [irc://irc.mozilla.org/aviarypl #aviarypl]

=====Portuguese (Portugal)=====

* [irc://irc.mozilla.org/mozilla-portugal #mozilla-portugal]

=====Philippines=====

* [irc://irc.mozilla.org/mozilla-ph #mozilla-ph]

=====Romanian=====

* [irc://irc.mozilla.org/romania #romania]

=====Russian=====
* [irc://irc.mozilla.org/mozilla-ru #mozilla-ru]

=====Serbian=====
* [irc://irc.mozilla.org/mozilla.sr #mozilla.sr]

=====Sinhala=====

* [irc://irc.mozilla.org/mozilla.lk #mozilla.lk]

=====Slovak=====

* [irc://irc.mozilla.org/mozilla-sk #mozilla-sk]

=====Slovenia=====

* [irc://irc.mozilla.org/slozilla #slozilla]

=====Spanish=====

* [irc://irc.mozilla.org/mozilla-hispano #mozilla-hispano]
* [irc://irc.mozilla.org/mozilla-mexico #mozilla-mexico]
* [irc://irc.mozilla.org/mozilla-venezuela #mozilla-venezuela]

=====Swedish=====

* [irc://irc.mozilla.org/mozilla.se #mozilla.se]

=====Tunisian=====

* [irc://irc.mozilla.org/mozillatunisia #mozillatunisia]

=====Ukrainian=====

* [irc://irc.mozilla.org/mozilla-ua #mozilla-ua]

=====Wolof=====

* [irc://irc.mozilla.org/l10n-wo #l10n-wo]

== Connection Notice ==

When you connect to our IRC server, you will get portscanned from 63.245.208.159, 63.245.212.23, or 63.245.216.214. This is an unfortunate but necessary step in order to cut down on the number of viruses and other malicious users attempting to communicate via our IRC servers. The portscan is checking for common ports used by known viruses and open proxy servers to ensure that your machine is not infected before allowing you to remain connected. By connecting to our IRC servers, you agree to have your computer portscanned by our server. If you don't like this, don't connect.

== Privacy Information ==

Our servers do not keep records of any of your conversations, but anyone in the channels you are in might do so and publish those conversation logs (and some channels are actively logged by users on those channels). If you have questions about this, ask the other users in the channel you are concerned about (every channel has its own culture). In general, you should assume that anything you say on IRC that is not in a private message will be recorded and possibly published somewhere, and even then you are depending on your trust that the person you are sending the message to will not to share it.

==Quotes Database==

Sometimes people say silly or memorable things on our server. We memorialize them forever on the [http://quotes.burntelectrons.org/ quotes database] managed by Tim De Pauw.

==Persistent Connection==
If you have access to a host that is always on you can run an irc session on it and connect/disconnect from that session without losing everything. This allows you to keep scrollback, stay present in channels when you are away, and have logs of what happens when you're not around. In this example I will use people.mozilla.org as my host. If someone can add good instructions for setting up a proxy in another way, please do. This tutorial will assume that you have an account on people.mozilla.org (or another server where you can ssh to it and run both 'screen' and 'irssi'), details on how to set this up are below. An alternative is [http://wiki.znc.in/ZNC ZNC].

===On the server===
<pre>
ssh lsblakk@people.mozilla.org
## create a bin dir
mkdir bin
cd bin
vim irc
## paste the following two lines (without the initial spaces) in the empty file:
#!/bin/bash
screen -raAd
## now hit ESC followed by :x and enter to save this file
## make the file executable
chmod -c a+x irc
## Start your irssi session:
screen irssi
</pre>
====Add Network/Server====
Replace <nick> and <password> with your registered Mozilla IRC nickname and password.
The following creates an autoconnect to irc.mozilla.org under the name Mozilla.
<pre>
/SERVER ADD -ssl -auto -network Mozilla irc.mozilla.org 6697
/NETWORK ADD -nick <nick> -user <nick> -autosendcmd "/^msg nickserv identify <password>;wait 2000" Mozilla
</pre>

====Add Channels (optional)====
Replace <nowiki>#channel</nowiki> with the channel you'd like to add. <pass> is an optional field, used when an IRC channel requires a password.
<pre>
/CHANNEL ADD -auto #channel Mozilla <pass>
</pre>
...repeat till satisfied!
====Good practices====
<pre>
/HILIGHT <nick>
</pre>
'''more soon'''

===References===
* [http://www.irssi.org/documentation/startup Irssi Startup HOWTO]
* [http://quadpoint.org/articles/irssi/ Irssi Basics]

MDN/Archives/Meetings/Community//2016/05-04

2016-05-04T17:42:46Z

Sheppy: /* Miscellaneous */ who will moderate? no idea

=Agenda/Notes=

The MDN community meeting takes place in the [irc://irc.mozilla.org/mdn #mdn] channel on irc.mozilla.org at 10 AM PDT (18:00 UTC). [http://arewemeetingyet.com/Los%20Angeles/2014-11-19/10:00/b/MDN%20Community%20meeting See the meeting time in your time zone.]

==Introductions==
Since lots of people lurk in #mdn, if you're actively attending the meeting please speak up and introduce yourself.

* Attending: sheppy, dvincent, chrismills, teoli

==Spam/Account creation status==
* Account creation has been turned back on!
* However, for the time being, newly created accounts cannot create a page. When they try to do so, they're prompted to file a bug or ask for help. This will be improved, and hopefully will be much more seamless when it's all done.

==Help wanted==
Please share documentation bugs that need work, or other things where you need short-term help.
* As always, you can find bugs you can help out with on our [http://www.joshmatthews.net/bugsahoy/?mdn=1 Bugs Ahoy] page.
* If you have ideas for things that should be tweeted out by @MozDevNet, please suggest it using our [https://docs.google.com/a/mozilla.com/forms/d/1cwNp_iA0cjNY8C9g-ff9rpf3fVg6OF_pKSFjxse0WPc/viewform handy form]!

===Learning area (chris)===

I am still writing lots of material for the MDN learning area, but would still love some help reviewing or writing material. You can see what kind of work is up for grabs at our [https://trello.com/b/LDggrYSV/learning-area-glossary Learning Area Trello Board]. Get in touch with me if you want to help (chrismills on IRC.)

===Trello board status update===

The MDN team is moving to a new process to align itself with the rest of the marketing organization.

==Blockers==
Is there anything keeping you from making progress?

==What are you working on?==
Please share recent accomplishments, and goals you have for the next few weeks.

* (sheppy) All methods on [https://developer.mozilla.org/en-US/docs/Web/API/RTCPeerConnection RTCPeerConnection] are documented, along with many related dictionaries and enums. Working on properties now.
* (chrismills) The Firefox OS area of MDN is now the [https://developer.mozilla.org/en-US/docs/Mozilla/B2G_OS B2G OS area]. Volunteers are driving this content now. All old material that no longer applies has been moved to Archive.
* (chrismills) Firefox OS for TV stuff has been moved to [https://developer.mozilla.org/en-US/docs/Mozilla/Firefox_OS_for_TV its own subtree] on MDN.
* Any future projects based on B2G OS will have its own tree like that.

==Actions==
===Previous===

===New/Continuing===

== Miscellaneous ==
Anything else we need to discuss synchronously?
* Who will moderate the next meeting?
** Undecided -- need to figure it out by mail

MDN/Archives/Meetings/Community//2016/05-04

2016-05-04T17:36:09Z

Sheppy: /* What are you working on? */ New trees for future B2G OS based projects

=Agenda/Notes=

The MDN community meeting takes place in the [irc://irc.mozilla.org/mdn #mdn] channel on irc.mozilla.org at 10 AM PDT (18:00 UTC). [http://arewemeetingyet.com/Los%20Angeles/2014-11-19/10:00/b/MDN%20Community%20meeting See the meeting time in your time zone.]

==Introductions==
Since lots of people lurk in #mdn, if you're actively attending the meeting please speak up and introduce yourself.

* Attending: sheppy, dvincent, chrismills, teoli

==Spam/Account creation status==
* Account creation has been turned back on!
* However, for the time being, newly created accounts cannot create a page. When they try to do so, they're prompted to file a bug or ask for help. This will be improved, and hopefully will be much more seamless when it's all done.

==Help wanted==
Please share documentation bugs that need work, or other things where you need short-term help.
* As always, you can find bugs you can help out with on our [http://www.joshmatthews.net/bugsahoy/?mdn=1 Bugs Ahoy] page.
* If you have ideas for things that should be tweeted out by @MozDevNet, please suggest it using our [https://docs.google.com/a/mozilla.com/forms/d/1cwNp_iA0cjNY8C9g-ff9rpf3fVg6OF_pKSFjxse0WPc/viewform handy form]!

===Learning area (chris)===

I am still writing lots of material for the MDN learning area, but would still love some help reviewing or writing material. You can see what kind of work is up for grabs at our [https://trello.com/b/LDggrYSV/learning-area-glossary Learning Area Trello Board]. Get in touch with me if you want to help (chrismills on IRC.)

===Trello board status update===

The MDN team is moving to a new process to align itself with the rest of the marketing organization.

==Blockers==
Is there anything keeping you from making progress?

==What are you working on?==
Please share recent accomplishments, and goals you have for the next few weeks.

* (sheppy) All methods on [https://developer.mozilla.org/en-US/docs/Web/API/RTCPeerConnection RTCPeerConnection] are documented, along with many related dictionaries and enums. Working on properties now.
* (chrismills) The Firefox OS area of MDN is now the [https://developer.mozilla.org/en-US/docs/Mozilla/B2G_OS B2G OS area]. Volunteers are driving this content now. All old material that no longer applies has been moved to Archive.
* (chrismills) Firefox OS for TV stuff has been moved to [https://developer.mozilla.org/en-US/docs/Mozilla/Firefox_OS_for_TV its own subtree] on MDN.
* Any future projects based on B2G OS will have its own tree like that.

==Actions==
===Previous===

===New/Continuing===

== Miscellaneous ==
Anything else we need to discuss synchronously?
* Who will moderate the next meeting?

MDN/Archives/Meetings/Community//2016/05-04

2016-05-04T17:35:15Z

Sheppy: /* What are you working on? */ TV

=Agenda/Notes=

The MDN community meeting takes place in the [irc://irc.mozilla.org/mdn #mdn] channel on irc.mozilla.org at 10 AM PDT (18:00 UTC). [http://arewemeetingyet.com/Los%20Angeles/2014-11-19/10:00/b/MDN%20Community%20meeting See the meeting time in your time zone.]

==Introductions==
Since lots of people lurk in #mdn, if you're actively attending the meeting please speak up and introduce yourself.

* Attending: sheppy, dvincent, chrismills, teoli

==Spam/Account creation status==
* Account creation has been turned back on!
* However, for the time being, newly created accounts cannot create a page. When they try to do so, they're prompted to file a bug or ask for help. This will be improved, and hopefully will be much more seamless when it's all done.

==Help wanted==
Please share documentation bugs that need work, or other things where you need short-term help.
* As always, you can find bugs you can help out with on our [http://www.joshmatthews.net/bugsahoy/?mdn=1 Bugs Ahoy] page.
* If you have ideas for things that should be tweeted out by @MozDevNet, please suggest it using our [https://docs.google.com/a/mozilla.com/forms/d/1cwNp_iA0cjNY8C9g-ff9rpf3fVg6OF_pKSFjxse0WPc/viewform handy form]!

===Learning area (chris)===

I am still writing lots of material for the MDN learning area, but would still love some help reviewing or writing material. You can see what kind of work is up for grabs at our [https://trello.com/b/LDggrYSV/learning-area-glossary Learning Area Trello Board]. Get in touch with me if you want to help (chrismills on IRC.)

===Trello board status update===

The MDN team is moving to a new process to align itself with the rest of the marketing organization.

==Blockers==
Is there anything keeping you from making progress?

==What are you working on?==
Please share recent accomplishments, and goals you have for the next few weeks.

* (sheppy) All methods on [https://developer.mozilla.org/en-US/docs/Web/API/RTCPeerConnection RTCPeerConnection] are documented, along with many related dictionaries and enums. Working on properties now.
* (chrismills) The Firefox OS area of MDN is now the [https://developer.mozilla.org/en-US/docs/Mozilla/B2G_OS B2G OS area]. Volunteers are driving this content now. All old material that no longer applies has been moved to Archive.
* (chrismills) Firefox OS for TV stuff has been moved to [https://developer.mozilla.org/en-US/docs/Mozilla/Firefox_OS_for_TV its own subtree] on MDN.

==Actions==
===Previous===

===New/Continuing===

== Miscellaneous ==
Anything else we need to discuss synchronously?
* Who will moderate the next meeting?

MDN/Archives/Meetings/Community//2016/05-04

2016-05-04T17:33:59Z

Sheppy: /* What are you working on? */ b2g os

=Agenda/Notes=

The MDN community meeting takes place in the [irc://irc.mozilla.org/mdn #mdn] channel on irc.mozilla.org at 10 AM PDT (18:00 UTC). [http://arewemeetingyet.com/Los%20Angeles/2014-11-19/10:00/b/MDN%20Community%20meeting See the meeting time in your time zone.]

==Introductions==
Since lots of people lurk in #mdn, if you're actively attending the meeting please speak up and introduce yourself.

* Attending: sheppy, dvincent, chrismills, teoli

==Spam/Account creation status==
* Account creation has been turned back on!
* However, for the time being, newly created accounts cannot create a page. When they try to do so, they're prompted to file a bug or ask for help. This will be improved, and hopefully will be much more seamless when it's all done.

==Help wanted==
Please share documentation bugs that need work, or other things where you need short-term help.
* As always, you can find bugs you can help out with on our [http://www.joshmatthews.net/bugsahoy/?mdn=1 Bugs Ahoy] page.
* If you have ideas for things that should be tweeted out by @MozDevNet, please suggest it using our [https://docs.google.com/a/mozilla.com/forms/d/1cwNp_iA0cjNY8C9g-ff9rpf3fVg6OF_pKSFjxse0WPc/viewform handy form]!

===Learning area (chris)===

I am still writing lots of material for the MDN learning area, but would still love some help reviewing or writing material. You can see what kind of work is up for grabs at our [https://trello.com/b/LDggrYSV/learning-area-glossary Learning Area Trello Board]. Get in touch with me if you want to help (chrismills on IRC.)

===Trello board status update===

The MDN team is moving to a new process to align itself with the rest of the marketing organization.

==Blockers==
Is there anything keeping you from making progress?

==What are you working on?==
Please share recent accomplishments, and goals you have for the next few weeks.

* (sheppy) All methods on [https://developer.mozilla.org/en-US/docs/Web/API/RTCPeerConnection RTCPeerConnection] are documented, along with many related dictionaries and enums. Working on properties now.
* (chrismills) The Firefox OS area of MDN is now the [https://developer.mozilla.org/en-US/docs/Mozilla/B2G_OS B2G OS area]. Volunteers are driving this content now. All old material that no longer applies has been moved to Archive.

==Actions==
===Previous===

===New/Continuing===

== Miscellaneous ==
Anything else we need to discuss synchronously?
* Who will moderate the next meeting?

MDN/Archives/Meetings/Community//2016/05-04

2016-05-04T17:22:38Z

Sheppy: add trello update

=Agenda/Notes=

The MDN community meeting takes place in the [irc://irc.mozilla.org/mdn #mdn] channel on irc.mozilla.org at 10 AM PDT (18:00 UTC). [http://arewemeetingyet.com/Los%20Angeles/2014-11-19/10:00/b/MDN%20Community%20meeting See the meeting time in your time zone.]

==Introductions==
Since lots of people lurk in #mdn, if you're actively attending the meeting please speak up and introduce yourself.

* Attending: sheppy, dvincent, chrismills, teoli

==Spam/Account creation status==
* Account creation has been turned back on!
* However, for the time being, newly created accounts cannot create a page. When they try to do so, they're prompted to file a bug or ask for help. This will be improved, and hopefully will be much more seamless when it's all done.

==Help wanted==
Please share documentation bugs that need work, or other things where you need short-term help.
* As always, you can find bugs you can help out with on our [http://www.joshmatthews.net/bugsahoy/?mdn=1 Bugs Ahoy] page.
* If you have ideas for things that should be tweeted out by @MozDevNet, please suggest it using our [https://docs.google.com/a/mozilla.com/forms/d/1cwNp_iA0cjNY8C9g-ff9rpf3fVg6OF_pKSFjxse0WPc/viewform handy form]!

===Learning area (chris)===

I am still writing lots of material for the MDN learning area, but would still love some help reviewing or writing material. You can see what kind of work is up for grabs at our [https://trello.com/b/LDggrYSV/learning-area-glossary Learning Area Trello Board]. Get in touch with me if you want to help (chrismills on IRC.)

===Trello board status update===

The MDN team is moving to a new process to align itself with the rest of the marketing organization.

==Blockers==
Is there anything keeping you from making progress?

==What are you working on?==
Please share recent accomplishments, and goals you have for the next few weeks.

* (sheppy) All methods on [https://developer.mozilla.org/en-US/docs/Web/API/RTCPeerConnection RTCPeerConnection] are documented, along with many related dictionaries and enums. Working on properties now.

==Actions==
===Previous===

===New/Continuing===

== Miscellaneous ==
Anything else we need to discuss synchronously?
* Who will moderate the next meeting?

MDN/Archives/Meetings/Community//2016/05-04

2016-05-04T17:06:23Z

Sheppy: /* Introductions */ account creation/spam

MDN/Archives/Meetings/Community//2016/05-04

2016-05-04T17:04:16Z

Sheppy: /* What are you working on? */ rtcpeerconnection

MDN/Archives/Meetings/Community//2016/05-04

2016-05-04T17:03:01Z

Sheppy: /* Help wanted */ twitter link

MDN/Archives/Meetings/Community//2016/05-04

2016-05-04T17:02:02Z

Sheppy: /* Introductions */ attendees 1

MDN/Archives/Meetings/Community//2016/05-04

2016-05-02T20:46:05Z

Sheppy: new for 5/6/16 meeting

MDN/Archives/Meetings/Community/

2016-05-02T20:44:35Z

Sheppy: add 5/6/16 meeting

= MDN Site Community Meetings =

==How to attend ==
Community meetings occur every two weeks on Wednesdays, in the #mdn IRC channel, at 10:00 US Pacific time (UTC-0800 Nov-Feb, UTC-0700 Mar-Oct). [http://arewemeetingyet.com/Los%20Angeles/2014-02-26/10:00/b/MDN%20Community%20meeting See the time and date of the next meeting, in your time zone.]

The [https://www.google.com/calendar/embed?src=7atgd2ovttdiea1a8p6fksksf8%40group.calendar.google.com MDN Events] calendar contains MDN community meetings, doc sprints, and other MDN-related events.

== Agendas/notes ==
The following pages collect agenda items prior to the meeting, and notes during or after the meeting. Please add new dates to the top of the list.

'''2016'''
* [[MDN/Meetings/Community/2016/05-04|2016-05-04]] 10:00 Pacific/17:00 UTC
* [[MDN/Meetings/Community/2016/04-20|2016-04-20]] 10:00 Pacific/17:00 UTC
* [[MDN/Meetings/Community/2016/04-06|2016-04-06]] 10:00 Pacific/17:00 UTC
* [[MDN/Meetings/Community/2016/03-23|2016-03-23]] 10:00 Pacific/17:00 UTC
* [[MDN/Meetings/Community/2016/03-09|2016-03-09]] 05:00 Pacific time/13:00 UTC
* [[MDN/Meetings/Community/2016/02-24|2016-02-24]]
* [[MDN/Meetings/Community/2016/02-10|2016-02-10]] 05:00 Pacific time/13:00 UTC
* [[MDN/Meetings/Community/2016/01-27|2016-01-27]]
* [[MDN/Meetings/Community/2016/01-13|2016-01-13]]

* [[MDN/Archives/Meetings/Community/2015|2015]]
* [[MDN/Archives/Meetings/Community/2014|2014]]
* [[MDN/Archives/Meetings/Community/2013|2013]]
* [[MDN/Archives/Meetings/Community/2012|2012]]
* [[MDN/Archives/Meetings/Community/2011|2011]]
* [[MDN/Archives/Meetings/Community/2010|2010]]

== How to run an MDN Community meeting ==

===Before the meeting===

====Create the agenda====
# Copy the content of the [[MDN/Meetings/Community/Agenda_template|Agenda template]] (in Edit mode, so you get the wiki markup).
# Create a link at the top of the Agenda/notes list, above, based on the date of the meeting.
# Click the link you just made and create the page.
# Paste in the agenda template.
# Make any changes that are needed, such as copying action items from the previous meeting into the Action Items section.
# Save the page.

====Announce the meeting====
On the Monday before the meeting is scheduled to happen, post an announcement to the dev-mdc mailing list. See [https://groups.google.com/forum/#!topic/mozilla.dev.mdc/LpwCwbCvFk8 this example] for a typical format. Be sure to include how to join the meeting, and a way to figure out the meeting time in all time zones. If there are issues that you already know will be discussed, you can mention them to spark interest in the meeting.

Also, on the day of the meeting, you can announce in the #mdn channel that the MDN Community meeting will happen in X hours, or Y minutes. Include a link to the agenda.

{|
|-
! !! US Pacific time !! UTC
|-
| "Early" meeting, US Daylight Saving Time (Mar-Oct) || 05:00 a.m. || 13:00
|-
| "Early" meeting, US Standard Time (Nov-Mar) || 06:00 a.m.|| 13:00
|-
| "Late" meeting, US Daylight Saving Time (Mar-Oct) || 10:00 a.m.|| 18:00
|-
| "Late" meeting, US Standard Time (Nov-Mar) || 10:00 a.m.|| 17:00
|}

If you're not sure which time is currently in effect, check the [http://en.wikipedia.org/wiki/Daylight_saving_time_in_the_United_States change-over dates].

===During the meeting===
As moderator, your job is to make sure that the meeting runs smoothly and stays on track, and also that all participants feel welcome and have an opportunity to "speak" if they want to.

* At the time of the meeting, announce that the meeting has started, and ask who is participating. Allow a little time for participants to self-identify. Be sure to welcome participants who are there for the first time, or first time in a long time.
* Review the action items from the previous meeting. Ask the people who were tasked to give a status update.
* For each of the items under "News" and "Discussion Topics", introduce the topic and ask the person who added it to start the discussion. Keep the emphasis on discussion, not on dumping information. Ask what decisions or actions are needed to move forward. Record any decisions in the notes for that item, and put any action items in the "New/Continuing" section.
* '''Moderation tips:'''
** Be mindful of the number of topics and the amount of time available. If a particular topic is taking a lot of time, ask whether it needs to be moved to the mailing list, or to another meeting.
** If the discussion wanders off the current topic, try to bring it back to the topic or introduce the next topic.
** If the discussion of a topic seems to be winding down, ask "Any other questions or comments about this?" and wait a minute or two for responses.

===After the meeting===
Review the IRC scrollback or log from the meeting and ensure that major discussion points, decisions, and action items are captured in the Agenda/notes page, so that someone who didn't attend the meeting can understand what happened.

MDN/Archives/Meetings/Community//2016/04-20

2016-04-20T17:14:46Z

Sheppy: /* What are you working on? */ agile switch

MDN/Archives/Meetings/Community//2016/04-20

2016-04-20T17:12:45Z

Sheppy: /* Blockers */ spam/account creation status

MDN/Archives/Meetings/Community//2016/04-20

2016-04-20T17:12:07Z

Sheppy: /* What are you working on? */ WebRTC progress

Webrtc/links

2016-04-13T22:29:25Z

Sheppy: /* Current links, wiki pages, and tools */ fix typo in layout

==Current links, wiki pages, and tools==
This list is not exhaustive and some wiki's will likely only make sense if you were at the meeting. Many wikis though are good reference if you can't attend a meeting or to put in agenda items before the next meeting.
{| class="wikitable fullwidth-table"
! Area !! Links !!
|-

| Metrics
|
*insert link to audio metrics here
|-

| Technical Documentation
|
* [https://developer.mozilla.org/en-US/docs/Web/API/WebRTC_API WebRTC documentation on MDN] (in progress)
|-

| QA
* Use this section for QA information for WebRTC
|
* placeholder
|-
| webRTC partners (cross test & validation, collaborative development)
|
* [https://wiki.mozilla.org/Firefox/Iterative_Hello_Development#Current Current Hello work]
* add links to companies working with WebRTC and co-developing
|-
| Communications and Marketing
|
* placeholder for link to latest updates
|-

|}

Webrtc/links

2016-04-13T22:28:27Z

Sheppy: Add link to docs on MDN

==Current links, wiki pages, and tools==
This list is not exhaustive and some wiki's will likely only make sense if you were at the meeting. Many wikis though are good reference if you can't attend a meeting or to put in agenda items before the next meeting.
{| class="wikitable fullwidth-table"
! Area !! Links !!
|-

| Metrics
|
*insert link to audio metrics here
|-

| Technical Documentation
|
* [https://developer.mozilla.org/en-US/docs/Web/API/WebRTC_API WebRTC documentation on MDN] (in progress)
|-
| QA
* Use this section for QA information for WebRTC
|
* placeholder
|-
| webRTC partners (cross test & validation, collaborative development)
|
* [https://wiki.mozilla.org/Firefox/Iterative_Hello_Development#Current Current Hello work]
* add links to companies working with WebRTC and co-developing
|-
| Communications and Marketing
|
* placeholder for link to latest updates
|-

|}

MDN/Archives/Meetings/Community//Agenda template

2016-04-06T17:19:36Z

Sheppy: /* Help wanted */ bugs ahoy!

=Agenda/Notes=

The MDN community meeting takes place in the [irc://irc.mozilla.org/mdn #mdn] channel on irc.mozilla.org at: DELETE ONE OF THE FOLLOWING
* 10 AM PDT (18:00 UTC). [http://arewemeetingyet.com/Los%20Angeles/2014-11-19/10:00/b/MDN%20Community%20meeting See the meeting time in your time zone.]
* 6 AM PDT (13:00 UTC). [http://arewemeetingyet.com/Los%20Angeles/2015-10-21/06:00/b/MDN%20Community%20meeting See the meeting time in your time zone.]

==Introductions==
Since lots of people lurk in #mdn, if you're actively attending the meeting please speak up and introduce yourself.

* Attending:

==Help wanted==
Please share documentation bugs that need work, or other things where you need short-term help.
* As always, you can find bugs you can help out with on our [http://www.joshmatthews.net/bugsahoy/?mdn=1 Bugs Ahoy] page.

==Blockers==
Is there anything keeping you from making progress?

==What are you working on?==
Please share recent accomplishments, and goals you have for the next few weeks.

==Actions==
===Previous===

===New/Continuing===

== Miscellaneous ==
Anything else we need to discuss synchronously?
* Who will moderate the next meeting?

MDN/Archives/Meetings/Community//2016/04-06

2016-04-06T17:17:06Z

Sheppy: /* Help wanted */ bugs ahoy!

=Agenda/Notes=

The MDN community meeting takes place in the [irc://irc.mozilla.org/mdn #mdn] channel on irc.mozilla.org at:
* 10 AM PDT (17:00 UTC). [http://arewemeetingyet.com/Los%20Angeles/2016-04-04/10:00/b/MDN%20Community%20meeting See the meeting time in your time zone.]

==Introductions==
Since lots of people lurk in #mdn, if you're actively attending the meeting please speak up and introduce yourself.

* Attending: jswisher, sheppy, fscholz, Jeremie, Sphinx, Danielle

==Help wanted==
Please share documentation bugs that need work, or other things where you need short-term help.
* As always, you can find bugs you can help out with on our [http://www.joshmatthews.net/bugsahoy/?mdn=1 Bugs Ahoy] page.

==Blockers==
Is there anything keeping you from making progress?
* Not a blocker per se, but note that the MDN team is moving to an agile "durable team" process which may cause changes in schedules, how things are managed, and so forth. We'll let you know when we do.

==What are you working on?==
* (sheppy) Working on the WebRTC reference
* (ops team) ElasticSearch upgrade (started 10:08 AM PDT, finished 10:11 AM PDT - go ops team!)
** Just a "keep things up to date" upgrade, mostly
** Re-index underway; search will keep working in the interim since the new index is built on the side and switched to only once finished
* (Jeremie) Anti-spam long term strategy

==Actions==
===Previous===

===New/Continuing===

== Miscellaneous ==
Anything else we need to discuss synchronously?
* Who will moderate the next meeting?

MDN/Archives/Meetings/Community//2016/04-06

2016-04-06T17:16:33Z

Sheppy: /* What are you working on? */ es detail

MDN/Archives/Meetings/Community//2016/04-06

2016-04-06T17:13:37Z

Sheppy: /* Blockers */ durable team

MDN/Archives/Meetings/Community//2016/04-06

2016-04-06T17:12:28Z

Sheppy: /* What are you working on? */ ES upgrade done