Change Details

Fields required in a wrap-up report: - Project description (as you would explain it to a layman who has no clue about MediaWiki). Please include screenshots with description - explaining how exactly the tool/extension works. - Missing features/known bugs. Add links to phabricator tasks for the same and leave a short explanation. - Demo server link - Resource links (Project in gerrit/github, extension link on wiki etc.) - Anything else you can think of, which can make contributing to this project easier for newcomers. (Please edit this task itself to write your report. Make sure you complete it by 21st of August when end-term evaluations start.)

===Project Description( incomplete )=== Many Wikimedia projects and developers use newsletters to broadcast recent developments or any set of relevant news to other Wikimedians. But having to find a newsletter main page out of all the wikis and then subscribing to it by adding your username to a wiki page doesn't really sound appealing. That's when @Qgil thought of centralizing the functions of all newsletters at one place, an idea which later shaped to an extension, Newsletter extension. >>! In T76199#1073178, @Qgil wrote: > My only motivation for the centralization is the need to offer a catalog with all the newsletters available in a wiki farm, and the possibility to subscribe/unsubscribe and receive notifications without having to visit or be an active editor of any wiki. If we solve these use cases, then I agree that each wiki community should be able to manage their own newsletters. - Missing features/known bugs. Add links to phabricator tasks for the same and leave a short explanation. - Demo server link - Resource links (Project in gerrit/github, extension link on wiki etc.) - Anything else you can think of, which can make contributing to this project easier for newcomers.

Fields required in a wrap-up report: - Project description (as you would explain it to a layman who has no clue about MediaWiki). Please include screenshots with description - explaining how exactly the tool/extension works.===Project Description( incomplete )=== Many Wikimedia projects and developers use newsletters to broadcast recent developments or any set of relevant news to other Wikimedians. But having to find a newsletter main page out of all the wikis and then subscribing to it by adding your username to a wiki page doesn't really sound appealing. That's when @Qgil thought of centralizing the functions of all newsletters at one place, an idea which later shaped to an extension, Newsletter extension. >>! In T76199#1073178, @Qgil wrote: > My only motivation for the centralization is the need to offer a catalog with all the newsletters available in a wiki farm, and the possibility to subscribe/unsubscribe and receive notifications without having to visit or be an active editor of any wiki. If we solve these use cases, then I agree that each wiki community should be able to manage their own newsletters. - Missing features/known bugs. Add links to phabricator tasks for the same and leave a short explanation. - Demo server link - Resource links (Project in gerrit/github, extension link on wiki etc.) - Anything else you can think of, which can make contributing to this project easier for newcomers. (Please edit this task itself to write your report. Make sure you complete it by 21st of August when end-term evaluations start.)