Kickoff meeting agenda (2014-09-19)[edit]

Discussion (~10min)[edit]

Who is on the team?
- 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.
External stakeholder
- Invite them as needed

Trevor with Bartosz, pretty much done
Teams will be able to use OOUI (not off brand) next week
Server-side OOjs UI (weeks)
- set of PHP classes that have the same API as JS classes (subset, naturally)
- WIP [Trevor]
  - for next meeting: bringing items 'back to life' with JS after created statically?

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.

Brion -> putting this onto the agenda for the arch committee, let's make a decision soon
- We would recommend mustache based language

Reach out to Derk-Jan [Tomasz]
Schedule re-ocurring meeting [Tomasz]
Get some movement going on the template RfC, with input from frontend group usage needs [Brion]
- Start thinking about and divide down the template vs live dynamic issues
Generate tentative Roadmap [Trevor]

Templating language
- Who should we include? Shahyar, Erik B, Kaldari
- Review RFC
  - open questions on dynamicalization of statically-generated template output?
    - (does this relate to oojs ui server-side generation?)
Server-side OOUI
- How to bind the generated HTML to the JavaScript objects.
  - (shared html templates that are recognised, KnockoutJS-like bind detection without rerendering the DOM)