Before *too* much more time has gone by, most of OpenACS 4 will have
been ported to PG and we'll be looking at other things to move to the
4.x framework.
So, Roberto and Pascal, guess how I think you should spend your summer
vacation :)
Seriously, the changes mentioned so far look pretty simple to
incorporate and we could certainly use them here at openacs.org as
well as in the 3.2.6 release.
But beyond one round of moderate effort at improving it, I think we
should be looking at an OpenACS 4 migration. There are (count them)
three ticket tracker packages from aD, one based on workflow and
incomplete. I happen to like the new-ticket-tracker in the SDM, but I
also think building the SDM pieces on top of acs-workflow makes a lot
of sense.
Anyway, I'm in no way trying to discourage effort to improve the SDM
in its current form - I want to get you two to think about
volunteering to help out (or take over, hey, I might as well swing for
the home run) the migration effort for 4.x.
There's also the project tracker package (alpha, development? Haven't
checked it out yet) in aD's repository that I've not imported into our
OpenACS 4 CVS repository. Project tracking is something not tackled
by the SDM. Integration of code and/or ideas from the aD work along
with the nice, easy-to-use mechanics of the SDM could lead to
something exciting.
Something I wish I had now, actually, as I track OpenACS 4 project
progress via files in new-file-storage etc.
