Change Details

This session will answer the following questions: * ... = Session Themes and Topics= * Theme: Architecting our code for change and sustainability * Topic: Definition of Core, how code fits together, architecture, code encapsulation, FE/BE separation, extension interface =Session Leader= * Technical Committee = Keep in mind: = * ... = Desired Outcomes: = * ... = 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** = Resources: = * ... ---- **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: * ...

This session will answer the following questions: * ... = Session Themes and Topics= * Theme: Architecting our code for change and sustainability * Topic: Definition of Core, how code fits together, architecture, code encapsulation, FE/BE separation, extension interface =Session Leader= * Technical Committee =Description= What is the acceptance criteria for the technical product? (Architecture principles). Dispel slim MW core say that "Do we want a slim MediaWiki or not?" is irrelevant and present the alternative thinking. Also what custom code can we replace with FLOSS components to reduce maintenance burden, and what are the tradeoffs for doing that = Keep in mind: = * ... = Desired Outcomes: = * ... = 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** = Resources: = * ... ---- **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: * ...

This session will answer the following questions: * ... = Session Themes and Topics= * Theme: Architecting our code for change and sustainability * Topic: Definition of Core, how code fits together, architecture, code encapsulation, FE/BE separation, extension interface =Session Leader= * Technical Committee =Description= What is the acceptance criteria for the technical product? (Architecture principles). Dispel slim MW core say that "Do we want a slim MediaWiki or not?" is irrelevant and present the alternative thinking. Also what custom code can we replace with FLOSS components to reduce maintenance burden, and what are the tradeoffs for doing that = Keep in mind: = * ... = Desired Outcomes: = * ... = 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** = Resources: = * ... ---- **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: * ...