[OOTB-hive] "Keep SPP IP proprietary"

Peter Löfgren peter at loftux.se
Tue Jun 16 06:52:54 BST 2015

This is interesting, and I think a step in the right direction.
What would be the features of Advanced Sharepoint classes that are left out
access to Community? Reading ALF-21295 I think this has the list what will
be in Open version, but what is left out? I've never been able to find
product page on AOS (or any other addon like Transformation server)

As much as I value the Open Source part of this I do not argue against
proprietary modules. After all, we have proprietary modules ourself. More
of a concern is that Community edition users will not be able to purchase
the full module. Not knowing what features AOS Community/Enterprise will
have, if I have to choose between a very slimmed downed Community that is
open source or a AOS full feature proprietary available for purchase for
all, I may go for the latter. I've argued this for modules/addons with
Alfresco employees before, but it seems like it is not going to happen.

I actually had a Community customer wanting to purchase this, but it was
not an option from Alfresco to offer this for them.

But best is of course full open source for the entire module :)
I'll even be happy with slimmed down version, as long as it at minimum
supports what the SPP module does today.


<richard.esplin at alfresco.com>:

> Thank you for the feedback, it is very useful.
> I just want to highlight that ALF-21304 is part of Epic ALF-21295. This is
> a
> proposal, and has not yet been approved by management.
> There were some concerns about my making the issues public, but I
> considered
> it important to explain the concerns some members of the team have about
> open
> sourcing AOS.
> One concern with the proposal was that members of the team feared the open
> source community would not appreciate a closed source module in Community
> Edition. It is good to know that many of you feel that is a reasonable
> approach for us to take. I want to make Community Edition as full-featured
> as
> possible, even if we are not able to release all of the code. I can see us
> taking this approach with other add-ons that are currently Enterprise-only.
> However, I think it is important that any proprietary modules in Community
> Edition be optional and that the open source product be robust and useful
> without them.
> Thank you again for the feedback.
> Richard
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.xtreamlab.net/pipermail/ootb-hive/attachments/20150616/c4fc2bb8/attachment.html>

More information about the OOTB-hive mailing list