Eric, .WRK has yet to be built. I'm going to be working on it at some point in the next few months, but even the organization of it is pretty tentative at this point. Lars was leading up the project, but seems to be working on some other projects right now.
It will happen, but it needs some attention and developer time. I am using ACS 3.4 for our Intranet, with a heavily customized interface. We've been using it for about two years, and I've learned a lot in the process, and hope to use that to help in the .WRK effort.
However, I'd like .WRK to be a pretty flexible entity.
One of the major problems with the ACS 3.4 version of the Intranet package was that it was written so specifically for ArsDigita's needs.
One concern I've had is that if one of us goes off and writes this package, it may do the same thing all over again. That certainly is what my own tendency would be.
Another problem I'm going to face, that many of the rest of you won't, is that I have to migrate all of my old data from ACS 3.4.
We've heavily customized the ticket tracker, to where it is not for tracking bugs, for is a collaborative to-do list. I've thought about porting it to OpenACS/dotWRK. I'm not really happy with any of the ticket trackers right now. None of them are general enough to be used for all to-do items, and I kind of like the interface we've developed here. However, it is a fair amount of work.
The whole project is fairly large though, especially because it's difficult for those involved to sit down and plan out how it might work. Collaborative programming works, but it's easier if you have something concrete to start from. Or at least that's my (limited) experience.
