rph wrote:It's that a cart - commercial, GPL, or otherwise - can't be all things to all users. It can only provide the framework they need to create it.
Outside of this topic, I think this comment is the most accurate thing ever said about any carts. This should be the main slogan of the cart.
May work from a purely preaching idealism sense (easy to do), but when it's used as an excuse to not do database optimisation that someone has determined is an area the cart could be improved, it's a bit rich (go back and look at it in context). The things the cart does do, it should do well. Not this 'half ass implement, add it to the features list and move on' that is happening at the moment.
These points pop up again:
1. Issues with getting code into the main source tree because Daniel is busy etc. and he does all the edits directly (I think at minimum QPhoria should be able to do commits too)
2. Complete lack of direction with the project so people concerned this may derail the timeframe for the tested production release
3. People not being able to raise valid issues with the code base without being shot down by 'idealism' and preaching.
If Sheldmandu has discovered an area in the code that could possibly be optimized it should be discussed and investigated. He hasn't come here to piss people off, he obviously has some valid points that the community could benefit from.
As for the fork, if someone forks and develops with more visibility, direction and using SVN/git they will get far more community momentum and contribution from skilled developers.
Fork again QPhoria (at 1.3.4), you know you want to.