= Session Themes and Topics=
* Theme: Enabling our engineers, staff, and volunteers to achieve our goals easier and faster
* Topic: Frontend Tooling, Development Tooling and Process
=Session Leader=
* Christoph Jauera
=Facilitator=
* Zakaria Oudrhiri
=Description=
What works and what doesn’t work in our current front-end development stack -- where should we focus our attention in order to streamline contributions from both staff and volunteers?
=Questions to answer during this session=
|**Question**|**Significance: Why is this question important? What is blocked by it remaining unanswered? **
|In our current front-end development stack, what works? What doesn’t work? |In many cases, the maintainers of a given technology are the ones who will see the fewest bugs -- they have a system that’s already up and running. This question provides an opportunity for others to talk about their own experiences with the technical stack.
|In our current front-end development process, what works? What doesn’t work? |As with technologies, it’s often the people who decide on a process who are least able to see problems with it. This will allow developers to talk about their own experiences with our front-end development process, and will provide guidance about what needs to be improved.
|What issues are people having with ResourceLoader, OOUI, and other older JS libraries? |Specifically relating to front-end components that are part of MediaWiki (or closely related), what issues do people encounter? What gaps in these libraries make life harder?
|What front-end components or processes can be renovated? Which ones need to be torn down and fully rebuilt? |This question provides guidance to both the degree of pain that various components cause, as well as the degree to which these components vary from what would be considered standard practice. The more inclination to tear something down, the more implied value in doing so.
=Scribe Instructions=
Please make a copy of the notes worksheet located here to take notes: https://docs.google.com/document/d/1J-wTeelHFGeXw6dO1ywkGr0NfnzG-cUykowc6aSKoWE/edit?usp=sharing
=Facilitator Instructions=
Use this document for reference: https://docs.google.com/document/d/1LEFWE5MJfhl2fHzqHiijmnX6PJEk1GRhkOMUowJYMqw
= Resources: =
* Session Guide: https://www.mediawiki.org/wiki/Wikimedia_Technical_Conference/2018/Session_Guide
= Session Structure =
* **Define session scope, clarify desired outcomes, present agenda**
* Discuss Focus Areas
** Discuss and Adjust. ''Note that we are not trying to come to a final agreement, we are just prioritizing and assigning responsibilities!''
** For each proposition [add etherpad link here]
*** Decides whether there is (mostly) agreement or disagreement and the proposition(s).
*** Decide whether there is more need for discussion on the topic, and how urgent or important that is.
*** Identify any open questions that need answering from others, and from who (product, ops, etc)
*** Decides who will drive the further discussion/decision process (ie: a four month deadline)
* Discuss additional strategy questions [add etherpad link here]. For each question:
** Decide whether it is considered important.
** Discuss who should answer it.
** Decide who will follow up on it.
* **Wrap up**
----
**Session Leaders** please:
[] Add more details to this task description.
[] Coordinate any pre-event discussions (here on Phab, IRC, email, hangout, etc).
[] Outline the plan for discussing this topic at the event.
[] Optionally, include what it will //not// try to solve.
[] Update this task with summaries of any pre-event discussions.
[] Include ways for people not attending to be involved in discussions before the event and afterwards.
----
Post-event Summary:
* ...
Action items:
* ...