As discussed in the meeting I went through and assigned some unassigned tickets. You can always move those to someone else if you can't do it, or ping people to get them to contribute. (Remember, being assigned doesn't mean you necessarily *do* the ticket, just that it is your responsibility to ensure it *gets done*) Some of you may have noticed (and if you didn't, check that you have your github account set to notify you!) that I added the 3.3.0 milestone to many many issues. Basically _most_ of the issues that were open and had Status:Go (with the logic that if they have that status then they should be done by the next release....right? Obviously not all of these will be done by the next release and most of them are not "release-blocking" in any way. You can just _remove_ the milestone, or if you know you will do it before the following release change the milestone to the 3.4.0 release (just added). The benefit of this is when we come to release 3.3.0 we'll go through all these and ask "Hey, this has been around since 2012, why the heck haven't we just *done* it already!" Best wishes, James -- Dr James Cummings, James.Cummings@newcastle.ac.uk School of English Literature, Language, and Linguistics, Newcastle University