Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

EE vs CE #116

Closed
gondo opened this issue Nov 7, 2012 · 7 comments
Closed

EE vs CE #116

gondo opened this issue Nov 7, 2012 · 7 comments
Labels
Fixed in 2.3.x The issue has been fixed in 2.3 release line Issue: Format is not valid Gate 1 Failed. Automatic verification of issue format is failed

Comments

@gondo
Copy link

gondo commented Nov 7, 2012

in the future, would you accept/ignore pull requests adding EE functionality into CE version?
f.e.: store credit is currently EE functionality, what if i would commit code to support this in CE?

@gfxguru
Copy link

gfxguru commented Nov 7, 2012

What a concept! I think that would be freaking awesome... But I don't see Magento going this route. I suggest we create a fork and establish our own enterprise capabilities into CE.

@gondo
Copy link
Author

gondo commented Nov 7, 2012

ok this is shifting away from my original question, which was addressed to Magento creators.

about the idea of CEE (community enterprise edition), its definitely doable even today, but it would have to be maintained, regularly merged with official releases, every new functionality would have to be covered by tests and tested on every release. this seems like full time job, it could be covered by donations, or other support. but it would required professionals to take care of. this topic can be reopened once m2 is officially released.

@altarroba
Copy link

Its taking apart from the filosofy if a bussiness need Enterprise features it must be able to pay Enterprise Edition if not they must review their politics and work this out OR Magento msut review their price politics, Community must be always be backened for a fulltime developer that can solve problems and help the community makig a Community enterprise edition its a nonsense that dissable main maintainers of the software (varien-magento) from getting income and only add troubles to a customer under the promisse od $0 tag price unable to meet cause the maintenance needed

@monocat
Copy link

monocat commented Nov 7, 2012

Thank you for your support guys. You are welcome to make contributions, but please note, not all contributions will be used or incorporated into the code for the Magento 2 project. The decision to incorporate the code or not is at the discretion of the Magento 2 development team.

@monocat monocat closed this as completed Nov 7, 2012
@gfxguru
Copy link

gfxguru commented Nov 8, 2012

Like I said. It's an awesome idea but Magento would not support this. I say we create a CEE repo.. Anyone else in?

@chnorton
Copy link

chnorton commented Nov 8, 2012

You might be able to get such a patch accepted into Mage+ https://github.com/mageplus/mageplus
Although I think they're more concerned with bug fixes and core improvements than entirely new features just at the moment. I would suggest that as a good place to check first though.

magento-team pushed a commit that referenced this issue Mar 6, 2015
DRAGONS S61, S62 Improve search adapter
VitaliyBoyko pushed a commit to VitaliyBoyko/magento2 that referenced this issue Nov 25, 2017
magento-engcom-team pushed a commit that referenced this issue Apr 13, 2018
MAGETWO-89388: Update zendframework/zend-code
@magento-engcom-team magento-engcom-team added the Fixed in 2.3.x The issue has been fixed in 2.3 release line label Jul 19, 2018
@magento-engcom-team
Copy link
Contributor

Hi @gondo. Thank you for your report.
The issue has been fixed in magento/graphql-ce#119 by @naydav in 2.3-develop branch
Related commit(s):

The fix will be available with the upcoming 2.3.0 release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Fixed in 2.3.x The issue has been fixed in 2.3 release line Issue: Format is not valid Gate 1 Failed. Automatic verification of issue format is failed
Projects
None yet
Development

No branches or pull requests

6 participants