But what is a newsletter? Is it a chunk of wikitext that gets put on a user's talk page, or an expanding set of wiki pages? Link to an example.
Also "an existing wiki page that will serve as main page". Main page of/for what? Explain and again link to an example.
I'm with you, SPage (WMF). I think a simple wireframe, or a paragraph or two describing what functionality this would produce, would be tremendously helpful. If I can help (e.g., by interviewing somebody and documenting what I learn), I'd be happy to do so. At the Signpost, we are continually looking for ways to automate aspects of our publication and notification processes, so that we can focus more heavily on the actual writing and editing of the newspaper...so I'm very interested in knowing more about what's envisioned here. -Pete F (talk) 20:32, 29 December 2016 (UTC)
OK, I understand it now. I initially thought this was an effort to ease the creation, publication, subscription, and delivery of newsletters. But (mainly through Quiddity's mockup image below) I now understand -- it's merely intended to ease the subscription and delivery aspects. There are already a number of newsletters (now in links in other threads) with existing subscription and delivery methods -- and, as far as I know, the only standard delivery method is talk page notification. The extension would centralize the subscription aspect, so that every user can subscribe to a variety of newsletters through a pane in their "preferences" screen; and it could also add Echo notification and email notification (and possibly email delivery as well) as options. Do I have that right, Qgil-WMF? -Pete Forsyth (talk) 06:04, 4 January 2017 (UTC)
Yes, we need to improve the Extension page (this is a proposed Google Code-in task right now, so we might get that page updated very soon thanks to new volunteers).
What is missing is a good definition of a newsletter. The content of the newsletter (main page and all the issues) are created independently as regular wiki pages, just like The Signpost does today. What this extension offers is the possibility to "register" your newsletter (probably better wording than "create"?) in order to ease
"Register" is a better word, yes! Much clearer to me. I don't know what a Google Code-in task is, or what the implications are, but if it means this is likely to be more fully developed and implemented in the Wikimedia world, that sounds like good news! -Pete Forsyth (talk) 22:39, 4 January 2017 (UTC)