Forum OpenACS Development: A couple of schedule questions...
release for ACS Core is due out at the end of this month. Is that
still more or less on track? Second, what near-term
enhancements to the core (if any) may not be included in this
release date and when might they be ready?
Third, are there any package owners out there who are willing to
voluntarily post rough projected completion dates? I realize that,
when you're doing this work on the side, going on record with a
goal release date has no real personal upside and lots of
personal downside. But if you feel comfortable putting out
projections (particularly for those modules that are pretty well
along), you'd be doing the community an (additional) service that
would be greatly appreciated.
Thanks in advance to all for both the update and the work done
that makes the update possible.
The biggest piece left for the ACS Core is portions of ACS Subsite. Steve Woodcock's going to try to finish it by August 1 after he returns from holiday, but it will be tight.
We have a proposed alpha release data for site-wide-search of August 10th, though maybe August 15th is more realistic - this is a big job as we're trying to work through details of abstracting out a search API so packages can work with Intermedia (oracle) or "the Russian Solution" (postgres). Neophytos is doing the bulk of the work on the module, Dan on the support pieces.
My impression is that most if not all of the assigned packages will be done by August 15th, but not by August 1st.
I'll work on getting more solid information this week.
packages will be done by August 15th, but not by August
<p>If that is the case, then the port is roughly a half a month
ahead of the original schedule. That's great news. Isn't it also
somewhat unusual for an Open Source project?</p>
But given that the core's taking longer than first expected I guess we're doing OK. The key is that the core pieces needed for basic package porting has been done for quite some time so package porting hasn't had to wait even though there's still work to be done on the core.
And we've had a higher degree of parallel development than I, at least, had first planned on. In other words, more volunteers stepped to the plate than expected. Hooray!
But keep in mind that some of these ports are going to need improvement, if nothing else because they're based on ACS 4.x Classic packages that need improvement, in some cases to work with core changes that are being made or discussed in order to get some of the unfinished pieces working in PG. Sitewide search, that must at minimum provide an API that can be used for both InterMedia and our PG full-text search solution, will undergo changes that will impact client packages.
Paying the price of clean, multi-db support, in other words ...
Still, I think things are really going quite well.
Unless a bunch of new volunteers show up in a hurry, we've got to get by with the volunteers we have. A couple of people e-mailed me offers of help this week, but I don't expect our volunteer base to grow much beyond where it is in the near term.
As people get freed up after porting packages I would hope that they'd be available to take on major improvement tasks like the admin stuff you mention. It's crucial stuff.
sort of improvements that Talli is talking about and when is it
time to start thinking about putting significant energy into new
modules/functionality? For example, I could imagine the
community switching into a beta test/improve mode during
September and maybe start focusing on new module
development by mid-October. What are the right milestones for