Confirmed users
2,473
edits
Compatibility/Mobile/2014-02-work-week: Difference between revisions
Jump to navigation
Jump to search
Compatibility/Mobile/2014-02-work-week (view source)
Revision as of 03:49, 1 February 2014
, 1 February 2014→Agenda Item Details
No edit summary |
|||
| Line 59: | Line 59: | ||
= Agenda Item Details = | = Agenda Item Details = | ||
=== 2013 review & 2014 strategy and goals === | |||
* What did we accomplish in 2013? | |||
* What has been working? What do we need to tweak/change? | |||
** Weekly Meetings - Satisfied? Things to improve? Rotating Scribe? Chairing? | |||
** Bugzilla | |||
* What is our focus for 2014? (Solving compat problems, recruiting and onboarding volunteers, etc.) | |||
* How will we measure our success? | |||
=== Mozilla Project and Corp meetings (team introduction) === | |||
* team introduction | |||
* Adam's summary of getting started with Web compat issues | |||
=== Working with volunteers === | |||
* Finding volunteers - it is really hard to engage with volunteers | |||
** WhatCanIDoForMozilla | |||
*** Status and how we can make progress | |||
*** Time to create flows to Web compat effort | |||
** Meeting with (future) volunteers | |||
*** Create a 101 on setting up events - Mozilla space specific? | |||
*** General guidelines on event participation - in what type of events should we participate in order not to duplicate effort of other Mozilla teams? | |||
* How do we make Web Compatibility a nicer place to work altogether? | |||
* Job description | |||
** Pair task to write job description for post on blogs, webcompat.com, other places? | |||
* Mentoring | |||
** Mentoring in the sense that we can help them to contact or they can help us for example with language skills. It gives more a sense of working together. Experience maybe with Spain and Adam. | |||
** What is required from mentoring for Web compat participants? | |||
** from [contactready] to ASSIGNED and [sitewait], how do we distribute the work, how do we make sure we moved on and still move the community forward. | |||
** New contributor's guide | |||
*** little handbook for testing, contacting, etc for Web compatibility issues. | |||
* Recognition / keeping people engaged | |||
** make a twitter list of volunteers who are actively participating on @MozWebCompat | |||
** make a geo map of volunteers and build recognitions for the work they are doing | |||
*** can we build this today? | |||
** Open Badges | |||
*** Outline the badges that we want to create an assign someone to create them | |||
** Tee-Shirt ({{bug|927478}}) | |||
** Stickers ({{bug|927478}}) | |||
*** small, in series, usable on laptop, and or even on paper notebooks (aka embodiement of achievements). | |||
=== Project definitions === | |||
* Team project backlog | |||
* Each project should have an clear mandate and expected duration (how much time are we willing to spend on the project?) | |||
=== AreWeCompatibleYet.com === | |||
* What's to be done? | |||
* Create issues on github? | |||
* Schedule for releases | |||
=== UA detection use cases === | |||
* Summarize use cases in a report - https://etherpad.mozilla.org/uadetection-usecases | |||
* UA profiles ready to use in other inspection tools (curl, httpie, etc, automated testing) - https://etherpad.mozilla.org/uaprofiles | |||
=== Web compat, QA, and automated testing === | |||
* how the web compat and QA teams should interact | |||
* Automated testing | |||
** Ensure everyone knows how to use the framework - read and write tests | |||
** Feedback for Hallvord and Seif | |||
** Improvements | |||
*** Finalize procedures for generating bug reports | |||
*** reporting bugs and let the automated tools analyze and annotate them | |||
*** Countries coverage for testing survey | |||
**** New countries to add | |||
**** Old countries to improve | |||
=== Bug process and Buzilla improvements === | |||
* Do we need to capture more information on the bug? | |||
* Should we try to create standards to allow for reporting? (eg. best method of 1st contact by region) | |||
* User Agent used for the tests. We see sometimes bugs which are landing in Tech Evangelism. Some of these sites have been tested with UA which are not production ones, and some sites will then fail. Should we recommend them to test with production ready UA? | |||
* Adam has some suggestions for ways in which we may be able to improve Bugzilla for the web compat community | |||
=== Working with other Mozilla teams === | |||
* Collaboration with other departments | |||
* Slidesets for devrel group about WebCompat | |||
* How should we work with developer advocates and the dev engagement team? | |||
=== webcompat.com planning === | |||
* high-level architectural decisions (i.e., sitemap, content-type) | |||
* determine what can be accomplished this week | |||
= Hack project board = | = Hack project board = | ||