Fri, Feb 21
@Isaac thanks! I'll email Diego now and will cc you.
Tue, Feb 18
Fri, Feb 14
@Isaac thank you. I reviewed and left some comments. Please run it by the team and ask that they get back to you in 1-2 days with feedback. I think this is almost ready to be sent to Diego Q on Tuesday/Wednesday. Thanks!
Wed, Feb 12
@bmansurov my understanding is that we can close this. resolving.
@Miriam all clear. thanks.
@Isaac I talked to Diego Q and he's ready to help. Can you prepare a doc that contains the information that we want the skeleton of any tool page (be it gapfinder or wiki-topic) to have? You can assume that the header and footer of the page are places where we want to have fixed type of content and what goes in between those parts is flexible from tool to tool. Ping me once you have it and I'm happy to do a pass and make changes. If we can send this out to Diego no later than early next week, that'd be great. (I asked him to start from the tools pages and then move to meta.)
@bmansurov please reach out to Bob West and get the latest code changes from him. Once the code is updated on our end, we should do the DNS switch as soon as BBlack and colleagues can.
Tue, Feb 11
@JAllemandou thanks for checking. I'll resolve the task then. (I don't know if the pipe is causing this flip in text.)
@Capt_Swing I have some updates on my end. I talked with our designer today and he's available to help. I told him that by the end of March we want the designs to be out on the meta pages which means he needs to leave time for any coding to be done on our end.
Mon, Feb 10
Approved. (hiring manager)
@MGerlach thanks. Please get in touch with Jaime Anstee; I learned recently that she's working on an index for knowledge equity and it's good to know how much of the knowledge gaps are part of her thinking and also if there's anything we can reuse from their work.
@Isaac thanks for the update. Given that we want to use this task to build a template for services we put in toolforge, please keep the task open until we finalize and update the design. I ping Diego Q. now with the request.
@Miriam can you explain briefly what the challenge with the categories is?
@Capt_Swing and @DED: thanks. As discussed in a meeting with Capt_Swing recently, please put the focus on finalizing all speakers for FY20 by the end of February. Please give the team one week to get back to you with time slots they want to use during the coming 4 showcases (March-June) and fill the rest. I have a couple of suggestions for inviting folks in your shared doc. Ping me if you want me to invite any of those folks.
Tue, Feb 4
@Miriam I just shared the link to where the data lives with you.
Mon, Feb 3
All clear and makes sense to me. thanks!
Jan 22 2020
@Isaac please go ahead with your recommended changes. Please reach out to Deb Zierten and keep me in cc. Please mention that these are short-term proposals and I'm still to reach out to her for the longer term changes.
Jan 21 2020
On my end: I received 3 requests from diego and submitted them as requests to the CTO. waiting to hear back.
thanks for the update. see below.
@Capt_Swing one update on my end is that I talked with the designer. They're on vacation until 2020-01-28 and will get back to us then.
Jan 14 2020
@JFishback_WMF thank you very much for your thorough analysis.
Jan 10 2020
Jan 9 2020
@bmansurov you can use this task for tracking and implementing the change for bringing the hosting of wikiworkshop.org to github.
Jan 8 2020
@ArielGlenn thanks for engaging on this ticket further. From the current conversation, it doesn't look to me as we can have a solution for having HTML dumps on a regular basis. I understand the capacity limitations on this front. I'll leave this task open for a future where we may be able to tackle it.
@Michele.tizzoni congratulations. That's a great news! :)
Jan 7 2020
Let's go with the existing model and only report items that we're an author of. Let's wait for Capt_Swing's input for a day and if he doesn't disagree, let's decline this task.
Jan 6 2020
@jcrespo thanks for working on this while most of us were away! :)
Dec 19 2019
Excellent. this task is ready on my end to be picked up by SRE-Access-Request. I remove myself as assignee.
@Aklapper is shell account name the same as shell username? If yes, it's in the task description. Also, yeah: this task is for sre-access-requests. I didn't add them earlier as we're still waiting for Aroraakhil to provide the public ssh key and for ottomata to confirm the group.
@Aroraakhil thanks. I updated the task description for this task to bring it closer to the template you linked to. Let's not open a new task. (We will add SRE-access-requests once all the pieces are prepared for them to take action.) Please click on Edit task on this page and fill out what's missing. :)
@Ottomata we have a new formal collaborator onboard: Akhil Arora. \o/ Akhil needs access to HDFS and stat machines. Can you check the "Access Group" in the task description and update it if I didn't get it right, please?
Dec 18 2019
Dec 16 2019
@ovasileva shall we decline this task per https://meta.wikimedia.org/wiki/Research:Surveys_on_the_gender_of_editors/Report#Recommendations ?
All: I will resolve this task as providing stats across many projects should ideally follow the recommendations in https://meta.wikimedia.org/wiki/Research:Surveys_on_the_gender_of_editors/Report#Recommendations .
@jcrespo makes sense. I'll schedule a meeting for after the holidays. :) (btw, I'm not sure when I can resolve this task. Please go ahead and do it if it's considered done from your perspective.)
Great. Thanks! :)
@MGerlach Thanks. Please also post to wikimedia-l and https://discuss-space.wmflabs.org/c/events/l/calendar .
Dec 12 2019
Dec 11 2019
@Miriam what Isaac said. thanks! :)
Dec 10 2019
@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.
Dec 9 2019
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.