This task would serve as a proposal for MVP for Newsletter extension. The features listed are the ones aimed to be completed before midterm hopefully. Feel free to stop by and drop ideas/suggestions.
== Publisher ==
* Create a newsletter
* Create a new issue for an existing newsletter
* Stop a newsletter, i.e wiping it out of the database (do we need to look at this right now? It is not urgent.)
Definitely not urgent. But since it is an easy feature thought of adding it. Sure, we can move the easy features for later.
* Add collaborators to the newsletter (what does this mean?)
Supposing a publisher has a draft of an issue and he wants his few others from the community to look into the draft or edit it before publishing. In the wiki way, you can have other edit it and revert those changes if necessary. But I was thinking of a scenario where the publisher wants few particular people to collaborate. Scope of this feature can be discussed further.
* Edit an issue (does this have any implications for the database? They are just wiki pages.)
hm, no.
== Reader ==
* Subscribing/Unsubscribing a newsletter (One thing is browsing and subscribing, another is unsubscribing, maybe they should be considered different features?) a newsletter
*Unsubscribing a newsletter
* Missing? Receiving a notification for new issues of a subscribed newsletter.
Email is the only mode of notification for a MVP ( was mentioned in the earlier version of MVP )
* Missing? How does the user knows that Newsletters even exist? How to discover.
For a user with Newsletter extension installed, he/she is expected to have a 'Manage Newsletters' link in Special: SpecialPages which list the available newsletters as well the newsletters to which the user has subscribed.