User Details
- User Since
- Feb 8 2019, 4:51 AM (43 w, 2 d)
- Availability
- Available
- IRC Nick
- ppelberg
- LDAP User
- Unknown
- MediaWiki User
- PPelberg (WMF) [ Global Accounts ]
Yesterday
Fri, Dec 6
Task description update*
- ADDING: "...know my comment was posted successfully." to the "User stories" section. We have discussed and planned for this [1]. Although, I am just now realizing it was not documented explicitly in the "User stories" section.
Task description update
- ADDED: link to the on-wiki conversation where we are asking for community members' feedback.
Updating the task description to include a link where this questions [1] is being discussed: Topic:Vcehgf0nr8rpi26a
Thu, Dec 5
Wed, Dec 4
Update: 4-Dec
- We are working to define how much of the previewing workflow we can design by EOD Friday, 6-Dec. Having minimal designs by this Friday should leave us enough time to have them implemented and live on the on the prototyper server by EOD Friday, 13-Dec, the time we're targeting for the initial round of usertesting.com testing to begin.
- In discussing the above this morning, we arrived at the following ranked open questions, which are now documented in the task description:
- 1. Where is the live preview shown in relationship to the text input area? Above it? Below it? Somewhere else?
- 2. How should the live preview be styled?
- 3. What should be shown within the preview window as the preview is being populated?
- 4. When should the preview window become visible to the user?
- 5. Should there be a "fallback" experience on slow connections? What should this experience look like?
- 6. Should contributors be able to hide and/or disable live previews?
Tue, Dec 3
Updating the "User stories" section of the task description to include the following:
- "Easily understand when content within a discussion was posted"
Wed, Nov 27
27-November update
- A first draft of the "Goal," "Hypotheses" and "Research questions" now exist in this Google Doc: OWC/Measurement Plan/Replying
Tue, Nov 26
Task description update
- Updating the task description to make it more explicit that it is important to monitor the activity of contributors, across experience levels, as part of this work.
These updates have been posted. See diff: https://www.mediawiki.org/w/index.php?title=Talk_pages_project%2FUpdates&type=revision&diff=3423932&oldid=3421663
Thanks for clarifying, @Neil_P._Quinn_WMF. Let's move our discussion for what metrics we might monitor to approximate "unproductive" behavior to this ticket: T239231
Mon, Nov 25
I think the way User:Thnidu articulates why they value previews is helpful: "...a large part of their value for me is spotting errors of execution as well as errors of intention." See: this thread
Sat, Nov 23
+1 @Neil_P._Quinn_WMF, thank you for your comment, @Alsee.
Tue, Nov 19
Updating task description
Update to task description
- Marking T236338 as resolved. See: T236338#5668607
Mon, Nov 18
Sat, Nov 16
As @matmarex noted in T235592#5646728, the "simultaneous approach" could be helpful in communicating to contributors they don't need to manually indent/outdent their replies or sign their comments.
Fri, Nov 15
Task description update
- Removing "⚠️" considering we now have a shortlist of target wikis we are preparing to approach.
Thu, Nov 14
Resolving this task as this analysis is what we needed for the, "Product October 2019 Quarter-in-Review" meeting – thank you, Megan.
Talked with @ovasileva. We agreed this is not a priority for either of our teams. We'll keep both the Editing and Web team tags on the task in case either team wants to pick it up at some point in the future.
Task description update:
- Clarifying definition of retention to include explicit mention of "cool down" period. This change has also been made to the Talk pages project/Glossary.
Wed, Nov 13
As we talked about during today's meeting, we are seeking more information about what use cases would benefit from the "simultaneous approach." [1]
We started testing today, with plans to finish on Thursday.
Tue, Nov 12
One potential explanation for the drop in edit completion rate among unregistered users, that begins in late June-2019 and accelerates on ~4-July-2019, is the start of the A/B test testing the VisualEditor as the default editor on mobile [1].