In reality I think it will be impossible for people to set even a rough schedule for the larger modules, at least people who are new to ACS 4.x.
So freestyle will dominate by necessity. What I think I'll do is ask folks working on larger modules to first do an assessment so we can get a handle on difficulties we might face.
For instance, a module that depends on Oracle's built-in java-based e-mail utils (are there any, or was that just ACES?) will be harder to port than something like News that is mostly a UI and presentation wrapper around the Content Repository.
The first thing we'll want will be a list of more difficult problems which need a non-Oracle solution, because there might well be overlaps between modules and we won't want to spend time solving problems twice. And we'll want to float ideas for solutions for comment by the community.
