anywhere, and that any such effort would be extremely painful and
time-consuming. I'll still rather pissed that aD never offered a
I'm curious what all the ACS 3 sites are doing development-wise. There
hasn't been a code repository for ACS 3 for over a year, and when I
inquired around about it, nobody seemed particularly interested in it.
It does seem like there were a lot of sites built on ACS 3.4, though,
and I imagine at least some of them must be under development.
So, my questions are:
1) If your site is built on ACS 3, do you ever have a plan to migrate
it to OpenACS?
2) If there are enough people thinking about this, wouldn't it make
sense to band together and create a migration guide / set of porting
tools to migrate as much of this data as possible to the new data
models? Perhaps we could share the pain and get it done more quickly.
3) If you plan to stick with your current platform of ACS 3, would you
be interested in helping out with maintaining a repository? Ybos has
volunteered to host it, but I don't think they have enough time to
maintain it. I'd be happy to help out, but I'm not sure how many other
folks out there are in the same situation as me. I'm already
maintaining a code repository for my own use. ;)
4) If I did go through all the pain of porting everything to OpenACS,
would I be rewarded with a platform that's going to have a migration
future? I'm not interested in another dead end... Is OpenACS 4 going
to be able to be ported to OpenACS 5?
5) I have a lot to contribute to OpenACS if there was a way to get
there from here. I've refined the Intranet portion of the ACS 3.4 code
full-time for over a year now, and developed the interface quite a
bit. I would love to bring these changes into the public domain so
other people could use it.