By and large the changes are fine except the decision to constrain CE users to just one subscriber. Everyone including small sites need fail-over capability. One of the clinching factors that lead us to select Magnolia when we were evaluating CMS options was multiple subscribers.
Rakesh On 09/09/2011 09:34, "Grégory Joseph" <[email protected]> wrote: > >Hi, > >Following my email announcing 4.5 yesterday, here is another, less >time-constrained, topic which we want to expose and discuss. > >There's an old itch that Magnolia, as a company, has wanted to scratch >for a while: we need to have a clearer distinction between the community >and the enterprise editions of Magnolia. It's always been a struggle >explaining what was different, and why. > >We've talked to various community members, partners, customers; we've >looked at what we have now and where the differences are, and realized >that we can indeed streamline and simplify them. And in helping >clarifying the distinction between the editions, we think we can drive >the development of *both* editions of the product further. > >Our current plan is to turn the following points into enterprise features: > * Multiple subscribers > * Multiple sites (this is already the case, as implemented with ETK) > * Workflow - at some point in the future, we will migrate to a new >workflow engine, and this new module will most likely be EE-only. > >The rationale here being that, quite simply, those are features that are >primarily used by larger enterprises. > >Conversely, we're looking into at least the following changes for the >community edition: > * STK's license changes to GPL. No more badge. We thought it was just >time to get rid of that barrier. We're now hoping for a broader STK user >base and eco system ! > * The imaging module goes to CE (GPL, open source and bundled with STK) >- no more silly non-resized images with CE. > * The commenting module will also go CE. This hasn't been discussed >much just yet, but I assume you'll still have the choice to use an >external commenting if you wish, but it just makes sense to have this >module along side the forum module, which it depends on. > >These are the main current plans, anyway. Other changes or ideas are not >out of the question, with the 2 main goals of streamlining the >differences, keeping them where they make sense from a business >perspective, all the while allowing greater adoption and participation >with the product we all love. > >In terms of schedule, STK 2.0, which will come with Magnolia 4.5, will >have its license changed. Other changes are currently not scheduled >precisely, so we're perhaps looking at making those other changes for 5.0. > >We realize these changes might bum some people out, but we also think >they will rejoice others; and that in general, it's a decision that will >help driving the product forward. As always, we look forward to your >feedback and will be happy to discuss or clarify points as needed. > > >Cheers, > > >Grégory Joseph >Magnolia International Ltd. > > >---------------------------------------------------------------------- >[email protected] http://www.magnolia-cms.com >Magnolia® CMS - Simple Open-Source Content Management >---------------------------------------------------------------------- > > > > > > > > >---------------------------------------------------------------- >For list details see >http://www.magnolia-cms.com/community/mailing-lists.html >To unsubscribe, E-mail to: <[email protected]> >---------------------------------------------------------------- > ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
