Commenting on behalf of the staff working on Wikimania to note that we'd like to move wikimania-info@ (noted above) and wikimania@ (which both currently direct to the same queue) to ITS in order to simplify workflows. I was originally planning to open a new task, but now having seen this one I'm thinking that might be duplicative.

Thank you so much @MatthewVernon!

Accidentally duplicated task. Closing. See T295835

I had suppressed the mailing lists from showing up in the digest but missed Education. That list is now also suppressed. Frequency of digests is default once per week, but maybe we should set it to less frequent.

Thanks @Aklapper. I removed the Space tag and added Comms, since that will presumably be the new home for this project.

This is still an important process that we expect our team to own. It is currently stalled due to the closing of Wikimedia Space (https://discuss-space.wmflabs.org/t/next-steps-on-wikimedia-space/3184), but will be restarted in another location in the future.

Declining this task per the Space announcement - https://discuss-space.wmflabs.org/t/next-steps-on-wikimedia-space/3184

Declining this task per the Space announcement - https://discuss-space.wmflabs.org/t/next-steps-on-wikimedia-space/3184

Declining this task per the Space announcement - https://discuss-space.wmflabs.org/t/next-steps-on-wikimedia-space/3184

Declining this task per the Space announcement - https://discuss-space.wmflabs.org/t/next-steps-on-wikimedia-space/3184

Declining this task per the Space announcement - https://discuss-space.wmflabs.org/t/next-steps-on-wikimedia-space/3184

Declining this task because of the Space announcement - https://discuss-space.wmflabs.org/t/next-steps-on-wikimedia-space/3184

Declining this task because of the Space announcement - https://discuss-space.wmflabs.org/t/next-steps-on-wikimedia-space/3184

Declining this task because of the Space announcement - https://discuss-space.wmflabs.org/t/next-steps-on-wikimedia-space/3184

Declining this task because of the Space announcement - https://discuss-space.wmflabs.org/t/next-steps-on-wikimedia-space/3184

Declining this task because of the Space announcement - https://discuss-space.wmflabs.org/t/next-steps-on-wikimedia-space/3184

Declining this task because of the Space announcement - https://discuss-space.wmflabs.org/t/next-steps-on-wikimedia-space/3184

The plugin was just released https://meta.discourse.org/t/multilingual-plugin/142740

To further articulate on the task description, users should be able to easily see events that are nearby and configure notifications based on that filter, to be notified whenever an event is posted within their specified range of geographical distance.

Ideally, the person inviting would be able to specify if the invite should set to "watching" any tags or categories for the invitee.

This bug was reported to the Events plugin developers and has been fixed per https://thepavilion.io/t/inconsistent-display-of-date-in-latest-feed/2002/9.

Considerations for flexibility of this feature, from a conversation on Space (https://discuss-space.wmflabs.org/t/can-the-software-remember-locations-for-recurring-events/2543/2):

Given any extra hours from the developer after the first round of multilingual features are deployed, this has priority.

@Samat, this should be fixed now. I've just tested from an admin and a test account. I created an event with a location, saved it, hit the Edit button below the post, and selected the location for editing. All previously entered fields appeared (rather than just the "Name optional" one). Give it a try and confirm! (For reference, here is your original report: https://discuss-space.wmflabs.org/t/edit-the-location-of-an-event/958/3).

Sure, go for it. We should have the first round of multilingual features for users to test this week, next week latest. Maybe the part 2 blog post could go up announcing the roll out of these features and talking about blog translations as a next step? I can write out the paragraph about the features for testing. Would that work?

Just invited you to a topic to verify.

Email appears to be working fine after the recent Discourse upgrade. I have removed -- %{site_description} from all three texts.

Given that there is already a place on-wiki to ask questions to the Foundation (https://meta.wikimedia.org/wiki/Ask_a_question), our intention is to update this page and integrate it into the process we establish.

We are starting work on this process this quarter and are aiming to have it up and running in the next few months.

Removing the VPS-Projects tag as we're going to look into the privacy element of this before doing more investigation on what's causing the issue from a technical standpoint.

Videos from other third party sites (Facebook and Vimeo, for example) embed a video player just fine. YouTube appears to be the blacklisted exception.

Confirmed that the links do appear in Discourse Meta "invite to topic" emails, although the formatting is still not great.

Based on feedback here and in the topic itself, we will be keeping development as simple as possible. We will commission work that:

• integrates the three options from MediaWiki into Space user profiles
• identifies strings that may be gendered in different languages
• provides a system for localizing those strings to make them responsive, across languages, to the pronoun selection

pinging @hdothiduc on this for thoughts before reporting upstream.

Thanks @Bawolff, the policy in the footer for Discourse MediaWiki is now updated.

We have started development on these features. We have organized the range of features into two types of improvements: multilingual discovery improvements and multilingual locale improvements.

To address the choice in privacy policy specifically: both https://discuss-space.wmflabs.org/privacy and https://discourse-mediawiki.wmflabs.org/privacy link directly to the Wikimedia Foundation Non-wiki privacy policy (https://wikimediafoundation.org/privacy-policy/). Legal reached out to us during the launch of Space and advised that the privacy policy link there. No task was created as the change was implemented immediately. After double checking with Legal about Discourse MediaWiki, the change was also made there, resolving a task that had been written prior to Space.

@Aklapper Apologies, I didn't respond earlier because the users were already voicing similar ideas in the topic. This is really not set in stone at all and we want something that will feel empowering and comfortable to people, that will also allow us to make sure Space is growing as an inclusive and diverse platform. I've explained more in the topic. Would be great to have your feedback there directly!

Quim has reminded me that, indeed, there are cases where Discourse does point out the gender of a user (particularly when the UI is not in English): https://meta.discourse.org/t/gender-and-translations/73728. This is also a UI issue that we will likely tackle at some point, but want to start a measure like this to bring more attention to diversity.

Discourse doesn't refer to users with pronouns, so the issue for us is more about awareness and visibility. We'd like to be able to promote gender diversity on Wikimedia Space, and have a range of options that people will feel comfortable with in self-identifying. It's just a different use case.

As far as I know, this is not exactly the avenue we're pursuing for outreach at this point. I'd advocate for closing this task and opening a new one about creating a client list, and then maybe another one about outreach to those people in particular. What do you think @Qgil?

Possibility of a drop-down menu, eliminating "I prefer not to say" as the field will be optional anyway. Additional space to specify different identity, when selected.