Change Details

T286466 introduced a new "Contribute" item within Minera Neue's navigation menu. This task involves the work with defining how this new "Contribute" menu item – and potentially the contribution types that appear within it – will be instrumented so that we can see how the completion rates of edits that originate through/from the new "Contribute" menu compare to those that originate through other editing entry points. [i] === Open question(s) - [ ] 1. What – if any – new instrumentation is required in order for us to compare how the edit completion rates vary between edits that originate through/from the new "Contribute" menu and those that originate through other editing contextual entry points. === Done - [ ] Answers to all Open question(s) are documented --- i. https://www.mediawiki.org/wiki/Edit_Discovery?useskin=vector-2022#Contextual_Entry_Points

T286466 introduced a new "Contribute" item within Minerva Neue's navigation menu. This task involves the work with implementing the instrumentation required to evaluate how people engage with this new "Contribute" menu item – and the contribution types that appear within it – in ways that enable us answer the `=== Research questions` listed below. === Research questions //The research questions below are !!copied from T332059!!.// |ID|Question |---|--- |1.|When people open the "Contribute" menu, do they find what they expect |2.|When people tap on something within the "Contribute" menu, does it do what they expected? | 3.| Who is accessing/using the new "Contribute" menu? |4.| Are people using this menu to publish edits that wikis value? |5.| //[optional] How does the rate at which people complete edits through the "Contribute" menu compare to the rates of other entry points? [i]// NOTE: the work to report on/answer research questions will happen in T332059. === Instrumentation requirements === Open question(s) - [ ] 1. What team (Editing/Language/Web) will assume responsibility for **implementing instrumentation**? - [ ] 2. What team (Editing/Language/Web) will assume responsibility for **verifying instrumentation is logged as expected on //client//**? - [ ] 3. Who will assume responsibility for **verifying instrumentation is logged as expected on //server//** === Done - [ ] All `=== Instrumentation requirements` are documented - [ ] Answers to all `=== Open questions` are documented - [ ] Instrumentation verified as logging correctly on //client// - [ ] Instrumentation verified as logging correctly on //server// --- i. We will answer question `5.` to the extent that instrumentation that has //already// be implemented enables us to. //Said another way: we will not invest any effort into instrumenting other editing entry points in order to answer this question.//

T286466 introduced a new "Contribute" item within Minerva Neue's navigation menu. This task involves the work with defining howimplementing the instrumentation required to evaluate how people engage with this new "Contribute" menu item – and potentially the contribution types that appear within it – will be instrumented so that we can see how the completion rates of edits that originate through/from the new "Contribute" menu compare to those that originate through other editing entry points. [i]in ways that enable us answer the `=== Research questions` listed below. === Open question(s)Research questions //The research questions below are !!copied from T332059!!.// |ID|Question |---|--- |1.|When people open the "Contribute" menu, do they find what they expect - [ ] 1.|2.|When people tap on something within the "Contribute" menu, does it do what they expected? | 3.| Who is accessing/using the new "Contribute" menu? |4.| Are people using this menu to publish edits that wikis value? |5.| //[optional] How does the rate at which people complete edits through the "Contribute" menu compare to the rates of other entry points? What – if any – new instrumentation is required in order for us to compare how the edit completion rates vary between edits that originate through/from the new "Contribute" menu and those that originate through other editing contextual entry points.[i]// NOTE: the work to report on/answer research questions will happen in T332059. === Instrumentation requirements === Open question(s) - [ ] 1. What team (Editing/Language/Web) will assume responsibility for **implementing instrumentation**? - [ ] 2. What team (Editing/Language/Web) will assume responsibility for **verifying instrumentation is logged as expected on //client//**? - [ ] 3. Who will assume responsibility for **verifying instrumentation is logged as expected on //server//** === Done - [ ] Answers to all Open question(s) are documentedll `=== Instrumentation requirements` are documented - [ ] Answers to all `=== Open questions` are documented - [ ] Instrumentation verified as logging correctly on //client// - [ ] Instrumentation verified as logging correctly on //server// --- i. https://www.mediawiki.org/wiki/Edit_Discovery?useskin=vector-2022#Contextual_Entry_PointsWe will answer question `5.` to the extent that instrumentation that has //already// be implemented enables us to. //Said another way: we will not invest any effort into instrumenting other editing entry points in order to answer this question.//