Change Details

Tickets like T322815 and T322816 involve the work with converging on the high level Edit Check user experience. //Where "high level" in this context refers to deciding things like how and when people will be made aware when they have not yet accompanied the content they are in the midst of adding with a source.// This task will lead us a layer deeper to define things like: 1. //What are the key moments at which people ought to be presented with a choice? E.g. when they are finished adding a new sentence, paragraph, or section, etc.// 2. //What choices are people presented with when an Edit Check is triggered?// 4. //What happens after people make a choice that we decide on exposing as a result of answering "2." ?// -- //Note: "happen" here refers to what happens in terms of both what the people who are in the midst of an edit see as well as what could on the backend (e.g. what metadata is associated with an edit based on a choice someone makes).// 4. //What happens in cases where people dismiss a choice/decline to engage with it?// 5. //Of the decision moments we identify, which will volunteers be able to configure on a per-project basis? What constraints ought to inform how volunteers can configure these moments?// === Stories - **As a member of the Editing Team** who is responsible for implementing the initial reference Edit Check, I need to see a "birds eye" view of the entire experience, so that I can evaluate the extent to which I think the experience will be successful in providing newcomers and Junior Contributors from Sub-Saharan Africa the feedback and tools necessary for them to feel empowered, equipped, and welcomed to make edits they are proud of and the volunteers who will be reviewing them value. - **As a Senior Contributor** who is knowledgable about the establishing processes and policies at a given project, I need to be able to audit the entirety of the Edit Check experience so that I can evaluate the extent to which I think Edit Check will guide newcomers and Junior Contributors from Sub-Saharan Africa to take actions that are valuable to the projects they are motivated to contribute to. === Requirements 🚧 @nayoub and @ppelberg need to finalize the below 🚧 - Create a flow chart/diagram that illustrates the following in sequence: -- **Decision moments:** the moments at which Edit Check will present people with a choice to make -- **Choices:** the range of actions people can take in response to a Decision Moment -- **Consequences**: the range of things that //could// happen as a result of someone making a particular choice --- //Note: I'm using "range" here to allude to the assumption that there will be particular "Consequences" that volunteers will be empowered to define, on a per-project basis.//

Tickets like T322815 and T322816 involve the work with converging on the high level Edit Check user experience. //Where "high level" in this context refers to deciding things like how and when people will be made aware when they have not yet accompanied the content they are in the midst of adding with a source.// This task will lead us a layer deeper to define things like: 1. //What are the key moments at which people ought to be presented with a choice? E.g. when they are finished adding a new sentence, paragraph, or section, etc.// 2. //What choices are people presented with when an Edit Check is triggered?// 4. //What happens after people make a choice that we decide on exposing as a result of answering "2." ?// -- //Note: "happen" here refers to what happens in terms of both what the people who are in the midst of an edit see as well as what could on the backend (e.g. what metadata is associated with an edit based on a choice someone makes).// 4. //What happens in cases where people dismiss a choice/decline to engage with it?// 5. //Of the decision moments we identify, which will volunteers be able to configure on a per-project basis? What constraints ought to inform how volunteers can configure these moments?// === Stories - **As a member of the Editing Team** who is responsible for implementing the initial reference Edit Check, I need to see a "birds eye" view of the entire experience, so that I can evaluate the extent to which I think the experience will be successful in providing newcomers and Junior Contributors from Sub-Saharan Africa the feedback and tools necessary for them to feel empowered, equipped, and welcomed to make edits they are proud of and the volunteers who will be reviewing them value. - **As a Senior Contributor** who is knowledgable about the establishing processes and policies at a given project, I need to be able to audit the entirety of the Edit Check experience so that I can evaluate the extent to which I think Edit Check will guide newcomers and Junior Contributors from Sub-Saharan Africa to take actions that are valuable to the projects they are motivated to contribute to. === Mockups/Storyboard [Figma: Editing/Edit Check](https://www.figma.com/file/t1MMZZiDjkqZMJwkjhyJNB/Editing%2FEdit-Check?node-id=230%3A6533&t=UDFGI23lX3bDTnqJ-0) (limited access for now) === Requirements 🚧 @nayoub and @ppelberg need to finalize the below 🚧 - Create a flow chart/diagram that illustrates the following in sequence: -- **Decision moments:** the moments at which Edit Check will present people with a choice to make -- **Choices:** the range of actions people can take in response to a Decision Moment -- **Consequences**: the range of things that //could// happen as a result of someone making a particular choice --- //Note: I'm using "range" here to allude to the assumption that there will be particular "Consequences" that volunteers will be empowered to define, on a per-project basis.//

Tickets like T322815 and T322816 involve the work with converging on the high level Edit Check user experience. //Where "high level" in this context refers to deciding things like how and when people will be made aware when they have not yet accompanied the content they are in the midst of adding with a source.// This task will lead us a layer deeper to define things like: 1. //What are the key moments at which people ought to be presented with a choice? E.g. when they are finished adding a new sentence, paragraph, or section, etc.// 2. //What choices are people presented with when an Edit Check is triggered?// 4. //What happens after people make a choice that we decide on exposing as a result of answering "2." ?// -- //Note: "happen" here refers to what happens in terms of both what the people who are in the midst of an edit see as well as what could on the backend (e.g. what metadata is associated with an edit based on a choice someone makes).// 4. //What happens in cases where people dismiss a choice/decline to engage with it?// 5. //Of the decision moments we identify, which will volunteers be able to configure on a per-project basis? What constraints ought to inform how volunteers can configure these moments?// === Stories - **As a member of the Editing Team** who is responsible for implementing the initial reference Edit Check, I need to see a "birds eye" view of the entire experience, so that I can evaluate the extent to which I think the experience will be successful in providing newcomers and Junior Contributors from Sub-Saharan Africa the feedback and tools necessary for them to feel empowered, equipped, and welcomed to make edits they are proud of and the volunteers who will be reviewing them value. - **As a Senior Contributor** who is knowledgable about the establishing processes and policies at a given project, I need to be able to audit the entirety of the Edit Check experience so that I can evaluate the extent to which I think Edit Check will guide newcomers and Junior Contributors from Sub-Saharan Africa to take actions that are valuable to the projects they are motivated to contribute to. === Mockups/Storyboard [Figma: Editing/Edit Check](https://www.figma.com/file/t1MMZZiDjkqZMJwkjhyJNB/Editing%2FEdit-Check?node-id=230%3A6533&t=UDFGI23lX3bDTnqJ-0) (limited access for now) === Requirements 🚧 @nayoub and @ppelberg need to finalize the below 🚧 - Create a flow chart/diagram that illustrates the following in sequence: -- **Decision moments:** the moments at which Edit Check will present people with a choice to make -- **Choices:** the range of actions people can take in response to a Decision Moment -- **Consequences**: the range of things that //could// happen as a result of someone making a particular choice --- //Note: I'm using "range" here to allude to the assumption that there will be particular "Consequences" that volunteers will be empowered to define, on a per-project basis.//