MozillaWiki - User contributions [en]

Reps/SOPs/Digital resources

2015-04-27T16:36:16Z

Mrz:

{{Remonav}}

This document describes the policies the Mozilla Reps Council agreed to apply when reviewing and approving [https://bugzilla.mozilla.org/form.reps.it Community IT requests].

==General requirements==

This are the general requirements evaluated in any request:

* The following questions should be answered: Why this request is it needed? How does it benefit Mozilla mission?
* The request coming from a known Mozilla community member.
* The requester represents the project he’s requesting resources for. Communities will be asked to provide a document explaining who owns these kind of requests.
* There is an established project/community (+6 months) supporting the request, already running in production stage.
* There is at least 2 people on the project responsible for the request and as main contact point.

==Domain Name==

* Full fit general requirements.

==Hosting==

* Hosting requests should include a twelve (12) month road map. Include link to wiki.mozilla.org or other documentation. This helps to evaluate the life cycle & life span of the request. Some microsites, for example, only have a six month life, while others such as discourse.mozilla-community.org will have an indefinite life span.
* In most cases, we try not to duplicate services that already exist. For example, Community IT team would prefer to migrate a Wordpress site into the Wordpress-as-a-Service instead of building a new Wordpress instance.
* The domain for the website has already been transferred to Mozilla’s Domain Registrar or will be transferred.

==Email==

* The domain name for the emails is already transferred to Mozilla.

==SSL==

* The domain name for the website is already transferred to Mozilla.

==FAQ==

'''Why does the domain name need to be transferred to Mozilla?'''

We want all Mozilla Community domains to be safe, not just now, but always. This means that they are properly renewed and monitored by Mozilla IT.

Mozilla will work with the existing Domain Name Owner to transfer to Mozilla’s Domain Registrar. This will help ensure that these domain names and properly renewed and monitored. It also avoids possible future domain renewal / maintenance issues.

It’s a good practice to avoid individuals to own community domains, avoiding bottlenecks, possible future personal conflicts and the well known bus factor. Historically this approach has been proven more effective than individuals owning mozilla-related domains.

Mozilla will only own the administrative part, but the community is responsible and owns any changes and decisions to it and its subdomains. At the moment of the request the requester should provide a document describing how the community is organized to be sure he’s the right person to own this request.

'''Will Mozilla modify the domain or its content without community approval?'''

No. While your domain will be at Mozilla’s Domain Registrar and Mozilla Domain Name Servers, Mozilla will not modify the domain without approval or direction from the domain’s Technical Contact.

The Mozilla Reps Council will work to ensure that this policy is followed.

'''Can I still use my own DNS instead of mozilla’s one?'''

Yes, you can request to use your custom NS to handle the domain zone instead of Mozilla’s one.

For various services, you may be required to delegate a sub-domain NS RR to Mozilla. This allows Community Ops greater flexibility in managing the service. For instance, you may be asked to delete your blog site to Amazon’s Route 53:

<pre>blog.communitysysadmins.org. IN NS ns-277.awsdns-34.com.</pre>

'''Can I request any type of hosting?'''

Yes! The Community IT Operations team will be happy to work with you to find the best solutions for your needs.

[[Category:Remosop]]

Reps/SOPs/Dismissal

2015-02-27T16:32:52Z

Mrz:

{{remonav}}

This page explains the procedure to follow to remove a Rep, Mentor, Council Member or Peer from the Mozilla Reps program. If the Rep would like to step out the program voluntarily, please refer to [[ReMo/SOPs/Leaving|Leaving SOP]].

===Removing a Rep===
'''STEP 1:''' 
Mentor writes an email to reps-council@mozilla.com with '''[Dismissal Request]''' in the subject header, to inform Council that their mentee is not fulfilling his/her responsibilities and provides detailed documentation to back their claim. 

'''STEP 2:''' 
Council has 7 days to review claim and decide whether to : 
a) re-assign mentee to another Mentor 
OR 
b) remove mentee from the program 

'''STEP 3:''' 
* If a): the Council Chair must follow Mentor re-assignment procedure (https://wiki.mozilla.org/ReMo/SOPs/Mentoring/Reassigning) 
* If b): the Council Chair must inform the mentee directly by email providing detailed explanation for the Council's decision and granting 7 days to appeal decision.

Email example:

[mailto:example@domain.com?subject=Mozilla%20Reps%20Status&body=Dear%20%5BNAME%5D%2C%0A%0AAs%20part%20of%20its%20efforts%20to%20continuously%20improve%20the%20Reps%20program,%20the%20Council%20recently%0Aconducted%20a%20process%20to%20gather%20feedback%20from%20Mentors%20to%20identify%20areas%20of%0Aimprovement%2C%20fresh%20opportunities%20but%20also%20identify%20Reps%20who%20would%0Abenefit%20from%20being%20relieved%20from%20their%20duties.%0A%0AAfter%20a%20thorough%20and%20difficult%20review%20process%2C%20the%20Council%20agreed%20that%0Ait%20is%20better%20for%20you%20to%20return%20to%20being%20exclusively%20a%20Mozilla%0Acontributor.%20Indeed%2C%20the%20Council%20is%20confident%20you%20will%20be%20able%20to%0Acontinue%20contributing%20to%20the%20Mozilla%20program.%0A%0AYour%20responsibilities%20as%20Reps%20will%20officially%20end%20on%20%5BDATE%5D%2C%20and%20your%0Aprofile%20page%20deactivated.%0A%0AThe%20Council%20would%20like%20to%20thank%20you%20for%20all%20your%20hard%20work%20as%20a%20Rep%20and%0Awish%20you%20continued%20success%20as%20a%20contributor.%20Should%20you%20have%20any%0Aquestions%20or%20wish%20to%20appeal%20this%20decision%2C%20please%20contact%20the%20Council%20in%20they%20next%207%20days.%20%0A%0ASincerely%2C%0A%0A%5BCHAIR%20NAME%5D%2C%0Aon%20behalf%20of%20the%20Reps%20Council Click here to launch mail]

<pre>
Dear [NAME],

As part of its efforts to continuously improve the Reps program, the Council recently
conducted a process to gather feedback from Mentors to identify areas of
improvement, fresh opportunities but also identify Reps who would
benefit from being relieved from their duties.

After a thorough and difficult review process, the Council has proposed that your
status as Rep be transitioned to Alumni. This means the expectations of this role are not longer applicable.

Your responsibilities as Reps will officially end on [DATE], and your
profile page deactivated.

The Council would like to thank you for all your hard work as a Rep and
wish you continued success as a valued Mozilla contributor. Should you have any
questions or wish to appeal this decision, please contact the Council in they next 7 days.

Sincerely,

[CHAIR NAME],
on behalf of the Reps Council
</pre>

'''STEP 4:''' 

Rep Admins will apply changes following [[ReMo/SOPs/Leaving#Reps_Admin_Actions|leaving actions]].

===Removing a Mentor===

'''STEP 1:''' 
Council chair writes an email to mentor to inform him/her that he/she is not fulfilling his/her responsibilities and their the mentor will be relieved of his/his duties as mentor. '''NB: It is critical to provide detailed explanation and hard facts to back the decision and make clear that the Mentor has 7 days to appeal the decision.''' 

'''STEP 2:''' 
After the appeal window is over and decision to remove still stands, the Council Chair must effectively remove the Mentor from the Mentors list on the portal and the wiki. 

'''STEP 3:''' 

===Removing/Replacing a Council Member===

'''STEP 1:''' 
Peers need to have a majority agreement that a Council member is not fulfilling his/her responsibilities 

'''STEP 2:''' 
If decision is unanimous, Peers must inform Module owner and ask him/her to take action 

'''STEP 3:''' 
Module owner writes an email to Council Member informing him/her that he/she is not fulfilling his/her responsibilities and that the Council Member has been relieved of his/his duties effective immediately. It is important to provide detailed explanation and hard facts to back the decision. 

'''STEP 4:''' 
Module owner must select a former Council member to fill the available seat until the next election 

'''STEP 5:''' 
Module owner updates the portal and wiki 

'''STEP 6:''' 
Module owner must inform reps-mentors that the list of Council members has been updated 

'''STEP 7:''' 
Module owner informs reps-general that the list of Council Members has been updated 

===Removing/Replacing the Council Chair===

'''STEP 1:''' 
Peers need to have a majority agreement that a Council Chair is not fulfilling his/her responsibilities 

'''STEP 2:''' Peers must inform Module owner and ask him/her to take action 

'''STEP 3:''' Module owner writes an email to Council Chair informing him/her that he/she is not fulfilling his/her responsibilities and that the Council Chair has been relieved of his/his duties effective immediately. It is important to provide detailed explanation and hard facts to back the decision. 

'''STEP 4:''' Module owner must select a current Council member to fill the role seat until the next Chair rotation 

'''STEP 5:''' Module owner updates the portal and wiki 

'''STEP 6:''' Module must inform reps-mentors that the list of Council members has been updated 

===Removing/Replacing a Peer===
'''STEP 1:'''
The Module Owner informs the Peer that he/she is not fulfilling his/her responsibilities and that he/she has been relieved of his/his duties effective immediately. It is important to provide detailed explanation and hard facts to back the decision. 

'''STEP 2:'''
Module owner chooses a replacement. 

'''STEP 3:'''
Module owner updates the portal and wiki accordingly. 
Module Owner

[[Category:Remosop]]

Reps/SOPs/Dismissal

2015-02-27T16:32:16Z

Mrz:

{{remonav}}

This page explains the procedure to follow to remove a Rep, Mentor, Council Member or Peer from the Mozilla Reps program. If the Rep would like to step out the program voluntarily, please refer to [[ReMo/SOPs/Leaving|Leaving SOP]].

===Removing a Rep===
'''STEP 1:''' 
Mentor writes an email to reps-council@mozilla.com with '''[Dismissal Request]''' in the subject header, to inform Council that their mentee is not fulfilling his/her responsibilities and provides detailed documentation to back their claim. 

'''STEP 2:''' 
Council has 7 days to review claim and decide whether to : 
a) re-assign mentee to another Mentor 
OR 
b) remove mentee from the program 

'''STEP 3:''' 
* If a): the Council Chair must follow Mentor re-assignment procedure (https://wiki.mozilla.org/ReMo/SOPs/Mentoring/Reassigning) 
* If b): the Council Chair must inform the mentee directly by email providing detailed explanation for the Council's decision and granting 7 days to appeal decision.

Email example:

[mailto:example@domain.com?subject=Mozilla%20Reps%20Status&body=Dear%20%5BNAME%5D%2C%0A%0AAs%20part%20of%20its%20efforts%20to%20continuously%20improve%20the%20Reps%20program,%20the%20Council%20recently%0Aconducted%20a%20process%20to%20gather%20feedback%20from%20Mentors%20to%20identify%20areas%20of%0Aimprovement%2C%20fresh%20opportunities%20but%20also%20identify%20Reps%20who%20would%0Abenefit%20from%20being%20relieved%20from%20their%20duties.%0A%0AAfter%20a%20thorough%20and%20difficult%20review%20process%2C%20the%20Council%20agreed%20that%0Ait%20is%20better%20for%20you%20to%20return%20to%20being%20exclusively%20a%20Mozilla%0Acontributor.%20Indeed%2C%20the%20Council%20is%20confident%20you%20will%20be%20able%20to%0Acontinue%20contributing%20to%20the%20Mozilla%20program.%0A%0AYour%20responsibilities%20as%20Reps%20will%20official%20end%20on%20%5BDATE%5D%2C%20and%20your%0Aprofile%20page%20deactivated.%0A%0AThe%20Council%20would%20like%20to%20thank%20you%20for%20all%20your%20hard%20work%20as%20a%20Rep%20and%0Awish%20you%20continued%20success%20as%20a%20contributor.%20Should%20you%20have%20any%0Aquestions%20or%20wish%20to%20appeal%20this%20decision%2C%20please%20contact%20the%20Council%20in%20they%20next%207%20days.%20%0A%0ASincerely%2C%0A%0A%5BCHAIR%20NAME%5D%2C%0Aon%20behalf%20of%20the%20Reps%20Council Click here to launch mail]

<pre>
Dear [NAME],

As part of its efforts to continuously improve the Reps program, the Council recently
conducted a process to gather feedback from Mentors to identify areas of
improvement, fresh opportunities but also identify Reps who would
benefit from being relieved from their duties.

After a thorough and difficult review process, the Council has proposed that your
status as Rep be transitioned to Alumni. This means the expectations of this role are not longer applicable.

Your responsibilities as Reps will officially end on [DATE], and your
profile page deactivated.

The Council would like to thank you for all your hard work as a Rep and
wish you continued success as a valued Mozilla contributor. Should you have any
questions or wish to appeal this decision, please contact the Council in they next 7 days.

Sincerely,

[CHAIR NAME],
on behalf of the Reps Council
</pre>

'''STEP 4:''' 

Rep Admins will apply changes following [[ReMo/SOPs/Leaving#Reps_Admin_Actions|leaving actions]].

===Removing a Mentor===

'''STEP 1:''' 
Council chair writes an email to mentor to inform him/her that he/she is not fulfilling his/her responsibilities and their the mentor will be relieved of his/his duties as mentor. '''NB: It is critical to provide detailed explanation and hard facts to back the decision and make clear that the Mentor has 7 days to appeal the decision.''' 

'''STEP 2:''' 
After the appeal window is over and decision to remove still stands, the Council Chair must effectively remove the Mentor from the Mentors list on the portal and the wiki. 

'''STEP 3:''' 

===Removing/Replacing a Council Member===

'''STEP 1:''' 
Peers need to have a majority agreement that a Council member is not fulfilling his/her responsibilities 

'''STEP 2:''' 
If decision is unanimous, Peers must inform Module owner and ask him/her to take action 

'''STEP 3:''' 
Module owner writes an email to Council Member informing him/her that he/she is not fulfilling his/her responsibilities and that the Council Member has been relieved of his/his duties effective immediately. It is important to provide detailed explanation and hard facts to back the decision. 

'''STEP 4:''' 
Module owner must select a former Council member to fill the available seat until the next election 

'''STEP 5:''' 
Module owner updates the portal and wiki 

'''STEP 6:''' 
Module owner must inform reps-mentors that the list of Council members has been updated 

'''STEP 7:''' 
Module owner informs reps-general that the list of Council Members has been updated 

===Removing/Replacing the Council Chair===

'''STEP 1:''' 
Peers need to have a majority agreement that a Council Chair is not fulfilling his/her responsibilities 

'''STEP 2:''' Peers must inform Module owner and ask him/her to take action 

'''STEP 3:''' Module owner writes an email to Council Chair informing him/her that he/she is not fulfilling his/her responsibilities and that the Council Chair has been relieved of his/his duties effective immediately. It is important to provide detailed explanation and hard facts to back the decision. 

'''STEP 4:''' Module owner must select a current Council member to fill the role seat until the next Chair rotation 

'''STEP 5:''' Module owner updates the portal and wiki 

'''STEP 6:''' Module must inform reps-mentors that the list of Council members has been updated 

===Removing/Replacing a Peer===
'''STEP 1:'''
The Module Owner informs the Peer that he/she is not fulfilling his/her responsibilities and that he/she has been relieved of his/his duties effective immediately. It is important to provide detailed explanation and hard facts to back the decision. 

'''STEP 2:'''
Module owner chooses a replacement. 

'''STEP 3:'''
Module owner updates the portal and wiki accordingly. 
Module Owner

[[Category:Remosop]]

Reps/SOPs/Dismissal

2015-02-27T16:30:35Z

Mrz: Minor corrections in email template.

{{remonav}}

This page explains the procedure to follow to remove a Rep, Mentor, Council Member or Peer from the Mozilla Reps program. If the Rep would like to step out the program voluntarily, please refer to [[ReMo/SOPs/Leaving|Leaving SOP]].

===Removing a Rep===
'''STEP 1:''' 
Mentor writes an email to reps-council@mozilla.com with '''[Dismissal Request]''' in the subject header, to inform Council that their mentee is not fulfilling his/her responsibilities and provides detailed documentation to back their claim. 

'''STEP 2:''' 
Council has 7 days to review claim and decide whether to : 
a) re-assign mentee to another Mentor 
OR 
b) remove mentee from the program 

'''STEP 3:''' 
* If a): the Council Chair must follow Mentor re-assignment procedure (https://wiki.mozilla.org/ReMo/SOPs/Mentoring/Reassigning) 
* If b): the Council Chair must inform the mentee directly by email providing detailed explanation for the Council's decision and granting 7 days to appeal decision.

Email example:

[mailto:example@domain.com?subject=Mozilla%20Reps%20Status&body=Dear%20%5BNAME%5D%2C%0A%0AAs%20part%20of%20its%20efforts%20to%20continuously%20improve%20the%20Reps%20program%20the%20Council%20recently%0Aconducted%20a%20process%20to%20gather%20feedback%20from%20Mentors%20to%20identify%20areas%20of%0Aimprovement%2C%20fresh%20opportunities%20but%20also%20identify%20Reps%20who%20would%0Abenefit%20from%20being%20relieved%20from%20their%20duties.%0A%0AAfter%20a%20thorough%20and%20difficult%20review%20process%2C%20the%20Council%20agreed%20that%0Ait%20is%20better%20for%20you%20to%20return%20to%20being%20exclusively%20a%20Mozilla%0Acontributor.%20Indeed%2C%20the%20Council%20is%20confident%20you%20will%20be%20able%20to%0Acontinue%20contributing%20to%20the%20Mozilla%20program.%0A%0AYour%20responsibilities%20as%20Reps%20will%20official%20end%20on%20%5BDATE%5D%2C%20and%20your%0Aprofile%20page%20deactivated.%0A%0AThe%20Council%20would%20like%20to%20thank%20you%20for%20all%20your%20hard%20work%20as%20a%20Rep%20and%0Awish%20you%20continued%20success%20as%20a%20contributor.%20Should%20you%20have%20any%0Aquestions%20or%20wish%20to%20appeal%20this%20decision%2C%20please%20contact%20the%20Council%20in%20they%20next%207%20days.%20%0A%0ASincerely%2C%0A%0A%5BCHAIR%20NAME%5D%2C%0Aon%20behalf%20of%20the%20Reps%20Council Click here to launch mail]

<pre>
Dear [NAME],

As part of its efforts to continuously improve the Reps program, the Council recently
conducted a process to gather feedback from Mentors to identify areas of
improvement, fresh opportunities but also identify Reps who would
benefit from being relieved from their duties.

After a thorough and difficult review process, the Council has proposed that your
status as Rep be transitioned to Alumni. This means the expectations of this role are not longer applicable.

Your responsibilities as Reps will officially end on [DATE], and your
profile page deactivated.

The Council would like to thank you for all your hard work as a Rep and
wish you continued success as a valued Mozilla contributor. Should you have any
questions or wish to appeal this decision, please contact the Council in they next 7 days.

Sincerely,

[CHAIR NAME],
on behalf of the Reps Council
</pre>

'''STEP 4:''' 

Rep Admins will apply changes following [[ReMo/SOPs/Leaving#Reps_Admin_Actions|leaving actions]].

===Removing a Mentor===

'''STEP 1:''' 
Council chair writes an email to mentor to inform him/her that he/she is not fulfilling his/her responsibilities and their the mentor will be relieved of his/his duties as mentor. '''NB: It is critical to provide detailed explanation and hard facts to back the decision and make clear that the Mentor has 7 days to appeal the decision.''' 

'''STEP 2:''' 
After the appeal window is over and decision to remove still stands, the Council Chair must effectively remove the Mentor from the Mentors list on the portal and the wiki. 

'''STEP 3:''' 

===Removing/Replacing a Council Member===

'''STEP 1:''' 
Peers need to have a majority agreement that a Council member is not fulfilling his/her responsibilities 

'''STEP 2:''' 
If decision is unanimous, Peers must inform Module owner and ask him/her to take action 

'''STEP 3:''' 
Module owner writes an email to Council Member informing him/her that he/she is not fulfilling his/her responsibilities and that the Council Member has been relieved of his/his duties effective immediately. It is important to provide detailed explanation and hard facts to back the decision. 

'''STEP 4:''' 
Module owner must select a former Council member to fill the available seat until the next election 

'''STEP 5:''' 
Module owner updates the portal and wiki 

'''STEP 6:''' 
Module owner must inform reps-mentors that the list of Council members has been updated 

'''STEP 7:''' 
Module owner informs reps-general that the list of Council Members has been updated 

===Removing/Replacing the Council Chair===

'''STEP 1:''' 
Peers need to have a majority agreement that a Council Chair is not fulfilling his/her responsibilities 

'''STEP 2:''' Peers must inform Module owner and ask him/her to take action 

'''STEP 3:''' Module owner writes an email to Council Chair informing him/her that he/she is not fulfilling his/her responsibilities and that the Council Chair has been relieved of his/his duties effective immediately. It is important to provide detailed explanation and hard facts to back the decision. 

'''STEP 4:''' Module owner must select a current Council member to fill the role seat until the next Chair rotation 

'''STEP 5:''' Module owner updates the portal and wiki 

'''STEP 6:''' Module must inform reps-mentors that the list of Council members has been updated 

===Removing/Replacing a Peer===
'''STEP 1:'''
The Module Owner informs the Peer that he/she is not fulfilling his/her responsibilities and that he/she has been relieved of his/his duties effective immediately. It is important to provide detailed explanation and hard facts to back the decision. 

'''STEP 2:'''
Module owner chooses a replacement. 

'''STEP 3:'''
Module owner updates the portal and wiki accordingly. 
Module Owner

[[Category:Remosop]]

IT/Community/WG/WordpressMS

2015-02-26T00:01:00Z

Mrz: Mrz moved page IT/Community/WG/WordpressMS to IT/Community/WG/WPaaS: name change

#REDIRECT [[IT/Community/WG/WPaaS]]

IT/Community

2014-12-18T17:28:51Z

Mrz:

= Overview =
Mozilla Community Sysadmins are individuals who are passionate about Mozilla, the open web and are passionate and knowledgeable about running websites and services (at scale!) to help support the Mozilla Community.

Community is the backbone of the Mozilla Project.

We are a global pack of Sysadmins supporting the Mozilla Community and, importantly, mentoring & teaching others with practical technical skills in hosting and running production websites and services, configuration management (puppet/chef), monitoring/alerting & oncall pager.

= Getting Involved =
We need you! Give us a shout out on one of the following communication channels and let us know you'd like to help!

* Join the discussion on [https://discourse.mozilla-community.org/category/community-it Discourse]
* Go to our IRC channel: [irc://irc.mozilla.org/%23communityit #CommunityIT on irc.mozilla.org]
* Join our weekly call

== Modules ==

We operate under a module system. A module is a discrete unit of code or activity. An owner is the person in charge of a module or sub-module. A peer is a person whom the owner has appointed to help them. A module may have multiple peers and, very occasionally, multiple owners.

* [[IT/Community/WG/Badgus|Badg.us]]
* [[IT/Community/WG/MCSHosting|Mozilla Communities Hosting (MCS)]]
* [[IT/Community/WG/Discourse|Discourse]]
* [[IT/Community/WG/WordpressMS|Multi-tenant WordPress "As a Service"]]
* [[IT/Community/WG/Infrastructure|Infrastructure]]

=== Archived Modules ===
These modules are no longer maintained, but their information is retained for historical purposes.

* [[IT/Community/WG/Phabricator|Phabricator]]

== Weekly Calls ==
{| class="wikitable"
|-
! Meeting !! Date & Time !! Meeting Notes
|-
| Bug/Action Triage || Weekly. [http://arewemeetingyet.com/Los%20Angeles/2014-11-06/09:00/w/Community%20Sysadmin%20Triage Thursdays @ 900 Pacific] || [https://communityit.etherpad.mozilla.org/Meeting Etherpad]
|-
| Infrastructure || Weekly. [http://arewemeetingyet.com/Los%20Angeles/2014-10-13/09:00/w/Community%20Sysadmin%20Infrastructure Mondays @ 930 Pacific] || [https://communityit.etherpad.mozilla.org/Meeting-Infrastructure Etherpad]
|-
|}

=== '''Meeting Agenda & Notes''' ===
* Upcoming/Current (look at revision history for older meetings)
** [https://communityit.etherpad.mozilla.org/Meeting Etherpad]

* '''Past Meetings'''
** [https://wiki.mozilla.org/IT/Community/Notes/2014-10-09 October 09 2014]
** [https://wiki.mozilla.org/IT/Community/Notes/2013-10-18 October 18 2013]
** [https://wiki.mozilla.org/IT/Community/Notes/2013-09-06 September 6 2013]
** [https://wiki.mozilla.org/IT/Community/Notes/2013-08-23 August 23 2013]
** [https://wiki.mozilla.org/IT/Community/Notes/2013-08-30 August 30 2013]

= Leadership and Contact Info =

* Project Manager and main point of contact: [https://mozillians.org/en-US/u/Kensie/ Majken "Kensie" Connor]

IT/Community

2014-12-05T19:59:08Z

Mrz:

= Overview =
Mozilla Community Sysadmins are individuals who are passionate about Mozilla, the open web and are passionate and knowledge about running websites and services (at scale!) to help support the Mozilla Community.

Community is the backbone of the Mozilla Project.

We are a global pack of Sysadmins supporting the Mozilla Community and, importantly, mentoring & teaching others with practical technical skills in hosting and running production websites and services, configuration management (puppet/chef), monitoring/alerting & oncall pager.

= Getting Involved =
We need you! Give us a shout out on one of the following communication channels and let us know you'd like to help!

* Join the discussion on [https://discourse.mozilla-community.org/category/community-it Discourse]
* Go to our IRC channel: [irc://irc.mozilla.org/%23communityit #CommunityIT on irc.mozilla.org]
* Join our weekly call

== Modules ==

We operate under a module system. A module is a discrete unit of code or activity. An owner is the person in charge of a module or sub-module. A peer is a person whom the owner has appointed to help them. A module may have multiple peers and, very occasionally, multiple owners.

* [[IT/Community/WG/Badgus|Badg.us]]
* [[IT/Community/WG/MCSHosting|Mozilla Communities Hosting (MCS)]]
* [[IT/Community/WG/Discourse|Discourse]]
* [[IT/Community/WG/WordpressMS|Multi-tenant WordPress "As a Service"]]
* [[IT/Community/WG/Infrastructure|Infrastructure]]

=== Archived Modules ===
These modules are no longer maintained, but their information is retained for historical purposes.

* [[IT/Community/WG/Phabricator|Phabricator]]

== Weekly Calls ==
{| class="wikitable"
|-
! Meeting !! Date & Time !! Meeting Notes
|-
| Bug/Action Triage || Weekly. [http://arewemeetingyet.com/Los%20Angeles/2014-11-06/09:00/w/Community%20Sysadmin%20Triage Thursdays @ 900 Pacific] || [https://communityit.etherpad.mozilla.org/Meeting Etherpad]
|-
| Infrastructure || Weekly. [http://arewemeetingyet.com/Los%20Angeles/2014-10-13/09:00/w/Community%20Sysadmin%20Infrastructure Mondays @ 930 Pacific] || [https://communityit.etherpad.mozilla.org/Meeting-Infrastructure Etherpad]
|-
|}

=== '''Meeting Agenda & Notes''' ===
* Upcoming/Current (look at revision history for older meetings)
** [https://communityit.etherpad.mozilla.org/Meeting Etherpad]

* '''Past Meetings'''
** [https://wiki.mozilla.org/IT/Community/Notes/2014-10-09 October 09 2014]
** [https://wiki.mozilla.org/IT/Community/Notes/2013-10-18 October 18 2013]
** [https://wiki.mozilla.org/IT/Community/Notes/2013-09-06 September 6 2013]
** [https://wiki.mozilla.org/IT/Community/Notes/2013-08-23 August 23 2013]
** [https://wiki.mozilla.org/IT/Community/Notes/2013-08-30 August 30 2013]

= Leadership and Contact Info =

* Project Manager and main point of contact: [https://mozillians.org/en-US/u/Kensie/ Majken "Kensie" Connor]

WeeklyUpdates/2014-11-10

2014-11-10T18:02:33Z

Mrz: /* Friends of Mozilla Friends of Mozilla */

{{WeeklyUpdateNav}}
<div style="clear:both; border: 4px solid rgb(40, 40, 40); text-align:center; padding: 2px; background: #FFFFCC; border-collapse: separate; -moz-border-radius: 10px; margin-top:20px;">
<big>'''Today's project call is all about celebrating 10 years of Firefox!'''
[[File:Firefox logo-only RGB.png|175px|center]]
'''The format of the call for today will be different. ''No need to fill in the wiki.'''''</big>
</div>

{{conf|8600}}

__TOC__

= All-hands Status Meeting Agenda =

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

== Friends of Mozilla [[Image:Tree.gif|Friends of Mozilla]] ==
Huge thanks to Community IT: [https://mozillians.org/en-US/u/yalam96/ Yousef Alam], [https://mozillians.org/en-US/u/scottlee/ Scott Lee], & [https://mozillians.org/en-US/u/mrz/ mrz] for their amazing work (and continued support and [http://health.mozilla-community.org/ monitoring]) setting up Mozilla Guides Discourse in time to launch with 'Get Involved Page'.

== Upcoming Events ==

=== This Week ===

=== Monday, {{#time:d F|{{SUBPAGENAME}}}} ===

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

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

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

* 10:00 AM Pacific / 18:00 UTC: Grow Mozilla discussion -- a forum for discussing community building at Mozilla
** [[Grow/Meeting_11_13_14|Agenda and dial-in information]] (feel free to add items to the agenda)

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

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

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

=== Next Week ===

== Project Status Updates (voice updates) ==

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

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

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

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

=== Webmaker ===
''Speaker Location:''

=== Mozilla Communities ===
''Speaker Location:''

== Speakers ==

The limit is 3 minutes per speaker. It's like a lightning talk, but don't feel that you have to have slides in order to make a presentation. If you plan on showing a video, you need to contact the Air Mozilla team before the day of the meeting or you will be deferred to the next week.

{| class="fullwidth-table wikitable"
|-
! [https://mozillians.org/u/USERNAME Presenter]
! Title
! Topic
! Location
! Share?
! Media
! More Details
|-
| Who Are You?
| What Do You Do?
| What are you going to talk about?
| Where are you presenting from? (Moz Space, your house, space)
| Will you be sharing your screen? (yes/no, other info)
| Links to slides or images you want displayed on screen
| Link to where audience can find out more information
|-
|}

= Roundtable =

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

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

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

|-
|}

= Welcome! =

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

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

|-
|}

== Introducing New Hires ==
{| class="fullwidth-table wikitable"
|-
! New Hire
! Introduced by
! Speaker location
! New Hire location
! Will be working on
|-
| ''Who is the new hire?''
| ''Who will be introducing that person?''
| ''Where is the introducer?''
| ''Where will the new person be working from?''
| ''What will the new person be working on?''
|-
| Richard Weiss
| Corey Sheilds
| Mountain View
| San Francisco
| AWS Solutions Architect
|-
| Nihan Kamal
| John Bernard
| Remote
| Remote
| Channel Marketing Manager
|-
| Linda Ypulong
| Derek Moore
| Mountain View
| San Francisco
| Ops Center Manager
|-
|-
|}

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

|-
|}

= <meta> =

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

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

=== Firefox ===

=== Platform ===

=== Cloud Services ===

=== Messaging ===

=== Mobile ===

=== IT ===

=== Release Engineering ===

=== QA ===

==== Test Execution ====

==== WebQA ====

==== QA Community ====

=== Automation & Tools ===

=== Security ===

=== Engagement ===

* [https://docs.google.com/a/mozilla.com/spreadsheets/d/1X5kUBkEAicEe2unDaaLGTYzAJbphWFoaJYBTasHrcHQ/edit#gid=1764494528 Engagement's Active Project Dashboard]

==== PR ====

==== Events ====

==== Social Support ====

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

WeeklyUpdates/2014-11-10

2014-11-10T17:54:17Z

Mrz: /* Friends of Mozilla Friends of Mozilla */

{{WeeklyUpdateNav}}
<div style="clear:both; border: 4px solid rgb(40, 40, 40); text-align:center; padding: 2px; background: #FFFFCC; border-collapse: separate; -moz-border-radius: 10px; margin-top:20px;">
<big>'''Today's project call is all about celebrating 10 years of Firefox!'''
[[File:Firefox logo-only RGB.png|175px|center]]
'''The format of the call for today will be different. ''No need to fill in the wiki.'''''</big>
</div>

{{conf|8600}}

__TOC__

= All-hands Status Meeting Agenda =

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

== Friends of Mozilla [[Image:Tree.gif|Friends of Mozilla]] ==
Huge thanks to Community IT: [https://mozillians.org/en-US/u/yalam96/ Yousef Alam], [https://mozillians.org/en-US/u/scottlee/ Scott Lee], & [https://mozillians.org/en-US/u/mrz/ mrz] for their amazing work (and continued support and monitoring) setting up Mozilla Guides Discourse in time to launch with 'Get Involved Page'.

== Upcoming Events ==

=== This Week ===

=== Monday, {{#time:d F|{{SUBPAGENAME}}}} ===

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

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

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

* 10:00 AM Pacific / 18:00 UTC: Grow Mozilla discussion -- a forum for discussing community building at Mozilla
** [[Grow/Meeting_11_13_14|Agenda and dial-in information]] (feel free to add items to the agenda)

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

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

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

=== Next Week ===

== Project Status Updates (voice updates) ==

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

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

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

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

=== Webmaker ===
''Speaker Location:''

=== Mozilla Communities ===
''Speaker Location:''

== Speakers ==

The limit is 3 minutes per speaker. It's like a lightning talk, but don't feel that you have to have slides in order to make a presentation. If you plan on showing a video, you need to contact the Air Mozilla team before the day of the meeting or you will be deferred to the next week.

{| class="fullwidth-table wikitable"
|-
! [https://mozillians.org/u/USERNAME Presenter]
! Title
! Topic
! Location
! Share?
! Media
! More Details
|-
| Who Are You?
| What Do You Do?
| What are you going to talk about?
| Where are you presenting from? (Moz Space, your house, space)
| Will you be sharing your screen? (yes/no, other info)
| Links to slides or images you want displayed on screen
| Link to where audience can find out more information
|-
|}

= Roundtable =

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

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

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

|-
|}

= Welcome! =

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

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

|-
|}

== Introducing New Hires ==
{| class="fullwidth-table wikitable"
|-
! New Hire
! Introduced by
! Speaker location
! New Hire location
! Will be working on
|-
| ''Who is the new hire?''
| ''Who will be introducing that person?''
| ''Where is the introducer?''
| ''Where will the new person be working from?''
| ''What will the new person be working on?''
|-
| Richard Weiss
| Corey Sheilds
| Mountain View
| San Francisco
| AWS Solutions Architect
|-
| Nihan Kamal
| John Bernard
| Remote
| Remote
| Channel Marketing Manager
|-
| Linda Ypulong
| Derek Moore
| San Francisco
| Mountain View
| Ops Center Manager
|-
|-
|}

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

|-
|}

= <meta> =

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

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

=== Firefox ===

=== Platform ===

=== Cloud Services ===

=== Messaging ===

=== Mobile ===

=== IT ===

=== Release Engineering ===

=== QA ===

==== Test Execution ====

==== WebQA ====

==== QA Community ====

=== Automation & Tools ===

=== Security ===

=== Engagement ===

* [https://docs.google.com/a/mozilla.com/spreadsheets/d/1X5kUBkEAicEe2unDaaLGTYzAJbphWFoaJYBTasHrcHQ/edit#gid=1764494528 Engagement's Active Project Dashboard]

==== PR ====

==== Events ====

==== Social Support ====

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

WeeklyUpdates/2014-11-10

2014-11-10T17:52:57Z

Mrz: /* Friends of Mozilla Friends of Mozilla */

{{WeeklyUpdateNav}}
<div style="clear:both; border: 4px solid rgb(40, 40, 40); text-align:center; padding: 2px; background: #FFFFCC; border-collapse: separate; -moz-border-radius: 10px; margin-top:20px;">
<big>'''Today's project call is all about celebrating 10 years of Firefox!'''
[[File:Firefox logo-only RGB.png|175px|center]]
'''The format of the call for today will be different. ''No need to fill in the wiki.'''''</big>
</div>

{{conf|8600}}

__TOC__

= All-hands Status Meeting Agenda =

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

== Friends of Mozilla [[Image:Tree.gif|Friends of Mozilla]] ==
Huge thanks to Community IT: [https://mozillians.org/en-US/u/yalam96/ Yousef Alam], [https://mozillians.org/en-US/u/scottlee/ Scott Lee], [https://mozillians.org/en-US/u/mrz/ mrz] for their amazing work(and continued support and monitoring) setting up Mozilla Guides Discourse in time to launch with 'Get Involved Page'.

== Upcoming Events ==

=== This Week ===

=== Monday, {{#time:d F|{{SUBPAGENAME}}}} ===

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

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

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

* 10:00 AM Pacific / 18:00 UTC: Grow Mozilla discussion -- a forum for discussing community building at Mozilla
** [[Grow/Meeting_11_13_14|Agenda and dial-in information]] (feel free to add items to the agenda)

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

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

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

=== Next Week ===

== Project Status Updates (voice updates) ==

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

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

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

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

=== Webmaker ===
''Speaker Location:''

=== Mozilla Communities ===
''Speaker Location:''

== Speakers ==

The limit is 3 minutes per speaker. It's like a lightning talk, but don't feel that you have to have slides in order to make a presentation. If you plan on showing a video, you need to contact the Air Mozilla team before the day of the meeting or you will be deferred to the next week.

{| class="fullwidth-table wikitable"
|-
! [https://mozillians.org/u/USERNAME Presenter]
! Title
! Topic
! Location
! Share?
! Media
! More Details
|-
| Who Are You?
| What Do You Do?
| What are you going to talk about?
| Where are you presenting from? (Moz Space, your house, space)
| Will you be sharing your screen? (yes/no, other info)
| Links to slides or images you want displayed on screen
| Link to where audience can find out more information
|-
|}

= Roundtable =

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

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

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

|-
|}

= Welcome! =

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

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

|-
|}

== Introducing New Hires ==
{| class="fullwidth-table wikitable"
|-
! New Hire
! Introduced by
! Speaker location
! New Hire location
! Will be working on
|-
| ''Who is the new hire?''
| ''Who will be introducing that person?''
| ''Where is the introducer?''
| ''Where will the new person be working from?''
| ''What will the new person be working on?''
|-
| Richard Weiss
| Corey Sheilds
| Mountain View
| San Francisco
| AWS Solutions Architect
|-
| Nihan Kamal
| John Bernard
| Remote
| Remote
| Channel Marketing Manager
|-
|-
|}

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

|-
|}

= <meta> =

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

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

=== Firefox ===

=== Platform ===

=== Cloud Services ===

=== Messaging ===

=== Mobile ===

=== IT ===

=== Release Engineering ===

=== QA ===

==== Test Execution ====

==== WebQA ====

==== QA Community ====

=== Automation & Tools ===

=== Security ===

=== Engagement ===

* [https://docs.google.com/a/mozilla.com/spreadsheets/d/1X5kUBkEAicEe2unDaaLGTYzAJbphWFoaJYBTasHrcHQ/edit#gid=1764494528 Engagement's Active Project Dashboard]

==== PR ====

==== Events ====

==== Social Support ====

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

WeeklyUpdates/2014-10-20

2014-10-20T01:15:42Z

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

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

__TOC__

= All-hands Status Meeting Agenda =

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

== Friends of Mozilla [[Image:Tree.gif|Friends of Mozilla]] ==

Najlepša hvala to Matjaž Horvat for contributing the Slovenian localization of the Firefox Activations Directory.

== Upcoming Events ==

=== This Week ===

=== Monday, {{#time:d F|{{SUBPAGENAME}}}} ===

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

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

=== Thursday, {{#time:d F|{{SUBPAGENAME}} +3 days}} ===
* [https://etherpad.mozilla.org/b2g-qa-bug-bash-2014-10-23 Bug Bash on Firefox OS v2.1] Please join us by contributing as little as 15 minutes of your time.
* Discourse maintenance @ 2200 UTC (3p US/Pacific). ''Duration 10 minutes''. See [http://health.mozilla-community.org health.mozilla-community.org] for more details.
** Change our email delivery service from Mandrill to Amazon SES ({{bug|1080703}})
** Add email addresses to categories ({{bug|1081738}})
** Change homepage to category view ({{bug|1081740}})

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

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

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

=== Next Week ===

== Project Status Updates (voice updates) ==

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

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

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

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

=== Webmaker ===
''Speaker Location:''

=== Mozilla Communities ===
''Speaker Location:''

== Speakers ==

The limit is 3 minutes per speaker. It's like a lightning talk, but don't feel that you have to have slides in order to make a presentation. If you plan on showing a video, you need to contact the Air Mozilla team before the day of the meeting or you will be deferred to the next week.

{| class="fullwidth-table wikitable"
|-
! [https://mozillians.org/u/USERNAME Presenter]
! Title
! Topic
! Location
! Share?
! Media
! More Details
|-
| Who Are You?
| What Do You Do?
| What are you going to talk about?
| Where are you presenting from? (Moz Space, your house, space)
| Will you be sharing your screen? (yes/no, other info)
| Links to slides or images you want displayed on screen
| Link to where audience can find out more information
|-
|-
| Jen Bertsch, ADC, and Greg Jost
| Brand stuff! And news editor
| Optimally redesigned web pages, TOS, and #embraceopen
| Mountain View, NYC, Paris
| No
| tbd
| #embraceopen
|-
|}

= Roundtable =

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

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

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

|-
|}

= Welcome! =

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

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

|-
|}

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

|-
|}

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

|-
|}

= <meta> =

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

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

=== Firefox ===

=== Platform ===

=== Cloud Services ===

=== Messaging ===

=== Mobile ===

=== IT ===

=== Release Engineering ===

=== QA ===

==== Test Execution ====

==== WebQA ====

==== QA Community ====

=== Automation & Tools ===

=== Security ===

=== Engagement ===

* [https://docs.google.com/a/mozilla.com/spreadsheets/d/1X5kUBkEAicEe2unDaaLGTYzAJbphWFoaJYBTasHrcHQ/edit#gid=1764494528 Engagement's Active Project Dashboard]

==== PR ====

==== Events ====

==== Social Support ====

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

WeeklyUpdates/2014-10-20

2014-10-20T01:15:21Z

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

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

__TOC__

= All-hands Status Meeting Agenda =

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

== Friends of Mozilla [[Image:Tree.gif|Friends of Mozilla]] ==

Najlepša hvala to Matjaž Horvat for contributing the Slovenian localization of the Firefox Activations Directory.

== Upcoming Events ==

=== This Week ===

=== Monday, {{#time:d F|{{SUBPAGENAME}}}} ===

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

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

=== Thursday, {{#time:d F|{{SUBPAGENAME}} +3 days}} ===
* [https://etherpad.mozilla.org/b2g-qa-bug-bash-2014-10-23 Bug Bash on Firefox OS v2.1] Please join us by contributing as little as 15 minutes of your time.
* Discourse maintenance @ 2200 UTC (3p US/Pacific). ''Duration 10 minutes''. See [http://health.mozilla-community.org health.mozilla-community.org] for more details.
** Change our email delivery service from Mandrill to Amazon SES ({{bug|1080703}}_
** Add email addresses to categories ({{bug|1081738}})
** Change homepage to category view ({{bug|1081740}})

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

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

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

=== Next Week ===

== Project Status Updates (voice updates) ==

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

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

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

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

=== Webmaker ===
''Speaker Location:''

=== Mozilla Communities ===
''Speaker Location:''

== Speakers ==

The limit is 3 minutes per speaker. It's like a lightning talk, but don't feel that you have to have slides in order to make a presentation. If you plan on showing a video, you need to contact the Air Mozilla team before the day of the meeting or you will be deferred to the next week.

{| class="fullwidth-table wikitable"
|-
! [https://mozillians.org/u/USERNAME Presenter]
! Title
! Topic
! Location
! Share?
! Media
! More Details
|-
| Who Are You?
| What Do You Do?
| What are you going to talk about?
| Where are you presenting from? (Moz Space, your house, space)
| Will you be sharing your screen? (yes/no, other info)
| Links to slides or images you want displayed on screen
| Link to where audience can find out more information
|-
|-
| Jen Bertsch, ADC, and Greg Jost
| Brand stuff! And news editor
| Optimally redesigned web pages, TOS, and #embraceopen
| Mountain View, NYC, Paris
| No
| tbd
| #embraceopen
|-
|}

= Roundtable =

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

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

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

|-
|}

= Welcome! =

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

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

|-
|}

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

|-
|}

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

|-
|}

= <meta> =

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

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

=== Firefox ===

=== Platform ===

=== Cloud Services ===

=== Messaging ===

=== Mobile ===

=== IT ===

=== Release Engineering ===

=== QA ===

==== Test Execution ====

==== WebQA ====

==== QA Community ====

=== Automation & Tools ===

=== Security ===

=== Engagement ===

* [https://docs.google.com/a/mozilla.com/spreadsheets/d/1X5kUBkEAicEe2unDaaLGTYzAJbphWFoaJYBTasHrcHQ/edit#gid=1764494528 Engagement's Active Project Dashboard]

==== PR ====

==== Events ====

==== Social Support ====

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

WeeklyUpdates/2014-10-20

2014-10-20T00:48:05Z

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

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

__TOC__

= All-hands Status Meeting Agenda =

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

== Friends of Mozilla [[Image:Tree.gif|Friends of Mozilla]] ==

Najlepša hvala to Matjaž Horvat for contributing the Slovenian localization of the Firefox Activations Directory.

== Upcoming Events ==

=== This Week ===

=== Monday, {{#time:d F|{{SUBPAGENAME}}}} ===

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

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

=== Thursday, {{#time:d F|{{SUBPAGENAME}} +3 days}} ===
* [https://etherpad.mozilla.org/b2g-qa-bug-bash-2014-10-23 Bug Bash on Firefox OS v2.1] Please join us by contributing as little as 15 minutes of your time.
* Discourse maintenance @ 2200 UTC (3p US/Pacific). ''Duration 10 minutes''. See [http://health.mozilla-community.org health.mozilla-community.org] for more details.
** {{bug|1080703}} ~ Change our email delivery service from Mandrill to Amazon SES
** {{bug|1081738}} ~ Add email addresses to categories
** {{bug|1081740}} ~ Change homepage to category view

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

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

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

=== Next Week ===

== Project Status Updates (voice updates) ==

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

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

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

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

=== Webmaker ===
''Speaker Location:''

=== Mozilla Communities ===
''Speaker Location:''

== Speakers ==

The limit is 3 minutes per speaker. It's like a lightning talk, but don't feel that you have to have slides in order to make a presentation. If you plan on showing a video, you need to contact the Air Mozilla team before the day of the meeting or you will be deferred to the next week.

{| class="fullwidth-table wikitable"
|-
! [https://mozillians.org/u/USERNAME Presenter]
! Title
! Topic
! Location
! Share?
! Media
! More Details
|-
| Who Are You?
| What Do You Do?
| What are you going to talk about?
| Where are you presenting from? (Moz Space, your house, space)
| Will you be sharing your screen? (yes/no, other info)
| Links to slides or images you want displayed on screen
| Link to where audience can find out more information
|-
|-
| Jen Bertsch, ADC, and Greg Jost
| Brand stuff! And news editor
| Optimally redesigned web pages, TOS, and #embraceopen
| Mountain View, NYC, Paris
| No
| tbd
| #embraceopen
|-
|}

= Roundtable =

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

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

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

|-
|}

= Welcome! =

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

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

|-
|}

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

|-
|}

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

|-
|}

= <meta> =

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

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

=== Firefox ===

=== Platform ===

=== Cloud Services ===

=== Messaging ===

=== Mobile ===

=== IT ===

=== Release Engineering ===

=== QA ===

==== Test Execution ====

==== WebQA ====

==== QA Community ====

=== Automation & Tools ===

=== Security ===

=== Engagement ===

* [https://docs.google.com/a/mozilla.com/spreadsheets/d/1X5kUBkEAicEe2unDaaLGTYzAJbphWFoaJYBTasHrcHQ/edit#gid=1764494528 Engagement's Active Project Dashboard]

==== PR ====

==== Events ====

==== Social Support ====

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

WeeklyUpdates/2014-10-20

2014-10-20T00:46:15Z

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

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

__TOC__

= All-hands Status Meeting Agenda =

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

== Friends of Mozilla [[Image:Tree.gif|Friends of Mozilla]] ==

Najlepša hvala to Matjaž Horvat for contributing the Slovenian localization of the Firefox Activations Directory.

== Upcoming Events ==

=== This Week ===

=== Monday, {{#time:d F|{{SUBPAGENAME}}}} ===

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

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

=== Thursday, {{#time:d F|{{SUBPAGENAME}} +3 days}} ===
* [https://etherpad.mozilla.org/b2g-qa-bug-bash-2014-10-23 Bug Bash on Firefox OS v2.1] Please join us by contributing as little as 15 minutes of your time.
* Discourse maintenance @ 2200 UTC (3p US/Pacific). See [http://health.mozilla-community.org health.mozilla-community.org] for more details.
** {{bug|1080703}} ~ Change our email delivery service from Mandrill to Amazon SES
** {{bug|1081738}} ~ Add email addresses to categories
** {{bug|1081740}} ~ Change homepage to category view

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

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

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

=== Next Week ===

== Project Status Updates (voice updates) ==

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

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

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

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

=== Webmaker ===
''Speaker Location:''

=== Mozilla Communities ===
''Speaker Location:''

== Speakers ==

The limit is 3 minutes per speaker. It's like a lightning talk, but don't feel that you have to have slides in order to make a presentation. If you plan on showing a video, you need to contact the Air Mozilla team before the day of the meeting or you will be deferred to the next week.

{| class="fullwidth-table wikitable"
|-
! [https://mozillians.org/u/USERNAME Presenter]
! Title
! Topic
! Location
! Share?
! Media
! More Details
|-
| Who Are You?
| What Do You Do?
| What are you going to talk about?
| Where are you presenting from? (Moz Space, your house, space)
| Will you be sharing your screen? (yes/no, other info)
| Links to slides or images you want displayed on screen
| Link to where audience can find out more information
|-
|-
| Jen Bertsch, ADC, and Greg Jost
| Brand stuff! And news editor
| Optimally redesigned web pages, TOS, and #embraceopen
| Mountain View, NYC, Paris
| No
| tbd
| #embraceopen
|-
|}

= Roundtable =

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

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

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

|-
|}

= Welcome! =

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

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

|-
|}

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

|-
|}

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

|-
|}

= <meta> =

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

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

=== Firefox ===

=== Platform ===

=== Cloud Services ===

=== Messaging ===

=== Mobile ===

=== IT ===

=== Release Engineering ===

=== QA ===

==== Test Execution ====

==== WebQA ====

==== QA Community ====

=== Automation & Tools ===

=== Security ===

=== Engagement ===

* [https://docs.google.com/a/mozilla.com/spreadsheets/d/1X5kUBkEAicEe2unDaaLGTYzAJbphWFoaJYBTasHrcHQ/edit#gid=1764494528 Engagement's Active Project Dashboard]

==== PR ====

==== Events ====

==== Social Support ====

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

WeeklyUpdates/2014-10-20

2014-10-20T00:42:39Z

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

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

__TOC__

= All-hands Status Meeting Agenda =

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

== Friends of Mozilla [[Image:Tree.gif|Friends of Mozilla]] ==

Najlepša hvala to Matjaž Horvat for contributing the Slovenian localization of the Firefox Activations Directory.

== Upcoming Events ==

=== This Week ===

=== Monday, {{#time:d F|{{SUBPAGENAME}}}} ===

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

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

=== Thursday, {{#time:d F|{{SUBPAGENAME}} +3 days}} ===
* [https://etherpad.mozilla.org/b2g-qa-bug-bash-2014-10-23 Bug Bash on Firefox OS v2.1] Please join us by contributing as little as 15 minutes of your time.
* Discourse maintenance. See [http://health.mozilla-community.org health.mozilla-community.org] for more details.
** {bug 1080703}
** {bug 1081738}
** {but 1081740 }

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

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

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

=== Next Week ===

== Project Status Updates (voice updates) ==

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

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

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

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

=== Webmaker ===
''Speaker Location:''

=== Mozilla Communities ===
''Speaker Location:''

== Speakers ==

The limit is 3 minutes per speaker. It's like a lightning talk, but don't feel that you have to have slides in order to make a presentation. If you plan on showing a video, you need to contact the Air Mozilla team before the day of the meeting or you will be deferred to the next week.

{| class="fullwidth-table wikitable"
|-
! [https://mozillians.org/u/USERNAME Presenter]
! Title
! Topic
! Location
! Share?
! Media
! More Details
|-
| Who Are You?
| What Do You Do?
| What are you going to talk about?
| Where are you presenting from? (Moz Space, your house, space)
| Will you be sharing your screen? (yes/no, other info)
| Links to slides or images you want displayed on screen
| Link to where audience can find out more information
|-
|-
| Jen Bertsch, ADC, and Greg Jost
| Brand stuff! And news editor
| Optimally redesigned web pages, TOS, and #embraceopen
| Mountain View, NYC, Paris
| No
| tbd
| #embraceopen
|-
|}

= Roundtable =

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

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

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

|-
|}

= Welcome! =

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

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

|-
|}

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

|-
|}

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

|-
|}

= <meta> =

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

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

=== Firefox ===

=== Platform ===

=== Cloud Services ===

=== Messaging ===

=== Mobile ===

=== IT ===

=== Release Engineering ===

=== QA ===

==== Test Execution ====

==== WebQA ====

==== QA Community ====

=== Automation & Tools ===

=== Security ===

=== Engagement ===

* [https://docs.google.com/a/mozilla.com/spreadsheets/d/1X5kUBkEAicEe2unDaaLGTYzAJbphWFoaJYBTasHrcHQ/edit#gid=1764494528 Engagement's Active Project Dashboard]

==== PR ====

==== Events ====

==== Social Support ====

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

IT/Community

2014-10-17T06:45:04Z

Mrz:

= Overview =
Mozilla Community Sysadmins are individuals who are passionate about Mozilla, the open web and are passionate and knowledge about running websites and services (at scale!) to help support the Mozilla Community.

Community is the backbone of the Mozilla Project.

We are a global pack of Sysadmins supporting the Mozilla Community and, importantly, mentoring & teaching others with practical technical skills in hosting and running production websites and services, configuration management (puppet/chef), monitoring/alerting & oncall pager.

= Getting Involved =
We need you! Give us a shout out on one of the following communication channels and let us know you'd like to help!

* Join the discussion on [https://discourse.mozilla-community.org/category/community-it Discourse]
* Go to our IRC channel: [irc://irc.mozilla.org/%23communityit #CommunityIT on irc.mozilla.org]
* Join our weekly call

== Modules ==

We operate under a module system. A module is a discrete unit of code or activity. An owner is the person in charge of a module or sub-module. A peer is a person whom the owner has appointed to help them. A module may have multiple peers and, very occasionally, multiple owners.

* [[IT/Community/WG/Badgus|Badg.us]]
* [[IT/Community/WG/MCSHosting|Mozilla Communities Hosting (MCS)]]
* [[IT/Community/WG/Discourse|Discourse]]
* [[IT/Community/WG/WordpressMS|WordPress Multisite]]
* [[IT/Community/WG/Infrastructure|Infrastructure]]

=== Archived Modules ===
These modules are no longer maintained, but their information is retained for historical purposes.

* [[IT/Community/WG/Phabricator|Phabricator]]

== Weekly Calls ==
{| class="wikitable"
|-
! Meeting !! Date & Time !! Meeting Notes
|-
| Bug Triage || Weekly. [http://arewemeetingyet.com/Los%20Angeles/2014-10-15/09:00/w/Community%20Sysadmin%20Bug%20Triage Wednesdays @ 1600 UTC] || [https://communityit.etherpad.mozilla.org/Meeting Etherpad]
|-
| Infrastructure || Weekly. [http://arewemeetingyet.com/Los%20Angeles/2014-10-13/09:00/w/Community%20Sysadmin%20Infrastructure Mondays @ 1630 UTC] || [https://communityit.etherpad.mozilla.org/Meeting-Infrastructure Etherpad]
|-
|}

=== '''Meeting Agenda & Notes''' ===
* Upcoming/Current (look at revision history for older meetings)
** [https://communityit.etherpad.mozilla.org/Meeting Etherpad]

* '''Past Meetings'''
** [https://wiki.mozilla.org/IT/Community/Notes/2014-10-09 October 09 2014]
** [https://wiki.mozilla.org/IT/Community/Notes/2013-10-18 October 18 2013]
** [https://wiki.mozilla.org/IT/Community/Notes/2013-09-06 September 6 2013]
** [https://wiki.mozilla.org/IT/Community/Notes/2013-08-23 August 23 2013]
** [https://wiki.mozilla.org/IT/Community/Notes/2013-08-30 August 30 2013]

IT/Community

2014-10-17T06:39:28Z

Mrz: /* Weekly Calls */

= Overview =
Mozilla Community Sysadmins are individuals who are passionate about Mozilla, the open web and are passionate and knowledge about running websites and services (at scale!) to help support the Mozilla Community.

Community is the backbone of the Mozilla Project.

We are a global pack of Sysadmins supporting the Mozilla Community and, importantly, mentoring & teaching others with practical technical skills in hosting and running production websites and services, configuration management (puppet/chef), monitoring/alerting & oncall pager.

= Getting Involved =
We need you! Give us a shout out on one of the following communication channels and let us know you'd like to help!

* Join the discussion on [https://discourse.mozilla-community.org/category/community-it Discourse]
* Go to our IRC channel: [irc://irc.mozilla.org/%23communityit #CommunityIT on irc.mozilla.org]
* Join our weekly call

== Modules ==

We operate under a module system. A module is a discrete unit of code or activity. An owner is the person in charge of a module or sub-module. A peer is a person whom the owner has appointed to help them. A module may have multiple peers and, very occasionally, multiple owners.

* [[IT/Community/WG/Badgus|Badg.us]]
* [[IT/Community/WG/MCSHosting|Mozilla Communities Hosting (MCS)]]
* [[IT/Community/WG/Discourse|Discourse]]
* [[IT/Community/WG/WordpressMS|WordPress Multisite]]
* [[IT/Community/WG/Infrastructure|Infrastructure]]

=== Archived Modules ===
These modules are no longer maintained, but their information is retained for historical purposes.

* [[IT/Community/WG/Phabricator|Phabricator]]

== Weekly Calls''' ==
{| class="wikitable"
|-
! Meeting !! Date & Time !! Meeting Notes
|-
| Bug Triage || Weekly. [http://arewemeetingyet.com/Los%20Angeles/2014-10-15/09:00/w/Community%20Sysadmin%20Bug%20Triage Wednesdays @ 1600 UTC] || [https://communityit.etherpad.mozilla.org/Meeting Etherpad]
|-
| Infrastructure || Weekly. [http://arewemeetingyet.com/Los%20Angeles/2014-10-13/09:00/w/Community%20Sysadmin%20Infrastructure Mondays @ 1630 UTC] || [https://communityit.etherpad.mozilla.org/Meeting-Infrastructure Etherpad]
|-
|}

=== '''Meeting Agenda & Notes''' ===
* Upcoming/Current (look at revision history for older meetings)
** [https://communityit.etherpad.mozilla.org/Meeting Etherpad]

* '''Past Meetings'''
** [https://wiki.mozilla.org/IT/Community/Notes/2014-10-09 October 09 2014]
** [https://wiki.mozilla.org/IT/Community/Notes/2013-10-18 October 18 2013]
** [https://wiki.mozilla.org/IT/Community/Notes/2013-09-06 September 6 2013]
** [https://wiki.mozilla.org/IT/Community/Notes/2013-08-23 August 23 2013]
** [https://wiki.mozilla.org/IT/Community/Notes/2013-08-30 August 30 2013]

IT/Community

2014-10-17T06:33:32Z

Mrz: /* Weekly Call */

= Overview =
Mozilla Community Sysadmins are individuals who are passionate about Mozilla, the open web and are passionate and knowledge about running websites and services (at scale!) to help support the Mozilla Community.

Community is the backbone of the Mozilla Project.

We are a global pack of Sysadmins supporting the Mozilla Community and, importantly, mentoring & teaching others with practical technical skills in hosting and running production websites and services, configuration management (puppet/chef), monitoring/alerting & oncall pager.

= Getting Involved =
We need you! Give us a shout out on one of the following communication channels and let us know you'd like to help!

* Join the discussion on [https://discourse.mozilla-community.org/category/community-it Discourse]
* Go to our IRC channel: [irc://irc.mozilla.org/%23communityit #CommunityIT on irc.mozilla.org]
* Join our weekly call

== Modules ==

We operate under a module system. A module is a discrete unit of code or activity. An owner is the person in charge of a module or sub-module. A peer is a person whom the owner has appointed to help them. A module may have multiple peers and, very occasionally, multiple owners.

* [[IT/Community/WG/Badgus|Badg.us]]
* [[IT/Community/WG/MCSHosting|Mozilla Communities Hosting (MCS)]]
* [[IT/Community/WG/Discourse|Discourse]]
* [[IT/Community/WG/WordpressMS|WordPress Multisite]]
* [[IT/Community/WG/Infrastructure|Infrastructure]]

=== Archived Modules ===
These modules are no longer maintained, but their information is retained for historical purposes.

* [[IT/Community/WG/Phabricator|Phabricator]]

== Weekly Calls''' ==
{| class="wikitable"
|-
! Meeting !! Date & Time !! Meeting Notes
|-
| Bug Triage || Weekly. [http://arewemeetingyet.com/Pacific/2014-10-15/09:00/w/Community%20Sysadmin%20Bug%20Triage Wednesdays @ 1600 UTC] || [https://communityit.etherpad.mozilla.org/Meeting Etherpad]
|-
| Infrastructure || Weekly. Mondays @ 1630 UTC || [https://communityit.etherpad.mozilla.org/Meeting-Infrastructure Etherpad]
|-
|}

=== '''Meeting Agenda & Notes''' ===
* Upcoming/Current (look at revision history for older meetings)
** [https://communityit.etherpad.mozilla.org/Meeting Etherpad]

* '''Past Meetings'''
** [https://wiki.mozilla.org/IT/Community/Notes/2014-10-09 October 09 2014]
** [https://wiki.mozilla.org/IT/Community/Notes/2013-10-18 October 18 2013]
** [https://wiki.mozilla.org/IT/Community/Notes/2013-09-06 September 6 2013]
** [https://wiki.mozilla.org/IT/Community/Notes/2013-08-23 August 23 2013]
** [https://wiki.mozilla.org/IT/Community/Notes/2013-08-30 August 30 2013]

IT/Community

2014-10-17T06:30:53Z

Mrz:

= Overview =
Mozilla Community Sysadmins are individuals who are passionate about Mozilla, the open web and are passionate and knowledge about running websites and services (at scale!) to help support the Mozilla Community.

Community is the backbone of the Mozilla Project.

We are a global pack of Sysadmins supporting the Mozilla Community and, importantly, mentoring & teaching others with practical technical skills in hosting and running production websites and services, configuration management (puppet/chef), monitoring/alerting & oncall pager.

= Getting Involved =
We need you! Give us a shout out on one of the following communication channels and let us know you'd like to help!

* Join the discussion on [https://discourse.mozilla-community.org/category/community-it Discourse]
* Go to our IRC channel: [irc://irc.mozilla.org/%23communityit #CommunityIT on irc.mozilla.org]
* Join our weekly call

== Modules ==

We operate under a module system. A module is a discrete unit of code or activity. An owner is the person in charge of a module or sub-module. A peer is a person whom the owner has appointed to help them. A module may have multiple peers and, very occasionally, multiple owners.

* [[IT/Community/WG/Badgus|Badg.us]]
* [[IT/Community/WG/MCSHosting|Mozilla Communities Hosting (MCS)]]
* [[IT/Community/WG/Discourse|Discourse]]
* [[IT/Community/WG/WordpressMS|WordPress Multisite]]
* [[IT/Community/WG/Infrastructure|Infrastructure]]

=== Archived Modules ===
These modules are no longer maintained, but their information is retained for historical purposes.

* [[IT/Community/WG/Phabricator|Phabricator]]

== Weekly Call''' ==
{| class="wikitable"
|-
! Meeting !! Date & Time !! Meeting Notes
|-
| Bug Triage || Weekly. Wednesdays @ 1600 UTC || [https://communityit.etherpad.mozilla.org/Meeting Etherpad]
|-
| Infrastructure || Weekly. Mondays @ 1630 UTC || [https://communityit.etherpad.mozilla.org/Meeting-Infrastructure Etherpad]
|-
|}

=== '''Meeting Agenda & Notes''' ===
* Upcoming/Current (look at revision history for older meetings)
** [https://communityit.etherpad.mozilla.org/Meeting Etherpad]

* '''Past Meetings'''
** [https://wiki.mozilla.org/IT/Community/Notes/2014-10-09 October 09 2014]
** [https://wiki.mozilla.org/IT/Community/Notes/2013-10-18 October 18 2013]
** [https://wiki.mozilla.org/IT/Community/Notes/2013-09-06 September 6 2013]
** [https://wiki.mozilla.org/IT/Community/Notes/2013-08-23 August 23 2013]
** [https://wiki.mozilla.org/IT/Community/Notes/2013-08-30 August 30 2013]

IT/Community

2014-10-17T06:26:59Z

Mrz:

= Overview =
Mozilla Community Sysadmins are individuals who are passionate about Mozilla, the open web and are passionate and knowledge about running websites and services (at scale!) to help support the Mozilla Community.

Community is the backbone of the Mozilla Project.

We are a global pack of Sysadmins supporting the Mozilla Community and, importantly, mentoring & teaching others with practical technical skills in hosting and running production websites and services, configuration management (puppet/chef), monitoring/alerting & oncall pager.

= Getting Involved =
We need you! Give us a shout out on one of the following communication channels and let us know you'd like to help!

* Join the discussion on [https://discourse.mozilla-community.org/category/community-it Discourse]
* Go to our IRC channel: [irc://irc.mozilla.org/%23communityit #CommunityIT on irc.mozilla.org]
* Join our weekly call

== Modules ==

We operate under a module system. A module is a discrete unit of code or activity. An owner is the person in charge of a module or sub-module. A peer is a person whom the owner has appointed to help them. A module may have multiple peers and, very occasionally, multiple owners.

* [[IT/Community/WG/Badgus|Badg.us]]
* [[IT/Community/WG/MCSHosting|Mozilla Communities Hosting (MCS)]]
* [[IT/Community/WG/Discourse|Discourse]]
* [[IT/Community/WG/WordpressMS|WordPress Multisite]]
* [[IT/Community/WG/Infrastructure|Infrastructure]]

=== Archived Modules ===
These modules are no longer maintained, but their information is retained for historical purposes.

* [[IT/Community/WG/Phabricator|Phabricator]]

== Weekly Call''' ==
* Weekly meeting are going through a reboot. ''TBD''
* [irc://irc.mozilla.org/#communityit #CommunityIT on irc.mozilla.org] for link. Otherwise, check the [https://communityit.etherpad.mozilla.org/Meeting Etherpad].

=== '''Meeting Agenda & Notes''' ===
* Upcoming/Current (look at revision history for older meetings)
** [https://communityit.etherpad.mozilla.org/Meeting Etherpad]

* '''Past Meetings'''
** [https://wiki.mozilla.org/IT/Community/Notes/2014-10-09 October 09 2014]
** [https://wiki.mozilla.org/IT/Community/Notes/2013-10-18 October 18 2013]
** [https://wiki.mozilla.org/IT/Community/Notes/2013-09-06 September 6 2013]
** [https://wiki.mozilla.org/IT/Community/Notes/2013-08-23 August 23 2013]
** [https://wiki.mozilla.org/IT/Community/Notes/2013-08-30 August 30 2013]

IT/Community

2014-10-17T06:23:51Z

Mrz:

== Overview ==
Mozilla Community Sysadmins are individuals who are passionate about Mozilla, the open web and are passionate and knowledge about running websites and services (at scale!) to help support the Mozilla Community.

Community is the backbone of the Mozilla Project.

We are a global pack of Sysadmins supporting the Mozilla Community and, importantly, mentoring & teaching others with practical technical skills in hosting and running production websites and services, configuration management (puppet/chef), monitoring/alerting & oncall pager.

== Getting Involved ==
We need you! Give us a shout out on one of the following communication channels and let us know you'd like to help!

* Join the discussion on [https://discourse.mozilla-community.org/category/community-it Discourse]
* Go to our IRC channel: [irc://irc.mozilla.org/%23communityit #CommunityIT on irc.mozilla.org]
* Join our weekly call

=== Modules ===

Community IT Ops operates under a module ownership governance system. A module is a discrete unit of code or activity. An owner is the person in charge of a module or sub-module. A peer is a person whom the owner has appointed to help them. A module may have multiple peers and, very occasionally, multiple owners.

* [[IT/Community/WG/Badgus|Badg.us]]
* [[IT/Community/WG/MCSHosting|Mozilla Communities Hosting (MCS)]]
* [[IT/Community/WG/Discourse|Discourse]]
* [[IT/Community/WG/WordpressMS|WordPress Multisite]]
* [[IT/Community/WG/Infrastructure|Infrastructure]]

==== Archived Modules ====
These modules are no longer maintained, but their information is retained for historical purposes.

* [[IT/Community/WG/Phabricator|Phabricator]]

=== Weekly Call''' ===
* Weekly meeting are going through a reboot. ''TBD''
* [irc://irc.mozilla.org/#communityit #CommunityIT on irc.mozilla.org] for link. Otherwise, check the [https://communityit.etherpad.mozilla.org/Meeting Etherpad].

==== '''Meeting Agenda & Notes''' ====
* Upcoming/Current (look at revision history for older meetings)
** [https://communityit.etherpad.mozilla.org/Meeting Etherpad]

* '''Past Meetings'''
** [https://wiki.mozilla.org/IT/Community/Notes/2014-10-09 October 09 2014]
** [https://wiki.mozilla.org/IT/Community/Notes/2013-10-18 October 18 2013]
** [https://wiki.mozilla.org/IT/Community/Notes/2013-09-06 September 6 2013]
** [https://wiki.mozilla.org/IT/Community/Notes/2013-08-23 August 23 2013]
** [https://wiki.mozilla.org/IT/Community/Notes/2013-08-30 August 30 2013]

IT/Community

2014-10-17T06:22:33Z

Mrz: Overview

= Overview =
Mozilla Community Sysadmins are individuals who are passionate about Mozilla, the open web and are passionate and knowledge about running websites and services (at scale!) to help support the Mozilla Community.

Community is the backbone of the Mozilla Project.

We are a global pack of Sysadmins supporting the Mozilla Community and, importantly, mentoring & teaching others with practical technical skills in hosting and running production websites and services, configuration management (puppet/chef), monitoring/alerting & oncall pager.

= Getting Involved =
We need you! Give us a shout out on one of the following communication channels and let us know you'd like to help!

* Join the discussion on [https://discourse.mozilla-community.org/category/community-it Discourse]
* Go to our IRC channel: [irc://irc.mozilla.org/%23communityit #CommunityIT on irc.mozilla.org]
* Join our weekly call

== Modules ==

Community IT Ops operates under a module ownership governance system. A module is a discrete unit of code or activity. An owner is the person in charge of a module or sub-module. A peer is a person whom the owner has appointed to help them. A module may have multiple peers and, very occasionally, multiple owners.

* [[IT/Community/WG/Badgus|Badg.us]]
* [[IT/Community/WG/MCSHosting|Mozilla Communities Hosting (MCS)]]
* [[IT/Community/WG/Discourse|Discourse]]
* [[IT/Community/WG/WordpressMS|WordPress Multisite]]
* [[IT/Community/WG/Infrastructure|Infrastructure]]

=== Archived Modules ===
These modules are no longer maintained, but their information is retained for historical purposes.

* [[IT/Community/WG/Phabricator|Phabricator]]

== Weekly Call''' ==
* Weekly meeting are going through a reboot. ''TBD''
* [irc://irc.mozilla.org/#communityit #CommunityIT on irc.mozilla.org] for link. Otherwise, check the [https://communityit.etherpad.mozilla.org/Meeting Etherpad].

=== '''Meeting Agenda & Notes''' ===
* Upcoming/Current (look at revision history for older meetings)
** [https://communityit.etherpad.mozilla.org/Meeting Etherpad]

* '''Past Meetings'''
** [https://wiki.mozilla.org/IT/Community/Notes/2014-10-09 October 09 2014]
** [https://wiki.mozilla.org/IT/Community/Notes/2013-10-18 October 18 2013]
** [https://wiki.mozilla.org/IT/Community/Notes/2013-09-06 September 6 2013]
** [https://wiki.mozilla.org/IT/Community/Notes/2013-08-23 August 23 2013]
** [https://wiki.mozilla.org/IT/Community/Notes/2013-08-30 August 30 2013]

IT/Community

2014-10-17T06:19:26Z

Mrz:

= Overview =

Mozilla Community Sysadmins are individuals who are passionate about Mozilla, the open web and are passionate and knowledge about running websites and services (at scale!) to help support the Mozilla Community.

Community is the backbone of the Mozilla Project.

We are a global pack of Sysadmins supporting the Mozilla Community and, importantly, mentoring & teaching others with practical technical skills in hosting and running production websites and services, configuration management (puppet/chef), monitoring/alerting & oncall pager

= Getting Involved =
We need you! Give us a shout out on one of the following communication channels and let us know you'd like to help!

* Join the discussion on [https://discourse.mozilla-community.org/category/community-it Discourse]
* Go to our IRC channel: [irc://irc.mozilla.org/%23communityit #CommunityIT on irc.mozilla.org]
* Join our weekly call

== Modules ==

Community IT Ops operates under a module ownership governance system. A module is a discrete unit of code or activity. An owner is the person in charge of a module or sub-module. A peer is a person whom the owner has appointed to help them. A module may have multiple peers and, very occasionally, multiple owners.

* [[IT/Community/WG/Badgus|Badg.us]]
* [[IT/Community/WG/MCSHosting|Mozilla Communities Hosting (MCS)]]
* [[IT/Community/WG/Discourse|Discourse]]
* [[IT/Community/WG/WordpressMS|WordPress Multisite]]
* [[IT/Community/WG/Infrastructure|Infrastructure]]

=== Archived Modules ===
These modules are no longer maintained, but their information is retained for historical purposes.

* [[IT/Community/WG/Phabricator|Phabricator]]

== Weekly Call''' ==
* Weekly meeting are going through a reboot. ''TBD''
* [irc://irc.mozilla.org/#communityit #CommunityIT on irc.mozilla.org] for link. Otherwise, check the [https://communityit.etherpad.mozilla.org/Meeting Etherpad].

=== '''Meeting Agenda & Notes''' ===
* Upcoming/Current (look at revision history for older meetings)
** [https://communityit.etherpad.mozilla.org/Meeting Etherpad]

* '''Past Meetings'''
** [https://wiki.mozilla.org/IT/Community/Notes/2014-10-09 October 09 2014]
** [https://wiki.mozilla.org/IT/Community/Notes/2013-10-18 October 18 2013]
** [https://wiki.mozilla.org/IT/Community/Notes/2013-09-06 September 6 2013]
** [https://wiki.mozilla.org/IT/Community/Notes/2013-08-23 August 23 2013]
** [https://wiki.mozilla.org/IT/Community/Notes/2013-08-30 August 30 2013]

IT/Community

2014-10-09T22:34:48Z

Mrz: /* Meeting Agenda & Notes */

= Our Mission =

'''Who we are'''

Mozilla Community IT Ops is a community of talented, volunteer Systems Administrators who devote their time and effort into supporting and managing community-based system infrastructure that support the Mozilla Project, while also learning and upgrading their skill sets in the progress.

'''What we are'''

We are a showcase for how to run the best of the best IT/Operations. We are open & transparent. We are a force multiplier, empowering the Community to promote Mozilla's Mission & Manifesto.

'''How we do it'''

Teaching and education are core to our mission and values. We mentor and teach today's skills and help put those skills to practical use by hosting and running production sites and services. We use [http://openbadges.org/ OpenBadges] to acknowledge skills and accomplishments.

= Getting Involved =
We need you! Give us a shout out on one of the following communication channels and let us know you'd like to help!

* Join the discussion on [https://discourse.mozilla-community.org/category/community-it Discourse]
* Go to our IRC channel: [irc://irc.mozilla.org/%23communityit #CommunityIT on irc.mozilla.org]
* Join our weekly call

== Modules ==

Community IT Ops operates under a module ownership governance system. A module is a discrete unit of code or activity. An owner is the person in charge of a module or sub-module. A peer is a person whom the owner has appointed to help them. A module may have multiple peers and, very occasionally, multiple owners.

* [[IT/Community/WG/Badgus|Badg.us]]
* [[IT/Community/WG/MCSHosting|Mozilla Communities Hosting (MCS)]]
* [[IT/Community/WG/Discourse|Discourse]]
* [[IT/Community/WG/WordpressMS|WordPress Multisite]]
* [[IT/Community/WG/Infrastructure|Infrastructure]]

=== Archived Modules ===
These modules are no longer maintained, but their information is retained for historical purposes.

* [[IT/Community/WG/Phabricator|Phabricator]]

== Weekly Call''' ==
* Weekly meeting are going through a reboot. ''TBD''
* [irc://irc.mozilla.org/#communityit #CommunityIT on irc.mozilla.org] for link. Otherwise, check the [https://communityit.etherpad.mozilla.org/Meeting Etherpad].

=== '''Meeting Agenda & Notes''' ===
* Upcoming/Current (look at revision history for older meetings)
** [https://communityit.etherpad.mozilla.org/Meeting Etherpad]

* '''Past Meetings'''
** [https://wiki.mozilla.org/IT/Community/Notes/2014-10-09 October 09 2014]
** [https://wiki.mozilla.org/IT/Community/Notes/2013-10-18 October 18 2013]
** [https://wiki.mozilla.org/IT/Community/Notes/2013-09-06 September 6 2013]
** [https://wiki.mozilla.org/IT/Community/Notes/2013-08-23 August 23 2013]
** [https://wiki.mozilla.org/IT/Community/Notes/2013-08-30 August 30 2013]

IT/Community

2014-10-09T15:31:26Z

Mrz: /* Weekly Call */

= Our Mission =

'''Who we are'''

Mozilla Community IT Ops is a community of talented, volunteer Systems Administrators who devote their time and effort into supporting and managing community-based system infrastructure that support the Mozilla Project, while also learning and upgrading their skill sets in the progress.

'''What we are'''

We are a showcase for how to run the best of the best IT/Operations. We are open & transparent. We are a force multiplier, empowering the Community to promote Mozilla's Mission & Manifesto.

'''How we do it'''

Teaching and education are core to our mission and values. We mentor and teach today's skills and help put those skills to practical use by hosting and running production sites and services. We use [http://openbadges.org/ OpenBadges] to acknowledge skills and accomplishments.

= Getting Involved =
We need your help!

* Join the discussion on [https://discourse.mozilla-community.org/category/community-it Discourse]
* Go to our IRC channel: [irc://irc.mozilla.org/%23communityit #CommunityIT on irc.mozilla.org]
* Join our weekly call

== Modules ==

Community IT Ops operates under a module ownership governance system. A module is a discrete unit of code or activity. An owner is the person in charge of a module or sub-module. A peer is a person whom the owner has appointed to help them. A module may have multiple peers and, very occasionally, multiple owners.

* [[IT/Community/WG/Badgus|Badg.us]]
* [[IT/Community/WG/MCSHosting|Mozilla Communities Hosting (MCS)]]
* [[IT/Community/WG/Discourse|Discourse]]
* [[IT/Community/WG/WordpressMS|WordPress Multisite]]
* [[IT/Community/WG/Infrastructure|Infrastructure]]

=== Archived Modules ===
These modules are no longer maintained, but their information is retained for historical purposes.

* [[IT/Community/WG/Phabricator|Phabricator]]

== Weekly Call''' ==
* Weekly meeting are going through a reboot. ''TBD''
* [irc://irc.mozilla.org/#communityit #CommunityIT on irc.mozilla.org] for link. Otherwise, check the [https://communityit.etherpad.mozilla.org/Meeting Etherpad].

=== '''Meeting Agenda & Notes''' ===
* Upcoming/Current (look at revision history for older meetings)
** [https://communityit.etherpad.mozilla.org/Meeting Etherpad]
* October 2013
** [https://wiki.mozilla.org/IT/Community/Notes/2013-10-18 October 18]
* September 2013
** [https://wiki.mozilla.org/IT/Community/Notes/2013-09-06 September 6]
* August 2013
** [https://wiki.mozilla.org/IT/Community/Notes/2013-08-23 August 23]
** [https://wiki.mozilla.org/IT/Community/Notes/2013-08-30 August 30]

Security Severity Ratings

2014-04-11T03:59:10Z

Mrz: /* Priority Matrix */

__TOC__

==Severity Ratings ==
{| class="wikitable collapsible" style="width: 100%"
! Severity Ratings & Examples
|-
|
The following items are keywords for the severity of an issue.

;'''sec-critical''': Exploitable vulnerabilities which can lead to the widespread compromise of many users requiring no more than normal browsing actions..
{| class="wikitable collapsible " style="width: 100%"
! ''sec-critical Examples:''
|-
|
* Overflows resulting in native code execution
* JavaScript injection into browser chrome
* Launching of arbitrary local application with provided arguments
* Filetype spoofing where executables can masquerade as benign content types
* Installation & execution of plugins/modules with chrome/native privileges, without user consent or via user dialog fatigue
* The severity of web application bugs can depend on the value of the data that could be compromised. Flaws that could be considered critical include
** XSS (Stored)
** CSRF
** Code Injection
** Authentication Flaws (which lead to account compromise)
** Session Management Flaws (which lead to account compromise)
|}

;'''sec-high''': Obtain confidential data from other sites the user is visiting or the local machine, or inject data or code into those sites, requiring no more than normal browsing actions. Indefinite DoS of the user's system, requiring OS reinstallation or extensive cleanup. Exploitable web vulnerabilities that can lead to the targeted compromise of a small number of users.
{| class="wikitable collapsible " style="width: 100%"
! ''sec-high Examples:''
|-
|
* Cross-site Scripting (XSS)
* Theft of arbitrary files from local system
* Spoofing of full URL bar or bypass of SSL integrity checks
* Memory read that results in data being written into an inert container (ie string or image) that is subsequently accessible to content
* XSS (Reflected)
*Failure to use TLS where needed to ensure confidential/security
|}

;'''sec-moderate''': Vulnerabilities which can provide an attacker additional information or positioning that could be used in combination with other vulnerabilities. Disclosure of sensitive information that represents a violation of privacy but by itself does not expose the user or organization to immediate risk. The vulnerability combined with another moderate vulnerability could result in an attack of high or critical severity (aka stepping stone). Indefinite application Denial of Service (DoS) via corruption of state, requiring application re-installation or temporary DoS of the user's system, requiring reboot. The lack of standard defense in depth techniques and security controls. Client bugs that might have high or critical results but require the user perform unusual or complex actions to trigger.
{| class="wikitable collapsible " style="width: 100%"
! ''sec-moderate Examples:''
|-
|
* Disclosure of OS username
* Disclosure of browser cache salt
* Disclosure of entire browsing history
* Detection of arbitrary local files
* Launching of arbitrary local application without arguments
* Local storage of passwords in unencrypted form
* Persistent DoS attacks that prevent the user from starting Firefox or another application in the future
* Missing Additional Security Controls (x-frame options, SECURE/HTTPOnly flags, etc)
* Error Handling Issues
|}
;'''sec-low''': Minor security vulnerabilities such as leaks or spoofs of non-sensitive information. Missing best practice security controls

{| class="wikitable collapsible " style="width: 100%"
! ''sec-low Examples:''
|-
|
* Detection of previous visit to a specific site
* Identification of users by profiling browsing behavior.
* Corruption of chrome dialogs or user input without the ability to spoof arbitrary messages
* Lack of proper input validation (not resulting in XSS or injection)
* Content spoofing (non-html)
|}
;'''sec-other''': Bugs that may not be exploitable security issues but are kept confidential to protect sensitive information. Bugs that contain sensitive information about the bug submitter or another user Bugs that are related to security issues currently unfixed in Mozilla products or other products

{| class="wikitable collapsible " style="width: 100%"
! ''sec-other Examples:''
|-
|
* Flaws we need to track that are not in our code base
|}
;'''Mitigating Circumstances''':
If there are mitigating circumstances that severely reduce the effectiveness of the exploit, then the exploit could be reduced by one level of severity. Examples of mitigating circumstances include difficulty in reproducing due to very specific timing or load order requirements, complex or unusual set of actions the user would have to take beyond normal browsing behaviors, or unusual software configuration.

As a rough guide, to be considered for reduction in severity an exploit should execute successfully less than 10% of the time. If measures can be taken to improve the reliability of the exploit to over 10% (by combining it with other existing bugs or techniques), then it should not be considered to be mitigated.
|}

==Additional Status Codes, Whiteboard Tracking Tags & Flags==
If a potential security issue has not yet been assigned a severity rating, or a rating is not appropriate, the whiteboard may instead contain one of the following security status codes.

=== Shared Keywords ===
{| style="width: 800px;" class="wikitable collapsible fullwidth-table"
! Shared Keywords
|-
! style="width:5%" | Code
! style="width:10%"| Description
! style="width:5%" | Examples
|-
|sec-audit
|Bug requires a code audit to investigate potential security problems. DO NOT USE for an actual vulnerability; if a bug has or might have a sec-low/sec-moderate/sec-high/sec-critical rating then it is not a sec-audit bug. Such a vulnerability might spawn a separate sec-audit bug as a task item to scan for the same pattern elsewhere in the code.
|Look for pattern x in library y
Audit file z for string buffer abuse.
|-
|sec-vector
|Flaws not in Mozilla controlled software, but can cause security problems for Mozilla users.
|Bugs in plugins
Bugs in system libraries used by Firefox
|-
|sec-want
|New features or improvement ideas related to security
|User interface refinements
Support for new types of authentication

Code refactoring / cleanup
|-
|sec-incident
| Issues resulting in an incident response or 'chemspill' actions by the security team.
| Sever compromise
Code issues that would cause client code to be respun.
|-
|<strike>sec-review-needed</strike> replaced with sec-review flag ?
|A security review is needed for the bug, this could mean a variety of things. If there is no secr:<username> in the whiteboard the item has not been triaged and action is unknown. Once triaged a note will be placed in the bug as to the action to be taken
|
|-
|<strike>sec-review-complete</strike> replaced with sec-review flag +
|The security review / actions desired have been completed. This will result in either a link to the notes from security actions or a note from the assigned resource in the bug.
|
|-
|}

=== Group Keywords ===
{| style="width: 800px;" class="wikitable collapsible fullwidth-table"
! Group Keywords
|-
! style="width:5%" | Code
! style="width:10%"| Description
! style="width:5%" | Examples
|-
| csectype- 
| Client Security (ie. Firefox, Thunderbird, etc)
|
{|class="wikitable collapsible fullwidth-table"
! csectype-
|-
! style="width:5%" | Code
! style="width:10%"| Description
|-
|csectype-bounds || client security issues due to incorrect boundary conditions (read or write)
|-
|csectype-disclosure || Disclosure of sensitive user data, personal information, etc in a client product.
|-
|csectype-dos || Used to tag client Denial of Service bugs. For web server denial of service bugs please use wsec-dos as these tend to be more severe. Search 28
|-
|csectype-intoverflow || client security issues due to integer overflow
|-
|csectype-oom || A client crash or hang that occurs in Out Of Memory conditions Search 2
|-
|csectype-other || client security issues that don't fit into other categories
|-
|csectype-priv-escalation || client privilege escalation security issues
|-
|csectype-sop || violations of the client Same Origin Policy (Universal-XSS bugs, for example).
|-
|csectype-uaf || client security issues due to a use-after-free Search 1
|-
|csectype-ui-redress || client security issues due to UI Redress attacks, either site-on-site ("clickjacking" and friends) or manipulation of the browser UI to fool users into taking the wrong action.
|-
|csectype-uninitialized || client security issues due to use of uninitialized memory
|-
|csectype-wildptr || client security issues due to pointer misuse not otherwise covered (see csectype-uaf, csectype-uninitialized, csectype-intoverflow, csectype-bounds)
|-
|}
|-
| wsec- 
| Web Security (Web Sites, Web Services, etc)
|
{|class="wikitable collapsible fullwidth-table"
! wsec-
|-
! style="width:5%" | Code
! style="width:10%"| Description
|-
|wsec-authentication || Website or server authentication security issues (lockouts, password policy, etc)
|-
|wsec-authorization || web/server authorization security issues
|-
|wsec-cookie || Cookie related errors (HTTPOnly / Secure Flag, incorrect domain / path)
|-
|wsec-crossdomain || Issue such as x-frame-options, crossdomain.xml, cross site sharing settings
|-
|wsec-crypto || Crypto related items such as password hashing
|-
|wsec-csrf || Cross-Site Request Forgery (CSRF) bugs in server products
|-
|wsec-disclosure || Disclosure of sensitive data, personal information, etc from a web service
|-
|wsec-dos || Used to denote web server Denial of Service bugs. For similar bugs in client software please use csectype-dos instead.
|-
|wsec-errorhandling || Any error handling issue
|-
|wsec-impersonation || Impersonation / Spoofing attacks (UI Redress, etc)
|-
|wsec-injection || Injection attacks other than SQLi or XSS
|-
|wsec-input || Failure to perform input validation. Most often you will probably use the xss tag instead
|-
|wsec-logging || Logging issues such as requests for CEF log points.
|-
|wsec-other || web/server security issues that don't fit into other categories
|-
|wsec-session || Issues related to sesson management (Session fixation, etc)
|-
|wsec-sqli || SQL Injection
|-
|wsec-xss || Cross-Site Scripting (XSS) bugs in server products
|-
|}
|-
| opsec- 
| Operations Security (Mozilla owned & operated severs and services)
|
{|class="wikitable collapsible fullwidth-table"
! opsec-
|-
! style="width:5%" | Code
! style="width:10%"| Description
|-
| opsec-access
| The identified issue is an access violation.
|-
|}
|}

=== Whiteboard Tags ===
{| style="width: 800px;" class="wikitable collapsible fullwidth-table"
! Whiteboard Tags
|-
! style="width:5%" | Code
! style="width:10%"| Description
! style="width:5%" | Examples
|-
|<strike>sec-assigned:UserAlias</strike> depricated for sec-review? flag with alias
|This designates the assigned security resource that is accountable for actions to be taken on the designated item. When possible the bug will be assigned to the security contact for action. This will be used when that is not possible or practical.
|sec-review?:curtisk@blah.bah indicates that curtisk is the accountable party for action
|-
|[Q2]
|This designates a bug as being identified as a request to be done or targeted for a given operational quarter. If no year is given it is for the current year.
|[Q2] indicates second quarter of the current calendar year, [Q1-2013] would be used to indicate a target for an upcoming quarter that has not occurred.
|-
|[k90]
|This designates a bug as being part of the Kilimanjaro effort so that it can be tracked, triaged and given appropriate priority and attention.
|
|-
|[basecamp]
|This designates a bug as being part of the basecamp sub effort of the Kilimanjaro effort.
|
|-
|[fennec]
|This designates a bug as being a critical bug for the efforts around our mobile browser project. This could be combined with either the [k9o] or [basecamp] tags as a bug could be part of both.
|
|-
|[triage needed]
|Used to mark a bug for weekly triage meeting.
|
|-
|<strike>[pending secreview]</strike> deprecated
| Indicates a secreview or tasks related to said review are yet to be completed.
|
|-
|[start mm/dd/yyyy][target mm/dd/yyyy]
|This indicates that expected dates to start and complete work on a given review or security bug.
|[start 01/29/2013][target 02/09/2013] indicates work will start on 29-Jan and expected target for completion on 09-Feb
|-
|<strike>[completed secreview]</strike> deprecated
| Indicates the given secreivew or related tasks have been completed
|
|-
|mentorship
| Indicates that a given bug is part of our security mentorship program. The assignee of said bug is the Mozilla mentor for such a bug.
|
|-
|[score:##]
|This indicates the relative severity score for risk rating bugs per the calculator at https://people.mozilla.com/~ckoenig/
|[score:30:moderate] shows that the issue has a numerical score of 30 and a severity of moderate.
|-
|[FX]
|Indicates an item related to Firefox
|
|-
|[FXOS]
|Indicates an item related to Firefox OS
|
|-
|[Web]
|Indicates an item related to our Web properties
|
|-
|u= c= p=
|These items are used to allow bugs to be tracked by scrumbu.gs for work tracking ([http://scrumbu.gs/help/ more info]).
|
|-
|s=
|This tag is used in conjunction with the scrumbu.gs tags above to indicate which sprint a given bug has been assigned.
|s=13q4.1 indicates the bug is in the year 2013, 4th quarter and sprint 1. Each sprint is 2 weeks long and it's calendar dates can be tracked on scrumbu.gs
|-
|}

=== Feature Page Codes ===
{| style="width: 800px;" class="wikitable collapsible fullwidth-table"
! Feature Page Codes
|-
! style="width:5%" | Code
! style="width:10%"| Description
! style="width:5%" | Examples
|-
|sec-review-needed
|A security review is needed for the feature, this could mean a variety of things. If there is no <username> in the notes then a full review needs to be scheduled, if a <username> is present than that person will follow-up with the feature team on whatever task is needed.
|
|-
|sec-review-complete
|The security review / actions desired have been completed. This will result in a link to the notes from security actions or a note from the assigned resource.
|
|-
|sec-review-active
| There are active tasks associated with the review that are yet to be completed in order for the review to be seen as completed. These will be captured in the "Action Items" section of the review notes.
|
|-
|sec-review-sched
| Security review tasks have been scheduled, if this is a full security review the date of the scheduled review will be present in the security notes.
|
|-
|sec-review-unnecessary
| After triage it was felt the feature needed no review or security actions.
|
|-
| Security health: <blank>
| There are no notes or status is unknown.
| Color: <None>
|-
| Security health: OK
| The tasks are on schedule or completed and are considered non-blocking.
| {{StatusHealthy|status=Color: Green}}
|-
| Security health: Blocked
| Some aspect of the security review has given cause to block the feature from further work or landing. The reasons will be listed in the security notes or linked to a larger review outcome for follow-up.
| {{StatusBlocked|status=Color: Yellow}}
|-
| Security health: At Risk
| Some aspect of the security review may cause the feature to be blocked or put the feature at risk of being off schedule.The reasons will be listed in the security notes or linked to a larger review outcome for follow-up.
| {{StatusAtRisk|status=Color: Red}}
|-
| Security health: Assigned
| Security tasks have been assigned to a member of the team to followup. The name of this resource will be in the security notes.
| {{StatusAssigned|status=Color: Teal}}
|-
|}
=== Flags ===
{| style="width: 800px;" class="wikitable collapsible fullwidth-table"
! Flags
|-
! style="width:5%" | Flag
! style="width:10%"| Description
! style="width:5%" | Settings
|-
| sec-review
| Security review - Requesting action from the security assurance team or showing the results of said action
|
{|class="wikitable fullwidth-table"
|-
! style="width:5%" | Setting
! style="width:10%"| Description
|-
|'?'|| Request for the security team to review the requested bug for action
|-
|'+'|| Bug has been reviewed, actions are done and the security team has no further concerns at this time
|-
|'-'|| But has been reviewed and found to be deficient in a security metric that should be mitigated
|-
|}
|-
| sec-bounty
| Shows the status of a bug with regards to a bounty payout per our bounty guidlines
|
{|class="wikitable fullwidth-table"
|-
! style="width:5%" | Setting
! style="width:10%"| Description
|-
|'?'|| Bug is nominated for review by the bounty committee
|-
|'+'|| Bug has been accepted and a payment will be made
|-
|'-'|| Bug does not meet criteria and a payment will ''not'' be made
|-
|}
|}
=== Priority Matrix===
{| class="wikitable collapsible " style="width: 100%"
! Priority Matrix (primarily OpSec)
|-
|
;'''Blocker''': Anything which is easily exploitable or reproducible and/or we are seeing active attempts to exploit. Anything which has a high impact to Mozilla should also be considered. This priority flag should communicate that other work is blocked
by this issue and it should be resolved immediately.
''Examples:''
* SQL injection or Injection Flaws and Remote File Inclusion (RFI)
* Anything which has been publicized as a 0day which falls into the 'Critical' category.
* Flaws being actively used in the wild (chemspill?).

;'''Critical''': Vulnerabilities which are exploitable and/or hard to reproduce. We are also not seeing these being actively exploited or have another means to protect against a vulnerability.
''Examples:''
* XSS
* CSRF and Authentication or token handling issues
:'''Major''': Vulnerabilities which have a slightly less degree of impact compared to Critical.
''Examples:''
* Content Spoofing
* Information Disclosure or Error Handling
;'''Normal''': Internal vulnerability with a low likelihood of being remotely exploitable.
|}

[[/Security_Severity_Ratings/archive | archive]]

IT/Community

2014-03-03T19:46:34Z

Mrz: Changed protection level for "IT/Community" (‎[move=sysop] (indefinite))

= Our Mission =

'''Who we are'''

Mozilla Community IT Ops is a community of talented, volunteer Systems Administrators who devote their time and effort into supporting and managing community-based system infrastructure that support the Mozilla Project, while also learning and upgrading their skill sets in the progress.

'''What we are'''

We are a showcase for how to run the best of the best IT/Operations. We are open & transparent. We are a force multiplier, empowering the Community to promote Mozilla's Mission & Manifesto.

'''How we do it'''

Teaching and education are core to our mission and values. We mentor and teach today's skills and help put those skills to practical use by hosting and running production sites and services. We use [http://openbadges.org/ OpenBadges] to acknowledge skills and accomplishments.

= Getting Involved =
We need your help!

* Join the [https://mail.mozilla.org/listinfo/communityit Mailing List]
* Go to our IRC channel: [irc://irc.mozilla.org/%23communityit #CommunityIT on irc.mozilla.org]
* Join our weekly call

== Modules ==

Community IT Ops operates under a module ownership governance system. A module is a discrete unit of code or activity. An owner is the person in charge of a module or sub-module. A peer is a person whom the owner has appointed to help them. A module may have multiple peers and, very occasionally, multiple owners.

* [[IT/Community/WG/Phabricator|Phabricator]]
* [[IT/Community/WG/Badgus|Badg.us]]
* [[IT/Community/WG/MCSHosting|Mozilla Communities Hosting (MCS)]]
* [[IT/Community/WG/Discourse|Discourse]]
* [[IT/Community/WG/WordpressMS|Wordpress Multisite]]
* [[IT/Community/WG/Infrastructure|Infrastructure]]

== '''Weekly Call''' ==
* Weekly Big Blue Button meeting, '''every other Friday at [http://www.wolframalpha.com/input/?i=3+PM+UTC+September+14+2013 8am US/Pacific (1500 UTC)]'''
* http://moz.bigbluebutton.org/moz/
** Room: Community IT
** Password: welcome

=== '''Meeting Agenda & Notes''' ===
* Upcoming
** [https://communityit.etherpad.mozilla.org/Meeting November 1]
* October 2013
** [https://wiki.mozilla.org/IT/Community/Notes/2013-10-18 October 18]
* September 2013
** [https://wiki.mozilla.org/IT/Community/Notes/2013-09-06 September 6]
* August 2013
** [https://wiki.mozilla.org/IT/Community/Notes/2013-08-23 August 23]
** [https://wiki.mozilla.org/IT/Community/Notes/2013-08-30 August 30]

IT/Community

2013-10-28T04:40:44Z

Mrz: /* Meeting Agenda & Notes */

= Our Mission =

'''Who we are'''

Mozilla Community IT Ops is a community of talented, volunteer Systems Administrators who devote their time and effort into supporting and managing community-based system infrastructure that support the Mozilla Project, while also learning and upgrading their skill sets in the progress.

'''What we are'''

We are a showcase for how to run the best of the best IT/Operations. We are open & transparent. We are a force multiplier, empowering the Community to promote Mozilla's Mission & Manifesto.

'''How we do it'''

Teaching and education are core to our mission and values. We mentor and teach today's skills and help put those skills to practical use by hosting and running production sites and services. We use [http://openbadges.org/ OpenBadges] to acknowledge skills and accomplishments.

= Getting Involved =
We need your help!

* Join the [https://mail.mozilla.org/listinfo/communityit Mailing List]
* Go to our IRC channel: [irc://irc.mozilla.org/%23communityit #CommunityIT on irc.mozilla.org]
* Join our weekly call

== Modules ==

Community IT Ops operates under a module ownership governance system. A module is a discrete unit of code or activity. An owner is the person in charge of a module or sub-module. A peer is a person whom the owner has appointed to help them. A module may have multiple peers and, very occasionally, multiple owners.

* [[IT/Community/WG/Phabricator|Phabricator]]
* [[IT/Community/WG/Badgus|Badg.us]]
* [[IT/Community/WG/MCSHosting|Mozilla Communities Hosting (MCS)]]
* [[IT/Community/WG/Discourse|Discourse]]
* [[IT/Community/WG/WordpressMS|Wordpress Multisite]]
* [[IT/Community/WG/Infrastructure|Infrastructure]]

== '''Weekly Call''' ==
* Weekly Big Blue Button meeting, '''every other Friday at [http://www.wolframalpha.com/input/?i=3+PM+UTC+September+14+2013 8am US/Pacific (1500 UTC)]'''
* http://moz.bigbluebutton.org/moz/
** Room: Community IT
** Password: welcome

=== '''Meeting Agenda & Notes''' ===
* Upcoming
** [https://communityit.etherpad.mozilla.org/Meeting November 1]
* October 2013
** [https://wiki.mozilla.org/IT/Community/Notes/2013-10-18 October 18]
* September 2013
** [https://wiki.mozilla.org/IT/Community/Notes/2013-09-06 September 6]
* August 2013
** [https://wiki.mozilla.org/IT/Community/Notes/2013-08-23 August 23]
** [https://wiki.mozilla.org/IT/Community/Notes/2013-08-30 August 30]

WeeklyUpdates/2013-10-28

2013-10-28T04:30:35Z

Mrz: /* Friday, {{#time:d F|{{SUBPAGENAME}} +4 days}} */

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

__TOC__

= All-hands Status Meeting Agenda =

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

== Friends of the Tree [[Image:Tree.gif|Friends of the Tree]] ==

* Alex Fuser & Julian Ceballos from Mozilla Mexico for their awesome help at the Firefox OS Apps Workshop in Guadalajara, Mexico on Saturday. Also, Anahi Felix, Jorge Garcia, and all the crew at @escuchomx ( a tech training facility in Guadalajara), for over the top hospitality. Gracias!

== Upcoming Events ==

=== This Week ===

=== Monday, {{#time:d F|{{SUBPAGENAME}}}} ===

=== Tuesday, {{#time:d F|{{SUBPAGENAME}} +1 day}} ===
Noon PST, Mozilla SF Commons + AirMozilla
WebFWD IV Demo Day "Dry Run"
Come hear our 8 teams (http://webfwd.org/portfolio) do a dry run of their presentations they'll share for the broader community the following night - held now to accomodate the time zones of many Mozillians who find 6:30pm PST inconvenient :)

=== Wednesday, {{#time:d F|{{SUBPAGENAME}} +2 days}} ===
Noon PST, Mozilla SF Commons + AirMozilla
WebFWD IV Graduation
Our 8 teams (http://webfwd.org/portfolio) will show their stuff on live stream and in person to our developer, startup, mentor and investor communities. Come support, grill and cheer them on! Note applications for our next class are also open at http://webfwd.org/apply - deadline is December 15 and location is like the web: worldwide.

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

=== Friday, {{#time:d F|{{SUBPAGENAME}} +4 days}} ===
* [http://www.wolframalpha.com/input/?i=3+PM+UTC+November+1+2013 8:00 AM Pacific / 13:00 UTC]: Community IT Bi-Monthly Meetup
** [[IT/Community#Weekly_Call|Agenda and dial-in information]] (feel free to add items to the agenda)

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

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

=== Next Week ===

== Product Status Updates (voice updates) ==

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

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

=== Thunderbird ===
''Speaker Location:''

=== Older Branch Work ===
''Speaker Location:''

=== Webmaker ===
''Speaker Location:''

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

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

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

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

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

== Speakers ==

The limit is 3 minutes per speaker. It's like a lightning talk, but don't feel that you have to have slides in order to make a presentation. If you plan on showing a video, you need to contact the Air Mozilla team before the day of the meeting or you will be deferred to the next week.

{| class="fullwidth-table"
|-
! Presenter
! Title
! Topic
! Location
! Share?
! Media
! More Details
|-
| Who Are You?
| What Do You Do?
| What are you going to talk about?
| Where are you presenting from? (Moz Space, your house, space)
| Will you be sharing your screen? (yes/no, other info)
| Links to slides or images you want displayed on screen
| Link to where audience can find out more information
|-
| Diane (Bisgeier) Tate (SF) + Didem Ersoz (MV)
| Run WebFWD, Mozilla's startup program
| Graduation & call for our next class!
| Moz SF & Mountain View
| no screen sharing
| no slides
| http://webfwd.org + http://webfwd.org/portfolio http://webfwd.org/apply
|-
|}

= Roundtable =

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

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

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

|-
|}

= Welcome! =

Let's say hello to some new Mozillians!

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

|-
|}

== Introducing New Hires ==
{| class="fullwidth-table"
|-
! New Hire
! Introduced by
! Speaker location
! New Hire location
! Will be working on
|-
| ''Who is the new hire?''
| ''Who will be introducing that person?''
| ''Where is the introducer?''
| ''Where will the new person be working from?''
| ''What will the new person be working on?''
|-
| Solomon Chiu
| Peter Chang
| Taipei
| Taipei
| Firefox OS - Media Recording
|-
| Wesley Huang
| Thomas Ho
| Taipei
| Taipei
| Firefox OS - Engineering PM
|-
|}

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

|-
|}

= <meta> =

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

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

=== Firefox ===

=== Platform ===

=== Services ===

=== Messaging ===

=== Mobile ===

=== IT ===

=== Release Engineering ===

=== QA ===

==== Test Execution ====

==== WebQA ====

==== QA Community ====

=== Automation & Tools ===

=== Security ===

=== Engagement ===

==== PR ====

==== Events ====

IT/Community

2013-10-28T04:29:48Z

Mrz: /* Meeting Agenda & Notes */

= Our Mission =

'''Who we are'''

Mozilla Community IT Ops is a community of talented, volunteer Systems Administrators who devote their time and effort into supporting and managing community-based system infrastructure that support the Mozilla Project, while also learning and upgrading their skill sets in the progress.

'''What we are'''

We are a showcase for how to run the best of the best IT/Operations. We are open & transparent. We are a force multiplier, empowering the Community to promote Mozilla's Mission & Manifesto.

'''How we do it'''

Teaching and education are core to our mission and values. We mentor and teach today's skills and help put those skills to practical use by hosting and running production sites and services. We use [http://openbadges.org/ OpenBadges] to acknowledge skills and accomplishments.

= Getting Involved =
We need your help!

* Join the [https://mail.mozilla.org/listinfo/communityit Mailing List]
* Go to our IRC channel: [irc://irc.mozilla.org/%23communityit #CommunityIT on irc.mozilla.org]
* Join our weekly call

== Modules ==

Community IT Ops operates under a module ownership governance system. A module is a discrete unit of code or activity. An owner is the person in charge of a module or sub-module. A peer is a person whom the owner has appointed to help them. A module may have multiple peers and, very occasionally, multiple owners.

* [[IT/Community/WG/Phabricator|Phabricator]]
* [[IT/Community/WG/Badgus|Badg.us]]
* [[IT/Community/WG/MCSHosting|Mozilla Communities Hosting (MCS)]]
* [[IT/Community/WG/Discourse|Discourse]]
* [[IT/Community/WG/WordpressMS|Wordpress Multisite]]
* [[IT/Community/WG/Infrastructure|Infrastructure]]

== '''Weekly Call''' ==
* Weekly Big Blue Button meeting, '''every other Friday at [http://www.wolframalpha.com/input/?i=3+PM+UTC+September+14+2013 8am US/Pacific (1500 UTC)]'''
* http://moz.bigbluebutton.org/moz/
** Room: Community IT
** Password: welcome

=== '''Meeting Agenda & Notes''' ===
* Upcoming
** [https://communityit.etherpad.mozilla.org/Meeting November 1]
* October 2013
** [https://communityit.etherpad.mozilla.org/Meeting October 18]
* September 2013
** [https://wiki.mozilla.org/IT/Community/Notes/2013-09-06 September 6]
* August 2013
** [https://wiki.mozilla.org/IT/Community/Notes/2013-08-23 August 23]
** [https://wiki.mozilla.org/IT/Community/Notes/2013-08-30 August 30]

IT/Community/WG/Discourse

2013-10-24T03:12:38Z

Mrz:

{| class="fullwidth-table"
|-
! Module Name
! Module Owner
|-
| Discourse || mrz
|}

=Summary=

[http://discourse.mozilla-community.org/ Test site] on mozilla-community.org.

= Documentation =
[[File:Discourse_diagram.png|200px|thumb|right|Architectural overview]]
== Overview ==
* '''Hosting Provider:''' HP Cloud
* '''Compute Region (AZ):''' US East (AZ2)

== Monitoring ==

== Instances ==
All images for webheads and HA Proxy are Ubuntu Precise 12.04 LTS Server 64-bit 20121026 (b)

=== HA Proxy ===
* '''Version:''' 1.4.18

{| class="fullwidth-table"
|-
! Name
! Service
! Flavor
! IP Addr
|-
| <tt>proxy1</tt> || haproxy || standard.medium || <tt>10.2.80.101</tt>
|-
| <tt>proxy2</tt> || haproxy || standard.medium || <tt>10.2.80.102</tt>
|}

=== Webheads ===

{| class="fullwidth-table"
|-
! Name
! Service
! Flavor
! IP Addr
|-
| <tt>discourse1</tt> || discourse/web || standard.medium || <tt>10.2.80.103</tt>
|-
| <tt>discourse2</tt> || discourse/web || standard.medium || <tt>10.2.80.104</tt>
|-
| <tt>discourse3</tt> || discourse/web || standard.medium || <tt>10.2.80.105</tt>
|}

=== Postgresql ===
* '''Version:''' 9.2

{| class="fullwidth-table"
|-
! Name
! Service
! Flavor
! Volume
! IP Addr
|-
| <tt>pgdb1</tt> || postgresql || highmem.large || pgdb1-data (100GB) || <tt>10.2.70.101</tt>
|-
| <tt>pgdb2</tt> || postgresql || highmem.large || pgdb2-data (100GB) || <tt>10.2.70.102</tt>
|-
| <tt>pgdb3</tt> || postgresql || highmem.large || pgdb3-data (100GB) || <tt>10.2.70.103</tt>
|-
| <tt>pgpool1</tt> || pgPool-II || standard.small |||| <tt>10.2.70.104</tt>
|-
| <tt>pgpool2</tt> || pgPool-II || standard.small |||| <tt>10.2.70.105</tt>
|}

= HP Cloud Reference =
== Flavors ==
<pre>
+-----+------------------+-----------+------+-----------+------+-------+-------------+-----------+
| ID | Name | Memory_MB | Disk | Ephemeral | Swap | VCPUs | RXTX_Factor | Is_Public |
+-----+------------------+-----------+------+-----------+------+-------+-------------+-----------+
| 100 | standard.xsmall | 1024 | 10 | 10 | | 1 | 1.0 | N/A |
| 101 | standard.small | 2048 | 30 | 10 | | 2 | 1.0 | N/A |
| 102 | standard.medium | 4096 | 30 | 50 | | 2 | 1.0 | N/A |
| 103 | standard.large | 8192 | 30 | 130 | | 4 | 1.0 | N/A |
| 104 | standard.xlarge | 15360 | 30 | 270 | | 4 | 1.0 | N/A |
| 105 | standard.2xlarge | 30720 | 30 | 540 | | 8 | 1.0 | N/A |
| 106 | standard.3xlarge | 61440 | 30 | 1070 | | 8 | 1.0 | N/A |
| 107 | standard.4xlarge | 92160 | 30 | 1620 | | 12 | 1.0 | N/A |
| 108 | standard.5xlarge | 122880 | 30 | 2170 | | 16 | 1.0 | N/A |
| 203 | highmem.large | 16384 | 30 | 130 | | 4 | 1.0 | N/A |
| 204 | highmem.xlarge | 30720 | 30 | 270 | | 4 | 1.0 | N/A |
| 205 | highmem.2xlarge | 61440 | 30 | 540 | | 8 | 1.0 | N/A |
+-----+------------------+-----------+------+-----------+------+-------+-------------+-----------+
</pre>

IT/Community

2013-10-24T03:11:59Z

Mrz: /* Modules */

= Our Mission =

'''Who we are'''

Mozilla Community IT Ops is a community of talented, volunteer Systems Administrators who devote their time and effort into supporting and managing community-based system infrastructure that support the Mozilla Project, while also learning and upgrading their skill sets in the progress.

'''What we are'''

We are a showcase for how to run the best of the best IT/Operations. We are open & transparent. We are a force multiplier, empowering the Community to promote Mozilla's Mission & Manifesto.

'''How we do it'''

Teaching and education are core to our mission and values. We mentor and teach today's skills and help put those skills to practical use by hosting and running production sites and services. We use [http://openbadges.org/ OpenBadges] to acknowledge skills and accomplishments.

= Getting Involved =
We need your help!

* Join the [https://mail.mozilla.org/listinfo/communityit Mailing List]
* Go to our IRC channel: [irc://irc.mozilla.org/%23communityit #CommunityIT on irc.mozilla.org]
* Join our weekly call

== Modules ==

Community IT Ops operates under a module ownership governance system. A module is a discrete unit of code or activity. An owner is the person in charge of a module or sub-module. A peer is a person whom the owner has appointed to help them. A module may have multiple peers and, very occasionally, multiple owners.

* [[IT/Community/WG/Phabricator|Phabricator]]
* [[IT/Community/WG/Badgus|Badg.us]]
* [[IT/Community/WG/MCSHosting|Mozilla Communities Hosting (MCS)]]
* [[IT/Community/WG/Discourse|Discourse]]
* [[IT/Community/WG/WordpressMS|Wordpress Multisite]]
* [[IT/Community/WG/Infrastructure|Infrastructure]]

== '''Weekly Call''' ==
* Weekly Big Blue Button meeting, '''every other Friday at [http://www.wolframalpha.com/input/?i=3+PM+UTC+September+14+2013 8am US/Pacific (1500 UTC)]'''
* http://moz.bigbluebutton.org/moz/
** Room: Community IT
** Password: welcome

=== '''Meeting Agenda & Notes''' ===
* Upcoming
** [https://communityit.etherpad.mozilla.org/Meeting October 18]
* October 2013
* September 2013
** [https://wiki.mozilla.org/IT/Community/Notes/2013-09-06 September 6]
* August 2013
** [https://wiki.mozilla.org/IT/Community/Notes/2013-08-23 August 23]
** [https://wiki.mozilla.org/IT/Community/Notes/2013-08-30 August 30]

IT/Community

2013-10-18T16:15:17Z

Mrz: /* Weekly Call */

= Our Mission =

'''Who we are'''

Mozilla Community IT Ops is a community of talented, volunteer Systems Administrators who devote their time and effort into supporting and managing community-based system infrastructure that support the Mozilla Project, while also learning and upgrading their skill sets in the progress.

'''What we are'''

We are a showcase for how to run the best of the best IT/Operations. We are open & transparent. We are a force multiplier, empowering the Community to promote Mozilla's Mission & Manifesto.

'''How we do it'''

Teaching and education are core to our mission and values. We mentor and teach today's skills and help put those skills to practical use by hosting and running production sites and services. We use [http://openbadges.org/ OpenBadges] to acknowledge skills and accomplishments.

= Getting Involved =
We need your help!

* Join the [https://mail.mozilla.org/listinfo/communityit Mailing List]
* Go to our IRC channel: [irc://irc.mozilla.org/%23communityit #CommunityIT on irc.mozilla.org]
* Join our weekly call

== Modules ==

Community IT Ops operates under a module ownership governance system. A module is a discrete unit of code or activity. An owner is the person in charge of a module or sub-module. A peer is a person whom the owner has appointed to help them. A module may have multiple peers and, very occasionally, multiple owners.

* [[IT/Community/WG/Badgus|Badg.us]]
* [[IT/Community/WG/MCSHosting|Mozilla Communities Hosting (MCS)]]
* [[IT/Community/WG/Discourse|Discourse]]
* [[IT/Community/WG/WordpressMS|Wordpress Multisite]]
* [[IT/Community/WG/Infrastructure|Infrastructure]]

== '''Weekly Call''' ==
* Weekly Big Blue Button meeting, '''every other Friday at [http://www.wolframalpha.com/input/?i=3+PM+UTC+September+14+2013 8am US/Pacific (1500 UTC)]'''
* http://moz.bigbluebutton.org/moz/
** Room: Community IT
** Password: welcome

=== '''Meeting Agenda & Notes''' ===
* Upcoming
** [https://communityit.etherpad.mozilla.org/Meeting October 18]
* October 2013
* September 2013
** [https://wiki.mozilla.org/IT/Community/Notes/2013-09-06 September 6]
* August 2013
** [https://wiki.mozilla.org/IT/Community/Notes/2013-08-23 August 23]
** [https://wiki.mozilla.org/IT/Community/Notes/2013-08-30 August 30]

IT/Community

2013-10-11T05:14:25Z

Mrz: /* Meeting Agenda & Notes */

= Our Mission =

'''Who we are'''

Mozilla Community IT Ops is a community of talented, volunteer Systems Administrators who devote their time and effort into supporting and managing community-based system infrastructure that support the Mozilla Project, while also learning and upgrading their skill sets in the progress.

'''What we are'''

We are a showcase for how to run the best of the best IT/Operations. We are open & transparent. We are a force multiplier, empowering the Community to promote Mozilla's Mission & Manifesto.

'''How we do it'''

Teaching and education are core to our mission and values. We mentor and teach today's skills and help put those skills to practical use by hosting and running production sites and services. We use [http://openbadges.org/ OpenBadges] to acknowledge skills and accomplishments.

= Getting Involved =
We need your help!

* Join the [https://mail.mozilla.org/listinfo/communityit Mailing List]
* Go to our IRC channel: [irc://irc.mozilla.org/%23communityit #CommunityIT on irc.mozilla.org]
* Join our weekly call

== Modules ==

Community IT Ops operates under a module ownership governance system. A module is a discrete unit of code or activity. An owner is the person in charge of a module or sub-module. A peer is a person whom the owner has appointed to help them. A module may have multiple peers and, very occasionally, multiple owners.

* [[IT/Community/WG/Badgus|Badg.us]]
* [[IT/Community/WG/MCSHosting|Mozilla Communities Hosting (MCS)]]
* [[IT/Community/WG/Discourse|Discourse]]
* [[IT/Community/WG/WordpressMS|Wordpress Multisite]]
* [[IT/Community/WG/Infrastructure|Infrastructure]]

== '''Weekly Call''' ==
* Weekly Big Blue Button meeting, '''every other Friday at [http://www.wolframalpha.com/input/?i=3+PM+UTC+September+14+2013 8am US/Pacific (1600 UTC)]'''
* http://moz.bigbluebutton.org/moz/
** Room: Community IT
** Password: welcome

=== '''Meeting Agenda & Notes''' ===
* Upcoming
** [https://communityit.etherpad.mozilla.org/Meeting October 18]
* October 2013
* September 2013
** [https://wiki.mozilla.org/IT/Community/Notes/2013-09-06 September 6]
* August 2013
** [https://wiki.mozilla.org/IT/Community/Notes/2013-08-23 August 23]
** [https://wiki.mozilla.org/IT/Community/Notes/2013-08-30 August 30]

IT/Community

2013-10-10T16:39:20Z

Mrz: /* Modules */

= Our Mission =

'''Who we are'''

Mozilla Community IT Ops is a community of talented, volunteer Systems Administrators who devote their time and effort into supporting and managing community-based system infrastructure that support the Mozilla Project, while also learning and upgrading their skill sets in the progress.

'''What we are'''

We are a showcase for how to run the best of the best IT/Operations. We are open & transparent. We are a force multiplier, empowering the Community to promote Mozilla's Mission & Manifesto.

'''How we do it'''

Teaching and education are core to our mission and values. We mentor and teach today's skills and help put those skills to practical use by hosting and running production sites and services. We use [http://openbadges.org/ OpenBadges] to acknowledge skills and accomplishments.

= Getting Involved =
We need your help!

* Join the [https://mail.mozilla.org/listinfo/communityit Mailing List]
* Go to our IRC channel: [irc://irc.mozilla.org/%23communityit #CommunityIT on irc.mozilla.org]
* Join our weekly call

== Modules ==

Community IT Ops operates under a module ownership governance system. A module is a discrete unit of code or activity. An owner is the person in charge of a module or sub-module. A peer is a person whom the owner has appointed to help them. A module may have multiple peers and, very occasionally, multiple owners.

* [[IT/Community/WG/Badgus|Badg.us]]
* [[IT/Community/WG/MCSHosting|Mozilla Communities Hosting (MCS)]]
* [[IT/Community/WG/Discourse|Discourse]]
* [[IT/Community/WG/WordpressMS|Wordpress Multisite]]
* [[IT/Community/WG/Infrastructure|Infrastructure]]

== '''Weekly Call''' ==
* Weekly Big Blue Button meeting, '''every other Friday at [http://www.wolframalpha.com/input/?i=3+PM+UTC+September+14+2013 8am US/Pacific (1600 UTC)]'''
* http://moz.bigbluebutton.org/moz/
** Room: Community IT
** Password: welcome

=== '''Meeting Agenda & Notes''' ===
* Upcoming
** [https://communityit.etherpad.mozilla.org/Meeting October 11]
* October 2013
* September 2013
** [https://wiki.mozilla.org/IT/Community/Notes/2013-09-06 September 6]
* August 2013
** [https://wiki.mozilla.org/IT/Community/Notes/2013-08-23 August 23]
** [https://wiki.mozilla.org/IT/Community/Notes/2013-08-30 August 30]

IT/Community/WG/Discourse

2013-10-09T22:01:20Z

Mrz: /* Instances */

{| class="fullwidth-table"
|-
! Module Name
! Module Owner
|-
| Discourse || Tom Farrow
|}

=Summary=

[http://discourse.mozilla-community.org/ Test site] on mozilla-community.org.

= Documentation =
[[File:Discourse_diagram.png|200px|thumb|right|Architectural overview]]
== Overview ==
* '''Hosting Provider:''' HP Cloud
* '''Compute Region (AZ):''' US East (AZ2)

== Monitoring ==

== Instances ==
All images for webheads and HA Proxy are Ubuntu Precise 12.04 LTS Server 64-bit 20121026 (b)

=== HA Proxy ===
* '''Version:''' 1.4.18

{| class="fullwidth-table"
|-
! Name
! Service
! Flavor
! IP Addr
|-
| <tt>proxy1</tt> || haproxy || standard.medium || <tt>10.2.80.101</tt>
|-
| <tt>proxy2</tt> || haproxy || standard.medium || <tt>10.2.80.102</tt>
|}

=== Webheads ===

{| class="fullwidth-table"
|-
! Name
! Service
! Flavor
! IP Addr
|-
| <tt>discourse1</tt> || discourse/web || standard.medium || <tt>10.2.80.103</tt>
|-
| <tt>discourse2</tt> || discourse/web || standard.medium || <tt>10.2.80.104</tt>
|-
| <tt>discourse3</tt> || discourse/web || standard.medium || <tt>10.2.80.105</tt>
|}

=== Postgresql ===
* '''Version:''' 9.2

{| class="fullwidth-table"
|-
! Name
! Service
! Flavor
! Volume
! IP Addr
|-
| <tt>pgdb1</tt> || postgresql || highmem.large || pgdb1-data (100GB) || <tt>10.2.70.101</tt>
|-
| <tt>pgdb2</tt> || postgresql || highmem.large || pgdb2-data (100GB) || <tt>10.2.70.102</tt>
|-
| <tt>pgdb3</tt> || postgresql || highmem.large || pgdb3-data (100GB) || <tt>10.2.70.103</tt>
|-
| <tt>pgpool1</tt> || pgPool-II || standard.small |||| <tt>10.2.70.104</tt>
|-
| <tt>pgpool2</tt> || pgPool-II || standard.small |||| <tt>10.2.70.105</tt>
|}

= HP Cloud Reference =
== Flavors ==
<pre>
+-----+------------------+-----------+------+-----------+------+-------+-------------+-----------+
| ID | Name | Memory_MB | Disk | Ephemeral | Swap | VCPUs | RXTX_Factor | Is_Public |
+-----+------------------+-----------+------+-----------+------+-------+-------------+-----------+
| 100 | standard.xsmall | 1024 | 10 | 10 | | 1 | 1.0 | N/A |
| 101 | standard.small | 2048 | 30 | 10 | | 2 | 1.0 | N/A |
| 102 | standard.medium | 4096 | 30 | 50 | | 2 | 1.0 | N/A |
| 103 | standard.large | 8192 | 30 | 130 | | 4 | 1.0 | N/A |
| 104 | standard.xlarge | 15360 | 30 | 270 | | 4 | 1.0 | N/A |
| 105 | standard.2xlarge | 30720 | 30 | 540 | | 8 | 1.0 | N/A |
| 106 | standard.3xlarge | 61440 | 30 | 1070 | | 8 | 1.0 | N/A |
| 107 | standard.4xlarge | 92160 | 30 | 1620 | | 12 | 1.0 | N/A |
| 108 | standard.5xlarge | 122880 | 30 | 2170 | | 16 | 1.0 | N/A |
| 203 | highmem.large | 16384 | 30 | 130 | | 4 | 1.0 | N/A |
| 204 | highmem.xlarge | 30720 | 30 | 270 | | 4 | 1.0 | N/A |
| 205 | highmem.2xlarge | 61440 | 30 | 540 | | 8 | 1.0 | N/A |
+-----+------------------+-----------+------+-----------+------+-------+-------------+-----------+
</pre>

IT/Community/WG/Discourse

2013-10-09T18:26:06Z

Mrz: /* Postgresql */

{| class="fullwidth-table"
|-
! Module Name
! Module Owner
|-
| Discourse || Tom Farrow
|}

=Summary=

[http://discourse.mozilla-community.org/ Test site] on mozilla-community.org.

= Documentation =
[[File:Discourse_diagram.png|200px|thumb|right|Architectural overview]]
== Overview ==
* '''Hosting Provider:''' HP Cloud
* '''Compute Region (AZ):''' US East (AZ2)

== Monitoring ==

== Instances ==
All images for webheads and HA Proxy are Ubuntu Precise 12.04 LTS Server 64-bit 20121026 (b) 
Postgresql images are CentOS 6.3 Server 64-bit 20130116 (b)

=== HA Proxy ===
* '''Version:''' 1.4.18

{| class="fullwidth-table"
|-
! Name
! Service
! Flavor
! IP Addr
|-
| <tt>proxy1</tt> || haproxy || standard.medium || <tt>10.2.80.101</tt>
|-
| <tt>proxy2</tt> || haproxy || standard.medium || <tt>10.2.80.102</tt>
|}

=== Webheads ===

{| class="fullwidth-table"
|-
! Name
! Service
! Flavor
! IP Addr
|-
| <tt>discourse1</tt> || discourse/web || standard.medium || <tt>10.2.80.103</tt>
|-
| <tt>discourse2</tt> || discourse/web || standard.medium || <tt>10.2.80.104</tt>
|-
| <tt>discourse3</tt> || discourse/web || standard.medium || <tt>10.2.80.105</tt>
|}

=== Postgresql ===
* '''Version:''' 9.2

{| class="fullwidth-table"
|-
! Name
! Service
! Flavor
! Volume
! IP Addr
|-
| <tt>pgdb1</tt> || postgresql || highmem.large || pgdb1-data (100GB) || <tt>10.2.70.101</tt>
|-
| <tt>pgdb2</tt> || postgresql || highmem.large || pgdb2-data (100GB) || <tt>10.2.70.102</tt>
|-
| <tt>pgdb3</tt> || postgresql || highmem.large || pgdb3-data (100GB) || <tt>10.2.70.103</tt>
|-
| <tt>pgpool1</tt> || pgPool-II || standard.small |||| <tt>10.2.70.104</tt>
|-
| <tt>pgpool2</tt> || pgPool-II || standard.small |||| <tt>10.2.70.105</tt>
|}

= HP Cloud Reference =
== Flavors ==
<pre>
+-----+------------------+-----------+------+-----------+------+-------+-------------+-----------+
| ID | Name | Memory_MB | Disk | Ephemeral | Swap | VCPUs | RXTX_Factor | Is_Public |
+-----+------------------+-----------+------+-----------+------+-------+-------------+-----------+
| 100 | standard.xsmall | 1024 | 10 | 10 | | 1 | 1.0 | N/A |
| 101 | standard.small | 2048 | 30 | 10 | | 2 | 1.0 | N/A |
| 102 | standard.medium | 4096 | 30 | 50 | | 2 | 1.0 | N/A |
| 103 | standard.large | 8192 | 30 | 130 | | 4 | 1.0 | N/A |
| 104 | standard.xlarge | 15360 | 30 | 270 | | 4 | 1.0 | N/A |
| 105 | standard.2xlarge | 30720 | 30 | 540 | | 8 | 1.0 | N/A |
| 106 | standard.3xlarge | 61440 | 30 | 1070 | | 8 | 1.0 | N/A |
| 107 | standard.4xlarge | 92160 | 30 | 1620 | | 12 | 1.0 | N/A |
| 108 | standard.5xlarge | 122880 | 30 | 2170 | | 16 | 1.0 | N/A |
| 203 | highmem.large | 16384 | 30 | 130 | | 4 | 1.0 | N/A |
| 204 | highmem.xlarge | 30720 | 30 | 270 | | 4 | 1.0 | N/A |
| 205 | highmem.2xlarge | 61440 | 30 | 540 | | 8 | 1.0 | N/A |
+-----+------------------+-----------+------+-----------+------+-------+-------------+-----------+
</pre>

WeeklyUpdates/2013-10-14

2013-10-09T04:13:02Z

Mrz: /* Friends of the Tree Friends of the Tree */

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

__TOC__

= All-hands Status Meeting Agenda =

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

== Friends of the Tree [[Image:Tree.gif|Friends of the Tree]] ==

* Williamr and his team for making improvements to the mozillians site
* [https://mozillians.org/en-US/u/ewong/ Edmund Wong] and [https://wiki.mozilla.org/IT/Community Community IT] (but especially ewong!) for migrating [http://badg.us badg.us] to [https://wiki.mozilla.org/IT/Community/WG/Badgus Community IT Infrastructure]
** Blog post ~ [http://mrz.velvet.org/2013/10/14/openbadges-badg-us-community-it OpenBadges, badg.us & Community IT]

== Upcoming Events ==

=== This Week ===

=== Monday, {{#time:d F|{{SUBPAGENAME}}}} ===

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

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

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

=== Friday, {{#time:d F|{{SUBPAGENAME}} +4 days}} ===
* [http://www.wolframalpha.com/input/?i=3+PM+UTC+October+14+2013 8:00 AM Pacific / 13:00 UTC]: Community IT Bi-Monthly Meetup
** [[IT/Community#Weekly_Call|Agenda and dial-in information]] (feel free to add items to the agenda)

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

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

=== Next Week ===

== Product Status Updates (voice updates) ==

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

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

=== Thunderbird ===
''Speaker Location:''

=== Older Branch Work ===
''Speaker Location:''

=== Webmaker ===
''Speaker Location:''

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

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

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

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

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

== Speakers ==

The limit is 3 minutes per speaker. It's like a lightning talk, but don't feel that you have to have slides in order to make a presentation. If you plan on showing a video, you need to contact the Air Mozilla team before the day of the meeting or you will be deferred to the next week.

{| class="fullwidth-table"
|-
! Presenter
! Title
! Topic
! Location
! Share?
! Media
! More Details
|-
| Who Are You?
| What Do You Do?
| What are you going to talk about?
| Where are you presenting from? (Moz Space, your house, space)
| Will you be sharing your screen? (yes/no, other info)
| Links to slides or images you want displayed on screen
| Link to where audience can find out more information
|-
|}

= Roundtable =

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

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

{| class="fullwidth-table"
|-
! Who are you?
! Area of question
! Question
|-
| ''What's your name? What do you work on?''
| ''Is your question about policy, a product, a Foundation initiative, etc.''
| ''What would you like to know?''
|-
| ''David Weir and a contributor''
| ''Summit question.''
| ''Were can we see picturs from the summit if you were not their, ?''

|-
|}

= Welcome! =

Let's say hello to some new Mozillians!

== Introducing New Hires ==
{| class="fullwidth-table"
|-
! New Hire
! Introduced by
! Speaker location
! New Hire location
! Will be working on
|-
| ''Who is the new hire?''
| ''Who will be introducing that person?''
| ''Where is the introducer?''
| ''Where will the new person be working from?''
| ''What will the new person be working on?''
|-
| Jane Hsu
|
|
| Taipei
| Firefox OS - Product Marketing, GTM (go to market)
|-
| Bevis Tseng
|
|
| Taipei
| Firefox OS - RIL team
|-
| Mike Tsai
|
|
| Taipei
| Firefox OS - UX (User Experience) team

|-
|}

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

|-
|}

= <meta> =

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

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

=== Firefox ===

=== Platform ===

=== Services ===

=== Messaging ===

=== Mobile ===

=== IT ===

=== Release Engineering ===

=== QA ===

==== Test Execution ====

==== WebQA ====

==== QA Community ====

=== Automation & Tools ===

=== Security ===

=== Engagement ===

==== PR ====

==== Events ====

WeeklyUpdates/2013-10-14

2013-10-09T04:12:34Z

Mrz: /* Friends of the Tree Friends of the Tree */

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

__TOC__

= All-hands Status Meeting Agenda =

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

== Friends of the Tree [[Image:Tree.gif|Friends of the Tree]] ==

* Williamr and his team for making improvements to the mozillians site
* [https://mozillians.org/en-US/u/ewong/ Edmund Wong] and [https://wiki.mozilla.org/IT/Community Community IT] (but especially ewong!) for migrating [http://badg.us badg.us] to [https://wiki.mozilla.org/IT/Community/WG/Badgus Community IT Infrastructure]
** Blog post ~ <a href="http://mrz.velvet.org/2013/10/14/openbadges-badg-us-community-it">OpenBadges, badg.us & Community IT</a>

== Upcoming Events ==

=== This Week ===

=== Monday, {{#time:d F|{{SUBPAGENAME}}}} ===

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

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

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

=== Friday, {{#time:d F|{{SUBPAGENAME}} +4 days}} ===
* [http://www.wolframalpha.com/input/?i=3+PM+UTC+October+14+2013 8:00 AM Pacific / 13:00 UTC]: Community IT Bi-Monthly Meetup
** [[IT/Community#Weekly_Call|Agenda and dial-in information]] (feel free to add items to the agenda)

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

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

=== Next Week ===

== Product Status Updates (voice updates) ==

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

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

=== Thunderbird ===
''Speaker Location:''

=== Older Branch Work ===
''Speaker Location:''

=== Webmaker ===
''Speaker Location:''

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

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

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

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

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

== Speakers ==

The limit is 3 minutes per speaker. It's like a lightning talk, but don't feel that you have to have slides in order to make a presentation. If you plan on showing a video, you need to contact the Air Mozilla team before the day of the meeting or you will be deferred to the next week.

{| class="fullwidth-table"
|-
! Presenter
! Title
! Topic
! Location
! Share?
! Media
! More Details
|-
| Who Are You?
| What Do You Do?
| What are you going to talk about?
| Where are you presenting from? (Moz Space, your house, space)
| Will you be sharing your screen? (yes/no, other info)
| Links to slides or images you want displayed on screen
| Link to where audience can find out more information
|-
|}

= Roundtable =

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

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

{| class="fullwidth-table"
|-
! Who are you?
! Area of question
! Question
|-
| ''What's your name? What do you work on?''
| ''Is your question about policy, a product, a Foundation initiative, etc.''
| ''What would you like to know?''
|-
| ''David Weir and a contributor''
| ''Summit question.''
| ''Were can we see picturs from the summit if you were not their, ?''

|-
|}

= Welcome! =

Let's say hello to some new Mozillians!

== Introducing New Hires ==
{| class="fullwidth-table"
|-
! New Hire
! Introduced by
! Speaker location
! New Hire location
! Will be working on
|-
| ''Who is the new hire?''
| ''Who will be introducing that person?''
| ''Where is the introducer?''
| ''Where will the new person be working from?''
| ''What will the new person be working on?''
|-
| Jane Hsu
|
|
| Taipei
| Firefox OS - Product Marketing, GTM (go to market)
|-
| Bevis Tseng
|
|
| Taipei
| Firefox OS - RIL team
|-
| Mike Tsai
|
|
| Taipei
| Firefox OS - UX (User Experience) team

|-
|}

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

|-
|}

= <meta> =

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

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

=== Firefox ===

=== Platform ===

=== Services ===

=== Messaging ===

=== Mobile ===

=== IT ===

=== Release Engineering ===

=== QA ===

==== Test Execution ====

==== WebQA ====

==== QA Community ====

=== Automation & Tools ===

=== Security ===

=== Engagement ===

==== PR ====

==== Events ====

WeeklyUpdates/2013-10-14

2013-10-09T04:11:42Z

Mrz: /* Friends of the Tree Friends of the Tree */

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

__TOC__

= All-hands Status Meeting Agenda =

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

== Friends of the Tree [[Image:Tree.gif|Friends of the Tree]] ==

* Williamr and his team for making improvements to the mozillians site
* [https://mozillians.org/en-US/u/ewong/ Edmund Wong] and [https://wiki.mozilla.org/IT/Community Community IT] (but especially ewong!) for migrating [http://badg.us badg.us] to [https://wiki.mozilla.org/IT/Community/WG/Badgus Community IT Infrastructure]
** Blog post ~ <a href="http:// http://mrz.velvet.org/2013/10/14/openbadges-bad…s-community-it/">OpenBadges, badg.us & Community IT</a>

== Upcoming Events ==

=== This Week ===

=== Monday, {{#time:d F|{{SUBPAGENAME}}}} ===

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

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

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

=== Friday, {{#time:d F|{{SUBPAGENAME}} +4 days}} ===
* [http://www.wolframalpha.com/input/?i=3+PM+UTC+October+14+2013 8:00 AM Pacific / 13:00 UTC]: Community IT Bi-Monthly Meetup
** [[IT/Community#Weekly_Call|Agenda and dial-in information]] (feel free to add items to the agenda)

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

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

=== Next Week ===

== Product Status Updates (voice updates) ==

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

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

=== Thunderbird ===
''Speaker Location:''

=== Older Branch Work ===
''Speaker Location:''

=== Webmaker ===
''Speaker Location:''

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

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

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

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

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

== Speakers ==

The limit is 3 minutes per speaker. It's like a lightning talk, but don't feel that you have to have slides in order to make a presentation. If you plan on showing a video, you need to contact the Air Mozilla team before the day of the meeting or you will be deferred to the next week.

{| class="fullwidth-table"
|-
! Presenter
! Title
! Topic
! Location
! Share?
! Media
! More Details
|-
| Who Are You?
| What Do You Do?
| What are you going to talk about?
| Where are you presenting from? (Moz Space, your house, space)
| Will you be sharing your screen? (yes/no, other info)
| Links to slides or images you want displayed on screen
| Link to where audience can find out more information
|-
|}

= Roundtable =

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

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

{| class="fullwidth-table"
|-
! Who are you?
! Area of question
! Question
|-
| ''What's your name? What do you work on?''
| ''Is your question about policy, a product, a Foundation initiative, etc.''
| ''What would you like to know?''
|-
| ''David Weir and a contributor''
| ''Summit question.''
| ''Were can we see picturs from the summit if you were not their, ?''

|-
|}

= Welcome! =

Let's say hello to some new Mozillians!

== Introducing New Hires ==
{| class="fullwidth-table"
|-
! New Hire
! Introduced by
! Speaker location
! New Hire location
! Will be working on
|-
| ''Who is the new hire?''
| ''Who will be introducing that person?''
| ''Where is the introducer?''
| ''Where will the new person be working from?''
| ''What will the new person be working on?''
|-
| Jane Hsu
|
|
| Taipei
| Firefox OS - Product Marketing, GTM (go to market)
|-
| Bevis Tseng
|
|
| Taipei
| Firefox OS - RIL team
|-
| Mike Tsai
|
|
| Taipei
| Firefox OS - UX (User Experience) team

|-
|}

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

|-
|}

= <meta> =

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

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

=== Firefox ===

=== Platform ===

=== Services ===

=== Messaging ===

=== Mobile ===

=== IT ===

=== Release Engineering ===

=== QA ===

==== Test Execution ====

==== WebQA ====

==== QA Community ====

=== Automation & Tools ===

=== Security ===

=== Engagement ===

==== PR ====

==== Events ====

IT/Community

2013-10-09T03:58:59Z

Mrz: /* Meeting Agenda & Notes */

= Our Mission =

'''Who we are'''

Mozilla Community IT Ops is a community of talented, volunteer Systems Administrators who devote their time and effort into supporting and managing community-based system infrastructure that support the Mozilla Project, while also learning and upgrading their skill sets in the progress.

'''What we are'''

We are a showcase for how to run the best of the best IT/Operations. We are open & transparent. We are a force multiplier, empowering the Community to promote Mozilla's Mission & Manifesto.

'''How we do it'''

Teaching and education are core to our mission and values. We mentor and teach today's skills and help put those skills to practical use by hosting and running production sites and services. We use [http://openbadges.org/ OpenBadges] to acknowledge skills and accomplishments.

= Getting Involved =
We need your help!

* Join the [https://mail.mozilla.org/listinfo/communityit Mailing List]
* Go to our IRC channel: [irc://irc.mozilla.org/%23communityit #CommunityIT on irc.mozilla.org]
* Join our weekly call

== Modules ==

Community IT Ops operates under a module ownership governance system. A module is a discrete unit of code or activity. An owner is the person in charge of a module or sub-module. A peer is a person whom the owner has appointed to help them. A module may have multiple peers and, very occasionally, multiple owners.

* [[IT/Community/WG/Badgus|Badg.us]]
* [[IT/Community/WG/MCSHosting|Mozilla Communities Hosting (MCS)]]
* [[IT/Community/WG/Discourse|Discourse]]
* [[IT/Community/WG/WordpressMS|Wordpress Multisite]]
* [[IT/Community/WG/MozFest|Moz Fest Event Support]]
* [[IT/Community/WG/Infrastructure|Infrastructure]]

== '''Weekly Call''' ==
* Weekly Big Blue Button meeting, '''every other Friday at [http://www.wolframalpha.com/input/?i=3+PM+UTC+September+14+2013 8am US/Pacific (1600 UTC)]'''
* http://moz.bigbluebutton.org/moz/
** Room: Community IT
** Password: welcome

=== '''Meeting Agenda & Notes''' ===
* Upcoming
** [https://communityit.etherpad.mozilla.org/Meeting October 11]
* October 2013
* September 2013
** [https://wiki.mozilla.org/IT/Community/Notes/2013-09-06 September 6]
* August 2013
** [https://wiki.mozilla.org/IT/Community/Notes/2013-08-23 August 23]
** [https://wiki.mozilla.org/IT/Community/Notes/2013-08-30 August 30]

IT/Community

2013-10-09T03:58:27Z

Mrz: /* Weekly Call */

= Our Mission =

'''Who we are'''

Mozilla Community IT Ops is a community of talented, volunteer Systems Administrators who devote their time and effort into supporting and managing community-based system infrastructure that support the Mozilla Project, while also learning and upgrading their skill sets in the progress.

'''What we are'''

We are a showcase for how to run the best of the best IT/Operations. We are open & transparent. We are a force multiplier, empowering the Community to promote Mozilla's Mission & Manifesto.

'''How we do it'''

Teaching and education are core to our mission and values. We mentor and teach today's skills and help put those skills to practical use by hosting and running production sites and services. We use [http://openbadges.org/ OpenBadges] to acknowledge skills and accomplishments.

= Getting Involved =
We need your help!

* Join the [https://mail.mozilla.org/listinfo/communityit Mailing List]
* Go to our IRC channel: [irc://irc.mozilla.org/%23communityit #CommunityIT on irc.mozilla.org]
* Join our weekly call

== Modules ==

Community IT Ops operates under a module ownership governance system. A module is a discrete unit of code or activity. An owner is the person in charge of a module or sub-module. A peer is a person whom the owner has appointed to help them. A module may have multiple peers and, very occasionally, multiple owners.

* [[IT/Community/WG/Badgus|Badg.us]]
* [[IT/Community/WG/MCSHosting|Mozilla Communities Hosting (MCS)]]
* [[IT/Community/WG/Discourse|Discourse]]
* [[IT/Community/WG/WordpressMS|Wordpress Multisite]]
* [[IT/Community/WG/MozFest|Moz Fest Event Support]]
* [[IT/Community/WG/Infrastructure|Infrastructure]]

== '''Weekly Call''' ==
* Weekly Big Blue Button meeting, '''every other Friday at [http://www.wolframalpha.com/input/?i=3+PM+UTC+September+14+2013 8am US/Pacific (1600 UTC)]'''
* http://moz.bigbluebutton.org/moz/
** Room: Community IT
** Password: welcome

=== '''Meeting Agenda & Notes''' ===

* August 2013
** [https://wiki.mozilla.org/IT/Community/Notes/2013-08-23 August 23]
** [https://wiki.mozilla.org/IT/Community/Notes/2013-08-30 August 30]
* September 2013
** [https://wiki.mozilla.org/IT/Community/Notes/2013-09-06 September 6]
* Upcoming
** [https://communityit.etherpad.mozilla.org/Meeting October 11]

IT/Community

2013-10-09T03:38:03Z

Mrz: /* Our Mission */

= Our Mission =

'''Who we are'''

Mozilla Community IT Ops is a community of talented, volunteer Systems Administrators who devote their time and effort into supporting and managing community-based system infrastructure that support the Mozilla Project, while also learning and upgrading their skill sets in the progress.

'''What we are'''

We are a showcase for how to run the best of the best IT/Operations. We are open & transparent. We are a force multiplier, empowering the Community to promote Mozilla's Mission & Manifesto.

'''How we do it'''

Teaching and education are core to our mission and values. We mentor and teach today's skills and help put those skills to practical use by hosting and running production sites and services. We use [http://openbadges.org/ OpenBadges] to acknowledge skills and accomplishments.

= Getting Involved =
We need your help!

* Join the [https://mail.mozilla.org/listinfo/communityit Mailing List]
* Go to our IRC channel: [irc://irc.mozilla.org/%23communityit #CommunityIT on irc.mozilla.org]
* Join our weekly call

== Modules ==

Community IT Ops operates under a module ownership governance system. A module is a discrete unit of code or activity. An owner is the person in charge of a module or sub-module. A peer is a person whom the owner has appointed to help them. A module may have multiple peers and, very occasionally, multiple owners.

* [[IT/Community/WG/Badgus|Badg.us]]
* [[IT/Community/WG/MCSHosting|Mozilla Communities Hosting (MCS)]]
* [[IT/Community/WG/Discourse|Discourse]]
* [[IT/Community/WG/WordpressMS|Wordpress Multisite]]
* [[IT/Community/WG/MozFest|Moz Fest Event Support]]
* [[IT/Community/WG/Infrastructure|Infrastructure]]

== '''Weekly Call''' ==
* Weekly Big Blue Button meeting, '''every Saturday at [http://www.wolframalpha.com/input/?i=4+PM+UTC+September+14+2013 9am US/Pacific (1600 UTC)]'''
* http://moz.bigbluebutton.org/moz/
** Room: Community IT
** Password: welcome

=== '''Meeting Agenda & Notes''' ===

* August 2013
** [https://wiki.mozilla.org/IT/Community/Notes/2013-08-23 August 23]
** [https://wiki.mozilla.org/IT/Community/Notes/2013-08-30 August 30]
* September 2013
** [https://wiki.mozilla.org/IT/Community/Notes/2013-09-06 September 6]
** [https://communityit.etherpad.mozilla.org/Meeting September 14]

IT/Community/WG/Discourse

2013-10-08T21:37:09Z

Mrz: /* Postgresql */

{| class="fullwidth-table"
|-
! Module Name
! Module Owner
|-
| Discourse || Tom Farrow
|}

=Summary=

[http://discourse.mozilla-community.org/ Test site] on mozilla-community.org.

= Documentation =
[[File:Discourse_diagram.png|200px|thumb|right|Architectural overview]]
== Overview ==
* '''Hosting Provider:''' HP Cloud
* '''Compute Region (AZ):''' US East (AZ2)

== Monitoring ==

== Instances ==
All images for webheads and HA Proxy are Ubuntu Precise 12.04 LTS Server 64-bit 20121026 (b) 
Postgresql images are CentOS 6.3 Server 64-bit 20130116 (b)

=== HA Proxy ===
* '''Version:''' 1.4.18

{| class="fullwidth-table"
|-
! Name
! Service
! Flavor
! IP Addr
|-
| <tt>proxy1</tt> || haproxy || standard.medium || <tt>10.2.80.101</tt>
|-
| <tt>proxy2</tt> || haproxy || standard.medium || <tt>10.2.80.102</tt>
|}

=== Webheads ===

{| class="fullwidth-table"
|-
! Name
! Service
! Flavor
! IP Addr
|-
| <tt>discourse1</tt> || discourse/web || standard.medium || <tt>10.2.80.103</tt>
|-
| <tt>discourse2</tt> || discourse/web || standard.medium || <tt>10.2.80.104</tt>
|-
| <tt>discourse3</tt> || discourse/web || standard.medium || <tt>10.2.80.105</tt>
|}

=== Postgresql ===
* '''Version:''' 9.2
'''Servers are not available by SSH locally, but via the pg-jump1 instance.
All traffic between the world and the servers are cancelled. You *must* communicate from a local server'''

{| class="fullwidth-table"
|-
! Name
! Service
! Flavor
! Volume
! IP Addr
! AZ
|-
|<tt>pg-master</tt>||postgresql||highmem.large||pg-master-data (200GB)||<tt>10.2.70.101</tt>||AZ2
|}

{| class="fullwidth-table"
|-
! Name
! Service
! Flavor
! Volume
! IP Addr
|-
| <tt>pgdb1</tt> || postgresql || highmem.large || pgdb1-data (100GB) || <tt>10.2.70.101</tt>
|-
| <tt>pgdb1</tt> || postgresql || highmem.large || pgdb2-data (100GB) || <tt>10.2.70.101</tt>
|}

= HP Cloud Reference =
== Flavors ==
<pre>
+-----+------------------+-----------+------+-----------+------+-------+-------------+-----------+
| ID | Name | Memory_MB | Disk | Ephemeral | Swap | VCPUs | RXTX_Factor | Is_Public |
+-----+------------------+-----------+------+-----------+------+-------+-------------+-----------+
| 100 | standard.xsmall | 1024 | 10 | 10 | | 1 | 1.0 | N/A |
| 101 | standard.small | 2048 | 30 | 10 | | 2 | 1.0 | N/A |
| 102 | standard.medium | 4096 | 30 | 50 | | 2 | 1.0 | N/A |
| 103 | standard.large | 8192 | 30 | 130 | | 4 | 1.0 | N/A |
| 104 | standard.xlarge | 15360 | 30 | 270 | | 4 | 1.0 | N/A |
| 105 | standard.2xlarge | 30720 | 30 | 540 | | 8 | 1.0 | N/A |
| 106 | standard.3xlarge | 61440 | 30 | 1070 | | 8 | 1.0 | N/A |
| 107 | standard.4xlarge | 92160 | 30 | 1620 | | 12 | 1.0 | N/A |
| 108 | standard.5xlarge | 122880 | 30 | 2170 | | 16 | 1.0 | N/A |
| 203 | highmem.large | 16384 | 30 | 130 | | 4 | 1.0 | N/A |
| 204 | highmem.xlarge | 30720 | 30 | 270 | | 4 | 1.0 | N/A |
| 205 | highmem.2xlarge | 61440 | 30 | 540 | | 8 | 1.0 | N/A |
+-----+------------------+-----------+------+-----------+------+-------+-------------+-----------+
</pre>

WeeklyUpdates/2013-10-14

2013-10-08T04:17:02Z

Mrz: /* Friday, {{#time:d F|{{SUBPAGENAME}} +4 days}} */

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

__TOC__

= All-hands Status Meeting Agenda =

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

== Friends of the Tree [[Image:Tree.gif|Friends of the Tree]] ==

* Williamr and his team for making improvements to the mozillians site
* [https://mozillians.org/en-US/u/ewong/ Edmund Wong] and [https://wiki.mozilla.org/IT/Community Community IT] (but especially ewong!) for migrating [http://badg.us badg.us] to [https://wiki.mozilla.org/IT/Community/WG/Badgus Community IT Infrastructure]
** See also <blog post>

== Upcoming Events ==

=== This Week ===

=== Monday, {{#time:d F|{{SUBPAGENAME}}}} ===

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

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

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

=== Friday, {{#time:d F|{{SUBPAGENAME}} +4 days}} ===
* [http://www.wolframalpha.com/input/?i=3+PM+UTC+October+14+2013 8:00 AM Pacific / 13:00 UTC]: Community IT Bi-Monthly Meetup
** [[IT/Community#Weekly_Call|Agenda and dial-in information]] (feel free to add items to the agenda)

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

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

=== Next Week ===

== Product Status Updates (voice updates) ==

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

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

=== Thunderbird ===
''Speaker Location:''

=== Older Branch Work ===
''Speaker Location:''

=== Webmaker ===
''Speaker Location:''

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

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

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

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

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

== Speakers ==

The limit is 3 minutes per speaker. It's like a lightning talk, but don't feel that you have to have slides in order to make a presentation. If you plan on showing a video, you need to contact the Air Mozilla team before the day of the meeting or you will be deferred to the next week.

{| class="fullwidth-table"
|-
! Presenter
! Title
! Topic
! Location
! Share?
! Media
! More Details
|-
| Who Are You?
| What Do You Do?
| What are you going to talk about?
| Where are you presenting from? (Moz Space, your house, space)
| Will you be sharing your screen? (yes/no, other info)
| Links to slides or images you want displayed on screen
| Link to where audience can find out more information
|-
|}

= Roundtable =

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

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

{| class="fullwidth-table"
|-
! Who are you?
! Area of question
! Question
|-
| ''What's your name? What do you work on?''
| ''Is your question about policy, a product, a Foundation initiative, etc.''
| ''What would you like to know?''
|-
| ''David Weir and a contributor''
| ''Summit question.''
| ''Were can we see picturs from the summit if you were not their, ?''

|-
|}

= Welcome! =

Let's say hello to some new Mozillians!

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

|-
|}

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

|-
|}

= <meta> =

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

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

=== Firefox ===

=== Platform ===

=== Services ===

=== Messaging ===

=== Mobile ===

=== IT ===

=== Release Engineering ===

=== QA ===

==== Test Execution ====

==== WebQA ====

==== QA Community ====

=== Automation & Tools ===

=== Security ===

=== Engagement ===

==== PR ====

==== Events ====

WeeklyUpdates/2013-10-14

2013-10-08T04:14:59Z

Mrz: /* Friends of the Tree Friends of the Tree */

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

__TOC__

= All-hands Status Meeting Agenda =

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

== Friends of the Tree [[Image:Tree.gif|Friends of the Tree]] ==

* Williamr and his team for making improvements to the mozillians site
* [https://mozillians.org/en-US/u/ewong/ Edmund Wong] and [https://wiki.mozilla.org/IT/Community Community IT] (but especially ewong!) for migrating [http://badg.us badg.us] to [https://wiki.mozilla.org/IT/Community/WG/Badgus Community IT Infrastructure]
** See also <blog post>

== Upcoming Events ==

=== This Week ===

=== Monday, {{#time:d F|{{SUBPAGENAME}}}} ===

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

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

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

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

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

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

=== Next Week ===

== Product Status Updates (voice updates) ==

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

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

=== Thunderbird ===
''Speaker Location:''

=== Older Branch Work ===
''Speaker Location:''

=== Webmaker ===
''Speaker Location:''

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

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

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

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

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

== Speakers ==

The limit is 3 minutes per speaker. It's like a lightning talk, but don't feel that you have to have slides in order to make a presentation. If you plan on showing a video, you need to contact the Air Mozilla team before the day of the meeting or you will be deferred to the next week.

{| class="fullwidth-table"
|-
! Presenter
! Title
! Topic
! Location
! Share?
! Media
! More Details
|-
| Who Are You?
| What Do You Do?
| What are you going to talk about?
| Where are you presenting from? (Moz Space, your house, space)
| Will you be sharing your screen? (yes/no, other info)
| Links to slides or images you want displayed on screen
| Link to where audience can find out more information
|-
|}

= Roundtable =

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

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

{| class="fullwidth-table"
|-
! Who are you?
! Area of question
! Question
|-
| ''What's your name? What do you work on?''
| ''Is your question about policy, a product, a Foundation initiative, etc.''
| ''What would you like to know?''
|-
| ''David Weir and a contributor''
| ''Summit question.''
| ''Were can we see picturs from the summit if you were not their, ?''

|-
|}

= Welcome! =

Let's say hello to some new Mozillians!

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

|-
|}

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

|-
|}

= <meta> =

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

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

=== Firefox ===

=== Platform ===

=== Services ===

=== Messaging ===

=== Mobile ===

=== IT ===

=== Release Engineering ===

=== QA ===

==== Test Execution ====

==== WebQA ====

==== QA Community ====

=== Automation & Tools ===

=== Security ===

=== Engagement ===

==== PR ====

==== Events ====

WeeklyUpdates/2013-10-14

2013-10-08T04:14:10Z

Mrz: /* Friends of the Tree Friends of the Tree */

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

__TOC__

= All-hands Status Meeting Agenda =

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

== Friends of the Tree [[Image:Tree.gif|Friends of the Tree]] ==

* Williamr and his team for making improvements to the mozillians site
* [https://mozillians.org/en-US/u/ewong/ Edmund Wong] and [https://wiki.mozilla.org/IT/Community Community IT] for migrating [http://badg.us badg.us] to [https://wiki.mozilla.org/IT/Community/WG/Badgus Community IT Infrastructure]
** See also <blog post>

== Upcoming Events ==

=== This Week ===

=== Monday, {{#time:d F|{{SUBPAGENAME}}}} ===

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

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

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

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

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

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

=== Next Week ===

== Product Status Updates (voice updates) ==

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

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

=== Thunderbird ===
''Speaker Location:''

=== Older Branch Work ===
''Speaker Location:''

=== Webmaker ===
''Speaker Location:''

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

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

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

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

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

== Speakers ==

The limit is 3 minutes per speaker. It's like a lightning talk, but don't feel that you have to have slides in order to make a presentation. If you plan on showing a video, you need to contact the Air Mozilla team before the day of the meeting or you will be deferred to the next week.

{| class="fullwidth-table"
|-
! Presenter
! Title
! Topic
! Location
! Share?
! Media
! More Details
|-
| Who Are You?
| What Do You Do?
| What are you going to talk about?
| Where are you presenting from? (Moz Space, your house, space)
| Will you be sharing your screen? (yes/no, other info)
| Links to slides or images you want displayed on screen
| Link to where audience can find out more information
|-
|}

= Roundtable =

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

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

{| class="fullwidth-table"
|-
! Who are you?
! Area of question
! Question
|-
| ''What's your name? What do you work on?''
| ''Is your question about policy, a product, a Foundation initiative, etc.''
| ''What would you like to know?''
|-
| ''David Weir and a contributor''
| ''Summit question.''
| ''Were can we see picturs from the summit if you were not their, ?''

|-
|}

= Welcome! =

Let's say hello to some new Mozillians!

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

|-
|}

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

|-
|}

= <meta> =

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

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

=== Firefox ===

=== Platform ===

=== Services ===

=== Messaging ===

=== Mobile ===

=== IT ===

=== Release Engineering ===

=== QA ===

==== Test Execution ====

==== WebQA ====

==== QA Community ====

=== Automation & Tools ===

=== Security ===

=== Engagement ===

==== PR ====

==== Events ====

WeeklyUpdates/2013-10-14

2013-10-08T04:13:49Z

Mrz: /* Friends of the Tree Friends of the Tree */

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

__TOC__

= All-hands Status Meeting Agenda =

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

== Friends of the Tree [[Image:Tree.gif|Friends of the Tree]] ==

* Williamr and his team for making improvements to the mozillians site
* [https://mozillians.org/en-US/u/ewong/ Edmund Wong] and [[https://wiki.mozilla.org/IT/Community Community IT] for migrating [http://badg.us badg.us] to [https://wiki.mozilla.org/IT/Community/WG/Badgus Community IT Infrastructure]
** See also <blog post>

== Upcoming Events ==

=== This Week ===

=== Monday, {{#time:d F|{{SUBPAGENAME}}}} ===

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

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

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

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

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

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

=== Next Week ===

== Product Status Updates (voice updates) ==

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

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

=== Thunderbird ===
''Speaker Location:''

=== Older Branch Work ===
''Speaker Location:''

=== Webmaker ===
''Speaker Location:''

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

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

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

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

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

== Speakers ==

The limit is 3 minutes per speaker. It's like a lightning talk, but don't feel that you have to have slides in order to make a presentation. If you plan on showing a video, you need to contact the Air Mozilla team before the day of the meeting or you will be deferred to the next week.

{| class="fullwidth-table"
|-
! Presenter
! Title
! Topic
! Location
! Share?
! Media
! More Details
|-
| Who Are You?
| What Do You Do?
| What are you going to talk about?
| Where are you presenting from? (Moz Space, your house, space)
| Will you be sharing your screen? (yes/no, other info)
| Links to slides or images you want displayed on screen
| Link to where audience can find out more information
|-
|}

= Roundtable =

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

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

{| class="fullwidth-table"
|-
! Who are you?
! Area of question
! Question
|-
| ''What's your name? What do you work on?''
| ''Is your question about policy, a product, a Foundation initiative, etc.''
| ''What would you like to know?''
|-
| ''David Weir and a contributor''
| ''Summit question.''
| ''Were can we see picturs from the summit if you were not their, ?''

|-
|}

= Welcome! =

Let's say hello to some new Mozillians!

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

|-
|}

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

|-
|}

= <meta> =

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

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

=== Firefox ===

=== Platform ===

=== Services ===

=== Messaging ===

=== Mobile ===

=== IT ===

=== Release Engineering ===

=== QA ===

==== Test Execution ====

==== WebQA ====

==== QA Community ====

=== Automation & Tools ===

=== Security ===

=== Engagement ===

==== PR ====

==== Events ====

WeeklyUpdates/2013-10-14

2013-10-08T04:12:34Z

Mrz: /* Friends of the Tree Friends of the Tree */

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

__TOC__

= All-hands Status Meeting Agenda =

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

== Friends of the Tree [[Image:Tree.gif|Friends of the Tree]] ==

* Williamr and his team for making improvements to the mozillians site
* Edmund Wong and Community IT for migrating [http://badg.us badg.us] to [https://wiki.mozilla.org/IT/Community/WG/Badgus Community IT Infrastructure]

== Upcoming Events ==

=== This Week ===

=== Monday, {{#time:d F|{{SUBPAGENAME}}}} ===

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

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

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

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

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

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

=== Next Week ===

== Product Status Updates (voice updates) ==

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

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

=== Thunderbird ===
''Speaker Location:''

=== Older Branch Work ===
''Speaker Location:''

=== Webmaker ===
''Speaker Location:''

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

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

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

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

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

== Speakers ==

The limit is 3 minutes per speaker. It's like a lightning talk, but don't feel that you have to have slides in order to make a presentation. If you plan on showing a video, you need to contact the Air Mozilla team before the day of the meeting or you will be deferred to the next week.

{| class="fullwidth-table"
|-
! Presenter
! Title
! Topic
! Location
! Share?
! Media
! More Details
|-
| Who Are You?
| What Do You Do?
| What are you going to talk about?
| Where are you presenting from? (Moz Space, your house, space)
| Will you be sharing your screen? (yes/no, other info)
| Links to slides or images you want displayed on screen
| Link to where audience can find out more information
|-
|}

= Roundtable =

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

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

{| class="fullwidth-table"
|-
! Who are you?
! Area of question
! Question
|-
| ''What's your name? What do you work on?''
| ''Is your question about policy, a product, a Foundation initiative, etc.''
| ''What would you like to know?''
|-
| ''David Weir and a contributor''
| ''Summit question.''
| ''Were can we see picturs from the summit if you were not their, ?''

|-
|}

= Welcome! =

Let's say hello to some new Mozillians!

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

|-
|}

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

|-
|}

= <meta> =

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

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

=== Firefox ===

=== Platform ===

=== Services ===

=== Messaging ===

=== Mobile ===

=== IT ===

=== Release Engineering ===

=== QA ===

==== Test Execution ====

==== WebQA ====

==== QA Community ====

=== Automation & Tools ===

=== Security ===

=== Engagement ===

==== PR ====

==== Events ====

IT/Community

2013-10-04T05:11:06Z

Mrz: /* Modules */

= Our Mission =
[https://communityit.etherpad.mozilla.org/Mission Work in progress...]

'''Who we are'''

Mozilla Community IT Ops is a community of talented, volunteer Systems Administrators who devote their time and effort into supporting and managing community-based system infrastructure that support the Mozilla Project, while also learning and upgrading their skill sets in the progress.

'''What we are'''

We are a showcase for how to run the best of the best IT/Operations. We are open & transparent. We are a force multiplier, empowering the Community to promote Mozilla's Mission & Manifesto.

'''How we do it'''

Teaching and education are core to our mission and values. We mentor and teach today's skills and help put those skills to practical use by hosting and running production sites and services. We use [http://openbadges.org/ OpenBadges] to acknowledge skills and accomplishments.

= Getting Involved =
We need your help!

* Join the [https://mail.mozilla.org/listinfo/communityit Mailing List]
* Go to our IRC channel: [irc://irc.mozilla.org/%23communityit #CommunityIT on irc.mozilla.org]
* Join our weekly call

== Modules ==

Community IT Ops operates under a module ownership governance system. A module is a discrete unit of code or activity. An owner is the person in charge of a module or sub-module. A peer is a person whom the owner has appointed to help them. A module may have multiple peers and, very occasionally, multiple owners.

* [[IT/Community/WG/Badgus|Badg.us]]
* [[IT/Community/WG/MCSHosting|Mozilla Communities Hosting (MCS)]]
* [[IT/Community/WG/Discourse|Discourse]]
* [[IT/Community/WG/WordpressMS|Wordpress Multisite]]
* [[IT/Community/WG/MozFest|Moz Fest Event Support]]
* [[IT/Community/WG/Infrastructure|Infrastructure]]

== '''Weekly Call''' ==
* Weekly Big Blue Button meeting, '''every Saturday at [http://www.wolframalpha.com/input/?i=4+PM+UTC+September+14+2013 9am US/Pacific (1600 UTC)]'''
* http://moz.bigbluebutton.org/moz/
** Room: Community IT
** Password: welcome

=== '''Meeting Agenda & Notes''' ===

* August 2013
** [https://wiki.mozilla.org/IT/Community/Notes/2013-08-23 August 23]
** [https://wiki.mozilla.org/IT/Community/Notes/2013-08-30 August 30]
* September 2013
** [https://wiki.mozilla.org/IT/Community/Notes/2013-09-06 September 6]
** [https://communityit.etherpad.mozilla.org/Meeting September 14]