Forum OpenACS Q&A: Re: Who wants to built .WRK?
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.
Althoug I agree with Jade that it is most likely that things will speed up more and more with a growing code-base, I also think that the project needs what in the oacs community seems to be called a 'gatekeeper' - otherwise I see a risk that people start independent dotWrk-a-like things (I know I would), which distracts valuable mantime from dotWrk.
Is there already somebody (actively) assuming that role? If time is an issue - I can 'donate' time to the project, not a whole lot (say 8h/week) but on a fairly structural basis for the coming 3-4 months at least ('cause it has a strong relation with part of my daytime job).
IRL pulling large projects is a big chunk of what I do, so besides coding I can bring something to the table here in the area of planning/coordinating/pushing.
To summarize: I've time to offer to spend on dotWrk-a-like things. I can either spend it on a 'fork' or on 'the real thing'.
Correct me if I'm wrong.