Show posts
Hello All,
I spent more than a year and half working with oscommerce and I was always frustrated
to be developing in PhP and most of the code being written by novice and unexperienced developers... Although the ideas of contributions were great, I had always to customize and sometimes fix some of them for our own requirements 
. However, as this community seems to be more JAVA centric and focused, it seems like my dreams came true to see an osCommerce-like solution entirely written in Java technology 
.. I was just googling again about oscommerce to help a friend of mine, who I was developing in php, and I found konakart 
... Since december 2006 when I stopped working with osCommerce, I was primarily focused on open-source java development using agile development... I truly believe that we could use open-source strategies and practices to repeat the same success osCommerce folks did, but this time using a more mature way of creating Distributed Software and our Contributions style entirely based on the same Java standards ...
1. Add a Project Management System such as CollabNet SourceForge Enterprise Edition to monitor discussions, development code and releases; If there's no budget for that
, why not using GoogleCode ? It offers from Subversion, Issue tracking system, etc...
2. Having a main Subversion repository for this solution somewhere contributers can write contributions
... The model could be something related to the Eclipse plug-in architecture and we could try to specify a way to resolve conflicts of plug-ins that may use the same code-line (why not using diffs and identify interface methods, etc??)
3. Plug-ins or contributions would be made by creating a branch on Subversion and the responsible for that would have to create and publish the required documentation, artifacts to install, and conflicts resolution strategy if a given piece of code changes something from the user's current installation...
4. The community could vote on general features to be on the next releases, and konakart as a company would decide to have it on the next release or not... Maybe by vote from the community?
Is there a way to have this project in this development structure? What's the license with the distributed code?
I propose the open-source community to openly discuss about this (Maybe going to Kailua-Kona
, in the Big Island to have a beer, seeing girls in bikini 
and surf)
Take care,
Marcello de Sales
San Francisco, CA
I spent more than a year and half working with oscommerce and I was always frustrated
to be developing in PhP and most of the code being written by novice and unexperienced developers... Although the ideas of contributions were great, I had always to customize and sometimes fix some of them for our own requirements . However, as this community seems to be more JAVA centric and focused, it seems like my dreams came true to see an osCommerce-like solution entirely written in Java technology .. I was just googling again about oscommerce to help a friend of mine, who I was developing in php, and I found konakart ... Since december 2006 when I stopped working with osCommerce, I was primarily focused on open-source java development using agile development... I truly believe that we could use open-source strategies and practices to repeat the same success osCommerce folks did, but this time using a more mature way of creating Distributed Software and our Contributions style entirely based on the same Java standards ...1. Add a Project Management System such as CollabNet SourceForge Enterprise Edition to monitor discussions, development code and releases; If there's no budget for that
, why not using GoogleCode ? It offers from Subversion, Issue tracking system, etc...2. Having a main Subversion repository for this solution somewhere contributers can write contributions
... The model could be something related to the Eclipse plug-in architecture and we could try to specify a way to resolve conflicts of plug-ins that may use the same code-line (why not using diffs and identify interface methods, etc??)3. Plug-ins or contributions would be made by creating a branch on Subversion and the responsible for that would have to create and publish the required documentation, artifacts to install, and conflicts resolution strategy if a given piece of code changes something from the user's current installation...
4. The community could vote on general features to be on the next releases, and konakart as a company would decide to have it on the next release or not... Maybe by vote from the community?
Is there a way to have this project in this development structure? What's the license with the distributed code?
I propose the open-source community to openly discuss about this (Maybe going to Kailua-Kona
, in the Big Island to have a beer, seeing girls in bikini and surf)Take care,
Marcello de Sales
San Francisco, CA