admin wrote:all these commercial tasks are interesting but artica must be branded before and used by more people
True - to be used by more people, it requires
1) a better organized public relations campaign on twitter + fb + other social networks...
2) Also, a specific plan for development , for Artica core code / a new plugin architecture (to allow 3rd party app projects to easily integrate into Artica) / phpunit test case code (an empty template of example code, to test any existing or new feature in Artica core, or plugins ).
3) A fully tested recommended IDE setup for the most popular PHP IDEs to hook into github / Xdebug / phpUnit, and how exactly they can download, edit, and push code updates. A procedure for David (or some designated persons) to test and accept/decline code contributions. These well organized collaboration procedures would serve to attract more contributors, because they are confident both in their development procedures, and that their machine IDE/etc. would be fully configured, up and running in 60 minutes max.
4) As the number of contributors and live running Artica systems grows, Artica will attract more and more major open source business software apps:
webERP / openERP / openBravo,
SugarCRM / Compiere / Salesforce / MS Dynamics CRM / VTiger /InfoAtHand,
pbx In A Flash / Elastix /Trixbox,
PostgreSQL / SQLServer / Oracle / DB2,
Magento / Zencart / osCommerce / ,
Zarafa / Open-X-Change, etc.
These business app projects will want to develop and contribute plugins, which install and integrate their apps more tightly and reliably, both with Artica, and with the other apps installed on Artica - one set of user logins/passwords used by all apps in each Artica organization!
They will provide very easy minimal screens for the admin to access, during the installation and update of settings.
They will also reuse code that the app project already has, to read/write the config files, always be in a correct state, and be able to adapt easily to user edits of the config files.