] on behalf of Development @ ORCA
Services AG [developm...@orca.ch]
Sent: Thursday, November 22, 2012 2:24 PM
To: dev-general@lists.oxidforge.org
Cc: Dino Fellmann - ORCA Services AG
Subject: Re: [oxid-dev-general] OXID Deployment System + The Community
Hi Dave
Thanks for your thoughts.
To put
Steinhaeuser
Gesendet: Freitag, 23. November 2012 12:09
An: dev-general@lists.oxidforge.org
Betreff: Re: [oxid-dev-general] OXID Deployment System + The Community
Hi guys,
@Dave: thanks for your thoughts. This is close to the way we are thinking
presently. But: no decisions made yet nor any time
-Ursprüngliche Daten-
Datum: 23.11.2012 13:02:31
Von: Frank Zunderer frank.zunde...@zunderer.de
An: dev-general@lists.oxidforge.org
Betreff: Re: [oxid-dev-general] OXID Deployment System + The Community
Vorgang: T-EK59Y2G4LW-57
Hi Marco,
in my opinion OXID could be much more bdquocommunity
Hi there,
this will never ever happen - oxid's enterprise features are mostly
coupled deeply into the core. I don't know why this is done,
but to me this looks like a prevention mechanism so nobody can
recreate enterprise features without hacking the core system or