Let's start from @Bawolff's review : https://www.mediawiki.org/wiki/User:Bawolff/review/Newsletter
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Duplicate | Qgil | T125545 Phabricator Q&A session for Community Liaisons | |||
| Resolved | Qgil | T116025 Goal: Align Community Liaison and Developer Relations project management practices | |||
| Resolved | Qgil | T119387 Community Liaison and Developer Relation quarterly goals for January - March 2016 | |||
| Declined | None | T104131 Exporting existing newsletter to the Newsletter extension | |||
| Resolved | Addshore | T110170 Goal: Deploy Newsletter extension in Wikimedia | |||
| Resolved | Qgil | T110366 Newsletter extension: Technical review | |||
| Resolved | Glaisher | T110490 Deleting a newsletter and subsequent clean up | |||
| Resolved | Glaisher | T110535 Batch queries and job queue for onEchoGetDefaultNotifiedUsers function | |||
| Resolved | 01tonythomas | T119058 Special:Newsletter fatals if the newsletter main page is deleted |
Event Timeline
Comment Actions
I would suggest marking the tasks in https://www.mediawiki.org/wiki/User:Bawolff/review/Newsletter 'Done' or 'Patched' depending on the status.
@Qgil Do you think instead we should create phabricator tasks ? ( There will be quite a lot )
Comment Actions
Marking items as {{done}} in the wiki page is enough. If there are items that take a significant amount of work, or are depending on existing Phabricator tasks, then we can create new tasks for them.
Comment Actions
Marking as Low priority only because we have agreed to focus first in T110642: Implement all the features required for running the Newsletter extension in Wikimedia.
Comment Actions
From today's weekly meeting:
<tinajohnson> So basically we have https://phabricator.wikimedia.org/T110491 and https://phabricator.wikimedia.org/T108301 left to finish off all the features
<tinajohnson> so the feature complete section will be done soon !
<qgil> tinajohnson, the two tasks you are linking look like "minor"
<qgil> I'm thinking when can we start the request
<tinajohnson> qgil: yeah they are
<addshore> I'll try and have another look over the whole extension in the next few days and see if anything catches my eye that needs to be done
<tinajohnson> qgil: hm, I'm guessing by the next meeting
<tinajohnson> addshore: Thanks!
<qgil> ok, sounds good.
<tinajohnson> qgil: I say next week, because we need to get the patches reviewed as well and new requests might come in any time
<tinajohnson> one of them has patch submitted
<qgil> Maybe we don't need to have everything fixed/reviewed before starting the technical review
<qgil> because that process will take time
<qgil> and we (well, you) :) can keep working while we get the feedback
<tinajohnson> oh okay, so do you want to start it before next Thursday ?
<qgil> No, I think next Thursday is fine
<tinajohnson> Great (exams end on Wednesday :))
<qgil> Meanwhile we can discuss at https://phabricator.wikimedia.org/T110366 whether there are any strict blocker for starting the technical review
<tinajohnson> sure
<qgil> (I s there a time of the year when Indian students are not doing exams?) :D
<tinajohnson> probably not :)
<tinajohnson> https://phabricator.wikimedia.org/T110491 is a blocker for sure
<qgil> I have to check the technical review process in detail, but maybe we can start with a list of known bugs identified.
<qgil> I mean, only the security review will take waiting time, that is why I want to start soon, now that UI and feature-wise it is basically complete
<tinajohnson> When you say bugs, the ones that are not in here ? https://phabricator.wikimedia.org/tag/mediawiki-extensions-newsletter/
<qgil> No, I mean those
<qgil> but the technical review will not bother about all of them
<tinajohnson> ah okay
Comment Actions
@Qgil as this is a subtask of the deployment goal I assume it is complete and can be closed?
Comment Actions
I think all relevant technical issues have been resolved. If new technical issues are found, they should be submitted as new tasks.