Skip to content

Paris Work Week

Jump to bottom Edit New page
karl edited this page Sep 30, 2015 · 34 revisions

Attendees

  • Karl Dubost
  • Mike Taylor
  • Guillaume Démésy
  • Hallvord Steen

Organized Schedule

Monday

✔︎ How to build Firefox + Try, etc.

✔︎ Agenda Planning

✔︎ Testing webcompat.com improvements

✔︎ Boring team logistics

  • Minutes (+ bug summary?) on wiki
  • How to run meetings
  • Team + personal goals/milestones
  • Revisit time of meetings/1:1s

Minutes:

Weekly meetings. Originally Karl was running the agenda. He stopped to see if others would step in. Mostly that didn't happen (though Mike sometimes puts in agenda items because he's super cool 🆒 😎. Hallvord suggested using our meeting time to talk through certain issues, as a sort of triage. 👍 We can also do country-specific meetings, triage bugs for a specific country - perhaps invite special guests if we have past contributors for that country.

  • TODO: Karl to investigate sending a weekly email of bugs that have been closed for the previous week for the compatibility mailing list.
  • TODO: Consider semi-regular project meeting updates about bug successes (again), but also to point out issues that we need help with, especially for contacting.

Tuesday

leftover

  • Abort + error management (errors.py?) See issue 713

✔︎ Pairing device for Remote WIFI debugging

✔︎ Logging capabilities for webc

Minutes

The system is here, it's usable. We could for example at a first step, use it to log domain names of issues in sqlite db. So we could use that for feeds by domain name and for addons to know if a domain name has been reported already.

✔︎ Spam abuse:

Minutes

not that much spam, we had a couple at the beginning and then the facebook for the last couple of weeks.

Some suggestions:
  • rel='nofollow' #716
  • block fb.com
  • ✔︎ update privacy policy to mention recording IP, timestamp, URI for spam control purposes (Issue #705)
  • set up service to delete logs older than 14 days #717
  • consider emailing logs, privacy implications
  • log the info via flask #719

✔︎ Scaling outreach + training

Should we reach out the participation team for their help? George roJustOneTer Do we want regular contributors or do we want contributing opportunities (as in one time help)? We have not done a very good job at training. Hallvord is playing with OBS. We might end up to do some recordings livestream.

  • TODO: Karl will contact past contributors for issues/good things with needscontact and contacting
  • TODO: I contacted site buttons. It will switch labels. It will say thank you. It will record statistics. I will offer a reminder option. This needs to be multiple tasks, it will lead to a personal dashboard.

✔︎ Discuss other evangelism needs (RC4, Desktop, etc.)

TODO: Mike Taylor will contact people from the security team to discuss about the outreach issues once SSL, RC4, etc bugs are landing in Tech Evangelism.

TEAM BUILDING

(Outside activity + discussions)

Wednesday

(With Guillaume, to email Alexa about schedule)

  • this morning hacking a bit on errors in Flask and JS
  • Guillaume arrived
  • Mike went through the agenda

Look at Microsoft (TheWebJustWorks) feedback on site

Microsoft seems not that much interested in fixing website bugs for Web Compatibility with IE. They are focusing on Edge. They gave us feedback

What is missing:

  • lack of priority, severity, site ranking. We like the idea of adding prioritization at the triage level. Needs work on how it should work #715
  • Platform specs: Hard because we do not necessary report from the tool where the issue is happening but interesting.
  • Voting Systems: Agreed to track the number of issues reported for the same domain.
  • Edge labels. See issue #707 Need to update the bot parser.
  • Connectivity with engineers. A way for site devs to follow up what's happening for domain names.

** What works/doesn't work ***

  • webcompat.com landing page is great
  • social|user interaction
  • Pinging MS if the issues are for everyone. Not useful.

** What would be cool? **

  • A bot that automatically outreach's to a sites support alias, web form.

What's working, not working

JS dependencies + UX

Styleguide

UI + UX improvements

  • #646 It would be indeed interesting to kill the thanks page and add a thanks and next step contributions.
  • #571 We keep "Bug reporting for the internet." Looking at the search from Apple home page right now, could be a way to do it. We should do testing for "Report bug" if it's obvious or not.
  • #545 "labels" to remove. Title font size smaller. Remove issue. @magsout / @karlcow proposes a layout.
  • #510 Let's fix the dashboard issue first #442. And then we can do this filter. The icon button is becoming a "My dashboard + Sign out" the way github does.
  • #501 linking bugs. Hallvord to do it
  • #482 Let's pick up colors for browser. and 1 for status. todo by @magsout
  • #445 Depends on #442. We'll do later once it's done.
  • #442 Dashboard

Issues + milestone priorization (w/ waffle)

Thursday

(With Guillaume and Karl at ParisWeb)

Moar UI webc

stuff

Friday

(Karl at ParisWeb and Hallvord leaving in afternoon)

more stuff

Old List

Add a custom footer
Add a custom sidebar
Clone this wiki locally