Are there other channels that you would prefer to use in addition to or instead of this forum for Movement Strategy updates and feedback? Why?

The first post contains a summary of the discussion so far. The top post is editable, and anyone can contribute to improving it. We will try to update it on a weekly basis in conjunction with the community review weekly reports.

1 Like

Please consider to retire Telegram support for general 2030 Wikimedia Strategy beyond urgency of LIVE events that need informal and fast exchanges - it is after all a chat platform *(maybe on steroids and popular) not ment to be used for sustained and persistent multi-topical discussions of big groups.


For Telegram (and long etc) there is a chance to resolve it with automatic notifications that each channel could fine-tune as they prefer. See Test automatic updates from this forum to Telegram, Discord, Slack, etc

I agree with the idea of not relying on these proprietary / commercial / chat channels for “official discussion”, and call everyone here instead.

@Zblace is right in proposing retiring Telegram as a discussion platform. Aside from other already listed downsides, the most serious is the issue of security and privacy. Telegram encrypts messages only while in transit from a device to the platform’s servers. Once there, the data is decrypted and can be seen by Telegram (and potentially other third parties).

  • My personal opinion is that the Forum has already demonstrated its ability to bring linguistically diverse communities under one roof. Therefore, it has effectively contributed to solving at least two of the key problems of under-represented communities - the language barrier and fragmentation of discussions.

I’m with you in theory, though I’d suggest we use carrots rather than sticks when it comes to moving folks away from Telegram. That is, any lengthy or official announcements can still be noted in the Telegram channel, but point to a post here, in this forum, where folks can see it in multiple languages.


Although it is not exactly the same, see Create automatic feed of Diff posts tagged with "Movement Strategy".

1 Like

About sending links to Telegram channels, we have a first test running:

It is also worth noting that we have started experimenting with the connection of Meta and Forum discussions with [DRAFT] Minimum Criteria for Hub Pilots (it’s an experimentation and learning process)

A post was split to a new topic: Possibility to send private messages to other users

A post was split to a new topic: Telegram questions

(From my reply on Meta. Not sure I need to do this manually, but didn’t see it here automatically by the time I posted.)

In my experience, Meta is often viewed as its own community (or lack thereof :stuck_out_tongue: ) and project. In practical use it’s not the central organizing space. There are many spaces being used for various groups, communities, regions, interests. Some entirely outside of Wikimedia Foundation supported spaces (like Discord!). As a movement as large and diverse as ours we can not ever have just one. This forum is project and language agnostic, is topic-focused, and is easier for new folks. I see this like I see my work with Diff. It is part of a dynamic ecosystem with many opportunities for folks to jump in and learn more. We can build “campaigns” around what we’re trying to discuss or work on to leverage these systems and spaces. I wouldn’t suggest someone just create a page on Meta as much as I wouldn’t suggest someone just post a blog on Diff and call it done. This forum is not a replacement for, but an addition too our toolset to work with communities.


Sure, but please with more care and option to fully opt out.
Current WMF practices of posting almost everything to almost every channel (and then with corrections) ((and with reminders)) in recent campaigns are just about the worse waste of volunteer attention #whichHasLIMITS @CKoerner_WMF Thank you for understanding.


Sure, as staff we need to be careful. When I say "campaign’ I think about being smart about who you’re trying to reach, and trying to talk to those folks where they are and in a meaningful way. So instead of sending a mass message to all 300+ Village Pumps and dropping a few links into Telegram groups, you figure out where the folks you are trying to reach are already gathering (talk pages? social media? local meetups?) and try to engage in a deeper way.

this topic is totally and highly relevant. I have opened a new thread to suggest some new general resources that perhaps we could explore to start to address this somewhat, in incremental steps.

one thing that I would like to suggest or propose, is a navbox for use at Wikipedia, which would be centered on the current decade, and provide a comprehensive set of link for discussions, decision processes, new procedural draft processes, etc. which are happening now.

if we entitle the navbox as “WMF processes for 2020s,” or something similar, then that provides some initial way to start to clear away some of the thickets and some of the fog clouds, and start to provide a clear, organized, comprehensible way to let the community know about various and general processes which are happening now, and which we would like highlight to them, for their input.

I would like to suggest that folks please visit the thread below to offer any comments or feedback they may have, if they are so inclined. but just to recap., I agree entirely with the importance of the topics being suggested and discussed here on this thread. thanks!

link to thread:

The relationship between the Forum and Meta needs to be clarified. Users preferring the use of Meta should be able to follow and participate in the Movement Strategy implementation. We have started to experiment with this Forum community review, also with the Pilot Criteria for Hubs. Feedback is welcome!

1 Like

Good that we understand each other,
but this still happens more often than not :-/
As for…

With all due respect I have heard this formulation at least 20 times by different WMF folx at different events, formulated in the same way, to the point that I fear it is a slide from power point presentation that circulates in your intranet to be repeated as mantra, but has no actual connection to lived experience. The worse interpretation of that IMHO is when I hear it as an argument to go post announcements in Facebook, Discord and other commercial channels, but not into any of the open/free/libre platforms *(we might be the last significant media community claiming freedom to consider Fediverse).

Anyway - ‘meeting communities’ is complex topic and I will not re-open it here.

1 Like

I favoir using this forum, namely, the DISCOURSE app, as a regular channel for discussiong sharing ideas, offering updates, ins short any and all deliberations required by the community.

in closing, one small note; please remember that the word “discourse” is an actual vocabulary word which itself means “discussion”!! this is not true of the name of other apps and platforms, i.e. “Telegram,” “Meta,” “Village Pump,” etc. so one small technical note or point of order, might be that when we refer to Discourse, let’s either be sure to call it “the app Discourse”! or alternately, maybe we can refer to this site as the “Forums,” but I’m not certain whether everyone else already knows what that means, or what it refers to. thanks!

Copied from Meta:

Perennial proposal: build a new silo to unite the old silos

Alas this never works.

Silo X will not unite the disparate wiki + IRC + email + FB + Discord + TG + WhatsApp + Insta discussions. Instead let’s aim for a small number of lovingly-integrated pieces, with enthusiastic maintainers. –SJ talk 14:56, 11 June 2022 (UTC)


One thing several colleagues have asked me is whether there is a way to “announce something once and have it syndicated to all the relevant channels”. Being the designated mass messenger and distribution coordinator on the Movement Strategy and Governance team, I certainly share the desire!

I could see MS Forum being that starting place, since there is already bots built to interface with it. To syndicate content to wikis would require allowing the Discourse RSS feed to be called by wiki projects that wish to opt-in. Then, an automatic feed of the most recent announcements that have been made here can be displayed (maybe an #announcement tag?).

I guess the drawback would be that it won’t generate an edit on the target wiki, and I’m not sure then if there would be a way to “watchlist” the feed for new content.

I can see on phabricator that @CKoerner_WMF has a similar feed set up for Diff posts on Meta. Chris do you have anything to share about that process? Has it done what you hoped? Is what I’m talking about possible? Did I correctly describe the benefits and drawbacks?

IMHO syndicated (category) blocks (like .rss feeds in blocks in WordPress) need not to have separate rendered page, let alone items in any other wiki, but just display as links to here.
Technical work I can imagine should be on generating RSS with all topics in all languages and checking if that works well enough *(+ having fallback that .rss displays also in EN which should be checked also by fellow humans :-p )…no? Categories of different types of announcements need most care *(and editorial overview), but if the block view is not enough than some custom work needs to be done beyond just rendering titles.

Yes, I also feel that this is a major goal and a major priority. Not only that, but if and when we do create a technical feed for communication and updates, we should make sure to make it very very easy for editors and members of the community to find it very very easily.

One suggestion I would like to strongly recommend is to create a navbox that provides the links to some pages that provide the steps to sign up to receive any such updates, and makes it very easy for anyone to understand the basic steps to do so.