Stephen R. van den Berg wrote: >Regarding point a and c, I realise time is precious, but if I get >earlier feedback, possibly in the form of what I'm doing wrong in the >patch and asking for a rewrite or improvement, then I'd learn the >structures of Roxen faster and that will improve the quality of the >patch at hand and future patches.
I know it is kind of a chicken and egg problem here, but would it be possible to give me (and possibly other interested parties, but at this point there are not a lot of contenders, I presume) commit access to the development version of Roxen? I understand that you are hesitant because you consider some of my patches substandard; then again I'm reasonably capable of deciding what is and what is not substandard; the most prevalent reason why I create substandard patches to begin with, is because I otherwise run the risk of having to maintain my own (large) patch for extended periods of time because noone has time to review it and check it in (as explained earlier). Giving me commit rights though would give me enough incentive to actually prepare and commit patches that are more thorough and complete. I'd be interested in committing to the development version. The production version is of less interest to me, since I'm used to using just the development version (as if it were the production version) for the past 10 years anyway. -- Stephen. If mind over matter is a matter of course, does it matter if nobody minds?
