View source for Devrel/Resources

== Internal Communication ==

=== Mailing Lists ===

We have two mailing lists, both <code>@mozilla.com</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/#!members/devrel Membership] includes CTO, DevRel, and Events Rep.

<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/#!members/devrel-team Membership] limited to 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. 

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

=== IRC Channels ===

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

* <code>#devrel</code>: Team channel (with [https://botbot.me/mozilla/devrel/ public logs]).
* <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>#airmozilla</code>: Chat regarding current broadcasts on [https://air.mozilla.org Air Mozilla]
* <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].

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

We use Vidyo for teleconferencing. You can install it from [https://v.mozilla.com v.mozilla.com].

Headsets are ''strongly'' recommended with Vidyo.

=== Team Calendars ===

You should be added to two calendars:

* '''Evangelism Speaking''', which tracks where the DevRel team is, including both conferences and PTO.
* '''CFPCalendar''', which tracks upcoming conference submission deadlines.

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

Mozilla has two primary directories

* [https://mozillians.org/ Mozillians], the Mozilla Community Directory
* [https://phonebook.mozilla.org/ Phonebook], the Mozilla Employee Directory

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

=== Twitter ===

We own two Twitter accounts:

* [https://twitter.com/mozhacks @MozHacks], which targets general web developers
* [https://twitter.com/mozappsdev @MozAppsDev], which focuses on webapps.

Credentials are on the [https://intranet.mozilla.org/Engagement/Developer_Engagement#Outreach_Channels Intranet]

=== YouTube ===

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

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.

=== Lanyrd ===

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.

== Other Resources ==

=== Wikis ===

Meeting minutes and other team information can be found on the [https://wiki.mozilla.org/Devrel wiki].

Mozilla also has:

* [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.

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

Many Mozilla projects, including Firefox itself, track issues in [https://bugzilla.mozilla.org Bugzilla].

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

We tend to care about two Bugzilla keywords:

* [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=ALL%20kw:DevAdvocacy DevAdvocacy], for bugs we file based on external feedback.
* [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=ALL%20kw:devrel-needed devrel-needed], for things we should evangelize once implemented

Watch [http://blog.gerv.net/2014/11/bugzilla-for-humans-ii/ Bugzilla for Humans II] to get a better understanding of how to work with Bugzilla.

== Other Notes ==

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

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

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

=== PTO (Paid Time Off) and Holidays ===

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.

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.

=== 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 [https://www.mozilla.org/en-US/MPL/license-policy/ 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 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.

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.

=== 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 [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] 

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 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:

<code>
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.
"""

Or Mozilla wordmark:
https://www.mozilla.org/en-US/styleguide/identity/mozilla/branding/

Text would be:

"""
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 Mozilla Manifesto <https://www.mozilla.org/en-US/about/manifesto/>
to learn even more about the values and principles that guide the pursuit
of our mission.

"""
</code>

=== Travel and Expenses ===

We use Egencia for booking most travel and lodging, though AirBNB is also available. Details and policies on [https://mana.mozilla.org/wiki/display/WPR/Travel+and+Egencia Mana].

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.

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

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

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

==== Winning the update 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.

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.

=== Business Cards ===

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

=== Remote Work ===

If you work remotely, familiarize yourself with the [https://mana.mozilla.org/wiki/pages/viewpage.action?pageId=35065222 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 [https://mana.mozilla.org/wiki/display/SD/CrashPlan+Install Mana].

=== Presentation Software ===

Use what you're most comfortable with, but consider using an HTML5 based slide framework like [https://github.com/hakimel/reveal.js reveal.js] if possible.

=== Screenflow and Other Software ===

We tend to like [http://www.telestream.net/screenflow/ Screenflow] for recording screencasts. Buy a license and expense it, or request a license through ServiceNow under Service Desk &rarr; Order something &rarr; Software Applications &rarr; Other Applications &rarr; Non-Catalog Software.

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

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

* [http://www.marco.org/podcasting-microphones Marco Arment's recommendations] (via Jen)
* [http://www.podcastmethod.co/podcasting-equipment-guide Dan Benjamin's recommendations] (via Jen)
* 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

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

== 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)
** Yammer email digests
* Accounts
** Lanyrd
** Hacks Blog
** GitHub (and added to Mozilla and Mozdevs organizations)
** Bugzilla
** Egencia
** people.mozilla.org (if desired)
* 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)
* Information
** Read the Manifesto
** Watch "Bugzilla for Humans II"
** Read Home Space Worker Guidelines (if applicable)