Devrel/Resources: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(Add link to personal safety information)
(Sweeping edits / updates)
 
Line 7: Line 7:
<code>devrel@</code>
<code>devrel@</code>
* [https://groups.google.com/a/mozilla.com/forum/#!forum/devrel Archives] visible to all MoCo/MoFo
* [https://groups.google.com/a/mozilla.com/forum/#!forum/devrel Archives] visible to all MoCo/MoFo
* [https://groups.google.com/a/mozilla.com/forum/#!members/devrel Membership] includes CTO, DevRel, and Events Rep.
* [https://groups.google.com/a/mozilla.com/forum/#!members/devrel Membership] includes DevRel management chain, events reps, etc.


<code>devrel-team@</code>
<code>devrel-team@</code>
* '''[https://groups.google.com/a/mozilla.com/forum/#!forum/devrel-team No archives]'''
* '''[https://groups.google.com/a/mozilla.com/forum/#!forum/devrel-team No archives]'''
* [https://groups.google.com/a/mozilla.com/forum/#!members/devrel-team Membership] limited to DevRel manager + direct reports.
* [https://groups.google.com/a/mozilla.com/forum/#!members/devrel-team Membership] is only DevRel manager + direct reports.


Strive to use the <code>devrel@</code> list as much as possible. It is not publicly accessible, so it is ok to talk about NDA'ed information there.  
Strive to use the <code>devrel@</code> list as much as possible. It is not publicly accessible, so it is ok to talk about NDA'ed information there.  
Line 17: Line 17:
For immediate concerns or private matters (PTO, etc.) use the <code>devrel-team@</code> list.
For immediate concerns or private matters (PTO, etc.) use the <code>devrel-team@</code> list.


=== IRC Channels ===
=== IRC / Slack Channels ===


We spend a lot of time on [[IRC]]. You might be interested in the following channels:
On Slack, you might be interested in the following channels:


* <code>#devrel</code>: Team channel (with [https://botbot.me/mozilla/devrel/ public logs]).
* <code>#devrel-team</code>: Our immediate team, ask an existing colleague for an invite.
* <code>#developer-outreach</code>: The broader Developer Outreach group at Mozilla
* <code>#et</code>: All of Emerging Technology
* <code>#moco</code>: Mozilla employees
 
Historically, we used [[IRC]], and many engineering teams still use IRC, however most of these channels have moved to Slack:
 
* <code>#devrel</code>: Our previous team channel (with [https://botbot.me/mozilla/devrel/ public logs]).
* <code>#awayteam</code>: Social channel for remote employees
* <code>#awayteam</code>: Social channel for remote employees
* <code>#moco</code>: Private MoCo employee channel ([https://mana.mozilla.org/wiki/display/AVSE/MoCo+Vidyo+Room+Security password])
* <code>#moco</code>: Private MoCo employee channel ([https://mana.mozilla.org/wiki/display/AVSE/MoCo+Vidyo+Room+Security password])
Line 27: Line 34:
* <code>#servicedesk</code>: Technical support
* <code>#servicedesk</code>: Technical support


Ideally you'll find a way to stay connected permanently, either by setting up a "bouncer" like [http://wiki.znc.in/ ZNC] or by using a service like [https://www.irccloud.com/ IRCCloud].
For IRC, Mozilla has a corporate [https://irccloud.mozilla.com private IRCCloud instance]. You can request an account by filing a Service Now ticket (Service Desk &rarr; Accounts &rarr; Other).
 
Mozilla has a [https://irccloud.mozilla.com private IRCCloud installation]. You can request an account by filing a Service Now ticket (Service Desk &rarr; Accounts &rarr; Other).


=== Vidyo ===
=== Vidyo ===
Line 41: Line 46:
You should be added to this private calendar:
You should be added to this private calendar:


* '''DevRel Travel and PTO''', a *private* calendar which tracks where the DevRel team is, including both work travel and PTO. Dan Callahad or Havi Hoffman can add you.
* '''DevRel Travel and PTO''', a *private* calendar which tracks where the DevRel team is, including both work travel and PTO. Dan Callahan or Havi Hoffman can add you.


You should add and contribute to these public calendars:
You should add and contribute to these public calendars:
Line 62: Line 67:
* '''[https://bit.ly/moz-tech-speaker-cal Tech Speakers appearances]''', where our Tech Speakers program posts their speaking appearances.
* '''[https://bit.ly/moz-tech-speaker-cal Tech Speakers appearances]''', where our Tech Speakers program posts their speaking appearances.
* '''[https://www.mozilla.org/en-US/contribute/events/ Community and Mozilla Reps events]''', where our broader Mozilla community post their public events.
* '''[https://www.mozilla.org/en-US/contribute/events/ Community and Mozilla Reps events]''', where our broader Mozilla community post their public events.
=== Yammer ===
Our [https://www.yammer.com/mozilla.com/ corporate Yammer] doesn't have a great reputation, but it can still be worthwhile to sign up for daily email digests to get a broader sense of what's going on within the company.


=== Directories ===
=== Directories ===
Line 82: Line 83:
We own the [https://hacks.mozilla.org/ Hacks Blog]. ([https://hacks.mozilla.org/wp-admin/ Admin link])
We own the [https://hacks.mozilla.org/ Hacks Blog]. ([https://hacks.mozilla.org/wp-admin/ Admin link])


Hacks uses your LDAP credentials for authentication. To get access to the Hacks blog, pester someone on the devrel-team mailing list.
Hacks uses your LDAP credentials for authentication. To get access to the Hacks blog, ask someone on the devrel-team mailing list.


=== Twitter ===
=== Twitter ===
Line 90: Line 91:
* [https://twitter.com/mozhacks @MozHacks], which targets general web developers
* [https://twitter.com/mozhacks @MozHacks], which targets general web developers
* [https://twitter.com/mozappsdev @MozAppsDev], which focuses on webapps.
* [https://twitter.com/mozappsdev @MozAppsDev], which focuses on webapps.
Credentials are on the [https://intranet.mozilla.org/Engagement/Developer_Engagement#Outreach_Channels Intranet]


=== YouTube ===
=== YouTube ===


We post on the [https://www.youtube.com/user/mozhacks Mozilla Hacks channel].
We post on the [https://www.youtube.com/user/mozhacks Mozilla Hacks channel].
Credentials are on the [https://intranet.mozilla.org/Engagement/Developer_Engagement#Outreach_Channels Intranet]


==== Adding subtitles ====
==== Adding subtitles ====
Line 109: Line 106:
Here's another way to do transcripts (that doesn't require using YouTube):
Here's another way to do transcripts (that doesn't require using YouTube):


1) Go to rev.com. Sign up/in. Fill out their forms and request a transcript for your video. It'll cost $1/min.  
# Go to rev.com. Sign up/in. Fill out their forms and request a transcript for your video. It'll cost $1/min.  
2) Be sure to order CAPTIONS. That will give you the needed timecode, so the video knows when to display which part of the transcript. https://www.rev.com/caption
# Be sure to order CAPTIONS. That will give you the needed timecode, so the video knows when to display which part of the transcript. https://www.rev.com/caption
3) When offered the chance (usually after ordering), do provide names of people and industry vocabulary (like the words CSS, JavaScript, etc). That will help the transcriber get more things right.
# When offered the chance (usually after ordering), do provide names of people and industry vocabulary (like the words CSS, JavaScript, etc). That will help the transcriber get more things right.
4) After you get the transcript, proof-read it and fix the mistakes. Sometimes there are a lot. If so, give that person a low rating. Usually it's pretty darn good. Still a lot of work for you to clean up, but way less work than transcribing it yourself.
# After you get the transcript, proof-read it and fix the mistakes. Sometimes there are a lot. If so, give that person a low rating. Usually it's pretty darn good. Still a lot of work for you to clean up, but way less work than transcribing it yourself.
5) If you are using YouTube, go there to add the captions, using their directions as a guide. https://support.google.com/youtube/answer/2734796?hl=en or https://www.youtube.com/watch?v=qYcj85tBje4. If you are using Vimeo, search their documentation for directions. If you are using AirMozilla, ping that team to find out if/how to do transcripts.   
# If you are using YouTube, go there to add the captions, using their directions as a guide. https://support.google.com/youtube/answer/2734796?hl=en or https://www.youtube.com/watch?v=qYcj85tBje4. If you are using Vimeo, search their documentation for directions. If you are using AirMozilla, ping that team to find out if/how to do transcripts.   
6) I recommend also publishing the transcript in the notes section of the video page, that way if someone goes to the webpage to watch, they can read along in a big block of text if they don't want to use the CC function. Just gives people options. It's easier for scanning and referring back to something. And it helps with SEO.
# I recommend also publishing the transcript in the notes section of the video page, that way if someone goes to the webpage to watch, they can read along in a big block of text if they don't want to use the CC function. Just gives people options. It's easier for scanning and referring back to something. And it helps with SEO.


=== Lanyrd ===
=== Notist ===


We're trying to standardize on listing our upcoming events in [http://lanyrd.com/ Lanyrd]. This is still a work in progress, but please sign up.
Some of us use and recommend [https://noti.st/ Notist] as a portfolio of of our presentations.


== Other Resources ==
== Other Resources ==


=== Wikis ===
=== Team Meeting Notes ===


Meeting minutes and other team information can be found on the [https://wiki.mozilla.org/Devrel wiki].
Our weekly meetings are recorded in [https://docs.google.com/document/d/1Dk0r4ijOxbJbVPEZ9dgURsJMwO03cLfRaLSeLCariZk Google Docs] (link visible to anyone at Mozilla).


Mozilla also has:
Older meeting minutes and other team information can be found on [https://wiki.mozilla.org/Devrel the wiki].
 
* [https://intranet.mozilla.org Intranet], an old employee Wiki
* [https://mana.mozilla.org Mana], the new employee Wiki that has mostly replaced the Intranet, especially for HR information
 
=== Etherpads ===
 
Most teams take meeting notes in [https://public.etherpad-mozilla.org/ Etherpad]. It's like a lightweight Google Doc.
 
The DevRel weekly meetings use the [https://public.etherpad-mozilla.org/p/devrel-weekly devrel-weekly] pad, with notes archived on the wiki after each meeting.
 
We put recordings of our talks on [https://public.etherpad-mozilla.org/p/devrel-talks-2016 the talks and videos pad].
 
You can create a pad with an arbitrary name by going to <code>https://public.etherpad-mozilla.org/p/pad-name-here</code>.
 
Etherpads (and their edit histories) are public.
 
=== Google Drive ===
 
Some teams use Google Docs pretty heavily. DevRel doesn't, but you should know that your Mozilla account has access to the standard Google tools.
 
Google Drive is a good place to put things that can't be public (NDA'd partner announcements, etc).
 
=== GitHub ===
 
Mozilla takes a somewhat scattershot approach to source control and issue tracking. The two main GitHub organizations that are likely to concern you as an employee are:
 
* [https://github.com/mozilla Mozilla], for general Mozilla projects.
* [https://github.com/mozdevs Mozdevs], more of a DevRel sandbox.
 
You should be a member of both of these organizations. Pester someone on devrel-team if not.
 
Some projects also live in [https://github.com/mozilla-b2g Mozilla-B2G] (Firefox OS) and [https://github.com/mozilla-services Mozilla-Services] (Sync, network service infrastructure).


=== Bugzilla ===
=== Bugzilla ===
Line 175: Line 140:
== Other Notes ==
== Other Notes ==


=== Okta and Single Sign-on (SSO) ===
=== Single Sign-on (SSO) ===


Many of our corporate websites, like ServiceNow and Egencia, use Okta for single sign-on.
Many internal websites, like ServiceNow and Egencia, use single-sign-on.


You can see a dashboard with links to services at https://mozilla.okta.com/.
You can see a dashboard with links to services at https://sso.mozilla.com/.


=== PTO (Paid Time Off) and Holidays ===
=== PTO (Paid Time Off) and Holidays ===
Line 185: Line 150:
For PTO, fill out [https://pto.mozilla.org/ the form] and make sure you CC <code>devrel-team</code>.
For PTO, fill out [https://pto.mozilla.org/ the form] and make sure you CC <code>devrel-team</code>.


When on PTO, traveling, or just out of the office, add the dates you'll be gone to the Evangelism Speaking calendar.
When on PTO, traveling, or just out of the office, add the dates you'll be gone to the "DevRel Travel + PTO" calendar.


To see what holidays we get, check out [https://mana.mozilla.org/wiki/pages/viewpage.action?pageId=33099367 Mana]. There are instructions for adding them to your Google Calendar on that page.
To see what holidays we get, check out [https://mana.mozilla.org/wiki/pages/viewpage.action?pageId=33099367 Mana]. There are instructions for adding them to your Google Calendar on that page.
Line 203: Line 168:
=== The Manifesto ===
=== The Manifesto ===


Mozilla Corporation (MoCo) is a normal company, but we're also a wholly owned subsidiary of the non-profit Mozilla Foundation (MoFo), which exists to safeguard and promote the Web as a public resource.
Mozilla Corporation (MoCo) is a normal corporation, but we're also a wholly owned subsidiary of the non-profit Mozilla Foundation (MoFo), which exists to safeguard and promote the Web as a public resource.


We have a [https://www.mozilla.org/en-US/about/manifesto/details/ manifesto] that explains our principles. It's DevRel's job to ensure that we're upholding that manifesto when working with the developers who build the Web.
We have a [https://www.mozilla.org/en-US/about/manifesto/details/ manifesto] that explains our principles. It's DevRel's job to ensure that we're upholding that manifesto when working with the developers who build the Web.
Line 215: Line 180:
If someone wants you to speak at their event, or wants Mozilla to sponsor their event, ask them to fill out the [https://bugzilla.mozilla.org/form.dev-engagement-event speaker request form] and mention you by name.
If someone wants you to speak at their event, or wants Mozilla to sponsor their event, ask them to fill out the [https://bugzilla.mozilla.org/form.dev-engagement-event speaker request form] and mention you by name.


Staff involvement at conferences + events: If staff wants to attend an event, approval should be from their team and manager and from their budget. If they want to speak at an event, submits proposal and is accepted, and rejected by their internal department to travel to the event, we can review the request under Dev Rel. They can file a bug (which helps us keep track of these requests instead of through email) [https://bugzilla.mozilla.org/form.dev-engagement-event speaker request form]
Staff involvement at conferences + events: If staff wants to attend an event, approval should be from their team and manager and from their budget.


Reps and community members should first go through the Reps Council for review.
Reps and community members should first go through the Reps Council for review.


Events where we have speakers confirmed, supporting with sponsorship, will be posted on our Evangelism calendar which flows into the Mozilla.org Events website, and verbally announced at our Monday Morning Project Calls.
=== Branding materials ===
 
==== Branding materials for sponsoring ====
 
We generally sponsor using the Firefox Developer Edition brand. This is a somewhat stock reply you can use when responding to organisers who want to get branding (logos, text) from us to display in their website and other promotional materials. Adjust as required:
 
<blockquote>
1. Please use the Developer Edition Wordmark + Logo from
https://www.mozilla.org/en-US/styleguide/identity/firefox/wordmarks/#firefox-developer
 
2. Please link to https://firefox.com/developer
 
3. For text, please use the following:
 
Built for those who build the Web.


Firefox Developer Edition brings your core dev tools together with some powerful new ones that will extend your ability to work across multiple platforms from one place. It’s everything you’re used to, only better. And only from Firefox.
Mozilla logos / icons / marks can be found at [https://mozilla.design/ mozilla.design]. Firefox itself follows the "[https://design.firefox.com/photon/welcome.html Photon Design System]." You can find Firefox logos under "[https://design.firefox.com/photon/visuals/product-identity-assets.html Product Identity Assets]."
</blockquote>
 
Alternatively, you can choose to use Mozilla's branding:
 
<blockquote>
 
1. Please use the Mozilla wordmark from https://www.mozilla.org/en-US/styleguide/identity/mozilla/branding/
 
2. Please link to https://www.mozilla.org/
 
3. For text, please use the following:
 
At Mozilla, we’re a global community of technologists, thinkers and builders working together to keep the Internet alive and accessible, so people worldwide can be informed contributors and creators of the Web. We believe this act of human collaboration across an open platform is
essential to individual growth and our collective future.
 
Read the <nowiki><a href="https://www.mozilla.org/about/manifesto/">Mozilla Manifesto</a></nowiki> to learn even more about the values and principles that guide the pursuit of our mission.
</blockquote>


=== Travel, Expenses & Event Reports ===
=== Travel, Expenses & Event Reports ===
Line 260: Line 194:
Request an Egencia account on Service Now under Workplace Resources &rarr; Travel
Request an Egencia account on Service Now under Workplace Resources &rarr; Travel


When traveling, add the dates you'll be gone to the Evangelism Speaking calendar.
When traveling, add the dates you'll be gone to the "DevRel Travel+PTO" calendar.


We use Expensify for managing reimbursement for work-related expenses. Details and policies on [https://mana.mozilla.org/wiki/display/FIN/Expensify+-+Employee+Expense+Reporting+System Mana].
We use Expensify for managing reimbursement for work-related expenses. Details and policies on [https://mana.mozilla.org/wiki/display/FIN/Expensify+-+Employee+Expense+Reporting+System Mana].
Line 266: Line 200:
(Tip: Most expenses should be marked as "reimbursable," and not as "billable" in Expensify.)
(Tip: Most expenses should be marked as "reimbursable," and not as "billable" in Expensify.)


'''EVENT FEEDBACK/Trip Reports:''' Speakers & all attendees (whether you're audience, speaker, staff): Please share your feedback about developer events here: http://bit.ly/devrel-event-report
==== Event Feedback / Trip Reports ====
 
Speakers & all attendees (whether you're audience, speaker, staff): Please share your feedback about developer events in the [https://docs.google.com/forms/d/e/1FAIpQLSfsD3aIwzPfiO7mhZMEWbN4irEdGO7fVjOTqY91VXtEa-j9-Q/viewform event feedback form].


==== Booking travel tips ====
==== Booking travel tips ====
Line 277: Line 213:


==== Travel Policy Guidelines  ====
==== Travel Policy Guidelines  ====
* The most current version of Mozilla travel policy for staff lives on [https://mana.mozilla.org/wiki/display/WPR/Travel+Policy mana], which is behind LDAP.  
* The most current version of Mozilla travel policy for staff lives on [https://mana.mozilla.org/wiki/display/WPR/Travel+Policy mana], which is behind LDAP.  
* Here are relevant excerpts for staff and volunteer contributors when booking travel for Mozilla:  
* Here are relevant excerpts for staff and volunteer contributors when booking travel for Mozilla:  
Line 302: Line 239:
=== Swag ===
=== Swag ===


We tend to focus on stickers since they're affordable, compact, and travel well.
We tend to focus on stickers since they're affordable, compact, and travel well. We usually print our own via [http://stickermule.com/ StickerMule].
 
You can order rolls of 500 3" Firefox stickers via [https://bugzilla.mozilla.org/form.gear Bugzilla], but we tend to prefer to print our own, higher quality stuff via [http://stickermule.com/ StickerMule].


If you need stickers, pester someone on <code>devrel-team</code> and we'll get some ordered or shipped.
If you need stickers, pester someone on <code>devrel-team</code> and we'll get some ordered or shipped.
Line 331: Line 266:


If you need other software, it's likely available in the ServiceNow catalog.
If you need other software, it's likely available in the ServiceNow catalog.
=== Video bumpers ===
You can add these before / after your screencasts:
https://www.dropbox.com/s/mckpgu1p2951crv/DevRelBumpers%3Atools.zip?dl=0
These come from [this bug https://bugzilla.mozilla.org/show_bug.cgi?id=1145759] and were rendered by Rainier.
=== Document Cameras ===
If you're doing a lot of work on mobile, the [http://www.ipevo.com/prods/IPEVO-Ziggi-HD-USB-Document-Camera IPEVO Ziggi-HD] USB Document Camera is a great choice. Buy one and expense it, or request one through ServiceNow under Service Desk &rarr; Order something &rarr; Accessories &rarr; Other &rarr; Non-Catalog Accessories


=== Audio Recording Equipment (i.e. microphones and so) ===
=== Audio Recording Equipment (i.e. microphones and so) ===
Line 351: Line 275:
* Jen uses a Heil PR40 when she's at home, and a Zoom H5 portable recorder and two Shure SM58s when on the road.
* Jen uses a Heil PR40 when she's at home, and a Zoom H5 portable recorder and two Shure SM58s when on the road.
* Potch uses a [http://www.amazon.com/M-Audio-Vocal-Studio-Recording-Microphone/dp/B004MZG1IO/ref=sr_1_4?ie=UTF8&qid=1442942758&sr=8-4&keywords=m+audio+microphone this bundle] for mobile recording
* Potch uses a [http://www.amazon.com/M-Audio-Vocal-Studio-Recording-Microphone/dp/B004MZG1IO/ref=sr_1_4?ie=UTF8&qid=1442942758&sr=8-4&keywords=m+audio+microphone this bundle] for mobile recording
=== people.mozilla.org ===
If you'd like some web space on people.mozilla.org, file a ticket on ServiceNow under Service Desk &rarr; Accounts &rarr; SSH to add a public SSH key to your LDAP account.
To generate an SSH keypair, see the [http://git-scm.com/book/en/v2/Git-on-the-Server-Generating-Your-SSH-Public-Key Git documentation].
Once added, you should be able to SSH or SFTP into <code>people.mozilla.org</code> and upload content into your <code>public_html</code> folder.
It will appear online at <code>https://people.mozilla.org/~ldapname/</code>.


== Traveling abroad ==
== Traveling abroad ==
Line 366: Line 280:
=== VISA ===
=== VISA ===


Depending on your nationality and residence country, some destination don't allow free pass through their borders. It is important to visit '''official tourist web sites''' for the countries you will visit to find out how to get your visit permit. The permit usually cost you a fee, expend this fee in your travel report.
Depending on your nationality and country of residence, you may need a visa to travel to international destinations. It is important to check with each country you will travel through to determine what documents you need, well in advance of your travel. Expense any visa fees with your other trip expenses.


=== Health considerations ===
=== Health considerations ===


Pay special attention to health considerations when traveling to developing countries. You will probably need vaccines and bring some medicines with you. Don't leave this to the end since some vaccines need time to be effective and other must be taken before entering the risk zone. The best thing you can do is to talk with your family doctor or look for government resources.
When traveling to developing countries, you will likely need additional immunization or travel medication. Look into this as soon as possible; many vaccines need weeks or months to become effective.
 
Your doctor can advise you on what you'll need. You can also check the [https://wwwnc.cdc.gov/travel/destinations/list CDC's Travelers' Health portal].


=== Medical insurance ===
=== Medical insurance ===


Mozilla employees are covered by a medical insurance while traveling. Print a copy of the [https://mana.mozilla.org/wiki/download/attachments/33099972/Mozilla%20Corp%20AXA%20Travel%20Assistance%20Program.2016.pdf?version=1&modificationDate=1464294135638&api=v2 Travel Assistance ID Card and Flyer], keep it among your traveling documents always on hand and label it "MEDICAL INSURANCE" in English and in the local language.
Mozilla has a medical insurance policy for employees and their dependents who are traveling on business. See the [https://mana.mozilla.org/wiki/display/PR/Travel+insurance%3A+Business travel insurance page] on Mana for details.
 
Make sure you print out the policy ID card and keep it with you while you travel.


=== Mobile data connection ===
=== Mobile data connection ===
Line 389: Line 307:
** Both Mailing Lists
** Both Mailing Lists
** Both Calendars (+ the company holiday one, if desired)
** Both Calendars (+ the company holiday one, if desired)
** Yammer email digests
* Accounts
* Accounts
** Lanyrd
** Hacks Blog
** Hacks Blog
** GitHub (and added to Mozilla and Mozdevs organizations)
** GitHub (and added to Mozilla organization)
** Bugzilla
** Bugzilla
** Egencia
** Egencia
** people.mozilla.org (if desired)
* Hardware / Gear
* Hardware / Gear
** Comfortable headset for Vidyo
** Comfortable headset for Vidyo
Line 407: Line 322:
** CrashPlan (if desired)
** CrashPlan (if desired)
** Expensify App
** Expensify App
** IRC client w/ persistent connection (e.g., IRCCloud)
** IRC client w/ persistent connection (e.g., IRCCloud, if desired)
* Information
* Information
** Read the Manifesto
** Read the Manifesto
** Watch "Bugzilla for Humans II"
** Watch "Bugzilla for Humans II"
** Read Home Space Worker Guidelines (if applicable)
** Read Home Space Worker Guidelines (if applicable)

Latest revision as of 21:51, 14 June 2018

Internal Communication

Mailing Lists

We have two mailing lists, both @mozilla.com:

devrel@

  • Archives visible to all MoCo/MoFo
  • Membership includes DevRel management chain, events reps, etc.

devrel-team@

Strive to use the devrel@ list as much as possible. It is not publicly accessible, so it is ok to talk about NDA'ed information there.

For immediate concerns or private matters (PTO, etc.) use the devrel-team@ list.

IRC / Slack Channels

On Slack, you might be interested in the following channels:

  • #devrel-team: Our immediate team, ask an existing colleague for an invite.
  • #developer-outreach: The broader Developer Outreach group at Mozilla
  • #et: All of Emerging Technology
  • #moco: Mozilla employees

Historically, we used IRC, and many engineering teams still use IRC, however most of these channels have moved to Slack:

  • #devrel: Our previous team channel (with public logs).
  • #awayteam: Social channel for remote employees
  • #moco: Private MoCo employee channel (password)
  • #airmozilla: Chat regarding current broadcasts on Air Mozilla
  • #servicedesk: Technical support

For IRC, Mozilla has a corporate private IRCCloud instance. You can request an account by filing a Service Now ticket (Service Desk → Accounts → Other).

Vidyo

We use Vidyo for teleconferencing. You can install it from v.mozilla.com.

Headsets are strongly recommended with Vidyo.

Team Calendars

You should be added to this private calendar:

  • DevRel Travel and PTO, a *private* calendar which tracks where the DevRel team is, including both work travel and PTO. Dan Callahan or Havi Hoffman can add you.

You should add and contribute to these public calendars:

  • CFP Calendar, which tracks upcoming conference submission deadlines, managed by Havi Hoffman. Editable by all of DevRel, so you can add CFPs you're tracking.
  • Mozilla Staff Speaking Appearances. You should add your public speaking appearances here, including the talk topic and conference information. You can see where other Mozilla staff are speaking (many people outside DevRel speak publicly!).
    • Please adhere to the following conventions when using this calendar:
      1. Only enter your own appearances.
      2. Use all-day calendar entries.
      3. Speaking multiple times at an event? Create multiple calendar entries.
      4. Name the entry like Name What @ Where (Topic), for example:
        • Alice Speaking @ FutureConf (ECMAScript 2023)
        • Bob Workshop @ WatFest (Hands-on CSS Centering)
        • Chris Keynote @ ConfConf (Representation Matters)
      5. Set the location to the event's city and country
      6. Be consistent with your name, title format, and verbs!

You might want to watch these public calendars:

Directories

Mozilla has two primary directories

People tend to put their cell phone number in the Phonebook so that folks can get in touch with them in an emergency or while they're on the road.

Outbound Messaging

Blog

We own the Hacks Blog. (Admin link)

Hacks uses your LDAP credentials for authentication. To get access to the Hacks blog, ask someone on the devrel-team mailing list.

Twitter

We own two Twitter accounts:

YouTube

We post on the Mozilla Hacks channel.

Adding subtitles

If you have written (and followed quite faithfully!) a script of your video, YouTube can do a pretty good job of calculating the timings and thus generate subtitles automatically without having to manually transcribe it or sending it to a transcription service.

Once you have uploaded the video, go to the video details page in the manager, and click on the "Subtitles and CC" tab, and then on the "Add new Subtitles or CC" blue button/dropdown on the right. It might ask you to select the video language beforehand. Select the language of your video (e.g. English (United Kingdom)) and then in "Select method" choose "Transcribe and auto-sync". Copy and paste the script into the text area and click "Set timings". This will take a bit - like one or two minutes. Refresh and see if the timing is right with the video preview in that page. You can adjust things there.

Each subtitle track will be a "draft". You need to click "publish" before it's available to everyone.

Here's another way to do transcripts (that doesn't require using YouTube):

  1. Go to rev.com. Sign up/in. Fill out their forms and request a transcript for your video. It'll cost $1/min.
  2. Be sure to order CAPTIONS. That will give you the needed timecode, so the video knows when to display which part of the transcript. https://www.rev.com/caption
  3. When offered the chance (usually after ordering), do provide names of people and industry vocabulary (like the words CSS, JavaScript, etc). That will help the transcriber get more things right.
  4. After you get the transcript, proof-read it and fix the mistakes. Sometimes there are a lot. If so, give that person a low rating. Usually it's pretty darn good. Still a lot of work for you to clean up, but way less work than transcribing it yourself.
  5. If you are using YouTube, go there to add the captions, using their directions as a guide. https://support.google.com/youtube/answer/2734796?hl=en or https://www.youtube.com/watch?v=qYcj85tBje4. If you are using Vimeo, search their documentation for directions. If you are using AirMozilla, ping that team to find out if/how to do transcripts.
  6. I recommend also publishing the transcript in the notes section of the video page, that way if someone goes to the webpage to watch, they can read along in a big block of text if they don't want to use the CC function. Just gives people options. It's easier for scanning and referring back to something. And it helps with SEO.

Notist

Some of us use and recommend Notist as a portfolio of of our presentations.

Other Resources

Team Meeting Notes

Our weekly meetings are recorded in Google Docs (link visible to anyone at Mozilla).

Older meeting minutes and other team information can be found on the wiki.

Bugzilla

Many Mozilla projects, including Firefox itself, track issues in Bugzilla.

You can use bugzil.la to shorten links, like this: https://bugzil.la/1000000

We tend to care about two Bugzilla keywords:

  • DevAdvocacy, for bugs we file based on external feedback.
  • devrel-needed, for things we should evangelize once implemented

Watch Bugzilla for Humans II to get a better understanding of how to work with Bugzilla.

Other Notes

Single Sign-on (SSO)

Many internal websites, like ServiceNow and Egencia, use single-sign-on.

You can see a dashboard with links to services at https://sso.mozilla.com/.

PTO (Paid Time Off) and Holidays

For PTO, fill out the form and make sure you CC devrel-team.

When on PTO, traveling, or just out of the office, add the dates you'll be gone to the "DevRel Travel + PTO" calendar.

To see what holidays we get, check out Mana. There are instructions for adding them to your Google Calendar on that page.

Mozilla Standard Time

Assume that everything is Pacific time unless otherwise specified.

Public By Default

Strive to do your work and hold your discussions in public. Mozilla an open, non-profit project with a vibrant community. Privacy makes it more difficult for volunteers to stay aware of or contribute to Mozilla's efforts.

Put a license on it!

Generally we use the Mozilla Public License 2 or Apache 2 for individual repositories created from scratch. When contributing to existing repositories (which is encouraged--we strive to be good open source citizens!), respect existing licenses. Here are the full details of Mozilla's License policy, where you can also find a handy flow chart to help you decide which license you should use.

The Manifesto

Mozilla Corporation (MoCo) is a normal corporation, but we're also a wholly owned subsidiary of the non-profit Mozilla Foundation (MoFo), which exists to safeguard and promote the Web as a public resource.

We have a manifesto that explains our principles. It's DevRel's job to ensure that we're upholding that manifesto when working with the developers who build the Web.

Don't Ask for Permission

Mozilla is an open, chaotic, participatory ball of fun. Push buttons, send emails, and edit wikis like you own the place.

Sponsorship and Speakers

If someone wants you to speak at their event, or wants Mozilla to sponsor their event, ask them to fill out the speaker request form and mention you by name.

Staff involvement at conferences + events: If staff wants to attend an event, approval should be from their team and manager and from their budget.

Reps and community members should first go through the Reps Council for review.

Branding materials

Mozilla logos / icons / marks can be found at mozilla.design. Firefox itself follows the "Photon Design System." You can find Firefox logos under "Product Identity Assets."

Travel, Expenses & Event Reports

We use Egencia for booking most travel and lodging, though AirBNB is also available. Details and policies on Mana.

Request an Egencia account on Service Now under Workplace Resources → Travel

When traveling, add the dates you'll be gone to the "DevRel Travel+PTO" calendar.

We use Expensify for managing reimbursement for work-related expenses. Details and policies on Mana.

(Tip: Most expenses should be marked as "reimbursable," and not as "billable" in Expensify.)

Event Feedback / Trip Reports

Speakers & all attendees (whether you're audience, speaker, staff): Please share your feedback about developer events in the event feedback form.

Booking travel tips

  • Short trips (less than a week) incur on the "unofficial business travel tax" so they might be even more expensive than a trip to the same place for 8 days. Sometimes it's cheaper to stay a day after or before and pay an extra hotel night, than coming back sooner. It's a good idea to juggle a bit and check various dates to find what's the best rate, if you can afford some flexibility.
  • When you have to connect, always aim for at least 1:30h of layover, specially in big airports. 2h should be good, 3-4 hours is a long break and could be a good option if your trip is really long so you can stretch legs, have a decent drink, etc. Anything more than that is going to drive you nuts; it's advised you try other options, as advised above.
  • Also: avoid busy and big airports or airports where meteorological conditions make it often hard to land or take off. Case in point: Chicago (ORD).
  • It's also better to book all travel with the same company or alliance, as if something goes wrong, it's easier to get rescheduled in their systems. Otherwise you'll be dealing with various companies that are not interested in your wellness (i.e. they don't care about you).
  • If anything goes wrong (cancelled flights, missed connections...), call Egencia (+1 (866) 397-2677 or +1 (702) 939-2530). It might take time, as they have to deal with airlines' systems and rules, but they will sort it out for you. That's what we pay them for.

Travel Policy Guidelines

  • The most current version of Mozilla travel policy for staff lives on mana, which is behind LDAP.
  • Here are relevant excerpts for staff and volunteer contributors when booking travel for Mozilla:
    • Low Fare: We try to balance cost savings with convenience and allow flights that are within $200 of the lowest otherwise logical fare as still being within policy. Any flights greater than $200 of the lowest logical fare will generate an "out of policy" notification and will require special approval.
    • Reasonable flights: We ask that you consider other departure times during your day of travel as well as longer trips.
    • Advance Purchase: Please book your travel at least 14 days in advance, otherwise you will get an "out of policy" notification that requires special approval. Flights more than 365 days in the future are also "out of policy".
    • Layovers: We do consider flights with 2 or more connections as unreasonable and don’t expect you to consider those as a "reasonable flight option".

Personal Safety and Harassment

Your safety is important to Mozilla. There are guidelines and resources available to you if you ever feel unsafe or harassed while representing Mozilla.

Winning the upgrade lottery

Although we travel Economy / Coach, there are ways you can experience a bit of luxury. First thing is to sign up for the fidelity program of the airline you're going to fly with. Enter your membership details in Egencia, so they get added to the flights you book.

If the flight is overbooked and they need to seat groups or families together, but they can't because you're taking one of the seats, and there is space on better cabins, they might relocate you, i.e. upgrade you.

You increase your upgrade chances by having more 'status' than other solo travellers in the flight. The more points, the higher in the list of upgrades you are.

The only exception is if you have special dietary requirements, as then they can't upgrade you because they prepare those meals per person in advance, and they can't serve you "lesser quality" food in a better cabin. So, specifying a special diet disqualifies you from an upgrade.

How do you find if you've been upgraded? When your ticket is scanned before boarding, they might get a 'new seat' alert, or if you use the airline app you might notice that your checked-in seat has been changed.

Swag

We tend to focus on stickers since they're affordable, compact, and travel well. We usually print our own via StickerMule.

If you need stickers, pester someone on devrel-team and we'll get some ordered or shipped.

Business Cards

To order business cards, request an account on in ServceNow under Workplace Resources → Business Cards

Remote Work

If you work remotely, familiarize yourself with the Home Space Worker Guidelines on Mana.

CrashPlan Backups

We have an enterprise subscription to CrashPlan for backups.

If you'd like to use it, check the instructions on Mana.

Presentation Software

Use what you're most comfortable with, but consider using an HTML5 based slide framework like reveal.js if possible.

Screenflow and Other Software

We tend to like Screenflow for recording screencasts. Buy a license and expense it, or request a license through ServiceNow under Service Desk → Order something → Software Applications → Other Applications → Non-Catalog Software.

If you need other software, it's likely available in the ServiceNow catalog.

Audio Recording Equipment (i.e. microphones and so)

TL;DR: the Blue Yeti with a pop up filter is a good combination.

Traveling abroad

VISA

Depending on your nationality and country of residence, you may need a visa to travel to international destinations. It is important to check with each country you will travel through to determine what documents you need, well in advance of your travel. Expense any visa fees with your other trip expenses.

Health considerations

When traveling to developing countries, you will likely need additional immunization or travel medication. Look into this as soon as possible; many vaccines need weeks or months to become effective.

Your doctor can advise you on what you'll need. You can also check the CDC's Travelers' Health portal.

Medical insurance

Mozilla has a medical insurance policy for employees and their dependents who are traveling on business. See the travel insurance page on Mana for details.

Make sure you print out the policy ID card and keep it with you while you travel.

Mobile data connection

The recommendation is to buy a local pre-paid SIM card. Use Prepaid Data SIM Card website to check the alternatives per country.

New Hire Checklist

  • Profiles
    • Mozillians
    • Phonebook (with cell phone, if willing)
    • Devrel Wiki Page
  • Subscriptions
    • Both Mailing Lists
    • Both Calendars (+ the company holiday one, if desired)
  • Accounts
    • Hacks Blog
    • GitHub (and added to Mozilla organization)
    • Bugzilla
    • Egencia
  • Hardware / Gear
    • Comfortable headset for Vidyo
    • Document camera (if needed)
    • Mozilla / Firefox Stickers
    • Business Cards
  • Software
    • Vidyo
    • Screenflow (or other)
    • CrashPlan (if desired)
    • Expensify App
    • IRC client w/ persistent connection (e.g., IRCCloud, if desired)
  • Information
    • Read the Manifesto
    • Watch "Bugzilla for Humans II"
    • Read Home Space Worker Guidelines (if applicable)
Retrieved from "https://wiki.allizom.org/index.php?title=Devrel/Resources&oldid=1195604"