Hi Greg,

This is great news.  Especially with regards to commenting and imaging going
to the community.  

To add to Richards reply, has there been any discussion about moving the
Categorization module to the community?  It would be really nice if Twigs
could depend on the Categorization module without having to fork features
for CE and EE users. I think other Forge projects could benefit from
Categorization being a community module, for instance a possible Blog module
(as Will already mentioned).

Thoughts? 

Cheers,
Matt

> From: Grégory Joseph <[email protected]>
> Reply-To: Magnolia Dev-List <[email protected]>
> Date: Fri, 9 Sep 2011 16:34:48 +0200
> To: Magnolia User-List <[email protected]>, Magnolia Dev-List
> <[email protected]>
> Subject: [magnolia-dev]  An outlook on the editions of Magnolia
> 
> 
> 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]>
----------------------------------------------------------------

Reply via email to