Topic on Project:Village Pump

Ack & thanks for your efforts!

Hi, after a long long journey... Special:Newsletters!

The Newsletter extension is a tool to facilitate subscription and delivery of newsletters hosted on MediaWiki-based sites. You can learn more about this extension at Help:Extension:Newsletter.

Any newsletters within the scope of MediaWiki.org can be created. In previous discussions it was agreed to only allow administrators to create newsletters. Once a newsletter is created, their publishers can announce new issues at will without requiring administrators anymore.

If you want to create a newsletter and you need an administrator to do it, just reply here specifying:

• the name of the newsletter
• a short description, allowing this newsletter to be recognized in a list with all the newsletters
• a wiki page for its home
• at least one publisher (MediaWiki.org username)

If you want to report problems, request features, or get involved in the project, please check MediaWiki-extensions-Newsletter in Phabricator.

Hello. Congratulations, great job! As always, hewiki can help in finding rtl errors. And there always are rtl errors. So, we'd like to create a newsletter, meanwhile in mediawiki, and one day it will move to hewiki, when available. The notifications will be redirections to upcoming sections in he:project:news. So all notificatons will come from mediawiki to hewiki using Echo interwiki system, and will appear on rtl to subscribers. I created this news project, and publish about 80% of messages there for users, every time there is some interesting new mediawiki engine feature, for example. So naturally, I'll write the notifications. So, could you please create a new newsletter: 1. הפומפיה (the grater in hebrew) 2. עדכונים שוטפים על ידיעות חדשות בדף ויקיפדיה:חדשות (ongoing updates about new issues on wikipedia:news) 3. Sorry, what do you mean in home page? I should create something here in mediawiki? In which namespace? 4. User:IKhitron Thank you very much.

Hi @IKhitron, thank you for your interest. There is one problem: interwiki prefixes like he:project:news are not supported yet (see phab:T174664). I recommend you to wait until that is solved. Also, the idea of "migrating later to Hebrew Wikipedia" is not clear either (phab:T110645 is where we discuss interwiki / multiwiki support). Would it be an option for you to start testing in https://test.wikipedia.org/wiki/Special:Newsletters? I'm sorry for not having better answers currently.

Hello, Qgil-WMF. I think I did not explain myself well. I do not talk about an hewiki newsletter, but a mediawiki one. Local. It's issues will be wikilinks to hewiki in regular wikicode, that's all. There isn't something that doesn't allow to create it just now. And I did not talk about technical migration. One day when the extension will be deployed on other wikis, we'll ask the subscribers to subscribe once more, locally. So, could you do this now, please? Thank you very much.

N3 Thanks for phab link, I don't need it, because I don't need interwiki service, as I said.

> It's issues will be wikilinks to hewiki in regular wikicode

This is not supported now. The extension will not accept a syntax like "he:project:news". This is exactly what phab:T174664 is about.

Maybe I did not understand, Qgil-WMF. But I still think we are talking about different things. I'm not talking about interwiki link in notification - there will be regular mw:homepageofnewsletter#something link there. If somebody clicks and comes to this page, they'll find the interwikilink there, in the text (of the issue), on regular wikitext content model page. Thank you.

Alright, sorry, now I understand. The main page is required. It is where you explain what the newsletter is about so users can decide whether they are interested in subscribing, and any other details you want to add. Newsletter issues point to pages, and they don't take into account #sections. In wikitext pages sections are pure representational, and things are prone to go wrong if someone edits the sections (as opposed to renaming pages, which by default leaves redirects). A simple option would be to use Flow topics for new announcements, from the discussion page of the newsletter main page. Each Flow topic is a page indeed.

Thank you. Very well, Qgil-WMF. Looks good for me. So the main page could be the flow border, and subscribe button will be added to the description, or I need a wikitext page as the main one and flow page for issues?

You need a main wikitext page, otherwise you will not have a discussion page to refer to.  :)

Great. So, I'll create a page and ask to convert its talk page to flow. So, it's the same question I asked at the beginning: In which namespace should I create the main page? I don't know this wiki structure. And "User" is not a good idea. Thank you very much.

A page in the main namespace is ok. You will get the Flow page automatically. There is no need to request anything.

Thank you for your kind recomendations. Done.

Could you, please, create a new newsletter:

1. הפומפיה

   (the grater in hebrew)

2. עדכונים שוטפים על ידיעות חדשות בדף ויקיפדיה:חדשות

   (ongoing updates about new issues on wikipedia:news)

3. הפומפיה
4. User:IKhitron

Thank you very much.

@IKhitron Y Done Newsletter:הפומפיה

As a first publisher not involved in the development or testing of the Newsletter extension, your feedback is highly appreciated.

Thank you very much.

Sorry for the time I spent you.

Three points:

• I think you can make a summary of our conversation (flow, main namespace and much more) and put it on the project page, so these questions will not be asked every time.
• You thought I'm talking about interwiki newsletter at the beginning. I didn't. I didn't even think it's possible, otherwise you would not deploy this extension on any wiki, even here on mediawiki. Just once on meta, and it could be enough for all wikis.
• But all this made me find a bug in Flow: it does not work well on Timeless. So it's an adventage. :-)

Thank you again.

Congratulations to all those who made Newsletter possible. Looking forward testing and trying to better the extension. Regards.