2015-04-18 21:10:45 UTC
I am very excited to see that OW is being actively developed, but am concerned about the appearance that there are two groups of contributors who appear to be working at cross purposes.
It appears that 99% of OW development work is being done by Jiri. If that is true, why don't we all get behind him by making his fork on GitHub the official fork?
The main obstacles might be (1) egos and (2) donated server politics. From a technical pov, IMO the contents of ow_daily.tar.bz2 should be frozen, with all new development done using Jiri's repository.
I'd like to hear from people who are currently actively contributing and also from past contributors who might become active again if interpersonal and/or other issues could be resolved.
Jiri and I have very different approaches to code development. We are polar opposites. Over the 15 years that I have been crafting the source code for IPDOS (tm), my policy has been to always stop making changes as soon as I know that a bug exists. I fix the bug right away, and then I resume crafting. Jiri, like many prolific coders, does not work that way. He prefers to drive forward to reach his development goal quickly. Although he tries to avoid introducing bugs, his focus is to get finished with whatever enhancement or port he is working on, and he views the task of finding and fixing the bugs that he introduced as either someone else's problem or as something he will take care of in a future project.
Both ways of working are reasonable. Both, IMO, are needed. What concerns me is that Jiri's approach seems to have alienated other would-be contributors who approach code craftwork more the way that I do, which is to go more slowly and to take the time to thoroughly test and debug as you go.
We need both kinds of contributors, and we need all contributors, of either kind, to be working together. Please join me by contributing to Jiri's fork and by making Jiri's fork the de-facto official development effort for OW. If you are concerned about the bugs that are being introduced by Jiri's whirlwind coding effort, join me in assisting Jiri by working to find and eliminate those bugs.