Release Management/New Hire Portal: Difference between revisions

Release Management/New Hire Portal (view source)

Revision as of 22:36, 11 February 2013

745 bytes added , 11 February 2013

→‎Tuesday

Lsblakk

Confirmed users

4,467

edits

@@ Line 28: / Line 28: @@
 = Tuesday =
-* Most people are in between 9-9:30, out by 6-6:30 (checking email a couple of times in the evening). Feel free to keep the hours that help you get your work done.
+* Most people are in the office between 9-9:30, out by 6-6:30 in their timezones
-* Working From Home (WFH) is also an option up to 2 times a week or so, but please hold off on that for a couple of weeks while you come up to speed.
+* Working From Home (WFH) is also an option up to 2 times a week or so, but please hold off on that for a couple of weeks while you come up to speed
-* Let the flood gates open first thing Tuesday - sign up for https://mail.mozilla.org/listinfo/release-drivers and https://lists.mozilla.org/listinfo/dev-planning. [https://bugzilla.mozilla.org/enter_bug.cgi?product=mozilla.org&component=Server%20Operations:%20Desktop%20Issues File a Bug] asking to be added to the release-mgmt@mozilla.com distribution list
+* Let the flood gates open first thing Tuesday - sign up for mailing lists:
-* You can check out archives of dev.planning on the online newsgroup at https://groups.google.com/group/mozilla.dev.planning/topics
+** [https://mail.mozilla.org/listinfo/release-drivers Release Drivers]
-* Subscribe to the RelMan calendar https://mail.mozilla.com/home/akeybl@mozilla.com/Release%20Management.html using the ICS link at the bottom.
+** [https://mail.mozilla.org/listinfo/b2g-release-drivers B2G Release Drivers]
-* Planning meeting at 11AM in WarpCore near your desk
+** [https://lists.mozilla.org/listinfo/dev-planning Dev-Planning]
-* Help Lukas track engineers down on IRC before the weekly beta cutoff. Also help by watching https://hg.mozilla.org/ and https://tbpl.mozilla.org/?tree=Mozilla-Beta to make sure they land and are successfully built.
+** [https://lists.mozilla.org/listinfo/dev-firefox Dev-Firefox]
-* Start setting up a personal/Mozilla blog. If you don't care about using your own domain consider using https://wordpress.com/.
+* [https://bugzilla.mozilla.org/enter_bug.cgi?product=mozilla.org&component=Server%20Operations:%20Desktop%20Issues File a Bug] asking to be added to the release-mgmt@mozilla.com distribution list
-* File a bug to get syndicated on Planet Mozilla (https://wiki.mozilla.org/Planet_Mozilla) and track down Asa in MV or on IRC to get you approved. He's a busy guy so tell him I sent you :)
+* You can check out [https://groups.google.com/group/mozilla.dev.planning/topics the archives of dev.planning] on the online newsgroup
-* Channel meeting at 2:00 PM in Warp Core on the 3rd floor. Introduce yourself (again, I know). Try to remember faces - these are our people, and we work with them on a daily basis.
+* Subscribe to the [https://mail.mozilla.com/home/akeybl@mozilla.com/Release%20Management.html RelMan calendar] using the ICS link at the bottom
-* Set up tool on your Mac for opening bug #s http://alex.keybl.com/?p=23. Also think about adding a keyboard shortcut for opening names in the Mozilla Phonebook (http://alex.keybl.com/?p=163). That's super helpful with getting to know people in email.
+* Channel meeting at 10AM in the Release Coordination Vidyo room
-* You may want to set up "Copy Better Link" https://builder.addons.mozilla.org/user/akeybl/ for copying bug titles as HTML links, and https://addons.mozilla.org/en-US/firefox/addon/bugzillajs/ to make Bugzilla more readable/usable.
+** Introduce yourself (again, I know)
-* Set up your Firefox to open initially with multiple profiles https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles. This is really helpful for reproducing issues.
+** Try to remember faces - these are our people, and we work with them on a daily basis
-* Set up your Firefox with Tree Style Tabs (https://addons.mozilla.org/en-US/firefox/addon/tree-style-tab/). This is important for the amount of info we're parsing through at any one time.
+* Planning meeting at 11AM (MTV: WarpCore for physical and Vidyo room)
-* Figure out how to search for bugs that are tracking for a specific Firefox release that are unresolved and have the "qawanted" keyword attached.
+* Start setting up a personal/Mozilla blog - use a tag to distinguish your posts on Mozilla topics and set up an RSS or Atom feed for that tag's posts
-* File an IT bug to get Windows/VMWare for your Mac. In the meantime, ask Marcia to show you where the lab is (2nd floor) and spend some time trying to reproduce the bugs you found. If you're able to, please comment in the bug. For crashes, look at the associated crash comments on http://crash-stats.mozilla.com/.
+* [https://bugzilla.mozilla.org/enter_bug.cgi?product=Websites&component=planet.mozilla.org File a Bug] to get syndicated on [https://wiki.mozilla.org/Planet_Mozilla Planet Mozilla] if that bug doesn't get resolved in the first week, get your manager/coworkers to prod the bug for you
-* Also look for bugs that have the regressionwindow-wanted keyword attached. Use http://harthur.github.com/mozregression/ to help find a regression window.
+* Set up [http://alex.keybl.com/?p=23 Alex's handy tool] on your Mac for opening bug numbers
-* Start idling in #b2g
+* Also think about [http://alex.keybl.com/?p=163 adding a keyboard shortcut] for opening coworkers' names in the internal Mozilla Phonebook as it's super helpful with getting to know people in email
+* Set up [https://builder.addons.mozilla.org/package/19466/latest/ "Copy Better Link"] for copying bug titles as HTML links, and https://addons.mozilla.org/en-US/firefox/addon/bugzillajs/ to make Bugzilla more readable/usable
+* Set up your Firefox to open initially with [https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles multiple profiles] as being able to do so is really helpful for reproducing issues
+* In your default profile install the following addons:
+** [https://addons.mozilla.org/en-US/firefox/addon/tree-style-tab/ Tree Style Tabs] for the amount of info we're parsing through at any one time you will find this add-on invaluable
+** [https://addons.mozilla.org/en-US/firefox/addon/bugzillajs/ Bugzilla JS] makes reading bugs much more user-friendly and provides several awesome improvements to navigating long bug lists
+** [https://addons.mozilla.org/en-US/firefox/addon/sqlite-manager Sqlite Manager] helps with viewing local sqlite dbs we use for some tools
+** Not required, but recommended: Adblock Plus, 1Password (buy & expense the app and get the mobile version too - keep all your passwords unique and on all your devices simultaneously)
+* Try out some Bugzilla searching starting [https://bugzilla.mozilla.org/query.cgi here]:
+** Figure out how to search for bugs that are tracking for a specific Firefox release that are unresolved and have the "qawanted" keyword attached
+* File a Service Now request to get Windows/VMWare for your Mac
+** If you're in MV ask Marcia to show you where the lab is (2nd floor) and spend some time trying to reproduce the bugs you found
+** If you're able to, please comment in the bug
+** For crashes, look at the associated crash comments on http://crash-stats.mozilla.com/
+* Also look for bugs that have the regressionwindow-wanted keyword attached
+** Use http://harthur.github.com/mozregression/ to help find a regression window.
 * Finish out your day with the 5PM B2G meeting (location is always TBD)