Members were chose by time available, previous work, critical to the groups success
How can the group can be most effective?
How does the group fit into the RFC process?
Not trying to sideline the RFC process
May not fit well into the day to day foundation acitivities
RFC's arent the great at follow and GSD
Jon wants to make sure he is not detached from Mobile
Jon will continue to be in Mobile Web working on tasks as neded but will involve the web team in using what this group produces
When should meetings be scheduled and how often?
Does this need to be a weekly meeting?
Play it by ear
What time? Early morning in SF
yeah probably a bit earlier for the remotes! +1
What are the group's short, mid and long term goals?
Trevor: "Every single team will be using the same technology to make the features that we make."
Brion: Mobile Apps will be a little different but still keep consistent where makes sense: use RL for styles, use a common templating system for customizable strings, etc
Making it easier for horizontal movement between teams by keeping things more consistent
Making it easier for newcomers to hack on our codebases by having simple, concise, common idioms for common tasks.
Form standardisation (buttons, inputs, selects, checkboxes, radios etc.)
Mobile and Growth (and soon Flow) to be using same markup/css
Bartosz has done the early work for a Grunt task that can a pile of SVGs and a JSON config file to generate the colored svg and png renderings and the LESS for them
(how can we do this at runtime with ResourceLoader? figure this out in near future!)
It aligns with the Core team's wish to "librarize" components that are currently internal to MediaWiki and to have a build step that readies the source tree for deployment.
It's almost certainly impossible to do rasterizing SVG→PNG in RL, as that takes on the order of seconds. Build step needed? :(
i would recommend modifying SVGs in RL and rasterizing via 404 handler?
Summary: The generated built files should also be included in version control. MW should be runnable straight from git/tarball.