In a similar manner to Firefox OS' UX Contributing page, we need a way of conveying the same information for Firefox.

Our illustrious intern @vtsatskin suggested we make documentation for UX contributors like the one for Mozilla webdev contributors here: http://mozweb.readthedocs.org/en/latest/

Maybe similar to what we were talking about for UX professionals @ezoehunt ?

I'm thinking we should put start piecing together a skeleton for our bootcamp. This would have sections for content proposed in #4. We shouldn't think of these as set in stone, so let's just get something out there and we can refine later.

Madhava's Email

Also: we have a wiki page specifically for UX hires now: https://intranet.mozilla.org/UX/New_Hires

Resources:

• General
  • https://intranet.mozilla.org/Main_Page
  • https://intranet.mozilla.org/New_Hire_Info
  • Lunch/food around the office: https://etherpad.mozilla.org/YBQZHA4auC
  • Mozilla Yammer instance: https://www.yammer.com/mozilla.com/
  • Phonebook (including org chart): https://phonebook.mozilla.org/
  • Making coffee on the Epoca (AKA "The Precious"): http://www.youtube.com/watch?v=6gykuptYAh0
  • Vidyo web client -- v.mozilla.com - log in with ldap
  • Book on "Producing Open Source Software" (section 6 - communications, in particular): http://producingoss.com/en/index.html
• IT
  • https://intranet.mozilla.org/New_Hire_IT_Guide
  • https://intranet.mozilla.org/New_Hire_IT_Checklist
  • it's called out in the above, but for extra emphasis -- set up backups and encrypt your laptop
  • Page for opening IT request bugs: https://bugzilla.mozilla.org/enter_bug.cgi?product=mozilla.org&format=itrequest
• HR
  • About 1-on-1s at Mozilla: https://intranet.mozilla.org/1_on_1%27s
  • Level (band) descriptions: https://intranet.mozilla.org/Level_Descriptions (blank for now, it seems - I have my own set)
  • PTO app: https://intranet.mozilla.org/pto/
• About using Bugzilla
  • http://bugzilla.mozilla.org
  • Good introductory overview: http://people.mozilla.org/~johnath/bugzilla/BugzillaForHumans.ogv
  • Hader-core tricks: http://bugzillatips.wordpress.com/2010/06/03/quicksearch-video/
  • Install this - Bugzilla Tweaks add-on: https://addons.mozilla.org/en-us/firefox/addon/bugzillajs/?src=search
• User-experience
  • Mozilla UX Blog: https://blog.mozilla.org/ux/
  • Firefox-ux team etherpad: http://firefox-ux.etherpad.mozilla.org/
  • Design Values Booklet - http://cl.ly/0E0Y210H2t46
  • There's a Dropbox share -- see below
• First-week things to do (many of these are covered in various of the above checklists):
  • edit your entry in the phonebook - https://ldap.mozilla.org/phonebook/ (see edit my entry link)
  • install an IRC client (colloquy) and register your nick (instructions above)
  • some channels: #ux, #ur, #mobile, #fx-team, #fistbump
  • Create a work flickr account, if you want to -- you can expense a pro account
  • install skitch, cloud.app, or both!
  • open an IT bug to get Adobe Suite
  • open an IT bug to get an android phone OR buy and expense one
  • create an egencia account (travel)
  • create a Expensify (also Bill.com, unless it's been done for you) account (expenses)
  • create a mozilla blog (or use your own) and get it connected to planet.mozilla.org
  • make sure Madhava books a 1:1 with you - http://www.dria.org/wordpress/archives/2010/02/25/1443/
• Weekly updates
  • Instead of a round-the-table weekly status meeting, we do it asynchronously by email.
  • On Mondays, just send me an email with:
    • What did you do last week
    • What are you going to do this week
    • Need help / getting blocked by anything?
• Recurring Meetings
  • Monday
    • [11am PST / 2pm EST] Mozilla project meeting https://wiki.mozilla.org/WeeklyUpdates
  • Tuesday
    • [10am PST / 1pm EST] Firefox Desktop development status meeting
    • [11am PST / 2pm EST] Firefox UX design critique session - https://firefox-ux.etherpad.mozilla.org/tuesdaycrit
  • Wednesday
    • [9:30am PST / 12:30pm EST] Mobile development status meeting https://wiki.mozilla.org/Mobile/Notes
    • [11am PST / 2pm EST] Firefox Product Call (OPTIONAL - as interested, only)
  • Thursday
    • [11am PST / 2pm EST] UX Show & Tell (OPTIONAL - as your time permits, or as you need feedback)

In the brainstorming (notes/brainstorming.md) is a list of possible contributors. It might be very useful to try to find out why they want to be part of the Mozilla UX community – basically what their needs are (or at least educatedly guess it)

If such info comes up: Should that be added to the brainstorming.md or is that file for documentation purposes?

Would be helpful to the community (both internal + external) if we had a list of all the nice UX'ers at Mozilla. @ryanfeeley I remember you putting something like this together a few months back. Would you be cool doing this? Can we include Mocos + Mofos?

As of January 1 2019, Mozilla requires that all GitHub projects include this CODE_OF_CONDUCT.md file in the project root. The file has two parts:

1. Required Text - All text under the headings Community Participation Guidelines and How to Report, are required, and should not be altered.
2. Optional Text - The Project Specific Etiquette heading provides a space to speak more specifically about ways people can work effectively and inclusively together. Some examples of those can be found on the Firefox Debugger project, and Common Voice. (The optional part is commented out in the raw template file, and will not be visible until you modify and uncomment that part.)

If you have any questions about this file, or Code of Conduct policies and procedures, please see Mozilla-GitHub-Standards or email [email protected].

(Message COC001)

We have a section called "Tools of the trade" where it should outline the various tools we use. As mentioned by @mhanratty in #4, we should identify people on the UX team who are "experts" at these tools. UX Contributors can go to them for advice and questions.

The MoFo team has a good process of marking good first bugs for UX contributors.

https://wiki.mozilla.org/Webmaker/Design

Here is the process:
• File a bug and tag the Whiteboard with [goodfirstbug] & [design]
• Assign a Mentor by adding an additional Whiteboard tag [mentor=???], replacing "???" with someone's name.
• When someone wants to take the bug, they can simply assign it to themselves if it's not taken already, or flag the mentor named in the bug for more information.
• Design work will need to be submitted for a Design Review before it can be implemented. The mentor can provide this review.

Here is what the list in Bugzilla looks like:
https://bugzilla.mozilla.org/buglist.cgi?quicksearch=product%3Awebmaker%2C%20whiteboard%3A%20goodfirstbug%2C%20design&list_id=9944094

From the discussion with @mhanratty in #11, we should inform the community through our mailing list about this new bootcamp we're developing. Quoting @mhanratty:

Awesome, love the enthusiasm! Since there aren't many folks on the github yet, maybe email the [email protected] and [email protected] lists about the idea of creating a bootcamp so people are aware and can give feedback. I would include the purpose of the bootcamp, why you are so passionate about it (i.e. as an intern this stuff was scattered everywhere or does not even exist), and a link to the webdev bootcamp for reference. You can link to the different github issues for people to get involved, learn more, and give feedback.

Information to convey:

• Purpose of bootcamp
• Why it's important
• Link to bootcamp
• What information are you looking for to start contributing?
• How to give feedback on existing sections

Currently we need to share the assets we use for Firefox on the Bootcamp wiki. For example, Firefox OS has their Design Asset Library.

Possible assets include:

• Australis PSDs
• Templates for doorhangers

Feel free to edit the list above with more assets that you know exist and should be included.

https://wiki.mozilla.org/Contribute/UX

We've outlined how to see what we're working on, but no outline of how to give feedback to those things.

When a UX contributor is ready to share their work, there should be a clear way of getting feedback from the UX team on their work.

Outline instructions for:

• Firefox Desktop
• Firefox for Android
• Firefox OS

https://wiki.mozilla.org/UX

Here is a rough draft of a design brief for contributor projects--something we could use for student projects that require mentorship and projects that are larger in scope and timeline.

https://docs.google.com/a/mozilla.com/document/d/1ylyIkqrHCW01-Xt-5SGO96TPd2njREDDQOJArpkMIH8/edit

FYI: The following changes were made to this repository's wiki:

• Restricting write access to contributors is strongly encouraged. Please make that change (documentation).

These were made as the result of a recent automated defacement of publically writeable wikis.

Need a section for Firefox under "How to Help > Project Specific involvement" for UX contributors who are interested in getting involved with Desktop/Firefox for Android projects
https://wiki.mozilla.org/UX/Community

Update the Marketplace UX wiki (https://wiki.mozilla.org/Marketplace/Marketplace_UX) to tell people how they can contribute UX to the Marketplace.

Content to add:
• Team members list and contact information
• Email lists to subscribe to ([email protected] AND [email protected]
• IRC channel: #marketplaceux
• Thursday Marketplace public meetings information
• Good first bugs list
• Process/rules for contributing

Here are some good contribution wiki pages that other teams have created:
Gaia UX: https://wiki.mozilla.org/Gaia/UxContributing
Webmaker: https://wiki.mozilla.org/Webmaker/Design

Some valuable assets for designers to understand the design language of Firefox OS can be found on the Building Blocks website. I'm not entirely sure where this should go, but probably where we direct community members to project specific assets.

It would be nice if we could provide to our contributors various user research we've conducted as well as external research that we've found useful. Ultimately we want all our research to be put in "this place" and part of the user research workflow to ensure it is up to date (instead of being an after-thought to update the wiki).

Following in the successful footsteps of the webdev bootcamp, I'm suggesting we use readthedocs.org for our bootcamp. They are open source so if we ever need to we can host it ourselves (e.g. the service is not offered anymore).

The nice thing about this service is that it generates documents from github repos. Also supports useful features like exporting to pdfs. Github hooks can be created for auto-updating docs on commits.

Marketplace Community Manager Amy Tsay has planned a "Marketplace Day" on Thursday, May 8th to try to bring more contributors into the project.

https://etherpad.mozilla.org/marketplace-day

I hope we can have some stuff ready for any UX contributors who might come. I'm thinking at a minimum we could have our "goodfirstbugs" list groomed and ready:

This link does not work: https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=Marketplace%20goodfirstbug&list_id=9958427

This link works: https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=Marketplace%20goodfirstbug&sharer_id=453984&list_id=10081714

What do you think: @pwalm @tsmuse @ezoehunt @brampitoyo