There's no sense in piling on to all the criticism that Six Apart is coming under for their announcements today about MT3--to Mena Trott's credit, she's left an awful lot of disappointed, critical trackbacks intact, at least as far as I can tell.
What I want to do instead is to talk a little about the way that I use MT, and the way that I had hoped to use it. First, I should be clear that I have no objection to 6A trying to make MT a source of revenue. Second, there are indications on the MT site that their licensing structure will make some allowances for educational users, which may go some distance to answering my concerns. That being said, here's what I'd once hoped for MT:
Personal
Currently, I'm maintaining two sites, but I've experimented with using MT as my primary interface for course syllabi. Under the current license structure, if I want to continue using MT this way, I'll either have to pay or dump sites once a course is over. Nor can I allow students temporary accounts to post to a site. And honestly, I don't make the kind of money that would allow me to pay for the kind of license I'd need to do these things. (3 users/5 blogs I can afford, but this year, I had upwards of 35 students in each semester.) The pricing structure appears to me to do very little to understand different classes of authors--as far as I can tell, there'd be no price difference between my attempt to enable a semester's worth of access to 20 students for a single course blog (or even hosting 20 blogs for a semester for students) and a company that hosts permanent blogs for 20 users.
But that's relatively minor. I can switch to 3, I suppose, although it will severely limit my range of possible activities, enough so that I'll probably take up Wordpress or Textpattern for potential course blogs.
Institutional
Ever since the U of Minnesota announced their UThink program, I've been thinking about how we (in my department) might do some of what that program does, albeit on a smaller scale. I've spoken with our tech people about installing MT on our server, putting together some site-specific documentation, and making it available to all faculty and grad students for personal and/or course use. Needless to say, our technology budget would not be sufficient to the task with MT3--there's no way to predict how many users there'd be, or how quickly people would take advantage of it, or even if they would. And given the initial sweep of their price scale, we'd be talking about thousands of dollars, which is prohibitive for us. We're a Mac unit on a PC campus, and even though we get great financial support from the university (fairly frequent upgrades, licenses, etc.), we don't have access to the root IT budget.
I'd also hoped to use MT in the fall to start up a department newsletter (or to restart it, I guess), again a many-to-one blog, but one that was ongoing rather than semesterly. We've talked about transferring our dept's homepage over into MT, or enabling an RSS feed on the homepage that would serve up newsletter items. But again, the cost would be prohibitive, unless we simply stick with MT2.6, and I don't guess that there'll be a whole lot of support or development for it down the road.
I'm going to go ahead and send 6A some feedback, and I hope that they take this to heart (if nothing else): the traditional model for educational licensing has been to drop 10-20% off of the price, but that's simply not going to do it here. With educational users, you're talking about very different patterns of usage, and a price scale that doesn't acknowledge those differences is going to simply drive off that market. It's conceivable, with even just a handful of power users, that the number of users and blogs in a writing program could reach into the thousands over a period of, say, 5 years. But the vast majority of those would be temporary and educational (i.e., non-commercial). Even the stable core (given grad students graduating and professors migrating) wouldn't necessarily be permanent. But you're talking about potentially wide fluctuations in the number of current users, and several potential levels of usage. Should a student required to post to a course blog once a week for 15 weeks cost as much as someone who's maintaining a daily site for years? Of course not. It's a lesson that Textpattern has already learned--I'll be waiting to see if 6A can say the same.
I must confess that I feel a little sad about this. MT has had a great deal to do with how I've learned about weblogs, and a disproportionate influence on how I think about them. The prospect of learning a new system and installation doesn't interest me a whole lot, but unless some major revisions occur, it doesn't look like MT3 is going to be my platform of choice. I haven't decided yet what I'm going to do, but I'll be really thinking about it this summer.