Elias Torres wrote:
I see in the Wiki page that this has a 3.X release target. Are there
serious considerations for this being done on 3.1. The reason I ask,
it's because I'd rather have 3.1 be tagging only. As a matter of fact a
dramatic change like this maybe should be 4.0.
I would agree with that. To do all of the Modular Roller stuff that is
suggested in that proposal requires a pretty significant reworking of
the base architecture for Roller, so I think it should be done as a
major rev.
It seemed that after a little discussion we had decided that maybe a
better near term goal was just to start separating out the planet code
so that it can be treated more like a module and more easily be built
and run on its own. I think that work could happen for 3.x.
-- Allen
You might already have thought of this, but would you see core
containing an APP implementation? It'd be very cool if we could deploy
core and just have APP, then slap weblogger on and you get weblogs!.
-Elias
Dave Johnson wrote:
Looks like I may have a requirement to deploy Planet independently of
Roller (but with Roller's Planet UI and the Roller rendering/caching
system). And others on the list have also expressed interest in
modularity. So I've started to think again about how to break up the
Roller code based into core, weblogger and planet modules.
I updated the proposal with some of my latest thinking:
<http://rollerweblogger.org/wiki/Wiki.jsp?page=Proposal_Modular_Roller>
The proposal has a way to go, but comments and suggestions are welcome.
- Dave
