-
Notifications
You must be signed in to change notification settings - Fork 191
Paris Work Week
- Date: September 28 - October 2nd, 2015.
- Location: https://wiki.mozilla.org/Paris
- Karl Dubost
- Mike Taylor
- Guillaume Démésy
- Hallvord Steen
- Minutes (+ bug summary?) on wiki
- How to run meetings
- Team + personal goals/milestones
- Revisit time of meetings/1:1s
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. 👍
- 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.
- Abort + error management (errors.py?) See issue 713
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.
not that much spam, we had a couple at the beginning and then the facebook for the last couple of weeks.
- rel='nofollow'
- block fb.com
- update privacy policy to mention recording IP, timestamp, URI for spam control purposes
- set up service to delete logs older than 14 days
- consider emailing logs, privacy implications
- log the info via flask
(With Guillaume, to email Alexa about schedule)
(With Guillaume and Karl at ParisWeb)
(Karl at ParisWeb and Hallvord leaving in afternoon)
- Testing: how to make it better, how to make it quicker for Japan
- Mocking?
- setup, teardown https://github.com/webcompat/webcompat.com/issues/664
- UI design: http://firefox-dev.tools/ for inspiration
- Retrospective: What's not working? What's working?
- Logging Capabilities https://github.com/webcompat/webcompat.com/issues/245
- Spam/Abuse strategies fighting https://github.com/webcompat/webcompat.com/issues/694
- Reduce JS dependency on real content, Use JS to improve User Experience
- Normalise and add a style guide (markup, js, css)
- API, error management. Abort and flask best practices. http://flask.pocoo.org/docs/0.10/patterns/apierrors/
- Microsoft TheWebJustWorks feedback about webcompat.com
- SSL type bugs and contact effort.
- Outreach, how do we scale and how can we train others?
- Revisit boring team logistics (Team meeting times, 1:1s, etc)
- Q4+ goals
- Compat spec stuff