3.2 will be launching this week. I know everyone will be itching to start talking about features for 3.3, but I’d like to put a moratorium on that for a week or two so that we can spend some dedicated time looking at the GSoC projects.
We have a history of getting great students, being excited about their projects, then not paying much attention once they’re underway. We need to change this. These students are potentially the next generation of WordPress leaders, and we should be paying close attention to their work (and thinking about how we can use it).
As it happens, next week is midterm for the GSoC students, which is perfect timing for a review, since all students are meant to have their projects coded and ready for testing by this point. After 3.2 is released, I’d like all the leads and committers (and any other interested contributors) to look over each project and provide feedback to the student/mentor groups. We could do this on our student blog, in IRC chats, or a combination.
Does anyone have a problem with postponing 3.3 talks for a week so we can make sure our GSoC kids are on the right track?
John James Jacoby 12:20 am on July 4, 2011 Permalink |
+1
mitcho (Michael 芳貴 Erlewine) 12:43 am on July 4, 2011 Permalink |
jjj, this isn’t Google+. :p
Will 1:07 am on July 4, 2011 Permalink |
+2
Andrew Nacin 4:12 pm on July 4, 2011 Permalink |
Absolutely +1. I’ve been working on pre-midterm evals for my students this weekend.
Suggesting the following:
– July 6. Post-release check-in of tickets and support threads, and general release de-brief.
– July 13. Ideas and scope chat for 3.3.
– July 20. Finalize scope, owners, and schedule.
bentrem 5:55 pm on July 4, 2011 Permalink |
Sidebar: a list of WP geeks on + might facilitate things.
Jane Wells 6:07 pm on July 4, 2011 Permalink |
Facilitate what?
Akif 12:32 pm on July 5, 2011 Permalink
Sure +3
3.2 rocks btw