It's hard to beat a person who never gives up. Do checkout MediaWiki-extensions-Newsletter !
- User Since
- Nov 6 2014, 12:42 PM (185 w, 3 h)
- IRC Nick
- LDAP User
- MediaWiki User
May 22 2017
Aug 6 2016
Jun 9 2016
@matthiasmullie Thanks a ton! Couldn't have explained it any better :)
May 27 2016
May 25 2016
May 19 2016
May 12 2016
Apr 21 2016
Apr 19 2016
Apr 5 2016
Woohoo! Thank you again everyone for this :) @ori , special thank you for the security review, we've been waiting for one forever!
Apr 3 2016
Thank you, Katie!
Apr 2 2016
Apr 1 2016
Hmm... just tested on http://newsletter-test.wmflabs.org/ and did not get the error. Wonder what's missing here :\
Mar 11 2016
Mar 10 2016
Closing this now. Tasks can be filed for further validation related bugs.
Mar 1 2016
@Unithiyashree @Prateechi Hi, , You both could work on Easy bugs(https://phabricator.wikimedia.org/project/board/169/) and make yourself strong candidates. We'll put up microtasks soon enough and completing them would help you get acquainted with Mediawiki code and the bug fixing procedure. Thank you for your interest!
Feb 25 2016
Feb 18 2016
@Glaisher, can this one be marked resolved ?
Feb 13 2016
Feb 4 2016
Jan 25 2016
Jan 23 2016
I think it would be better to decide what all kinds of inputs are allowed for the form fields that needs validation. Two pages have forms and thus require validation, Special:ManageNewsletter and Special:CreateNewsletter.
Jan 22 2016
Dec 8 2015
@Mhutti1, Thank you!
Dec 7 2015
Dec 5 2015
@Glaisher, could you elaborate on what you meant by email notifications can be prettier ?
Nov 28 2015
Nov 19 2015
Nov 17 2015
Nov 12 2015
@Glaisher, this one can be marked 'Resolved'? :)
Once T117043 is merged, only those newsletters which can be managed by the logged in user will be listed. So only if you are a publisher do you get a list of newsletters in Special: NewsletterManage, nullifying the need of 'manage-newsletter' right ?
The patch submitted for this task makes sure that the entries listed in the table are just those newsletters which can be managed by the logged in user. Should a filter for the table be added as well ?
Nov 11 2015
Nov 10 2015
Nov 6 2015
@Haritha28, this task is kept aside for students who will be participating in Google Code In this December.
Nov 2 2015
Oct 30 2015
- permissions model is binary? publisher or not? this seems a bit weird...
We did have 'owners' and 'publishers' earlier.. but then we removed the owners and decided to give the sysops the 'newsletter-addpublisher' permission because the roles of owner were limited.
- how many publishers can a single newsletter have?
- how do I add or remove a publisher?
You can remove a publisher in Special:ManageNewsletter using the 'Remove' button you see on the 'Action' column. Only a publisher or a sysop can do this action.
- not clear what the contributors column is... single username?
- not sure this column is needed at all
List the publishers or those who contribute to the newsletter.
Oct 29 2015
Oct 28 2015
Oct 27 2015
Oct 26 2015
@Tgr Thank you for the pointers!
Oct 23 2015
Oct 22 2015
Good job for an initial draft! Please also mention the main project task in your proposal (Phab task of project : <task id> .. or anything similar to that).
Oct 21 2015
@Devirk, From a really quick search I found these tasks which can serve as microtasks,
Oct 14 2015
The usual procedure is we come up with a plan for a Minimum Viable Product (MVP) after the project period starts to be completed by the end of mid term evaluations,. Maybe in this case, we should come up with an MVP right now which can be completed by a student and will come under Outreachy's scope.