@Esanders OK. How many months until it goes to production? I realize that an exact number is impossible to know, but an estimate would be helpful.

Brendan's previous explanation was about audio echoes. My question from my previous post is about dropped audio.

Thanks. I've asked about the timeline in that other task.

I'm wondering for the timeline of the rollout for this project. Is this 2 to 3 years away from going live, or are we likely to see changes to the wikitext editor within the next 6-12 months on production sites?

I'm closing this as resolved, but I'm a bit reluctant because I still suspect that Hangouts is at fault for some problems. @bcampbell aside from the echo issue, what about the dropped audio issue? I notice that even in one-on-one meetings, Hangouts has a tendency to have problems like dropping audio, and this seems to be even more of a problem when in many-to-many meetings.

I feel that Google Hangouts is too buggy, so yes, there is a reason to investigate a replacement for it. It is possible that WMF could retain BlueJeans for internal use and replace public meetings with some other tool, whether that is BlueJeans, Zoom, or some other competitor.

This could potentially be a big deal for my video series. Is this planned to get done anytime in the next 12 months, or is this years away from being implemented?

@Aklapper: I mostly have WMF Office IT in mind for this task, but it may be of interest to affiliates as well. The US Wikimedians are now using Zoom for our monthly meetings, and I am finding it to be more reliable than Hangouts. I believe that WMF has tested BlueJeans but I don't know what the outcomes of that testing were. I would also encourage WMF Office IT to test Zoom. I believe that the best person to be the task owner might be @bcampbell.

Thanks for diagnosing this issue Matt. It's counterintuitive to me that people wouldn't get notifications for messages on their talk page, especially since the community seems to feel so strongly about having the OBOD to notify about talk page messages. I would suggest that buy default people should be notified for all edits to their talk pages, especially keeping in mind that some users make errors in saying that an edit is minor when it's not. Giving the user the option to disable notifications for minor edits makes sense to me, but by default I think that editors should be notified of all edits on their talk pages.

Note that I did receive an email about a change on my ENWP talk page so perhaps the problem is specific to Meta. I have checked my Meta settings and verified that email notifications are enabled for talk page messages.

Floor no longer works at WMF and Jan-Bart is no longer on the Board. :) Perhaps tflanagan will consider appointing some new list admins at some point.

Please note that this bug is a big deal for my IEG video project, and I imagine that it affects Fundraising and others who use video subtitles as well. I would like to triage this as high priority if that's OK.

I would appreciate an improvement to the calendar situation, not just for tech events but also for finance, fundraising, community, and everything else. I haven't looked into Cargo or SMW calendars in any detail, but I'd like to see *some* kind of progress on an open source calendar that can be used widely including outside of WMF by affiliates. Thanks!

@Egedda have you uploaded the Project Planning Document to Commons yet?

I see that @brion authored https://phabricator.wikimedia.org/rETMH9f808c924577f075624e1fd582b44d4b5b92d388, but I was not prompted to install a WebM plugin in either Edge or IE.

In T120497#1995233, @Egedda wrote:

In T120497#1994930, @Pine wrote:

Per discussion on the Analytics mailing list, would it be possible for the students to publish their Project Planning Document on Commons under a CC-BY or CC-BY-SA license?

We would be glad to release our Project Planning Document under CC BY-SA, but since it is a part of our grade, we need to check with our course supervisor first. Most likely, he will have no problem with it, we just have to make sure.
Fun seeing so much interest in our doings!

In T120497#1995046, @JEumerus wrote:

If it's text, might Wikisource work as well? According to https://commons.wikimedia.org/wiki/Commons:Project_scope, text should be used in Commons only if it's in form of text files that are of use to other Wikimedia Projects.

The document is a more or less our analysis of the project, risks, our project plan and stuff, a pdf consisting mostly of text but a couple of images.
Commons seems like the better choice to me.

Per discussion on the Analytics mailing list, would it be possible for the students to publish their Project Planning Document on Commons under a CC-BY or CC-BY-SA license?

Thank you!

Is there an incident report for this that we can see, or a link to the place where it will be posted when it's published?

@Dzahn @RobH thank you.

Commons is down again for me.

Update: Commons is working now, but not Meta.

@Mike_Peel agreed.

I think he was able to get the video to play on the Commons page. There haven't been other reports of users experiencing problems with Firefox on Windows 10 as far as I know, so I'll mark this Phabricator task as closed-invalid for now. Anyone can reopen if we get other reports of similar problems.

Thanks! Can you also add something about the issue that the upload tool should only load small chunks of files at a time into the browser's memory so that a 20GB upload doesn't result in the browser attempting to load all 20GB into RAM and/or pagefile at once?

We're having this same problem on the Cascadia mailing list.

Thanks for working on this. I'm going to remove myself from the cc list but I'm glad to know that this is happening.

Ok, since the default is the Wikipedia-like "anyone can edit", I'll update that setting momentarily.

Project membership wasn't restricted at the time; what was restricted was editing the project details.

@Dzahn Joady has informed me that HR is currently using Asana exclusively, so I am locking down the Phabricator HR project as best as possible while keeping the information that's currently there intact.

Joady has informed me that HR is currently using Asana exclusively, so I'm in the process of locking down the Human-Resources project as best as possible while keeping intact the information that's currently there.

@Dzahn I've added that task to HR at your request. Even with the project description locked, anyone can add tasks to the project.

@Dzahn: Human-resources added at your request.

@Qgil no, please see discussion above. I didn't create the HR project. However, I did lock down the one that existed at Gayle's request. Since Gayle is no longer with us and I'm just mainly guarding that project to prevent misuse, I'm happy to re-open it if there's a request from HR. It sounds like you think this is a good idea, so I'll run this by Joady.

This is already done on other projects; I believe that Learning and Evaluation and the Community Liaisons also have some projects set up this way. If you'd like to have a broader discussion about when restricting project editing to certain users should or shouldn't be allowed, I suggest opening up a new task for that, and/or discussing with Quim and/or Terry.

@Aklapper yes, Gayle requested that I restrict that project. My understanding is that WMF rarely uses that project, and that HR does almost all of its work privately, probably in Asana which Finance also uses (and I think that Community Resources uses as well). So, essentially, that project is mostly a placeholder in case HR eventually moves at least some of its work to Phabricator. Interestingly, it seems that WMF's technical security people do use Phabricator for their private work, so perhaps HR, CR and Finance will move to Phabricator eventually, perhaps with some public and some private work in separate projects.

Nothing yet. I'm in discussions with Victor Grigas. I'm juggling a lot of balls, not sure when I will have more to share about the VE-specific script. In the longer term, I am drafting an IEG proposal here for a more comprehensive video, and would welcome comments and suggestions on the talk page: https://meta.wikimedia.org/wiki/Grants:IEG/Motivational_and_educational_video_to_introduce_Wikimedia

Note that VE training video, mostly aimed at new editors, is in development.

Please do keep this good idea updated. I may integrate this into my VE training video, or remove some planned content from the script if it will be covered by the tour.

Great, I may borrow these for my long-promised VisualEditor tutorial video. What screen capture software did you use to make these?

More info:

I'm guessing that this should also be in the Security project so I'll boldly add it.

An incremental approach that is specific to the tech community might make sense. Gerrit sounds like a good next step.

In T90534#1180253, @yuvipanda wrote:

@Pine @scfc since this seems to be a common enough confusion, I've created a page at https://wikitech.wikimedia.org/wiki/Labs_labs_labs with some rudimentary information about what different people call 'labs'. Edits welcome.

As for wikimetrics, it runs on *Labs*, and is unrelated to *Tool Labs*.

@Nemo_bis People can discuss policy modifications wherever they like. However, I would agree that any actual RfCs that may emerge from this discussion should be held on-wiki.

My intention was to ask for confirmation. I was not making an accusation.

@yuvipanda I was told by a Wikimetrics user that the reliability of Wikimetrics depends on Labs, so you may want to check with someone in Wikimetrics to verify whether or not there are any Wikimetrics dependencies on Labs and/or Tool Labs.

Relevant suggestions from the Inspire campaign. Pinging @Siko to see if she wants to comment here or try to integrate these Inspire ideas with a broader friendly space policy and the related tasks noted in Phabricator.

There seems to be some interest in this subject on the Gender Gap mailing list.

I have found additional templates missing from articles when viewed on Mobile Web, some of which are more significant than others. It appears that a decision was made to remove many, perhaps all, templates from being displayed inline. This should be reconsidered, since important content is being hidden from users on mobile web.

Is there a commitment to having Citoid running in production in Q3?