One trend I noticed is towards making controllers responsible for a particular facet of a model. For example, we used to have a single controller that supported all the operations on a teacher's class, but now we have about 10 controllers, one which supports student attendance, another which supports the gradebook, and another which supports the teacher's view of the class forum, etc.
The codebase could be improved some more, but I think it's already pretty lean and mean. In another post, I'll contrast the edu 2.0 code base statistics against those from Moodle and Sakai.
The last month of edu 2.0 progress has been particularly satisfying, as we added another 1,000 members as well as some key new features.
Here are some of the site statistics taken from our internal dashboard:
A new community game "daily quest" was added.
The gradebook was improved to support weighted categories.
Thousands of new educational resources have been added by our community.
700+ classes are now under development by teachers in our community.
2,000+ teachers are registered members of the site.
3,400+ students are enrolled in classes hosted on our site.
150+ interest groups have been created and over 1,900 members have joined these groups.
110,000+ messages have been exchanged between our members.
20,000+ chat messages have been sent on our chat system.
Hundreds of minor enhancements were made.
Up until now we haven't done any marketing because we wanted to wait until the site matured. And although we still have tons of features in the pipeline, I think it's far enough along to start promoting the site. So next month will be the first "marketing month" for us!
I'm in Puerto Rico right now and looking forward to presenting at the Blogfesors 2008 conference. There should be 100+ blogging professors there, and we're going to be talking all about the use of technology and social tools in education. My own presentation is going to cover both edu 2.0 and my ideas about how to fundamentally improve education systems.