Change Details

The Edit Check project, and the way in which we are implementing the initial heuristic (T329988#8654867), assumes that volunteers will be able to configure and iterate upon its underlying logic over time (T327959). This task involves the work of identifying what technical approaches are available for offering volunteers (on a per-project basis) the configurability this project depends on. === 🚧 Configurability Requirements 🚧 // Once complete, this section will contain the types/level of configurability any technical approach will need to offer volunteers.// - Define who Edit Check is made available for based on the following parameters -- Account age -- Account type (logged in/out) -- Edit count - Determine what Edit Checks are enabled for what account types -- //Note: this assumes a future where multiple checks exist.// - Add/edit/remove the rules that determine when a particular Edit Check is initiated - Customize facts of the Edit Check user experience including: -- The language that appears within the UI Edit Check will present to people -- Where/how references are automatically inserted within articles -- What happens when people //decline// to add a reference when prompted. //See T329593 for more.// - Determine what namespace(s) a given Edit Check is available/activated within -- // See more in T324730#8661854 and T324730#8662603.// - Meta: All "business logic" will need to be stored in ways such that changes that are made on-wiki are //automatically// synchronized with the code Edit Check "runs" on -- //For more context here see [Meeting/Platform + Editing: 1 March 2023 meeting notes](https://docs.google.com/document/d/1Rh5utQWXkI0o6HAWPpXJRA-Auz8s6B4P07eWfX2-Vf0/edit#)// === Technical Approaches **Approach #1**: Use Community Configurations (via Growth Team): T323811 **Approach #2: TBD** **Approach #3: TBD** === Done - [ ] The "Technical Approaches" section is populated with the technical approaches that //could// meet the "Configurability Requirements" and the tradeoffs the Editing Team will need to consider when deciding which to move forward with. //This decision will be made in T330112.//

The Edit Check project, and the way in which we are implementing the initial heuristic (T329988#8654867), assumes that volunteers will be able to configure and iterate upon its underlying logic over time (T327959). This task involves the work of identifying what technical approaches are available for offering volunteers (on a per-project basis) the configurability this project depends on. === 🚧 Configurability Requirements 🚧 // Once complete, this section will contain the types/level of configurability any technical approach will need to offer volunteers.// - Define who Edit Check is made available for based on the following parameters -- Account age -- Account type (logged in/out) -- Edit count - Determine what Edit Checks are enabled for what account types -- //Note: this assumes a future where multiple checks exist.// - Add/edit/remove the rules that determine when a particular Edit Check is initiated - Customize facts of the Edit Check user experience including: -- The language that appears within the UI Edit Check will present to people -- Where/how references are automatically inserted within articles -- What happens when people //decline// to add a reference when prompted. //See T329593 for more.// - Determine what namespace(s) a given Edit Check is available/activated within -- // See more in T324730#8661854 and T324730#8662603.// - Meta: All "business logic" will need to be stored in ways such that changes that are made on-wiki are //automatically// synchronized with the code Edit Check "runs" on -- //For more context here see [Meeting/Platform + Editing: 1 March 2023 meeting notes](https://docs.google.com/document/d/1Rh5utQWXkI0o6HAWPpXJRA-Auz8s6B4P07eWfX2-Vf0/edit#)// === Technical Approaches **Approach #1**: Use Community Configurations (via Growth Team): T323811 **Approach #2:** Use the [MediaWiki namespace](https://en.wikipedia.org/wiki/Help:MediaWiki_namespace) - E.g. [en:MediaWiki:Citoid-template-type-map.json](https://en.wikipedia.org/wiki/MediaWiki:Citoid-template-type-map.json) **Approach #3: TBD** === Done - [ ] The "Technical Approaches" section is populated with the technical approaches that //could// meet the "Configurability Requirements" and the tradeoffs the Editing Team will need to consider when deciding which to move forward with. //This decision will be made in T330112.//

The Edit Check project, and the way in which we are implementing the initial heuristic (T329988#8654867), assumes that volunteers will be able to configure and iterate upon its underlying logic over time (T327959). This task involves the work of identifying what technical approaches are available for offering volunteers (on a per-project basis) the configurability this project depends on. === 🚧 Configurability Requirements 🚧 // Once complete, this section will contain the types/level of configurability any technical approach will need to offer volunteers.// - Define who Edit Check is made available for based on the following parameters -- Account age -- Account type (logged in/out) -- Edit count - Determine what Edit Checks are enabled for what account types -- //Note: this assumes a future where multiple checks exist.// - Add/edit/remove the rules that determine when a particular Edit Check is initiated - Customize facts of the Edit Check user experience including: -- The language that appears within the UI Edit Check will present to people -- Where/how references are automatically inserted within articles -- What happens when people //decline// to add a reference when prompted. //See T329593 for more.// - Determine what namespace(s) a given Edit Check is available/activated within -- // See more in T324730#8661854 and T324730#8662603.// - Meta: All "business logic" will need to be stored in ways such that changes that are made on-wiki are //automatically// synchronized with the code Edit Check "runs" on -- //For more context here see [Meeting/Platform + Editing: 1 March 2023 meeting notes](https://docs.google.com/document/d/1Rh5utQWXkI0o6HAWPpXJRA-Auz8s6B4P07eWfX2-Vf0/edit#)// === Technical Approaches **Approach #1**: Use Community Configurations (via Growth Team): T323811 **Approach #2: TBD**** Use the [MediaWiki namespace](https://en.wikipedia.org/wiki/Help:MediaWiki_namespace) - E.g. [en:MediaWiki:Citoid-template-type-map.json](https://en.wikipedia.org/wiki/MediaWiki:Citoid-template-type-map.json) **Approach #3: TBD** === Done - [ ] The "Technical Approaches" section is populated with the technical approaches that //could// meet the "Configurability Requirements" and the tradeoffs the Editing Team will need to consider when deciding which to move forward with. //This decision will be made in T330112.//