@Miriam actually, if I may put a slight pressure: Given that Research Report will go out next week and we will link to research.wikimedia.org , let's make sure we have that info updated on the website.
@Pginer-WMF this is very helpful. Let me talk with a couple of folks in the team and get back to you.
Mon, Dec 9
Diego is moving out of this space. I moved the task to research-backlog. We should come back to it once we know how to staff it.
We've had multiple attempts at this and it's not possible to move forward on this front without availability of engineering, design, and UX resources. The experiments envisioned all require changes in workflows and UIs for experimentation purposes, the kind of resources Research is neither staffed with or has access to.
All: what is left to be done on this task? (I'm for now removing Research and will add back if we define goals for the next 3 months.)
currently stalled as the track may keep the previous year's dataset.
@Aklapper I'll move this to research-backlog, thanks for assigning it to yourself. :)
all: I have removed Research. I will remain on this task in case my help is needed anywhere.
a long time has passed since this research is published and we don't have the blog option at the moment.
@Miriam I have temporarily assigned this task to you so we know on our end who owns the task. Please feel free to reassign to the right person and/or take any other steps needed.
@MarcoAurelio can you confirm if this is already done and we can resolve this task?
This continues to be stalled as the position is not restored.
given that we're not hiring at the moment, I declined the task.
This is now on hold due to the wait that is needed for the System of Performance recommendations to conclude.
We're for now not sending out blog posts until there is more information about the Technology blog (as wikimediafoundation blog won't be an option). The focus of the writing in the next 3 months will be on the paper.
@Pginer-WMF is the task description updated? I'd like to do a pass over this task and see what we can potentially pick up starting January 2020.
Folks, I removed Research. Happy to help if our help is needed at some point.
Moving this to research-backlog. @Amire80 it would be helpful to have an update from you about the status of this task. Is this something you're still interested in? Has anything changed since we last visited it on your end?
I reassigned the task to DED. We're still working with srijan on this. The reassignment makes it clearer on our end who we can poke for status updates.
This is now done. There are a few touch-points with folks in Product that were involved in the first and second onboarding project that MGerlach worked on and those are not required steps for closing this task.
I have done many iterations of this in solo, in collaboration with other Technolog managers and the managers from the rest of the org.
Thu, Dec 5
Wed, Dec 4
Tue, Dec 3
@tizianopiccardi thanks for the update and great to see that you're there. :) Please make sure you advertise for it on wiki-research-l when the right time arrives.
Wed, Nov 27
Fri, Nov 22
@MGerlach Jon Katz mentioned that he will read the report and he will get back to you with any feedback he has on the Discussion page of the report or via email. I asked him to report any item missing in the analysis that is key for understanding the reader-->create account transition. He may have other questions outside of this realm that can be added to Future Directions in the page. Let's plan to resolve this task in a week unless major feedback comes in via Jon.
Thu, Nov 21
fantastic! Let's finalize it today in our 1:1. :)
Wed, Nov 20
I started the documentation at https://docs.google.com/document/d/1DjXlkO-x4K2YG1-J0VVKUkUtGwOuxvx5ixsAq3sLFa8/edit#
This discussion happened during FY20 Research offsite. The current state of documentation is captured in https://office.wikimedia.org/wiki/Research/Documentation and we're working on the future state of documentation in Research which will conclude by 2019-12-30.
This work is now concluded.
@Nuria do you expect this task to be addressed by the better bot detection approach you're implementing? If yes, I'd like to close it.
@Miriam should we prioritize this bug to be fixed?