==== webcompat.com - architecture overview ====
Info session to learn about how data flows through the system (end to end). Other questions?
==== webcompat.com - deploys ====
Hack session to work on the work left to get someone else to deploy the site (other than Mike).
==== webcompat - VPNs ====
==== webcompat - H2 planning ====
* What are the projects we will continue to work on for the rest of 2017? What should we kill? What new projects? ==== webcompat - team meetings ====A quick discussion on all our current meetings to decide if what we do works for us. ==== go faster - H2 planning ====* What's the current status for webcompat gofaster and what comes next?
==== Google Tier 1 planning ====
Review bugs filed by SoftVision and plan how we can move forward.
==== webcompat newsletters ====
More projects at Mozilla are making a nice review of what happened recently under the form of a newsletter/blog post. Examples: [https://blog.nightly.mozilla.org/2017/06/21/these-weeks-in-firefox-issue-19/ Photon Engineering Newsletter #6], [https://this-week-in-rust.org/blog/2017/06/20/this-week-in-rust-187/ This week in Rust], [https://ehsanakhgari.org/blog/2017-06-16/quantum-flow-engineering-newsletter-13 Quantum Flow Engineering Newsletter]. Been there, done that at W3C [https://www.w3.org/blog/author/karl/ open web platform weekly summary]. It takes time, but it's valuable. It sometimes require a bit the participation of everyone. It also ties into the topic of transparency that Dennis mentioned a couple of times.
Thomas on IRC on June 22, suggested we use etherpad to collect things. So we started as an experiment
[https://public.etherpad-mozilla.org/p/webcompat-news webcompat-news]. Feel free to add stuff there and we will see where it goes.
==== webcompat - transparency on what the team is working on ====
As Dennis mentioned a few weeks back, it's hard to keep track on who is working on what right now. Maybe we can find a good way to make things more transparent as a short brief in our meetings on everyone's status or making everyone's quarterly goals transparent (if possible).
==== webcompat.com - Living Style Guide (LSG) ====
With the refactor, we'd like to work on a Living Style Guide to build a base for the upcoming refactor of the page.
This will include
- a "grid system",
- website modules that will be build upon the grid system including defined HTML semantics,
- the structure for the LSG (usage of modules, documentation of colors, fonts etc),
- Tests (How much do we need to change due to CSS / semantics refactor)
- Visual Regression Testing for LSG (http://webdriver.io/guide/services/visual-regression.html)
- Ownership of LSG
With the LSG we will be on the same page to proceed with the refactor remotely as well as be able to manage small releases plus have a clearer entry point for new contributors.
==== webcompat.com - Discuss LSG related questions ====
A few questions need to be discussed before we start working on the LSG:
- How do we want to handle SVG's?
- How do we want to handle font loading as we will probably switch to Open Sans (Example: http://webcompat.github.io/design/)?
- How should the naming conventions for CSS look like?
- We would need to decide on the audience of contributors for the LSG, so we know how the documentation should look like.
- How do we want to handle the CSS development (e.g. pull from webcompat.com in LSG for testing purpose) as the same CSS should serve both (webcompat.com & LSG), so we can run manual / automated visual testing for it.
==== webcompat.com - Discuss roadmap for refactor in Q3 / 4 ====
With everyone working remotely, it would be great to discuss a rough roadmap for the refactor of webcompat.com.
A few questions that fall under that topic would be:
- What needs to be done?
- Who would like to help and take over which tasks?
- What needs to go in which milestone?
- When do we tackle the JS refactor?
==== webcompat.com - Discuss roadmap for refactor in Q3 / 4 (low prio) ====
Following questions can be interesting to discuss, but are not high priority as they can be discussed in a remote meeting at some later point:
- Webpack rebuild
- Tooling for JS refactor (Mostly framework discussion + tools for handling npm dependencies, test coverage...)
==== webcompat.com - testing ====
As we will change semantics and naming conventions for webcompat.com and the LSG, we will need to put some work in the tests. How much do we want to change? Just fixing the tests? Or do we want to make more improvements as we are on it already? How would those improvements look like? What is out of scope?
==== webcompat.com - type-media ====
We receive a lot of type-media issues. We need to clarify a couple of things.
- Do we push them in needs-diagnosis once identified?
- Who is handling them in needs-diagnosis? alfredoyang?
- We have the webhook being developed by karl.
- Do we kill the handling of those?
==== webcompat.com - Atom feed for issues ====
Part of the SF Milestones on Github. I will work on this during San Francisco Work Week.
https://github.com/webcompat/webcompat.com/milestone/35
==== webcompat.com dev - committing on your repo ====
It seems there are two styles of coding for branches. Some people will commit on webcompat.com repo a branch, and some will do it on their personal fork. We pushed people to do it on their own repo in the past to avoid any kerfuffles on webcompat.com.
==== Communications channels and openess ====
There is a trend that we need to stop and fix. We have a tendency to use non-open communication channels for things which are not Mozilla-secret sensitive. Each time we share something on a private channel, each time we lower the sense of the community. Mundane stuff, simple links to geeky stuff, etc. All of that is useful for the community even if there are just peeping.
==== Webcompat.com Responsibilities Overview ====
How the responsibilities worked out since [[Compatibility/Meetings/2017-04-work-week|Berlin Meeting]]? Do we need to readjust the path? tweak? Do we sail as-is?
==== Webcompat.com San Francisco Milestone ====
We have a [https://github.com/webcompat/webcompat.com/milestone/35 San Francisco Milestone] for Webcompat.com. Let's try to tackle it before the work week.
==== GoFaster hacking time ====
(Dennis, Eric, Mike, (Tom)) Dennis is running into some difficulties while adopting the GoFaster addon to newer standards (especially [https://bugzilla.mozilla.org/show_bug.cgi?id=1371442 bug 1371442]) and would love an hour or two of concentrated Gecko-knowledge to discuss these in a group.
==== Half-day or evening team building ====
Let's do something not work related together. The bigger the team the harder it becomes but we will probably find out something. If you have ideas, propose them here.
==== Webcompat.com Localization ====
(Adam) In the past we have generally pushed back on this idea, due to the possibility of increased bug reports in languages we don't understand. We currently get bugs from many different countries, with no description of the problem. Can we somehow encourage users to leave descriptions in their native language without doing full localization? It's easy to Google translate and currently these reports are being closed anyway.
[[Category:Web Compatibility]]
