10
Quote:
If i propose a module and I read in response another download, i think is not correct.
Why is this not correct?
If you're developing a commercial module that you want to sell, I could understand that you don't want anybody to mention other downloads because this could create a competition for your module, and you could make less money with it.
But in the Open Source world, we want benefit from other ideas, code, etc., so we can improve on it, and give back to the community.
From XOOPS perspective, or from any other Open Source project, due to limited time and resources, it is better for us when three developers work:
a) on the same module
together, or
b) on three different modules
If these three developers are "reinventing the wheel", each of them creating a module solving the same problem, then this is not quite productive from the community perspective.
When I see somebody working in a module, and I am aware of a similar solution, I always provide links to existing solutions saying something like:
"Hey, maybe you can find some cool code or ideas that you could use in your solution".
The most successful Open Source projects are Masters in collaboration and in avoiding the "Not Invented Here" syndrome.
